on 15-05-2022 11:33
I'm trying to put my Hub 5 into modem mode to avoid double routing with my Draytek. It works fine with the Hub in router mode - the Draytek gets its IP address from the Hub (192.168.0.xx). However, when I change the Hub to modem mode, the Draytek won't get an IP address.
If I plug the Hub into my laptop when in modem mode, the external IP address is assigned to the laptop so I know the Hub is successfully in modem mode. The Draytek is in "obtain an IP address automatically" mode since that's the way it gets an IP address when the hub is in router mode, but when I switch the hub to modem mode, the Draytek isn't getting the external IP address.
I've tried to turn the Hub and the Draytek on in various order, but so far no success. Again - everything works perfectly in router mode but not in modem mode.
Any thoughts? I've read various messages about doing things in the right order, but so far no success.
on 15-05-2022 16:33
on 15-05-2022 16:35
I had trouble with mine in modem mode when it's not fully sync'd up and online.. The 192.168.100.1 webpage stalls and sometimes becomes 192168.0.1
But give it 7 days for VM's DHCP to catch up if there is a max-clients-per-CPE set.. I get a 7day lease, but always come back to the same IP, hub3 or 5 or 4 (I think)..
^^ 7day lease...
Always pains with dhcp catching up!
NEAL
on 15-05-2022 17:43
"webpage stalls and sometimes becomes 192168.0.1" this is because your default gateway is not 192.168.0.1 I see it's in the 192.168.220.x range. It's the these new hubs work.
"But give it 7 days for VM's DHCP" this is your WAN address and it has a lease time of 7 days. it will normally be the same WAN address unless the MAC address of the hub or your router changes. Another reason for this to change is if VM do a re-segmentation of the CMTS, otherwise you will retain the same WAN IP address, this is why VM WAN addresses are called "sticky".
15-05-2022 18:09 - edited 15-05-2022 18:09
You got modem mode working with a laptop do this again then use the clone MAC option in your router then connect the router to the hub should just work.
If this does not work it might be a bug with the hub 5 we need to check that we can make windows do by reg key "DhcpConnForceBroadcastFlag" to 1 in case that bug is happening or VM DHCP is a problem for your area.
on 15-05-2022 22:59
>> There are 10 types of people: those who understand b
But there are prople that understand ethernet/IP too... Let us handle it, I'm dead good with both.... I'm helping explain and give practical advice on fixing real-world-y stuff..
The 100.1 stalling isn't anything you can understand I don't think.. It's the drop-outs and back-ins that make it a pain with the netgear. Every T3 causes the ethernet to pop off, most likely to me. Thanks for your input 🙂
on 16-05-2022 00:00
Lol, I left a message on here and about 2 minutes later, lotal loss.. of IP
This is where 192.168.100.1 turns into 0.1.... until the next timeout...
Network wide? I've got the mobile at lease
NEAL
on 18-05-2022 09:22
Hi @mbvogeldenebeim thanks for your post here in the Community.
I'm really sorry, but we don't support with third party devices such as external routers when our Hubs are in Modem Mode.
Great to hear that as things stand though, your performance is working well in Router Mode - if you do need any further assistance please continue to post in here and our VIP's will do their best to offer further help, I'd also advise contacting Draytek's support too just in case they can provide anything further.
Many thanks
on 18-05-2022 12:34
I have done this numerous times in this exact order. No luck.
on 18-05-2022 12:36
I have tried to set the Draytek's WAN MAC address to the laptop's MAC address that successfully gets an IP address through the Hub in modem mode.
Still no success. But I'm just leaving it in router mode and hoping that the combination of the port 4 speed and the new device hardware is an improvement over Hub4 performance.
on 18-05-2022 12:38
Still not working. Can you check if there's an issue with VM DHCP servers in modem mode?