Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
We are running WDS on server2012 and it's doing fine with older machines. But we bought new stack of HP's with Intel i217-lm NIC, it is using Boot agent GE v.1.5.50.
When we are trying to boot it gets ip via dhcp, but ends with error:
PXE-E55: ProxyDHCP service did not reply to request on port 4011
I tried to change dhcp scope options by MS recommendations:
Option 60= PXEClient
Option 66= WDS server name or IP address
Option 67= Boot file name
Any suggestions
To see if the DHCP process is where the problem lies, one test to try is running Wireshark on the DHCP server to see if the packet was received by the server, and if the server sent the packet back to the i217 adapter.
If the packet reached the DHCP server but didn't get sent back maybe it is a firewall issue. I would also check the IP address leases and make sure everything looks error-free (ie no duplicate IPs, bad addresses).
Also if you want to verify that there are not known PXE issues with the i217 adapters, or if there any quirks, you can ask the Wired Ethernet blog at communities.intel.com about the issue you're seeing. They usually have someone who can help from Intel on there.
Workaround was booting from network in UEFI mode. There is limitations regarding new Intel's boot agent
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 months ago.
Improve this question
I was wondering is it possible to create a veth interface and connect it directly to physical interface of NIC? I see most of the online solutions using bridges, however I am curious if it would be possible to bypass them for simple connection.
These are the some commands I tried to achieve this, but received error:
sudo ip link add veth1 type veth
sudo ip link set veth1 master ens3f0np0
(ens3f0np0 being physical interface)
Error I received after second command was: RTNETLINK answers: Operation not supported
It seems that MACVLAN would be solution needed for this scenario.
Following is a helpful link:
Red Hat MACVLAN explanation
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have a number of machines which I would like to check using my Nagios box. They sit behind a machine which is reachable from my Nagios box; all are running Linux. These machines have no routing to outside networks. If I need to reach the machines manually I either ssh to the intermediate box and then ssh to the other machines, or I'll use ssh to forward a port.
I usually use SNMP for most of my checks. So my thought is that prior to my Nagios box running a check I could have it run a command to forward the needed port, then get rid of the forward when done. Can anyone guide me on the best way to do this?
Thanks!
You probably want to look into Nagios passive checks. As described in the documentation:
Passive checks are useful for monitoring services that are:
Asynchronous in nature and cannot be monitored effectively by polling
their status on a regularly scheduled basis
Located behind a firewall and cannot be checked actively from the monitoring host
Your use case is pretty clearly the second one.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have this routing table:
I used SSH to be able to use my Raspberry Pi on my laptop screen. Everything was fine until I opened my browser and wanted to ping Google in the terminal. I can't, though.
When I try to ping 8.8.8.8 (Google's nameserver), I get the message below the routing table in the image above. But the strange thing is, when I run SSH with PuTTY on a different laptop, the Internet connection is fine. So probably the problem is on my laptop.
How can I fix this issue?
Seems like you are using 192.168.1.1 as a gateway, yet you have configured 192.168.137.0/24 as the network.
You should either try to configure the default gateway to - perhaps - 192.168.137.1 or your IP address to 192.168.1.x.
An ifconfig output would be handy.
Edit:
Add default gateway:
route add default gw 192.168.137.1
You might also need to remove current default gateway(s).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
Scenario: Main Linux Server is Connected to Local Switch Gateway. From Gateway to the network.
Now i can able to get the IP of the Remote Clients/Users who logged into the Server.
Linux Command : *"who -u" (gives me the IP Address of the users IP Address).*
For getting the MAC Address of the same user. I tried the arp -a command, It gave the switch MAC-Address only. I cant able to get the Remote Clients/User MAC Address.
Linux Command : "arp -a" (gives me the MAC Address of the Switch).
How to the MAC Address of the Remote Clients Machines ?
Note : My Client Machines can run on any OS (Windows/Linux/Solaris).
MAC addresses doesn't get routed, so the IP address would have to be of a host on your network. You will have to ping the IP address first and then use arp -a; like
ping <Remote_IP_Address>
arp -a <Remote_IP_Address>
See this related posts here
is-there-a-way-to-find-the-mac-address-of-a-remote-machine-i-have-connected-to-w
how-to-find-the-mac-address-of-a-remote-computer
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I work with embedded Linux systems that sometimes want to get their IP address from a DHCP server. The DHCP Client client we use (dhcpcd) has limited retry logic. If our device starts up without any DHCP server available and times out, dhcpcd will exit and the device will never get an IP address until it's rebooted with a DHCP server visible/connected. I can't be the only one that has this problem. The problem doesn't even seem to be specific to embedded systems (though it's worse there). How do you handle this? Is there a more robust client available?
The reference dhclient from the ISC should run forever in the default configuration, and it should acquire a lease later if it doesn't get one at startup.
I am using the out of the box dhcp client on FreeBSD, which is derived from OpenBSD's and based on the ISC's dhclient, and this is the out of the box behavior.
See http://www.isc.org/index.pl?/sw/dhcp/
You have several options:
While you don't have an IP address, restart dhcpcd to get more retries.
Have a backup static IP address. This was quite successful in the embedded devices I've made.
Use auto-IP as a backup. Windows does this.
Add to rc.local a check to see if an IP has been obtained. If no setup an 'at' job in the near future to attempt again. Continue scheduling 'at' jobs until an IP is obtained.