I had a dumb Comcast modem. I had a Netgear WNDR3700v3 plugged into it, and I had port forwarding set up on the Netgear. All worked as desired.
Comcast replaced my modem with an Arris TG1682G. I put the Arris into bridge mode, and didn't change the Netgear's configuration. Port forwarding doesn't work.
If I put the Arris back into router mode, I can forward ports to the Netgear. The Netgear then forwards the ports properly.
I've done a lot of testing, and it seems that traffic is not getting past the bridge.
I spent a lot of time with Comcast support, but eventually we decided we were running in circles.
Does anyone know where I've gone wrong?
You didn't say, so it's worth asking. Do you have the Netgear connected to port1 in bridge?
OK then, have you tried a quick 2 sec press of the reset button, with the Netgear connected. In bridge the gateway acts like a straight modem of course and has to be powercycled or reset whenever the device directly connected is changed.
You may have already tried that of course. Just saying.
I am having the same trouble with port fwd.
The TG1682 seems to work well with wifi, wired etc.. Good speeds and connection just port foward'nd blows.
I was trying to port fwd only thru the 1682 with no luck so I bought a Netgear AC3200. Enabled bridge mode and opened ports on the Netgear. Still no access to those ports.
Also I seem to motice when in bridge mode my speed drops from 125mb to 50mb... No idea there. Main focus is port fowarding.
Any luck on your end?
Actually, I did get everything working. Although I never was sure I identified what caused the problem, I did get it to go away. The key seems to have been resetting the gateway to "factory" state, and working from there. If you don't want to use your internal router, then you don't want your gateway in bridge mode.
Here is the procedure that should do it:
By the way, your router's IP address will not be the same as the address your gateway originally had. That threw me for a loop, at first.
I'm not sure what to tell you about my speed, because I didn't do a before and after test. I'm getting 29+Mb down and 6+Mb up. That's seems pretty good, but everything depends upon what you're paying for. You're evidently on a faster data plan than I am.
I have sucecess.
Well I am ended up going though the TG1864 Comcast modem.
I followed your instructions.
The master reset(hold for 30 sec) I think was a big factor.
I then went into bridge mode. While PC still wired I was able to see the net.
I then did a port checker and the ports I checked were open.
Then proceded to hook up the Netgear router. and fwd'd the ports I wanted open. Did port checker while on the netgear and my specific ports were still open.
I said let me try one more time wiht the TG1864. I did a master reset(30 sec hold)
Logged into the UI and setup my wifi password etc and then went to adavanced to fwd my ports. Did a port checker and all was good. I was stoked. Its been almost 3 mths of messing around.
Going to return the netgear.
I was very happy with the speed and wifi with the comcast modem.
For some reason in bridge mode my speed would throttle way back to like 40-50mb.....vs 125mb.
Even with the PC connected directly to the comcast modem in bridge mode.
Not sure the issue there.
I didn't do any speed testing.
I am still using my Netgear, because I like the degree of control it gives me. I turn the guest network on only when guests need it.
As I understand it, when the Home Hotspot is enabled it is really only available to other Xfinity Internet customers at certain levels. That would exclude my brother, but include passers-by. The Netgear's guest network gives me the choice of who can or can't use it.
I have also, at times, forced a channel selection. I'm not sure that made a big difference, but with my physical layout anything helps.
What you described perfectly worked for me. Steps
- change xfinity modem-router to bridge mode
- connect your router to port 1 in xfinity router
- power down both routers
- start routers
- now your router has external IP instead of 10.0.0.x
- your port forwarding is accessible from extranet now!