I got the gigabit service installed about a week or so back in NYC. I have my own router for VPN etc so I had them switch the device into bridge mode. All worked fine until today; I had to power cycle the modem to move it and now it's stopped working in bridge mode.
After powering up, it comes up and assigns a 192.168.1.100 address to the connected router. I can see the management interface on 192.168.0.1, until the cable network is fully connected (network status goes from "denied" to "allowed").
At that point, it just goes dead to the world. I put Wireshark on it to see what was going on. The modem does not respond to DHCP Discover broadcast from the router. I also tested it with a direct, Ethernet connected laptop to make sure. I see a whole bunch of ARP traffic coming from a Cisco device and some LLDP from what I assume is the modem itself.
If I go into the management interface just while it's connecting and switch it to NAT / 'router' mode, it reboots and works fine. I get a 192.168.1.x address assigned to the WAN port of my router and I have internet connectivity. However, obviously VPN and incoming port forwarding etc. that's setup in my router doesn't work. Switch back to bridge mode and it stops working again.
So basically it works in NAT mode, doesn't work in bridge mode. Telephone techs not able to identify the issue and say it looks OK from their end, but seem not to be able to switch the device mode from their end. Every time I call in I get someone new and they want to run the same "reboot the computer" playbook.
Next callout slot is Weds night, so wondering if anyone had any suggestions or a way to get through to level 2 / level 3.
↧