Advanced DMZ

[yokushka]

Bell, please fix hub 4000 Advanced DMZ bug - public IP is not provided for device with static IP address. In my case device also need to be put in DMZ by MAC and not by IP.

[Adventureboy]

Thank you Eric, however the ip, subnet, gateway and DNA servers are issued with DHCP from Bell.  I don't think Bell uses PPPoE in Ontario for Giga Hub.  I cannot change it unless I move to Static IP which Bell does not support.  I am running RouterOS.  Perhaps I am missing something?

[Eric1194]

Yes, That totally normal, again, Bell give /32 on the PPPoE on your router OS, you will need to go to (IP -> DHCP Client -> select you interface) Make sure "Add Default Route" is set to Yes. Then you can confirm buy going into (IP -> Routes) confirm you have a 0.0.0.0/0 with Bell DHCP gateway.

[Adventureboy]

Thank you Eric, very much appreciate your help.

I have the default route set up, but Bell refuses to let this route connect:

The details of the DHCP that are issued for the WAN by Bell has a subnet of /24.  As far as I can tell, the route is set up correctly as per the above.  The gateway is unreachable.

[Eric1194]

Even if Router os Mark it as unreachable, can you ping directly from the router OS ? I remember having this issue, and sometime changing the gateway to just the interface fixed the issue. I don't use router OS anymore, so I can't compare, but I might give it a try if I have some time.

[Adventureboy]

Hi Eric, many thanks for your help.  Turns out I read on this forum somewhere that Bell does not do PPPoE for Ontario but rather just automatic DHCP.   This is not true, at least for the Giga Hub.  Bell will issue the DHCP ip, gateway, etc. but it will not allow you to access them (unreachable) without authentication.  Your help and reference to PPPoE sent me down the right path - many thanks for that.

Switching from Automatic to PPPoP with my Bell userid/password solved the issue and seems to be working now.

[Mist]

Hi @BellPatricia, I'm using Giga Hub2 I observed WAN interruptions every 10 minutes.
Bell Giga Hub Port 5 (10 GbE) logs show link down/up at those times.
My ASUS router immediately reports ‘WAN restored’ and re-DHCPs the same public IP for 600 seconds.
Please escalate to engineering to correct the 600-second IP-passthrough lease or port-flap bug.”

Date Range: November 4–5, 2025

This report summarizes correlated WAN interruption events observed between the user's ASUS GT-AXE16000 router
and the Bell Giga Hub modem during the period of November 4–5, 2025.

Each disconnection event from the Bell side (Port 5, 10G Ethernet link) directly aligns with a WAN restoration event
on the ASUS router. The evidence indicates the Bell modem is renewing the DMZ/IP-passthrough DHCP lease every
600 seconds (10 minutes), causing brief service interruptions.

Correlated Event Table

Time (EST)	Bell Log Event	ASUS Log Event	Interpretation
Nov 4 21:02	Port 5 link down/up (10G Full)	WAN restored + DHCP 600s lease	Short Internet cut; lease reset
Nov 4 21:12	Port 5 link reset	WAN restored + DHCP 600s lease	Repeat 10-min interval
Nov 4 21:22	Port 5 link reset	WAN restored + DHCP 600s lease	Repeat 10-min interval
Nov 4 21:32	Port 5 link reset	WAN restored + DHCP 600s lease	Repeat 10-min interval
Nov 4 21:42	Port 5 link reset	WAN restored + DHCP 600s lease	Repeat 10-min interval
Nov 4 21:52	Port 5 link reset	WAN restored + DHCP 600s lease	Repeat 10-min interval
Nov 4 22:02	Port 5 link reset	WAN restored + DHCP 600s lease	Repeat 10-min interval
Nov 5 00:01	Port 5 link reset	WAN restored + DHCP 600s lease	Pattern continues overnight

Conclusion

The consistent 600-second cycle strongly suggests a Bell-side issue with IP-passthrough DHCP lease renewals or
Port 5 (10G) PHY resets. The ASUS router operates correctly, merely reacquiring its lease each time the Bell
Giga Hub forces a renewal. These interruptions result in 2–5 second Internet drops every 10 minutes.

Extend IP-passthrough lease time to 24 hours or correct forced port resets or Inspect Giga Hub Port 5 link stability and firmware?

Thanks