topic Re: Advanced DMZ in Internet

Advanced DMZ

yokushka — Tue, 24 Jan 2023 16:57:08 GMT

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.

Re: Bell hub 4000 Advanced DMZ bug

BellPatricia — Tue, 24 Jan 2023 16:52:58 GMT

Hi there @yokushka, thanks for reaching out to the Bell Community.

When you configure ADMZ on device X and device X requests an IP address via DHCP (dynamic not static IP), the Home Hub will offer device X the public IP address.

If you have set up a static IP address, that means your device will never request an IP address and for that reason will never be in ADMZ.

In the Home Hub GUI (192.168.2.1) under Advanced settings > DMZ you can pick the device you want to add in DMZ. The MAC address should be listed there too.

Let the Community know if you have any other questions.

- Patricia

Dmz not passing public ip to router

Ben2 — Tue, 24 Jan 2023 05:43:59 GMT

I just received a HH Giga and can't seem to get an ip address on my router (Asus Ax88u) when configured in DMZ and advanced DMZ with the router mac.

I used to connect with the same router using the SFP from the HH3000 in a media adapter bypassing it completely. Everything was working fine with PPPOE connection with myû asus router.

Now I want to use de Giga hub but I just can't get it to connect either in PPPOE or with DMZ. Am I missing something here? The Hub works well if I connect directly to it.

Re: Dmz not passing public ip to router

Ben2 — Tue, 24 Jan 2023 20:59:13 GMT

Here is what I tried:

HH giga in dmz. Advanced DMZ with mac address of router as the device. WAN port of router in LAN port of HH Giga and internet connection as Automatic IP.

2nd setup: HHGiga in dmz with IP of the router, Router in static IP. Same connections as setup 1

3rd setup: HH Giga in dmz and advanced DMZ with mac of the router. Router in PPPOE with b1*** credentials.Same connections as setup 1.

The weird thing is that HH assigns a weird IP to my router when I look at connected devices (169.1.1.1) which in turn doesnt work with my router that says ISP DHCP does not function properly.

What am I doing wrong?

Re: Bell hub 4000 Advanced DMZ bug

yokushka — Sat, 04 Feb 2023 13:27:09 GMT

Patricia, Thank you for your answer. However, with full respect if it is what your developers told you, they were not completely honest with you. In this case, please remove from firmware option to DMZ device by IP.
With full respect and Thank you in advance.

Re: Advanced DMZ

Eric1194 — Tue, 14 Feb 2023 18:08:56 GMT

Hi, I have weird issue with Advance DMZ also, My device do get the public IP, but for Some reason the Subnet mask is (128.0.0.0) Causing issue as it overlaps with other subnet on my firewall. I have found a temporary fix, I just set my device to static with the public and change the subnet mask to (/32) (255.255.255.255) everything work for a few days then just nothing. I just got my Firmware updated to 1.16, but same issue.

Re: Advanced DMZ

snowblower — Fri, 05 May 2023 17:50:09 GMT

I also have seen this "169.1.1.1" IP address when I attempted to use "Advanced DMZ" feature. 169.1.1.1 is an allocated public IP address, so this looks like a bug. And the connection didn't work, to boot. I reverted to regular DMZ and it worked.

ADMZ on Giga Hub giving bad gateway

Adventureboy — Sun, 01 Oct 2023 00:44:30 GMT

Hi team, I have a new fibre internet service and looking to use ADMZ so I am not double NATted. I have my router set up and configured and the WAN ip is passed through the Giga Hub as expected however the subnet mask is bad and the gateway is in a completely different subnet making it impossible for the ADMZ to work.

My IP address was delivered using DHCP as 184.xxx.xxx.xxx. My Subnet mask was delivered as 255.255.255.0/24. My Gateway was delivered as 10.xxx.xxx.xxx. This configuration simply won't work. The netmask needs to be 0.0.0.0/0. or the gateway needs to be in the same subnet as the issued ip.

Any thoughts on how to get this fixed?

Re: Advanced DMZ

Adventureboy — Mon, 02 Oct 2023 19:13:07 GMT

@BellPatricia I do not see anything in the history that addresses the incorrect ip details I receive from Bell's Giga Hub when set to ADMZ mode. I am not using static ip. The ip details are give to my router through DHCP and of course, I have no control on what the Bell Giga Hub sends. Will firmware version 1.19 solve this? I am on FW 1.16.5

Re: Advanced DMZ

Eric1194 — Mon, 02 Oct 2023 23:56:36 GMT

Hi I did not test since 1.16.0, but I did today on 1.16.5, and everything work as expected, my router got the public IP of the modem, and did not get a /1 or (128.0.0.0) subnet, I got a /24 (255.255.255.0) that I was expecting like the HH3000 use to do. and for the default gateway, I had it static set to the internal IP of the HH4000 and that was working, for testing I change it to dynamic, and got an IP outside the subnet of my public IP, this make sense since Bell do /32 on the PPPoE side, and the HH4000 like the HH3000 do some weird routing inside to allow access to the local subnet and the internet with the public IP. Would love to know more in detail how that is accomplish, but I have my Idea. Now I will see how stable this is, if it last longer then 24hours haha.

Re: Advanced DMZ

DMot — Tue, 03 Oct 2023 23:41:38 GMT

hey @Eric1194 - this is very promising to hear! Have you seen any packet loss or latency issues?

Re: Advanced DMZ

Adventureboy — Wed, 04 Oct 2023 12:26:15 GMT

Thanks for the info Eric. Unfortunately I am on a recent Giga Hub running 1.16.5 and ADMZ does not work. It issues an ip and gateway on different subnets and kills all internet.

Re: Advanced DMZ

DMot — Wed, 04 Oct 2023 12:44:02 GMT

I got all excited and tested it -- Internet worked, I got a public IP on my WAN port for my router -- but had packet loss and latency right away so I switched back to double NAT. I sure with we had a fix. @BellPatricia can we help with testing for a fix?

Re: Advanced DMZ

Eric1194 — Wed, 04 Oct 2023 12:50:35 GMT

So far 0 issue! I get my full speed (3gbps/3gpbs), 0 latency added, 0 packet drops. More stable that it use to be, before I could not do more then 24hours before the connection would drop entirely.

Re: Advanced DMZ

Eric1194 — Wed, 04 Oct 2023 13:02:43 GMT

Thats normal, Bell do /32 IP on the PPPoE, you need to set your self, in your router, a default route pointing to the gateway so basically (0.0.0.0/0 -> Bell DHCP gateway) that should fix your issue.

Re: Advanced DMZ

Adventureboy — Wed, 04 Oct 2023 13:29:24 GMT

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?

Re: Advanced DMZ

Eric1194 — Wed, 04 Oct 2023 13:35:13 GMT

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.

Re: Advanced DMZ

Adventureboy — Wed, 04 Oct 2023 14:31:35 GMT

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.

Re: Advanced DMZ

Eric1194 — Wed, 04 Oct 2023 15:32:49 GMT

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.

Re: Advanced DMZ

Adventureboy — Wed, 04 Oct 2023 15:57:52 GMT

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.