Probe does not request IPv4 address via DHCP
Hello, My probe(ID 16372) has disconnected from the Atlas network and in the Status I see USB flash corrupted. I did the troubleshooting - power off the probe, remove the USB, power on the probe, waited 10 mins, plugged brand new 4G USB. Several times with no success, So I decided to do a traffic capture of the uplink port where the probe is connected to. According to the capture the probe does not send DHCP requests. It sends only IPv6 traffic - Multicast Listener reports and Neighbor solicitation. Hence not getting IP address. I did several restarts - no change. Anybody has seen this issue before ? Any hints how to deal with such issue ? Thanks Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
Hi, On 2017/06/08 16:39 , Stanish Stanishev wrote:
So I decided to do a traffic capture of the uplink port where the probe is connected to. According to the capture the probe does not send DHCP requests. It sends only IPv6 traffic - Multicast Listener reports and Neighbor solicitation. Hence not getting IP address. I did several restarts - no change.
Anybody has seen this issue before ? Any hints how to deal with such issue ?
There seems to be a very rare condition where in the config on the built-in flash DHCP gets disabled. I noticed that some time ago and added code to newer firmwares to check for this condition and re-enable DHCP. The best way to fix this is to place the probe in a network that offers IPv6. Philip
Hello, Philip, Today I connected the probe to IPv6 network. Below is what happened: 1. After boot probe got IPv6 address 2a01:5a8:2:5:6666:b3ff:fec5:fa6. 2. I did a traffic capture and saw the probe connected to 2001:67c:2e8:11::c100:1319 (woolsey.ipv6.atlas.ripe.net) and there was a short communication via SSL. 3. Then the probe became silent. I waited ten minutes and plugged a new USB stick however the probe did not try to connect ATLAS infrastructure anymore. Note: The router assigns recursive DNS servers (2001:4860:4860::8888 2001:4860:4860::8844) via ICMP6 Option 25 in Router Advertisement messages. I have also tried to assign DNS servers via the RIPE Probe Management Web Interface but no difference, Thank You Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
On 2017/06/12 13:55 , Stanish Stanishev wrote:
Note: The router assigns recursive DNS servers (2001:4860:4860::8888 2001:4860:4860::8844) via ICMP6 Option 25 in Router Advertisement messages. I have also tried to assign DNS servers via the RIPE Probe Management Web Interface but no difference,
There are some limitations when the probe is running from its internal flash. Fortunately, there is a way around that. The probe is now connected. Philip
Ah, Thank you so much for the support. May I ask you to share what did you do in order to make the probe connect again to the Atlas ? Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
On 2017/06/13 14:07 , Stanish Stanishev wrote:
Ah, Thank you so much for the support. May I ask you to share what did you do in order to make the probe connect again to the Atlas ?
Normally the probe receives the name of a controller to connect to. If the probe doesn't have access to DNS resolvers then it cannot connect. We have a trick to provide the probe with either an IPv4 or an IPv6 literal. In theory the system will detect that the probe has troubles resolving DNS and will switch to that automatically. We have to figure out why that didn't happen for your probe. But it can also be activated manually. Philip
Hello, Thank you for the details. Do I need to assist you somehow for finding the reason, why the automatic way for providing the probe with literal did not happen ? Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
On 2017/06/23 16:34 , Stanish Stanishev wrote:
Thank you for the details. Do I need to assist you somehow for finding the reason, why the automatic way for providing the probe with literal did not happen ?
Thanks for the offer. We already found the reason and this situation should now be covered. Philip
Hello, It seems, I have absolutely same problem with probe #24361. Probe has disconnected on 2017-07-10, and now (on IPv6 network, with address 2001:470:1f0b:527:16cc:20ff:fe48:be04) it remains silent, except short communication with woolsey.ipv6.atlas.ripe.net via SSL. May I ask for doing this trick again for this probe? Mikhail. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
participants (3)
-
Mikhail Okhotin -
Philip Homburg -
Stanish Stanishev