Internet Connection Lost every 2 Hours after Migration from Firmware Version 1.3.0 to 1.4.x WAN DHCP
Internet Connection Lost every 2 Hours after Migration from Firmware Version 1.3.0 to 1.4.x WAN DHCP
Hallo,
nach Update der Firmeware von Version 1.3.0 nach 1.4.x fordert der Router alle 2 Stunden eine neue IP Adresse beim ISP an (Internetverbindung dynamische IP).
im Log ist der Eintrag
vorhanden. Es wird hier auch hart die Internetverbindung gekappt und somit habe ich alle 2 Stunden einen Ausfall von ca. 20 Sekunden.
Habe hierzu auch den ISP kontaktiert. Bei diesem gibt es hierzu keine Änderungen.
Nachdem ich wieder auf die Version 1.3.0 zurück gesprungen bin, läuft alles wieder tadellos.
Der ISP gab noch den Hinweis, dass sie das gleich Problem bereits mit LANCOM nach einem Firmware Update hatten. Hier bessere LANCOM die Firmware nach und anschließend funktionierte dies wieder.
Werden mit der Version 1.4.x neu irgendwelche Broadcast Meldungen Richtung ISP verschickt und auf Grund dessen Rückmeldung dann die IP neu geholt?
Danke und vG
Marco
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
MarcoSch wrote
Hi @Clive_A,
do you had the time to check the wireshark file? Do you need more data / information about my system? Thank you, Marco
Confirmed that this is a problem with the DHCP renewal. The DHCP server did not reply to the renewal from the router. So the connection is dropped and it generates the renewal failure log.
After the renewal, it will dial for the Internet instantly. So, it dialed for the connection. Based on the Wireshark analysis, the reply server is not the same so we assume it traveled and passed through a DHCP relay.
And in this case, the router quickly declined it but we cannot locate the reason for why it declined the DHCP offer from the DHCP server.
But in your Wireshark, the part that is missing, and it is important to know, is that ER7206 dialed again after the decline. And this was not captured and not sure if this was successfully get you connected or not. We need to know this before we come to a conclusion. If you can get us the Wireshark result after that time and it could be helpful for our diagnosis.
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
MarcoSch wrote
Hi @Clive_A,
did you have the time to check the wireshark file? Do you need more data / information about my system? Thank you, Marco
Further analysis. I'll put the conclusion in the first place.
Conclusion: The router behaves as expected. No issue was found on the ER7206.
Reason: ARP detects the IP conflict. So, it declines and re-dials.
1856 decline released the ER7206 IP address.
After this, it dialed again, and this time, ARP snooping showed no IP conflict and it worked since then.
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
Please use English if we need to further discuss this issue.
Based on the title, and the screenshot, it is clear that the DHCP server fails to renew it.
- Copy Link
- Report Inappropriate Content
Hey @Clive_A,
Thanks for Your response. Now in english.
Hello,
after updating the firmware from version 1.3.0 to 1.4.x, the router requests a new IP address from the ISP every 2 hours (Internet connection dynamic IP).
The Internet connection is also cut hard here and so I have an outage of approx. 20 seconds every 2 hours.
I have also contacted the ISP about this. They have not made any changes.
After I switched back to version 1.3.0, everything is running smoothly again.
The ISP also pointed out that they already had the same problem with LANCOM after a firmware update. LANCOM then improved the firmware and everything worked again.
Are any new broadcast messages sent to the ISP with version 1.4.x and is the IP then retrieved again based on the response?
Thank you
marco
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
MarcoSch wrote
Hey @Clive_A,
Thanks for Your response. Now in english.
Hello,
after updating the firmware from version 1.3.0 to 1.4.x, the router requests a new IP address from the ISP every 2 hours (Internet connection dynamic IP).
The Internet connection is also cut hard here and so I have an outage of approx. 20 seconds every 2 hours.
I have also contacted the ISP about this. They have not made any changes.
After I switched back to version 1.3.0, everything is running smoothly again.
The ISP also pointed out that they already had the same problem with LANCOM after a firmware update. LANCOM then improved the firmware and everything worked again.
Are any new broadcast messages sent to the ISP with version 1.4.x and is the IP then retrieved again based on the response?
Thank you
marco
Who is your ISP?
The 20 seconds downtime means the connection is down DHCP renewal failed and requested a new IP.
Can you Wireshark on your WAN? Take a snip and show the interaction which might be helpful for me to diagnose the issue.
Please mosaic your sensitive information. Here is a list of information considered sensitive:
1. Public IP address on your WAN if your WAN is.
2. Real MAC address of your device.
3. Your personal information including address, domain name, and credentials.
For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.
- Copy Link
- Report Inappropriate Content
Hey @Clive_A,
my isp is named suec dacor in coburg / germany. I think it is a sub Company from vodafone. It is how you said. The connection is down while the ip renewal. There must be a difference between Version 1.3.0 and 1.4.x cause when i get back to 1.3.0 all is fine. I can wireshark but i it will be possible next week cause i am out of Office this week. Thank you, marco
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
MarcoSch wrote
Hey @Clive_A,
my isp is named suec dacor in coburg / germany. I think it is a sub Company from vodafone. It is how you said. The connection is down while the ip renewal. There must be a difference between Version 1.3.0 and 1.4.x cause when i get back to 1.3.0 all is fine. I can wireshark but i it will be possible next week cause i am out of Office this week. Thank you, marco
Will check this with the test team and see if there are any known cases like this.
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
MarcoSch wrote
Hey @Clive_A,
my isp is named suec dacor in coburg / germany. I think it is a sub Company from vodafone. It is how you said. The connection is down while the ip renewal. There must be a difference between Version 1.3.0 and 1.4.x cause when i get back to 1.3.0 all is fine. I can wireshark but i it will be possible next week cause i am out of Office this week. Thank you, marco
We checked with the team.
Unfortunately, we do not have any progress on cases like this. We cannot locate the cause of this issue until we have a Wireshark result to show the process of renewal failure.
Please capture this failure process on your WAN and contact us when you are back.
- Copy Link
- Report Inappropriate Content
Hey @Clive_A,
today i was able to wireshark the port.
I load the firmware 1.4.2 im my router er7206 v1. after two hours you can see in the wireshark log, that there are two offers and acks. there is another ack with an icmp errer "port unreachable" before. But i don't know, if this one matters.
Here is the screenshot from the log in the omada software and the wireshark capture.
In the capture file i was filtering for udp==68 (dhcp). if you need more information, i also had the full log from 16:27 to 16:40.
Thanks a lot for checking this.
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
MarcoSch wrote
Hey @Clive_A,
today i was able to wireshark the port.
I load the firmware 1.4.2 im my router er7206 v1. after two hours you can see in the wireshark log, that there are two offers and acks. there is another ack with an icmp errer "port unreachable" before. But i don't know, if this one matters.
Here is the screenshot from the log in the omada software and the wireshark capture.
In the capture file i was filtering for udp==68 (dhcp). if you need more information, i also had the full log from 16:27 to 16:40.
Thanks a lot for checking this.
Will look into this. Thanks for your time.
- Copy Link
- Report Inappropriate Content
Hi @Clive_A,
do you had the time to check the wireshark file? Do you need more data / information about my system? Thank you, Marco
- Copy Link
- Report Inappropriate Content
Hi @MarcoSch
Thanks for posting in our business forum.
MarcoSch wrote
Hi @Clive_A,
do you had the time to check the wireshark file? Do you need more data / information about my system? Thank you, Marco
Confirmed that this is a problem with the DHCP renewal. The DHCP server did not reply to the renewal from the router. So the connection is dropped and it generates the renewal failure log.
After the renewal, it will dial for the Internet instantly. So, it dialed for the connection. Based on the Wireshark analysis, the reply server is not the same so we assume it traveled and passed through a DHCP relay.
And in this case, the router quickly declined it but we cannot locate the reason for why it declined the DHCP offer from the DHCP server.
But in your Wireshark, the part that is missing, and it is important to know, is that ER7206 dialed again after the decline. And this was not captured and not sure if this was successfully get you connected or not. We need to know this before we come to a conclusion. If you can get us the Wireshark result after that time and it could be helpful for our diagnosis.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 375
Replies: 20
Voters 0
No one has voted for it yet.