Panoramic Modem/Router set to bridge mode keeps rebooting periodically
My modem is probably 3 months old. About 3 weeks ago it started rebooting itself for no apparent reason. I have it set in Bridge mode so I can use my own firewall and router. I've noticed my upstream signal on all channels are 52 or greater. Is that a problem? I also don't get full gigabit service... probably more like 500Mb. Any ideas? When I check with whatismyip.com i get a different cox ip address from what the internals of the cox modem says... both are cox ip addresses. not internal ones since it is in bridge more I expected them both to be the same. Any chance that is a problem?
Cox Customer Service Complaint: Gryphon Router
I picked up a new router at 3:00 pm on 09/24. I talked to Cox cable online chat prior to buying it, and they told that I would need to enable bridge mode on my wifi. So I get the router, had to follow the instructions to enable bridge mode. I go to the IP Address, Admin Tool -- turns out the login info. isnt the default login. I go on online chat for another 3 hours, where they try to troubleshoot and change the password. No one had any idea what they were doing. They told me to call a technician, after I wasted 3 hours. I had even asked if it would be better to call instead, they said no. So I end up calling anyways, I called 2 times on my cell phone, disconnected after 5 minutes, each time. Called another few time on the home phone, disconnected. Luckily, one service rep was able to help me do a hard reset for 90 seconds and I was able to get the login info to enable bridge mode. I spent another hour on customer service just for them to tell me there was an outage in my area and that they couldn't help me until it was done. So I waited till it was over, tried connecting the router, yet it still was unable to connect. SO I call again, talk with a service rep, she tells me to reset it, it doesn't work. Tells me to call a technician, tells me I'll get charged $75 if it's not Cox's problem... that I had to pay $10 a month to avoid this. No help, at all. I hung up, spent the next 3 hours trying to to disable bridge mode... FYI the Ethernet cable said it had no IP address. Finally I figured out to hard reset the WiFi. It worked, I disabled the bridge mode. You know what, I plugged the router into the modem, and it worked perfectly. I wasted 10+ hours following Cox's instructions, and no one is properly trained to give me the correct information. 10 hours when all I had to do was plug it in to the back of the Modem. I am being appalled by your customer service.Issue With Bridged CM And pfSense FW
My Netgate SG-2220 FW running pfSense gets itspublic IP from a bridged Arris TG1682. Logs suggest connectivity is lost mostly in the earlymorning hours around the time the IP address is renewed. The only way I can restore connectivity is torelease and renew the public IP. I've made some incremental tweaks to the WANDHCP client configuration but so far haven't hit the sweet spot. For those who'vebridged a Cox modem and are using your own firewall, what settings did you have to tweak to make your setup reliable, e.g. add a host name, IPalias or change DHCP protocol timings?
Need help setting up Technicolor modem/router in Bridged mode
Hello, I am having issues successfully setting up my home network with my Cox-provided Technicolor modem/router in Bridged mode, using my own router. My network topology is as follows: (Cox Technicolor modem - port 1) --> (router/firewall) --> (switch) --> (wireless access point) --> (WiFi laptop) I've configuredthe port on my router/firewall statically, using the IP address/gateway/DNS address settings that the Technicolor modem/router uses when it operates as both modem and router.I was not sure what subnet mask to use (was not visible in the Technicolor modem/router settings), so I used /24. I've setup my own router/firewall to use private 192.168.0.x/24 address space for DHCP to the LAN supported by the switch and wireless access point. The WiFi laptop can successfully connect to my wireless network and obtain an IP address from the private address space configured on my router/firewall. From the laptop I can ping the wireless access point, the switch, and the router/firewall successfully. However, when I try continuous pings to the Technicolor modem (on 192.168.100.1), the pings will succeed and fail intermittently. On a continuous ping test I'll see a handful of successful pings followed by some failures (destination unreachable), followed by another few successful pings, etc. This cycle continuously repeats with varying numbers of successful & failed pings. One constant I've noticed is that just before pings fail, the time is under 10ms,but upon recovering from a series of failures, the first successful ping takes considerably longer - 1000 to 3000+ milliseconds. All subsequent successful pings take the usual <10ms time, until they fail and the cycle repeats itself. Under this configuration I am not able to route out to the internet, and I'm left with no choice but to reset the Technicolor and put it back in modem/router mode. My question is: am I setting up my own router correctly? I tried configuring the router to obtain its IP/subnet/gateway/DNS configurations via DHCP but it does not seem to work. When I configure everything statically (and while my ping test is yielding successful pings) I can see Cox's gateway in my routers ARP table. This tells me that, at least briefly, my router is able to talk to Cox's gateway. What am I doing wrong or missing? Sidenote: I thought that maybe the ping errors were caused by the Technicolor modem not always responding correctly, but this does not seem to be the case. I configured my laptop with a static IP in the 192.168.x.x address space and connected it directly to one of the ethernet ports on the Technicolor modem and all continuous pings come back successfully and under 10ms.