D-Link Forums
Eagle Pro AI => R15 => Topic started by: Mbombo on January 07, 2022, 12:22:36 AM
-
Hi!
I'm working in a small ISP - and we run isc-dhcp-server for our customers.
The ISC DHCP server is only running IPv4
I tried almost all firmware for the R15 router, also the latest hotfix firmware 1.04.04
We started pushing a few R15 routers to our customers, and discovered that they keeps disconnection and asking for new lease every three minuets.
It looks like the router is dropping the leases, and when trying to get at new lease.
The R15 sometimes keep chancing the IP address.
If I look in the MAC table on my switch, I see to MAC addresses, both LAN and WAN - where I normal only see the WAN MAC
I discovered that the IPv6 setting on the R15 is default set to "Auto Detection". If I chance the setting to "Local Connectivity Only" it's working just fine, no disconnects and stops chancing IP address constantly.
So, can there be some miscommunication with how the ISC DHCP server handles IPv6 request from the R15 router?
The ISC DHCP server is default configuration, and only listing on IPv4 interface. I created a simple DHCP scope.
Here is some post of the ISC DHCP logs
Jan 7 07:48:18 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.20 (10.5.5.2) from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:48:18 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:49:47 raspberrypi dhcpd[796]: DHCPDISCOVER from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:49:48 raspberrypi dhcpd[796]: DHCPOFFER on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:49:48 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.20 (10.5.5.2) from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:49:48 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:51:17 raspberrypi dhcpd[796]: reuse_lease: lease age 89 (secs) under 25% threshold, reply with unaltered, existing lease for 10.5.5.20
Jan 7 07:51:17 raspberrypi dhcpd[796]: DHCPDISCOVER from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:51:18 raspberrypi dhcpd[796]: DHCPOFFER on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:51:18 raspberrypi dhcpd[796]: reuse_lease: lease age 90 (secs) under 25% threshold, reply with unaltered, existing lease for 10.5.5.20
Jan 7 07:51:18 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.20 (10.5.5.2) from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:51:18 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:52:47 raspberrypi dhcpd[796]: DHCPDISCOVER from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:52:48 raspberrypi dhcpd[796]: DHCPOFFER on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:52:48 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.20 (10.5.5.2) from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:52:48 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:54:17 raspberrypi dhcpd[796]: reuse_lease: lease age 89 (secs) under 25% threshold, reply with unaltered, existing lease for 10.5.5.20
Jan 7 07:54:17 raspberrypi dhcpd[796]: DHCPDISCOVER from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:54:18 raspberrypi dhcpd[796]: DHCPOFFER on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:54:18 raspberrypi dhcpd[796]: reuse_lease: lease age 90 (secs) under 25% threshold, reply with unaltered, existing lease for 10.5.5.20
Jan 7 07:54:18 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.20 (10.5.5.2) from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:54:18 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:55:46 raspberrypi dhcpd[796]: DHCPDISCOVER from a8:63:7d:64:27:b3 via eth1
Jan 7 07:55:47 raspberrypi dhcpd[796]: DHCPOFFER on 10.5.5.21 to a8:63:7d:64:27:b3 via eth1
Jan 7 07:55:47 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.21 (10.5.5.2) from a8:63:7d:64:27:b3 via eth1
Jan 7 07:55:47 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.21 to a8:63:7d:64:27:b3 via eth1
Jan 7 07:55:47 raspberrypi dhcpd[796]: DHCPDISCOVER from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:55:48 raspberrypi dhcpd[796]: DHCPOFFER on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:55:49 raspberrypi dhcpd[796]: DHCPREQUEST for 10.5.5.20 (10.5.5.2) from a8:63:7d:64:27:b3 (R15) via eth1
Jan 7 07:55:49 raspberrypi dhcpd[796]: DHCPACK on 10.5.5.20 to a8:63:7d:64:27:b3 (R15) via eth1
Here are some logs from the R15 that keeps disconnection the WAN - Dont mind that date and time is a little off :)
https://pastebin.com/e9mkGHVP (https://pastebin.com/e9mkGHVP)
-
Seems to be a private IP address 10.5.5.20 for the WAN port.
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
- If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>Double NAT (http://www.practicallynetworked.com/networking/fixing_double_nat.htm) and How NAT Works (http://computer.howstuffworks.com/nat.htm). Call the ISP and ask to see if the ISP modem can be bridged. To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ (http://www.dslreports.com/shownews/Networking-101-The-DMZ-137550). Disable ALL WiFi radios on the modem. Also check the routers DHCP IP address maybe conflicting with the ISP modems IP address of 192.168.0.1. Check to see if this is the same on the ISP modem, and if modem can't be bridged, change the DIR router to 192.168.1.1 or .0.254.
Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on a Router (http://forums.dlink.com/index.php?topic=56344.msg219023#msg219023)
-
Hi FurryNutz :)
Thanks for your reply!
I am the ISP, and we provide public IP addresses for our customers. So no modem at all!
Our customers normal buy a home router by them self, we do have a simple web shop where they can buy the R15.
My example in this post is a replication of the issue just on a test ISC DHCP server with IPv4 addresses only. Just to test if I could reproduce the issue.
As I did write, I discovered that the IPv6 setting on the R15 is default set to "Auto Detection". If I chance the setting to "Local Connectivity Only" it's working just fine, no disconnects and stops chancing IP address constantly.
I see both LAN and WAN MAC address on my access switch where the customer router is connected to. I think there is something wrong with how the R15 router handles IPv6 requests when the ISC DHCP server do not offer IPv6 addresses and not even listing on an IPv6 interface.
But then I chance IPv6 setting to "Local Connectivity Only" it's stopping showing the LAN MAC address in the MAC table - which is normal for a home router (Only showing WAN mac address)
-
I recommend you contact D-Link support and let them know what your seeing.
-
I have just contacted D-Link. Thanks for your time!
-
👍
-
@mbombo Please contact support in your country to report the issue to the engineers. I know in the US the R15 does have an issue with a specific ISP (Spectrum) issuing IPv6 addresses so may be a similar issue. Let us know if you get the issue resolved.