The Graveyard - Products No Longer Supported > DIR-878
I managed to get 1.10 running...
zeny1:
--- Quote from: GreenBay42 on February 15, 2019, 06:35:55 PM ---Good point. v1.11 fixed xbone and ps4 connectivity issues and a specific ISP/modem issue for Canada. I am going to assume 1.11 will have similar issues as 1.12.
Note when updating to 1.10, make sure you update to v1.04 included in the firmware package and then 1.10. That adds the encryption. If you try to update 1.10 from 1.00 it will fail.
--- End quote ---
I see. I managed to get 1.10 running. I have left everything stock, haven't played with any of settings. Everything seems to be working well, except during DSLreports speedtests I am getting a lot of bufferbloat, seen spikes up to the 300MS range in download and 200MS in the upload range.
Could it be because I am a Canadian and have that weird ISP issue you mention here? I have a gigabit connection with the ISP called "Rogers" with a modem model CODA 4582.
Or do you have a recommended setting to input ? I saw there's a lot in the security tab, but I left everything off as I am guessing default settings are default for a reason.
Thank you
FurryNutz:
If this is your modem:
https://www.hitrontech.com/product/coda-4582/
Then you already have router and wifi.
* 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 and How NAT Works. 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. 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
zeny1:
--- Quote from: FurryNutz on February 22, 2019, 06:34:15 AM ---If this is your modem:
https://www.hitrontech.com/product/coda-4582/
Then you already have router and wifi.
* 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 and How NAT Works. 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. 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
--- End quote ---
Hello, I have put my modem/router on bridge mode, but I am having to reset my router every hour or so because it fails to DHCP ipv4. Losses communication with the modem it seems.
Getting the same issues as http://forums.dlink.com/index.php?topic=72818.0 and http://forums.dlink.com/index.php?topic=73788.0
I manage to get a log file and it says the same thing as the first link. I have to manually power off my router and turn it back on. I suspect this is what the admin was saying on having fixed modem issues in Canada. I'll be loading up 1.11v now and see if it fixes the issue. Will report on here soon!
2019-02-22 12:44:07 [RC]: Wan(eth3) Disconnect
2019-02-22 12:44:07 ipsec_setup: ...Openswan IPsec stopped
2019-02-22 12:57:41 [RC]: Wan(eth3) Disconnect
2019-02-22 12:57:41 [RC]: Wan(eth3) Disconnect
2019-02-22 12:57:42 [DNSMASQ]: failed to bind DHCP server socket: Address already in use
2019-02-22 12:57:42 [DNSMASQ]: FAILED to start up
2019-02-22 12:57:42 ipsec_setup: ...Openswan IPsec stopped
2019-02-22 12:57:42 ipsec_setup: ...Openswan IPsec stopped
2019-02-22 12:57:44 [RC]: Current Wan interface is eth3 , mode is dhcp
2019-02-22 12:57:44 [RC]: Wan(eth3) Disconnect
2019-02-22 12:57:45 ipsec_setup: ...Openswan IPsec stopped
2019-02-22 12:59:20 [RC]: Wan(eth3) Disconnect
2019-02-22 12:59:20 [RC]: Wan(eth3) Disconnect
2019-02-22 12:59:20 [DNSMASQ]: failed to bind DHCP server socket: Address already in use
2019-02-22 12:59:20 [DNSMASQ]: FAILED to start up
2019-02-22 12:59:20 ipsec_setup: ...Openswan IPsec stopped
2019-02-22 12:59:20 ipsec_setup: ...Openswan IPsec stopped
2019-02-22 12:59:20 [RC]: Current Wan interface is eth3 , mode is dhcp
2019-02-22 12:59:20 [RC]: Wan(eth3) Disconnect
2019-02-22 12:59:21 ipsec_setup: ...Openswan IPsec stopped
FurryNutz:
Ok, keep us posted.
zeny1:
--- Quote from: FurryNutz on February 22, 2019, 10:46:35 AM ---Ok, keep us posted.
--- End quote ---
So far so good. 1.11 does indeed fix issues with Rogers internet and any other of their resellers (Teksavvy etc)
Navigation
[0] Message Index
[#] Next page
Go to full version