Double NAT on Xbox One - Home Network Advice

timmy85 · 30 Oct 2019 at 22:05

I'm after some help with my shody home network please gents.

My xbox one connects to the internet fine, but displays that it detects double NAT.

I use a Talktalk VDSL router on IP 192.168.1.1

The talktalk router has DHCP enabled ranging from 192.168.1.2 to 192.168.1.254.

Connected to the talktalk router via ethernet on ip 192.168.2.1 is an Asus RT-AC3200 handling all other network ethernet and wifi traffic and also has DHCP enabled starting at 192.168.2.2. The xbox is therefore connected directly to the asus RT-AC3200 via ethernet.

It appears the talktalk router still has NAT enabled, so does the Asus.

Which should it be left enabled on and which should be disabled to resolve the double NAT issue?

TIA

Rainmaker · 30 Oct 2019 at 22:22

Why do you have a router connected to another router? Are you just trying to get more ports to connect to? If that's the case, you need a switch. Routers mediate between two separate networks, not the same network - hence your issues. If you really did want two networks (eg trusted/untrusted or LAN/servers/iot) then you need to configure either separate subnets on different physical ports of the one router, or use VLANs.

If it's because you want the features of the Asus then use that instead of the TalkTalk router, not behind it.

Zefan · 30 Oct 2019 at 23:53

Rainmaker said:
If it's because you want the features of the Asus then use that instead of the TalkTalk router, not behind it.

It's likely the intent is to get the Talk Talk device to act as a modem, which the Asus can't do as it's a RT model.

If my assumption is correct, the solution here is to turn your Talk Talk device to "modem mode". Have a google about for this, you'll find many people will have already been through this process and will likely guide you hassle free to functioning-network bliss. It'll involve turning DHCP and NAT off on your "modem" device, leaving all of that to the Asus router. You'll need to enter your ISP provided access details in to the Asus for this to work.

Steveocee · 31 Oct 2019 at 01:20

The really simple answer is to move the ASUS into AP mode or it may be called bridge mode. It removes all "routing" functionality and behaves alike a switch with a wireless AP attached. Job done, no messing and double NAT removed. Honestly I don't know why people suggest some of the things they do on this forum.

timmy85 · 31 Oct 2019 at 08:25

Rainmaker said:
Why do you have a router connected to another router? Are you just trying to get more ports to connect to? If that's the case, you need a switch. Routers mediate between two separate networks, not the same network - hence your issues. If you really did want two networks (eg trusted/untrusted or LAN/servers/iot) then you need to configure either separate subnets on different physical ports of the one router, or use VLANs.

If it's because you want the features of the Asus then use that instead of the TalkTalk router, not behind it.

I dont think the Asus has a modem in it?

Zefan said:
It's likely the intent is to get the Talk Talk device to act as a modem, which the Asus can't do as it's a RT model.

If my assumption is correct, the solution here is to turn your Talk Talk device to "modem mode". Have a google about for this, you'll find many people will have already been through this process and will likely guide you hassle free to functioning-network bliss. It'll involve turning DHCP and NAT off on your "modem" device, leaving all of that to the Asus router. You'll need to enter your ISP provided access details in to the Asus for this to work.

Yes you are correct. The idea was to benefit from the additional functionality of the asus router.

Steveocee said:
The really simple answer is to move the ASUS into AP mode or it may be called bridge mode. It removes all "routing" functionality and behaves alike a switch with a wireless AP attached. Job done, no messing and double NAT removed. Honestly I don't know why people suggest some of the things they do on this forum.

If I switch the mode do I lose some functionality of the Asus such as QoS etc?

Steveocee · 31 Oct 2019 at 08:46

timmy85 said:
If I switch the mode do I lose some functionality of the Asus such as QoS etc?

Yes you would but it's not like you'd be making the best of it anyway. Anything connected to your TT router would have been carrying the same priority as your ASUS router so to be fair if anything your devices would actually have more priority as the traffic wouldn't be getting NAT'd through the ASUS.

Don't get hung up on stupid consumer buzz words, QoS only really works when you control both ends of a link, on a consumer router all you are doing ir re-arranging the transmit of your packets which the ISP will likely round robin or apply their own QoS/Management to anyway.

timmy85 · 31 Oct 2019 at 12:25

Steveocee said:
Yes you would but it's not like you'd be making the best of it anyway. Anything connected to your TT router would have been carrying the same priority as your ASUS router so to be fair if anything your devices would actually have more priority as the traffic wouldn't be getting NAT'd through the ASUS.

Don't get hung up on stupid consumer buzz words, QoS only really works when you control both ends of a link, on a consumer router all you are doing ir re-arranging the transmit of your packets which the ISP will likely round robin or apply their own QoS/Management to anyway.

I have been though. All traffic routes through the asus with qos enabled for different devices etc.

The xbox has a tendency to max out my download speed when updating games, which impacts the smart tv streaming frustratingly. The QoS config stops that from happening.

Also got the wife's smart phone connecting at a snail's pace but dont tell her

pepp77 · 31 Oct 2019 at 12:37

That is BWM not QOS

As others have said having two routers setup as routers will always result in a double NAT. The turning the TT router into a modem only mode suggestion is the best one to try and use.

Caged · 31 Oct 2019 at 12:37

Buy a VDSL modem and plug it into the Asus router.

timmy85 · 31 Oct 2019 at 15:33

pepp77 said:
That is BWM not QOS

As others have said having two routers setup as routers will always result in a double NAT. The turning the TT router into a modem only mode suggestion is the best one to try and use.

Quite right you are! BWM is what I am most keen on keeping in place.

Is it just simply a case of turning dhcp and nat off on the talktalk router to essentially place it in modem mode? I cant recall seeing anything in terms of a setting for "modem mode".

It's a D-link dsl 3782.

pepp77 · 31 Oct 2019 at 16:14

https://community.talktalk.co.uk/t5/Broadband/DLINK-DSL-3782-bridge-modem-mode/td-p/2228089

Might help

PHoSawyer · 2 Nov 2019 at 20:46

Steveocee said:
The really simple answer is to move the ASUS into AP mode or it may be called bridge mode. It removes all "routing" functionality and behaves alike a switch with a wireless AP attached. Job done, no messing and double NAT removed. Honestly I don't know why people suggest some of the things they do on this forum.

This, turn it into AP mode so it's just doing the wifi connectivity, turn everything else off like NAT and DHCP. If you currently connect into a WAN port you may need to move it to the LAN. Your devices will then pick up an address from the upstream router and you will then only have one NAT to deal with.

timmy85 · 3 Nov 2019 at 18:12

Caged said:
Buy a VDSL modem and plug it into the Asus router.

Managed to solve this by swapping the talktalk router for an old HG612 BT modem I has lying around. Thanks all for your suggestions!

timmy85 · 4 Nov 2019 at 13:11

Looks like I'm not 100% out of the woods with this yet. HG612 modem keeps disconnecting every 5 minutes or so......

I'm in work so only have access to the Asus router, can't get into the modem yet. Will be back unplugging things tonight

timmy85 · 11 Nov 2019 at 12:18

I'm still struggling with this. If I connect the hg612 modem, or if I use the talktalk d-link router in bridge mode, everything connect and works, but I seem to get random drops in the vdsl connection every 5 to 10 minutes? I cannot for the life of me figure out what the cause is?

Zefan · 11 Nov 2019 at 13:00

Can you check the logs of both devices? The aim would be to check around the time the issue presents itself and look for evidence that could lead you further.

timmy85 · 11 Nov 2019 at 13:06

I can't seem to connect to the D-Link router over the network at the moment for some reason, even when the internet is connected. I've pulled the below off the asus

Nov 11 11:04:54 WAN Connection: ISP's DHCP did not function properly.
Nov 11 11:04:54 DualWAN: skip single wan wan_led_control - WANRED off
Nov 11 11:04:55 nat: apply redirect rules
Nov 11 11:04:55 rc_service: udhcpc 8671:notify_rc start_firewall
Nov 11 11:04:56 miniupnpd[8372]: shutting down MiniUPnPd
Nov 11 11:04:56 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 11:04:56 wan: finish adding multi routes
Nov 11 11:04:56 rc_service: udhcpc 8671:notify_rc stop_upnp
Nov 11 11:04:56 rc_service: waitting "start_firewall" via udhcpc ...
Nov 11 11:04:57 miniupnpd[8716]: version 1.9 started
Nov 11 11:04:57 miniupnpd[8716]: HTTP listening on port 38062
Nov 11 11:04:57 miniupnpd[8716]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:04:57 rc_service: udhcpc 8671:notify_rc start_upnp
Nov 11 11:04:57 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 11 11:04:57 miniupnpd[8716]: shutting down MiniUPnPd
Nov 11 11:04:58 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 11 11:04:59 ddns update: ez-ipupdate: starting...
Nov 11 11:04:59 miniupnpd[8719]: version 1.9 started
Nov 11 11:04:59 miniupnpd[8719]: HTTP listening on port 48627
Nov 11 11:04:59 miniupnpd[8719]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:04:59 WAN Connection: WAN was restored.
Nov 11 11:04:59 ddns update: asus_private() interface =eth0
Nov 11 11:04:59 ddns update: g_asus_ddns_mode == 2
Nov 11 11:05:00 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 11 11:05:00 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Mon, 11 Nov 2019 11:04:59 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 11 11:05:00 ddns update: retval= 0, ddns_return_code (,200)
Nov 11 11:05:00 ddns update: asusddns_update: 0
Nov 11 11:05:01 ddns: ddns update ok
Nov 11 11:05:01 ddns update: exit_main
Nov 11 11:05:16 BWDPI: fun bitmap = 7f
Nov 11 11:05:16 rc_service: udhcpc 8671:notify_rc start_firewall
Nov 11 11:05:17 miniupnpd[8719]: shutting down MiniUPnPd
Nov 11 11:05:17 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 11:05:17 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 10031 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 10033 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 10036 is big. Consider r2q change.
Nov 11 11:05:17 kernel: HTB: quantum of class 10037 is big. Consider r2q change.
Nov 11 11:05:17 miniupnpd[8849]: version 1.9 started
Nov 11 11:05:17 miniupnpd[8849]: HTTP listening on port 48584
Nov 11 11:05:17 miniupnpd[8849]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:05:18 kernel: HTB: quantum of class 10039 is big. Consider r2q change.
Nov 11 11:05:18 kernel: HTB: quantum of class 20039 is big. Consider r2q change.
Nov 11 11:05:18 dhcp client: bound 79.67.41.160 via 79.67.32.1 during 900 seconds.
Nov 11 11:27:24 WAN Connection: ISP's DHCP did not function properly.
Nov 11 11:27:25 DualWAN: skip single wan wan_led_control - WANRED off
Nov 11 11:27:25 nat: apply redirect rules
Nov 11 11:27:28 rc_service: udhcpc 9175:notify_rc start_firewall
Nov 11 11:27:29 miniupnpd[8849]: shutting down MiniUPnPd
Nov 11 11:27:29 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 11:27:29 wan: finish adding multi routes
Nov 11 11:27:29 rc_service: udhcpc 9175:notify_rc stop_upnp
Nov 11 11:27:29 rc_service: waitting "start_firewall" via udhcpc ...
Nov 11 11:27:30 miniupnpd[9219]: version 1.9 started
Nov 11 11:27:30 miniupnpd[9219]: HTTP listening on port 38180
Nov 11 11:27:30 miniupnpd[9219]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:27:30 rc_service: udhcpc 9175:notify_rc start_upnp
Nov 11 11:27:30 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 11 11:27:30 miniupnpd[9219]: shutting down MiniUPnPd
Nov 11 11:27:31 WAN Connection: WAN was restored.
Nov 11 11:27:31 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 11 11:27:32 miniupnpd[9225]: version 1.9 started
Nov 11 11:27:32 miniupnpd[9225]: HTTP listening on port 53556
Nov 11 11:27:32 miniupnpd[9225]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:27:32 ddns update: ez-ipupdate: starting...
Nov 11 11:27:32 ddns update: asus_private() interface =eth0
Nov 11 11:27:32 ddns update: g_asus_ddns_mode == 2
Nov 11 11:27:33 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 11 11:27:33 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Mon, 11 Nov 2019 11:27:31 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 11 11:27:33 ddns update: retval= 0, ddns_return_code (,200)
Nov 11 11:27:33 ddns update: asusddns_update: 0
Nov 11 11:27:33 ddns: ddns update ok
Nov 11 11:27:33 ddns update: exit_main
Nov 11 11:27:49 BWDPI: fun bitmap = 7f
Nov 11 11:27:49 rc_service: udhcpc 9175:notify_rc start_firewall
Nov 11 11:27:50 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Nov 11 11:27:50 miniupnpd[9225]: shutting down MiniUPnPd
Nov 11 11:27:50 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 10031 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 10033 is big. Consider r2q change.
Nov 11 11:27:50 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 11:27:50 kernel: HTB: quantum of class 10036 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 10037 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 10039 is big. Consider r2q change.
Nov 11 11:27:50 kernel: HTB: quantum of class 20039 is big. Consider r2q change.
Nov 11 11:27:50 dhcp client: bound 79.67.41.160 via 79.67.32.1 during 900 seconds.
Nov 11 11:27:51 miniupnpd[9374]: version 1.9 started
Nov 11 11:27:51 miniupnpd[9374]: HTTP listening on port 59948
Nov 11 11:27:51 miniupnpd[9374]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:49:55 WAN Connection: ISP's DHCP did not function properly.
Nov 11 11:49:56 DualWAN: skip single wan wan_led_control - WANRED off
Nov 11 11:49:56 nat: apply redirect rules
Nov 11 11:49:59 rc_service: udhcpc 9661:notify_rc start_firewall
Nov 11 11:50:00 miniupnpd[9374]: shutting down MiniUPnPd
Nov 11 11:50:00 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 11:50:00 wan: finish adding multi routes
Nov 11 11:50:00 rc_service: udhcpc 9661:notify_rc stop_upnp
Nov 11 11:50:00 rc_service: waitting "start_firewall" via udhcpc ...
Nov 11 11:50:01 miniupnpd[9705]: version 1.9 started
Nov 11 11:50:01 miniupnpd[9705]: HTTP listening on port 43108
Nov 11 11:50:01 miniupnpd[9705]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:50:01 rc_service: udhcpc 9661:notify_rc start_upnp
Nov 11 11:50:01 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 11 11:50:01 miniupnpd[9705]: shutting down MiniUPnPd
Nov 11 11:50:02 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 11 11:50:03 miniupnpd[9709]: version 1.9 started
Nov 11 11:50:03 miniupnpd[9709]: HTTP listening on port 38616
Nov 11 11:50:03 miniupnpd[9709]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 11:50:03 ddns update: ez-ipupdate: starting...
Nov 11 11:50:03 ddns update: asus_private() interface =eth0
Nov 11 11:50:03 ddns update: g_asus_ddns_mode == 2
Nov 11 11:50:05 WAN Connection: WAN was restored.
Nov 11 11:50:05 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 11 11:50:06 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Mon, 11 Nov 2019 11:50:04 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 11 11:50:06 ddns update: retval= 0, ddns_return_code (,200)
Nov 11 11:50:06 ddns update: asusddns_update: 0
Nov 11 11:50:06 ddns: ddns update ok
Nov 11 11:50:06 ddns update: exit_main
Nov 11 11:50:21 BWDPI: fun bitmap = 7f
Nov 11 11:50:21 rc_service: udhcpc 9661:notify_rc start_firewall
Nov 11 11:50:22 miniupnpd[9709]: shutting down MiniUPnPd
Nov 11 11:50:22 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Nov 11 11:50:22 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Nov 11 11:50:22 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Nov 11 11:50:22 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Nov 11 11:50:22 kernel: HTB: quantum of class 10031 is big. Consider r2q change.
Nov 11 11:50:22 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 11:50:22 kernel: HTB: quantum of class 10033 is big. Consider r2q change.
Nov 11 11:50:22 kernel: HTB: quantum of class 10036 is big. Consider r2q change.
Nov 11 11:50:22 kernel: HTB: quantum of class 10037 is big. Consider r2q change.
Nov 11 11:50:23 kernel: HTB: quantum of class 10039 is big. Consider r2q change.
Nov 11 11:50:23 kernel: HTB: quantum of class 20039 is big. Consider r2q change.
Nov 11 11:50:23 dhcp client: bound 79.67.41.160 via 79.67.32.1 during 900 seconds.
Nov 11 11:50:23 miniupnpd[9865]: version 1.9 started
Nov 11 11:50:23 miniupnpd[9865]: HTTP listening on port 54512
Nov 11 11:50:23 miniupnpd[9865]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:12:32 WAN Connection: ISP's DHCP did not function properly.
Nov 11 12:12:33 rc_service: udhcpc 10160:notify_rc start_firewall
Nov 11 12:12:33 miniupnpd[9865]: shutting down MiniUPnPd
Nov 11 12:12:34 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:12:34 DualWAN: skip single wan wan_led_control - WANRED off
Nov 11 12:12:34 wan: finish adding multi routes
Nov 11 12:12:34 nat: apply redirect rules
Nov 11 12:12:34 rc_service: udhcpc 10160:notify_rc stop_upnp
Nov 11 12:12:34 rc_service: waitting "start_firewall" via udhcpc ...
Nov 11 12:12:34 miniupnpd[10207]: version 1.9 started
Nov 11 12:12:34 miniupnpd[10207]: HTTP listening on port 37876
Nov 11 12:12:34 miniupnpd[10207]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:12:35 rc_service: udhcpc 10160:notify_rc start_upnp
Nov 11 12:12:35 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 11 12:12:35 miniupnpd[10207]: shutting down MiniUPnPd
Nov 11 12:12:36 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 11 12:12:36 miniupnpd[10211]: version 1.9 started
Nov 11 12:12:37 miniupnpd[10211]: HTTP listening on port 45129
Nov 11 12:12:37 miniupnpd[10211]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:12:37 ddns update: ez-ipupdate: starting...
Nov 11 12:12:37 ddns update: asus_private() interface =eth0
Nov 11 12:12:37 ddns update: g_asus_ddns_mode == 2
Nov 11 12:12:38 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 11 12:12:38 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Mon, 11 Nov 2019 12:12:36 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 11 12:12:38 ddns update: retval= 0, ddns_return_code (,200)
Nov 11 12:12:38 ddns update: asusddns_update: 0
Nov 11 12:12:38 ddns: ddns update ok
Nov 11 12:12:38 ddns update: exit_main
Nov 11 12:12:40 WAN Connection: WAN was restored.
Nov 11 12:12:40 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:12:52 BWDPI: fun bitmap = 7f
Nov 11 12:12:52 rc_service: udhcpc 10160:notify_rc start_firewall
Nov 11 12:12:53 miniupnpd[10211]: shutting down MiniUPnPd
Nov 11 12:12:53 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Nov 11 12:12:53 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Nov 11 12:12:53 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Nov 11 12:12:53 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Nov 11 12:12:53 kernel: HTB: quantum of class 10031 is big. Consider r2q change.
Nov 11 12:12:53 kernel: HTB: quantum of class 10033 is big. Consider r2q change.
Nov 11 12:12:53 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:12:53 kernel: HTB: quantum of class 10036 is big. Consider r2q change.
Nov 11 12:12:54 kernel: HTB: quantum of class 10037 is big. Consider r2q change.
Nov 11 12:12:54 kernel: HTB: quantum of class 10039 is big. Consider r2q change.
Nov 11 12:12:54 kernel: HTB: quantum of class 20039 is big. Consider r2q change.
Nov 11 12:12:54 dhcp client: bound 79.67.41.160 via 79.67.32.1 during 900 seconds.
Nov 11 12:12:54 miniupnpd[10363]: version 1.9 started
Nov 11 12:12:54 miniupnpd[10363]: HTTP listening on port 32937
Nov 11 12:12:54 miniupnpd[10363]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:33:08 rc_service: httpd 291:notify_rc start_autodet
Nov 11 12:35:05 WAN Connection: ISP's DHCP did not function properly.
Nov 11 12:35:05 DualWAN: skip single wan wan_led_control - WANRED off
Nov 11 12:35:05 nat: apply redirect rules
Nov 11 12:35:06 rc_service: udhcpc 10665:notify_rc start_firewall
Nov 11 12:35:06 miniupnpd[10363]: shutting down MiniUPnPd
Nov 11 12:35:07 wan: finish adding multi routes
Nov 11 12:35:07 rc_service: udhcpc 10665:notify_rc stop_upnp
Nov 11 12:35:07 rc_service: waitting "start_firewall" via udhcpc ...
Nov 11 12:35:07 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:35:07 miniupnpd[10709]: version 1.9 started
Nov 11 12:35:07 miniupnpd[10709]: HTTP listening on port 56368
Nov 11 12:35:07 miniupnpd[10709]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:35:08 rc_service: udhcpc 10665:notify_rc start_upnp
Nov 11 12:35:08 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 11 12:35:08 miniupnpd[10709]: shutting down MiniUPnPd
Nov 11 12:35:09 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 11 12:35:09 miniupnpd[10712]: version 1.9 started
Nov 11 12:35:09 miniupnpd[10712]: HTTP listening on port 39508
Nov 11 12:35:09 miniupnpd[10712]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:35:09 ddns update: ez-ipupdate: starting...
Nov 11 12:35:09 ddns update: asus_private() interface =eth0
Nov 11 12:35:09 ddns update: g_asus_ddns_mode == 2
Nov 11 12:35:10 WAN Connection: WAN was restored.
Nov 11 12:35:10 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 11 12:35:11 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Mon, 11 Nov 2019 12:35:09 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 11 12:35:11 ddns update: retval= 0, ddns_return_code (,200)
Nov 11 12:35:11 ddns update: asusddns_update: 0
Nov 11 12:35:11 ddns: ddns update ok
Nov 11 12:35:11 ddns update: exit_main
Nov 11 12:35:27 BWDPI: fun bitmap = 7f
Nov 11 12:35:27 rc_service: udhcpc 10665:notify_rc start_firewall
Nov 11 12:35:27 miniupnpd[10712]: shutting down MiniUPnPd
Nov 11 12:35:28 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 10031 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 10033 is big. Consider r2q change.
Nov 11 12:35:28 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:35:28 kernel: HTB: quantum of class 10036 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 10037 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 10039 is big. Consider r2q change.
Nov 11 12:35:28 kernel: HTB: quantum of class 20039 is big. Consider r2q change.
Nov 11 12:35:28 dhcp client: bound 79.67.41.160 via 79.67.32.1 during 900 seconds.
Nov 11 12:35:28 miniupnpd[10866]: version 1.9 started
Nov 11 12:35:28 miniupnpd[10866]: HTTP listening on port 34238
Nov 11 12:35:28 miniupnpd[10866]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:57:28 rc_service: httpd 291:notify_rc start_autodet
Nov 11 12:57:36 WAN Connection: ISP's DHCP did not function properly.
Nov 11 12:57:36 DualWAN: skip single wan wan_led_control - WANRED off
Nov 11 12:57:37 nat: apply redirect rules
Nov 11 12:57:38 rc_service: udhcpc 11165:notify_rc start_firewall
Nov 11 12:57:39 wan: finish adding multi routes
Nov 11 12:57:39 miniupnpd[10866]: shutting down MiniUPnPd
Nov 11 12:57:39 rc_service: udhcpc 11165:notify_rc stop_upnp
Nov 11 12:57:39 rc_service: waitting "start_firewall" via udhcpc ...
Nov 11 12:57:39 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:57:39 miniupnpd[11209]: version 1.9 started
Nov 11 12:57:39 miniupnpd[11209]: HTTP listening on port 52596
Nov 11 12:57:39 miniupnpd[11209]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:57:40 rc_service: udhcpc 11165:notify_rc start_upnp
Nov 11 12:57:40 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 11 12:57:40 miniupnpd[11209]: shutting down MiniUPnPd
Nov 11 12:57:41 start_ddns: update WWW.ASUS.COM dyndns, wan_unit 0
Nov 11 12:57:41 miniupnpd[11212]: version 1.9 started
Nov 11 12:57:41 miniupnpd[11212]: HTTP listening on port 33604
Nov 11 12:57:41 miniupnpd[11212]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:57:42 ddns update: ez-ipupdate: starting...
Nov 11 12:57:42 ddns update: asus_private() interface =eth0
Nov 11 12:57:42 ddns update: g_asus_ddns_mode == 2
Nov 11 12:57:42 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 443.
Nov 11 12:57:43 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Mon, 11 Nov 2019 12:57:41 GMT^M Server: Apache^M X-Powered-By: PHP/5.6.30^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Nov 11 12:57:43 ddns update: retval= 0, ddns_return_code (,200)
Nov 11 12:57:43 ddns update: asusddns_update: 0
Nov 11 12:57:43 ddns: ddns update ok
Nov 11 12:57:43 ddns update: exit_main
Nov 11 12:57:44 WAN Connection: WAN was restored.
Nov 11 12:58:00 BWDPI: fun bitmap = 7f
Nov 11 12:58:00 rc_service: udhcpc 11165:notify_rc start_firewall
Nov 11 12:58:00 miniupnpd[11212]: shutting down MiniUPnPd
Nov 11 12:58:01 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Nov 11 12:58:01 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 10031 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 10033 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 10036 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 10037 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 10039 is big. Consider r2q change.
Nov 11 12:58:01 kernel: HTB: quantum of class 20039 is big. Consider r2q change.
Nov 11 12:58:01 miniupnpd[11351]: version 1.9 started
Nov 11 12:58:01 miniupnpd[11351]: HTTP listening on port 35561
Nov 11 12:58:01 miniupnpd[11351]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 11 12:58:01 dhcp client: bound XX.XX.XX.XXX via XX.XX.XX.XX during 900 seconds.

timmy85 · 13 Nov 2019 at 21:12

A small update on this. It appears there was a fault on the line which resulted in Talktalk sending an openreach engineer out.

A stable connection has been restored, however I am unable to access the talktalk dsl router (which is now in bridgemode) via 192.168.1.1?

VaderDSL · 15 Nov 2019 at 06:34

timmy85 said:
A small update on this. It appears there was a fault on the line which resulted in Talktalk sending an openreach engineer out.

A stable connection has been restored, however I am unable to access the talktalk dsl router (which is now in bridgemode) via 192.168.1.1?

i might be wrong but this might be expected behaviour, in bridge mode it is just passing on the Wan connection to your ASU’s router. Therefore most consumer routers in bridge mode have their web interface disabled. You generally have to do a hard reset to then access web interface if you want to set it up again , at least on the consumer routers I’ve used I’ve had to, but I could be wrong, don’t have first hand experience with the routers you’re using.

timmy85 · 15 Nov 2019 at 11:16

VaderDSL said:
i might be wrong but this might be expected behaviour, in bridge mode it is just passing on the Wan connection to your ASU’s router. Therefore most consumer routers in bridge mode have their web interface disabled. You generally have to do a hard reset to then access web interface if you want to set it up again , at least on the consumer routers I’ve used I’ve had to, but I could be wrong, don’t have first hand experience with the routers you’re using.

I think you might be right. I've had to reset it and have gone back to double nat. With the talktalk router in bridge mode, the Asus keeps losing an internet connection. The talktalk router configured in normal mode with dhcp is rock solid. That leads me to believe I'm missing something with the config on the asus....