08-27-2013 11:35 AM
People say it's a lot like the 2Wire 3600, but the menus don't look the same to me.
I Happily follow instructions with screenshots.
My local tech geek is not able to handle this for some reason... Help?
Solved by: Go to Solution.
08-27-2013 2:25 PM
I've looked every where I can think of and can not find anything on what you want to do. Hopefully one of the community managers will stop in and address your issue./question.
08-27-2013 2:58 PM
The main page does look different between the 3600 and the 5031, but if I remember correctly, the firewall settings are the same, and that is where you need to go to make the appropriate changes to create a bridge like mode for a 3rd party device.
You want to login to https://192.168.1.254. It may ask you for a system password, which can be found on the side of your modem.
From there, click on the link to Customize Firewall
On Step 1, you want to choose the device that you want to be in "bridge" mode. If you do not see it, make sure that your router is setup on DHCP mode and directly connected to our router.
Once you have it selected, go down to Step 2 and scroll down further and choose Allow all applications (DMZplus mode).
After that you want to restart your router, and check the WAN IP Address it is getting. It should be a public IP address if everything was configured correctly.
Let us know how it goes.
08-27-2013 5:53 PM
Hi David. Thank You! I am on this again first thing in the morning and will
follow your instructions; Gratefully, R
On Tue, Aug 27, 2013 at 2:58 PM, Community Mailer
08-29-2013 3:52 PM
10-09-2013 10:10 AM
You are failing to mention the 5310nv does not support true bridge mode though. I tried to hook up a 750n Linksys to my gateway to put it in the dmz for the 5310 only allows 1 unit to be in the dmz and if 2 units are sharing the same ports it flags their ip addresses and locks them offline until you reboot the 5310. I was able to get hardwired connections working through the 750 but the wireless had a constant conflict that ATT tech support and the Pace mfg. 5310 could not resolve.
02-25-2014 7:03 PM
I used these instructions today to bridge a 5031NV to a D-Link DIR-655. Everything went pretty well, except devices connected to the DLink router are getting 20-80% worse performance, websites loading slower and speed tests come back weak. I can resolve speeds by hooking directly to the 5031, but then am limited by the local 10/100 ports instead of using the 10/100/1000 infrastructure that exists on the rest of my network
- Any Ideas?
- edited 10-27-2017 8:53 AM by ATTCommunityTea
Got my internet speed (cake) and gigabit LAN (eating it, too)! The trick I believe was 'Attack Detection' in advanced FW settings.
See here: http://forums.att.com/t5/Device-Setup/AT-amp-T-Modem-Router-Apple-Airport-Extreme/td-p/3607835#.Uw1o...
There is no true bridge mode on the 2Wire routers. However, you can still configure it such that almost all functions of your own router will work properly.
1. Set your router's WAN interface to get an IP address via DHCP. This is required at first so that the 2Wire recognizes your router.
2. Plug your router's WAN interface to one of the 2Wire's LAN interfaces.
3. Restart your router, let it get an IP address via DHCP.
4. Sign into the 2Wire router's interface. Go to Settings -> Firewall -> Applications, Pinholes, and DMZ
5. Select your router under section (1).
6. Click the DMZPlus button under section (2).
7. Click the Save button.
8. Restart your router, when it gets an address via DHCP again, it will be the public outside IP address. At this point, you can leave your router in DHCP mode (make sure the firewall on your router allows the DHCP renewal packets, which will occur every 10 minutes), or you can change your router's IP address assignment on the WAN interface to static, and use the same settings it received via DHCP.
9. On the 2Wire router, go to Settings -> Firewall -> Advanced Configuration
10. Uncheck the following: Stealth Mode, Block Ping, Strict UDP Session Control.
11. Check everything under Outbound Protocol Control except NetBIOS.
12. Uncheck NetBIOS under Inbound Protocol Control.
13. Uncheck all the Attack Detection checkboxes (7 of them).
14. Click Save.
Your router should now be able to route as if the 2Wire was a straight bridge, for the most part.
Inbound port 22 might be blocked, and inbound ports 8000-8015 might also be blocked, and there's nothing that can be done about it.
This is how I have my 2Wire configured, and I have a Cisco 2811 behind it doing IPSec, IPv6 tunnels, etc.
02-27-2014 7:29 PM
03-24-2014 8:32 AM
Thank you g3n3parmesan. That worked like a charm. Very informational. I have been trying to figure out how to do this since I switched to Uverse. Now I can use my Cisco router again
04-02-2014 4:39 PM
I cannot see my Cisco Router at all under those settings. I've put it in DHCP mode and it is connected directly to the router, but I only see wireless connections in the Firewall settings.
I want to use my Cisco Router instead of the PACE 5031nv because it has a much farther range and can support more devices at once. The wireless router I want to use is the Cisco Linsys E2500.
04-03-2014 11:56 AM
I am sorry about the issues you are having with connecting your Cisco E2500 with the Pace 5031. One thing to look at is to see what WAN IP address you are getting. To check:
This should be the information that the Pace 5031 provides the Cisco, so you'll have an IP address that looks something like 192.168.1.x and the Default Gateway should be 192.1681.254 assuming no changes.
If you are not getting that, let us know what IP you are getting. Try different Ethernet cables and ports to see if there is any issue with the physical connection.
Hope this helps.
07-16-2014 10:32 AM
I recently was switched to Uverse internet from the old AT&T DSL and had to switch to the Pace 5031NV. I was using a 2wire 2701HG-B and was able to bridge it with no problem. I currently have a Linksys WRVS4400N v2 connected to a server. I have a PC and a laptop that access the server through the Linksys. The only thing I need the Pace for is the internet connection, not routing, so I "bridged" it using your instructions below. It worked perfectly and I was able to access the internet while connected the Linksys router. However, after a week or so, I lost service. AT&T came out and spent a day working on my lines and determined that the line going upstairs where my server and Linksys router are located was not strong enough to receive the signal. So they had to install the Pace downstairs where the signal was stronger. This leaves me with a problem of either having to pay someone to rewire my house (which I rent, not own!) so I can connect the Pace to the Linksys upstairs or just drop a long ethernet cable downstairs connecting the Linksys to the Pace everytime I need to use it. Neither of these are really an option! So my question, is it possible to "bridge" the Pace like I did following your instructions, but do it wirelessly, since I can't physically connect to the Linksys upstairs? Being able to connect the Pace to Linksys wirelessly would solve the problem and save me having to rewire a rented house!! Any help would be greatly appreciated!
Visit these related resourcesView New Device Help!