[khx73]

Turned down another chance to "upgrade" to the HH3000 again a couple days ago... Catching up with this thread, it seems this was still the right choice

 

[Stevetryingtofigureitout]

En faite moi je me demande pourquoi tout le monde se casse la tête.

Pour bridger la Borne 3000 il suffit de brancher son routeur sur celui-ci puis d’entrée les configuration PPPOE dans votre routeur, automatiquement vous vous retrouvez avec l’adresse IP public de celui-ci et toute la gestion sera sous le control de votre routeur vous n’aurez pas de problème avec le double NAT.

Ensuite vous pouvez désactiver toutes les babioles sur la borne 3000, WI-FI, UPNP etc…

L’IPTV continue de fonctionner en WI-FI sur la bande dédier, il faut juste s’assurer que le récepteur câblé reste brancher sur la Borne 3000 et non sur votre autre réseau local principale.

Au sujet de l’Advanced DMZ il existe beaucoup de problème et une DMZ n’est pas tout-fait ce que vous pensez. Certes sa peut fonctionner mais sa ne sera jamais optimal.

Sinon vous aurez toujours la solution de prendre le GPON de Bell et de l’installer sur un convertisseur / routeur compatible puis de créer les vlan. Simple pour l’Internet plus complexe pour L’IPTV.

PS : vos info PPOE Bell peu vous les fournir.

Je comprends que ce poste date deja de 2 ans, mais quoi faire si mon router ne supporte pas en 2020 PPPoe ?Je parle ici du Eero Pro 6. Si tu me dis que de le mettre en Bridge alors la reponse est nom car je perd tout les "features" tel que homekit etc. etc. Sggestions ?

 

[byrneo]

Just to echo advanced dmz woes: I purchased the Netgear nighthawk AX1800 Router and AP:
1) Set the router up as a DHCP client, did all the firmware updates etc.
2) Plugged Netgear into port 1 LAN of the HH3000. Logged into the HH3000 on my laptop, configured Advanced DMZ. Picked the internet interface mac address from the Netgear (important) and put that as the advanced DMZ client. Hit save.
3) Rebooted everything.
4) Advanced DMZ Works! Router pulled the 157.xxx whatever it was Bell IP address, all my home network clients are on 192.168.1.xxx networks, correctly getting their IPs from the Netgear.

5) Netgear internet port goes to Bell HH, but netgear LAN port goes back to a switch (that 10 other clients in my house connect to). All the wired clients also correctly get 192.168.1.xxx IPs.

6) All worked great for a day. Suddenly no devices on my network can reach the internet anymore. But can all still see each other. I can still manage the Netgear from any device. Everyone can ping 192.168.1.1 (Netgear) but nobody can ping 192.168.2.1 anymore (Bell HH). Could before. I could manage both devices before, but now to get to the HH I have to plug my laptop directly into it again.

7) Checking the advanced DMZ in HH;my Netgear IP address has changed to like 169.2.1.1 or something crackers like that.
8) Go back into the Netgear WAN, still shows 157.x.x.x real bell IP on the Internet interface. #7 and #8 are at odds with each other.

9) Factory reset all the netgear stuff, set it all up from scratch again. Works fine again for a few hours.
10) Bam, network died again. Netgear shows the Bell real WAN IP is still there, but once again can't get to internet, can't ping 192.168.2.1. Sure enough, HH3000 shows advanced DMZ device again having invalid IP.

TLDR: I set advanced DMZ up correctly, but it only works for a little while. Router itself appears to keep DHCP address from Bell, but in the HH3000 DMZ screen the device in DMZ changes to a 169.2.1.1 (or something invalid like that). I have no idea why this keeps happening.

Ultimately returned the Netgear, but I believe the problem is the HH3000 fooling things up. I saw way back another poster had a similar issue as me but didn't see if it was ever solved.

 

[MDodson65]

Hi all,

I am using a HH3000 and a Linksys mesh with 3 nodes. I also tried to move the main node of the Linksys Mesh to the advanced DMZ of the HH3000. The configuration was easy, pick the MAC address of the Linksys, add it to the DMZ and check 'Advanced DMZ'. Save and reboot the HH3000. Once the HH3000 got back, I power cycled the Linksys main node. After a few minutes, the Linksys Mesh was back and the LED shows green (means: up and running). However, the Linksys app showed, that the Linksys Mesh obtained the WAN IP from the HH3000, but did not get Internet access.

It looks like I was able to -kind of- successfully add the Linksys Mesh to the advanced DMZ of the HH3000, but I do not understand, why the Linksys Mesh did not get internet access.
I removed the Linksys Mesh from DMZ, rebooted all and now the entire system is running like before.

However - I would like to understand, why the Linksys Mesh did not get Internet access when added to the advanced DMZ of the HH3000. Hopefully, someone here can help

Cheers!

 

[stingmao]

Hi all,

I am using a HH3000 and a Linksys mesh with 3 nodes. I also tried to move the main node of the Linksys Mesh to the advanced DMZ of the HH3000. The configuration was easy, pick the MAC address of the Linksys, add it to the DMZ and check 'Advanced DMZ'. Save and reboot the HH3000. Once the HH3000 got back, I power cycled the Linksys main node. After a few minutes, the Linksys Mesh was back and the LED shows green (means: up and running). However, the Linksys app showed, that the Linksys Mesh obtained the WAN IP from the HH3000, but did not get Internet access.

It looks like I was able to -kind of- successfully add the Linksys Mesh to the advanced DMZ of the HH3000, but I do not understand, why the Linksys Mesh did not get internet access.
I removed the Linksys Mesh from DMZ, rebooted all and now the entire system is running like before.

However - I would like to understand, why the Linksys Mesh did not get Internet access when added to the advanced DMZ of the HH3000. Hopefully, someone here can help

Cheers!

I am in Atlantic area where PPPoE is not available. The only method of using HH3000 with my Google Next wifi system is advanced DMZ in order to avoid double NAT.

The GNW didn't work in the first place even HH3000 already assigns public IP to GNW. I tried to power cycle GNW but still the same.

And then I found if I disable/enable ADMZ and delete/add router , GNW will pull public IP from HH3000 and work. Or restart GNW first, then HH3000, the whole system will be back to work. So power outage will not affect them, as it only takes 2 mins for GNW to boot up. But I am thinking I have to restart HH3000 again if Google push updates to main router.


However, even ADMZ is working, the problem that I think double NAT causes still bothers me. Sometimes network would be stuck on a certain device(Phone, iPad, TV etc), I have to disconnect wifi and connect it back.

 

[Craigwell]

I thought about creating a new thread, and I still might - but I see this one has had some legs over the years.

Having the same issues with forwarding, DMZ and ADMZ with this.

Part of it is trying not to be relayed with an HNT AP (LoRaWan). No dice, doesn't matter what I do.

Also trying to have a Minecraft server for the kids, all works great on LAN, but I cannot get the host PC outward facing in any respect.

In each case (as relevant). I've tried DDNS with NOIP.com, and plugged the credentials into the HH3K, which then reports "synchronized", but no luck. I've also tried port forwarding the correct ports, to reserved local IP, no luck. Then tried DMZ the host pc/device, no luck, and finally, the ADMZ same thing.

Is there anything new on this? My FW is SG482220DC

How about a reset to factory defaults on the HH3K? Would I need Bell to configure remotely if I do this? I have backed up settings.

 

[khx73]

Turned down another chance to "upgrade" to the HH3000 again a couple days ago... Catching up with this thread, it seems this was still the right choice

Well, I finally got an offer I couldn't refuse... HH3000 installed today. Sad to see the R3000 go.
Now in the broken A-DMZ club

 

[idallen]

I have a fully working Bell Home Hub 3000 Advanced DMZ configured
on one interface of a multi-homed home server.

EDIT: I had to give up using the ADMZ in favour of pass-through PPPoE, because the Hub disabled the ADMZ any time the machine rebooted, requiring manual resetting of the ADMZ on the Hub. Pass-through PPPoE "just works" with no messing about on the Hub.

I have access to the Hub's private LAN out the same interface card as
the WAN. I can ping (ICMP) both inbound and outbound. Traceroute works.
Clients on the Hub LAN can access the DMZ using the Hub WAN address,
and the DMZ can access Hub LAN clients using LAN IP addresses.

The DMZ interface functions exactly as if it were directly on the open
Internet, using the WAN address of the Hub as its IP address. The other
functions of the Hub are untouched.

This got long, so I rewrote it and posted it here: Fixing the Advanced DMZ in the Bell Home Hub 3000 router

 

[khx73]

The above fix may have worked for those in PPPoE land... but Bell Aliant uses DHCP.. so it doesn't work here.

 

[khx73]

Ok.. I've waited 2 days to make sure it was going to last before posting this.

I tried Advanced DMZ two days ago and it's working for me, connected to my linux based router/fw machine I've been using for years.
What prompted me to try it was a replacement HH3000 I was sent due to my other one failing. I figured I'd give it a go, because why not.
I did have to enable/disable it on the HH3000 a couple times (with release/renews on my router), but it works, and has been solid now for 48 hours.
Further, I was helping a friend set up a home network last night, and enabled it on his HH3000 as well, and it worked right away.

My HH3000:
Firmware version: SG482220DC
User interface version: 5.2.6
Hardware version: 5566-000002-005

Interested in any comments/questions from the Broken ADMZ Club on here!

 

[colinpeddle]

@khx73 how's it holding up?

 

[khx73]

@colinpeddle - Sorry for the late reply.

It's holding up just great! Since that post I've been using it non-stop with only very few hiccups.
I've also moved to a MikroTik RB5009 router. ADMZ still working just fine.

I've gained a fair bit of insight and experience to this whole issue the past few months.. Happy to share with anyone struggling with this.

The ONE single most important thing to know about ADMZ and the HH3000 is this:
If the ethernet link between the HH3000 and your ADMZ device flaps (drops) at all, the HH3000 silently stops routing traffic to your device. Period.

• This happens if the ethernet cable is unplugged, even briefly.
• It happens if you reboot your ADMZ device.
• It can happen if the cable is bad/loose.
• Symptoms:
  • Your ADMZ device will still say it has the public IP, but you won't receive any traffic.
  • DHCP Release/Renew will not fix it.
  • You can't even get to 192.168.2.1 (HH3000 default) through your ADMZ device.

Fortunately, there is an easy way to avoid this:
Place a simple switch between the HH3000 and your ADMZ device. This keeps the ethernet link alive from the HH3000's point of view, even if your ADMZ device gets unplugged, reboots, whatever. This seems to eliminate the majority of connectivity losses.

If you find yourself stuck in ADMZ with no connectivity:

• Using another device connected directly to the HH3000 (wired or wifi):
  1. Connect to the HH3000 and toggle the whole DMZ feature OFF, save, ON, save again.
  2. Release/renew your lease on your ADMZ device. Traffic should be restored.
• If you don't have access to another device to do this, or don't want to:
  • Temporarily change the MAC address of your ADMZ device, Release/Renew DHCP.
  • You should get a new private IP, with connectivity. Now do steps 1 and 2 above.

I've been working on MikroTik scripts to handle some of this automatically. Including one that senses if the DHCP client is stuck on the "rebinding..." status and forces a DHCP release. This restores ADMZ connectivity if your public IP has changed for some reason.

The work continues...