After some time I have finally been able to reconfigure the network on my NVidia Jetson after the ethernet stopped working abruptly. I hope that by understanding what exactly is happening in the lines below I can better understand what is occurring when my computer communicates with my router.
- What does the listening on and sending on information mean and stand for?
- What is an xid?
- Why port 67?
- Who is sending DHCPDISCOVER, and who is sitting at 255.255.255.255?
- What are the various odd numbered intervals 3, 5, 12, 67?
- Why finally is a DHCPREQUEST made, and who decided the ip address requested?
ubuntu@tegra-ubuntu:~$ sudo ifdown eth0
RTNETLINK answers: No such process
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:04:4b:26:fd:7b
Sending on LPF/eth0/00:04:4b:26:fd:7b
Sending on Socket/fallback
DHCPRELEASE on eth0 to 10.0.0.1 port 67 (xid=0x7b85fd90)
ubuntu@tegra-ubuntu:~$ sudo ifup eth0
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:04:4b:26:fd:7b
Sending on LPF/eth0/00:04:4b:26:fd:7b
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x37e8201)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x37e8201)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0x37e8201)
DHCPREQUEST of 10.0.0.35 on eth0 to 255.255.255.255 port 67 (xid=0x37e8201)
DHCPOFFER of 10.0.0.35 from 10.0.0.1
DHCPACK of 10.0.0.35 from 10.0.0.1
bound to 10.0.0.35 -- renewal in 275106 seconds.
3
,5
,12
are timeouts, which are randomized and are longer and longer as theyDHCPDISCOVER
not getting any answer from a server and times out. The thirdDHCPDISCOVER
sent reached theDHCP
-server and it got an answer before the "12" timeout.