wrote: Hi
,
Can you try running a tcpdump packet capture on the WAN interface to see if there are any replies to the DHCP requests?
After rebooting the device, run the following command from the CLI:
sudo tcpdump -i ethX -n -e udp port 67 or port 68
Replace X with the number of your WAN interface.
-Ben
Sorry for the delay, i have been away from home for 4 days.
Done this and the below is the output (i have removed my public ip and replaced with x.x.x.x:
admin@router:~$ sudo tcpdump -i eth4 -n -e udp port 67 or port 68 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth4, link-type EN10MB (Ethernet), capture size 262144 bytes 12:56:40.708744 fc:ec:da:73:d0:57 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fc:ec:da:73:d0:57, length 300 12:56:40.924375 a0:f3:e4:47:4a:30 > fc:ec:da:73:d0:57, ethertype IPv4 (0x0800), length 364: x.x.x.x.67 > x.x.x.x.68: BOOTP/DHCP, Reply, length 322 12:56:40.925229 fc:ec:da:73:d0:57 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 343: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from fc:ec:da:73:d0:57, length 301 12:56:40.942597 a0:f3:e4:47:4a:30 > fc:ec:da:73:d0:57, ethertype IPv4 (0x0800), length 364: x.x.x.x.67 > x.x.x.x.68: BOOTP/DHCP, Reply, length 322 ^C 4 packets captured 4 packets received by filter 0 packets dropped by kernel
I switched the router off at 12:50, the router was back up and able to get into the GUI by 12:51:30, it then took 5 minutes to send the initial DHCP request to my ISP (using these capture logs), as soon as it sent the request it recieved it back straight away and connected fine.
But why the 5 minute delay in the first place?
Thanks