This thread's discussion is locked. If it doesn't give you the information you need, head to its forum board for active discussions or to start a new discussion.
I have placed my T3200 fibre modem into bridged mode...
It works fine for about an hour and then goes offline,, requiring a reboot to get my connection back...
any ideas ???
I have factory reset the mode many times,,, currently it is factory mode, with wifi disabled and in bridged mode...
Solved! Go to Solution.
have not tried the last step....
but the previous entries were all about power saving feature...
my bridged modem is plugged into a Sonicwall NSA2400 firewall that has no power saving features..
So......., try the last step in the link posted earlier.
Bridging does not bypass the T3200M, it only causes it to pass traffic without processing it.
There may be clues in the actiontec log.
Also you may have to enable wifi on the actiontec so that you can look at lan port status before and after the failure. Also the port status post failure may be a clue, if cycling up down or just down.
Same problem on different ports or cables
Outta curiosity, did the "T3200M wonkines" start when you put it in Bridge Mode??
I had a T3200M for quite a few months with no issues ... decided to put 'er in Bridge so I could do some IoT stuff. Worked fine for a few weeks, then within the last week, the T3200M would reboot it self up to a 10 times in 24hr period. Called up Telus, they couldn't see any logs on the device, so they sent out a technician. Tech said they've been having issues with the devices and the software ... (and somehow replacing with same model & firmware would solve it) ... I left the new devices in default mode and it worked fine for first 12 hrs. Figured "sweet, all clear" ... put it into Bridge Mode and worked fine for next 12 hrs .. then <bam> ... have had 3 restarts in 4 hours.
I've switched Port Bridging off as I have a sneaking suspicion that Telus just straight up doesn't play nice with it at all.
Numerous times on phone calls they say they don't support it and don't recommend it, usually with excuse that "it's confusing for people and it's troublesome" ... maybe to lay-person who doesn't understand proper networking
Unfortunately, because can't pull logs off the devices as it's all locked down, there's no way to verify it isn't Telus mucking with something as a means to discover bridging.
I'm doing a test trial to see how many self-restarts happen with port bridging off, but unless someone at Telus can prove (ex: via logs) that they are not sabotaging something (accidental or otherwise), then I'm gonna guess it's actually Telus who doesn't understand networking and that's why they don't want others turning on bridging.
I'm seeing reports from others where bridging "magically start working" then all of a sudden in last week the modem keeps self-restarting ...
What's up Telus?
just discovered this in my Sonicwall log,,,
not sure if it's the T3200 or the sonicwall causing it
when this happens I loose WAN connection and need to release,renew..
151 04/08/2018 10:01:21.256 Warning Firewall Event Wan IP Changed 22.214.171.124, 0, X1
152 04/08/2018 10:01:21.256 Info DHCP Client DHCP Client got ACK from server. 126.96.36.199, 67, X1 188.8.131.52, 68 184.108.40.206
153 04/08/2018 10:01:17.944 Info DHCP Client Sending DHCP REQUEST. 0.0.0.0, 68, X1 255.255.255.255, 67 220.127.116.11
154 04/08/2018 10:01:17.944 Info DHCP Client Got DHCP OFFER. Selecting. 18.104.22.168, 67 22.214.171.124, 68 126.96.36.199
155 04/08/2018 10:01:17.928 Info DHCP Client Sending DHCP DISCOVER. 0.0.0.0, 68, X1 255.255.255.255, 67
156 04/08/2018 10:01:17.928 Warning Firewall Event WAN DHCPC IP Changed
157 04/08/2018 10:01:16.816 Info DHCP Client Sending DHCP RELEASE. 188.8.131.52, 68 10.27.191.182, 67 184.108.40.206
Is the "release/renew" on the T3200M or your bridged modem as well?
I have a Nighthawk X4S and when the T3200M hiccups, it eventually reconnects after approx 4 min ... then my Nighthawk has to reconnect as well, so another ~3-4 min .... sometimes up to 10 min.
I'm curious if given enough time (~15min?) both your devices will recover on their own, or the _only_ way is to reboot?
this log is from the NSA2400 firewall,,,
it looses connection after 20-50 minutes...
It has reconnected itself twice after 6-9 hours...
but a release/renew on the WAN interface connected to the T3200 fixes issue..
duh,, never mind,,, those release renew commands are from me...
so,, the 2400 and the t3200 looses connectivity for some reason ???
I did connect a notebook straight to the T3200 and it seems to maintain connection..??
when the WAN ip address changes on a Sonicwall NSA2400 it requires either a reboot or WAN ip release/renew..
When I take the T3200 out of bridged mode and hook it up to my Sonicwall,, the WAN ip on the sonicwall gets a 192.168.1.* address...
Just in case I added a reservation for the Sonicwall on the T3200.
It has been stable for the past couple of hours...
Conclusion : in Bridged mode the T3200 seems to be getting a new WAN ip, which casuses disconnect on the NSA2400..
going to try to put the NSA2400 in the DMZ of the T3200 ,,, or port forwarding the entire range to it.