10-10-2011 01:13:06 PM
I tried some of the tutorials in this thread, but I am still unable to get internet.
Here is what I am trying to do
I have two computers connected to the 2Wire router that came from ATT, and I have two more that I want to be connected to another router (TP-Link) because it's a gigabit router and I transfer files very often between PC3 and PC4.
I have a wire from a LAN port of 2Wire going to the WAN port of the TP-Link router. I followed the steps in one of Joe's first posts, and everything was set up like it said it would be. (The TP-Link router got the external IP and ect) However I have no internet connectivity on PC3 and PC4
I did tried changing routers default address pool from 192.168.1.100-200 to 192.168.2.100-200, but that didn't help.
Thank you for your time.
10-10-2011 01:45:37 PM
To do this you have to open all ports on the 2Wire router. If you have already done this then I don't know what the problem can be. I have similar setup but with a Belkin router and works fine with two different IP pools like you have. FYI the two PC on the 2wire router will be more accessible to hacks with all the ports open...i have all my PC on my Belkin and 1 of my SlingBoxes and my Xbox connected to the 2wire since they could not connect through Belkin
10-10-2011 01:53:02 PM
^ I don't have all the ports open on 2Wire, but the LAN port that the router is connected to is set for DMZPlus.
10-10-2011 02:01:34 PM
10-10-2011 06:02:51 PM
Don't follow the instructions in post 2 of this thread. For your application, follow the instructions in post 13. This will turn your TPLink into a switch + wireless access point. You will not use the WAN port on the TPLink, just the LAN ports.
10-10-2011 08:31:21 PM
^ That work perfectly, thank you so much!
I did see it before, but I figured I needed the other steps.
Thank you again! I can finally enjoy my gigabit network again.
10-14-2011 03:43:40 PM - edited 10-14-2011 03:50:57 PM
Joe, (and everyone else), if you're still prowling around here, I could really use some help. I've been at this for quite a while, so any advice would be hugely appreciated.
I have the 2Wire RG, a Time Capsule (1st gen), a Mac Mini running OSX Server 10.6, a pile of switches, and a block of static IP's from Uverse.
The environment is a small business (25-30 people in and out on laptops, phones, a couple of hard-wired desktops, etc.)
My goals are relatively simple, but I can't seem to figure it out.
The main goal is to set up the Mini as an FTP server that can be accessed through the LAN and from the WAN.
Secondary goals would be wireless network printing, as well as two separate wireless networks (the time capsule serving specifically N-enabled devices, while the 2-wire would deal with everything else a/b/g, whatever).
Edit: I also wouldn't mind having some DNS resolution for the Mini on the LAN.
This seems to be the only thing on the internet that I can find that deals with the 2Wire, so I hope you all can help me out.
Thanks in advance.
10-14-2011 04:16:53 PM
I recommend you start a new thread in the High Speed Internet section, and we have a forum member by the name of Oz who is pretty good with Apple stuff. I'll let him respond in your new thread and hopefully he can assist you.
10-17-2011 01:28:17 PM
I tried the other forum and Oz responded, but said he wasn't sure exactly what to do with the networking. Maybe I'll give it another try and put it in more generalized terms, rather than specific hardware, since you seem to be the resident networking genius.
I think there's only a couple things tripping me up, and I should be able to troubleshoot on my own once I have the main skeleton figured out.
I have: A server that I would like to do DHCP, FTP, and some DNS Resolution; a wireless router that can be put in bridge mode, the RG, and a block of static IPs.
My main questions are:
Where do I need to point my static IP (to which piece of hardware)?
Do I need to add a supplimentary network in the RG setup?
Should I place anything in the DMZ?
Are there any ports I should need to open up?
What would be the physical cabling setup?
RG --> Router --> Server ?
RG --> Router ?
If this still doesn't make sense, I apologize for bothering you.
10-17-2011 02:45:12 PM
1. The 2Wire RG cannot route packets to a gateway (i.e. there is no way to insert a static route). This means that you can't use the static IPs behind your own router. You can use the static IPs for devices directly connected to the RG, or you can have devices behind your own router where that router is using NAT (DMZ setup), but you can't do both at the same time.
2. If you need DHCP and DNS services running on the server, the DHCP service on the 2Wire RG cannot be turned off. Since you cannot have 2 DHCP servers running on the same logical network, this pushes you towards the solution where your server is behind your router, and your router is doing NAT as the DMZ device.
I would set things up as follows:
1. Cabling should be RG -> Router -> Server.
2. Follow my directions in post 2 of this thread to configure your router as the DMZ device, so it gets the public outside IP.
3. Don't bother with your static IPs.
4. Open the FTP port on your router (port 21, with NAT help) to enable FTP services to your server from outside.
5. Disable DHCP on your router's LAN interface, enable DHCP on your server, configure it to hand out itself as the DNS resolver as well.
6. Your clients on your side of the router should now get DHCP addresses from your server, and use your server as the DNS resolver, and your router as the default gateway. They can also access the server on it's private IP address.
7. Outside users can access the server on FTP using it's public IP address (the DMZ IP address on the router).
8. If you want the server resolvable by name from outside, you will need to run split horizon DNS. This means that your inside clients use one DNS server (your own server) where it's name resolves to the inside private IP, and your outside clients use a DNS server where the server name resolves to the outside public IP.
11-15-2011 09:09:46 PM
Thanks for the help in this thread -- I've been troubleshooting some issues and your comments have been invaluable.
I do have a question, though. I followed the instructions in post 2 on this thread (turning the 2Wire into a pseudo-bridge) and have a Netgear WNR2000v3 in the DMZ, with all my other devices hanging off the Netgear (had to do this because my wife works from home and has a SIP phone that connects to an IP PBX at her work that I simply could not get to play nice with the 2Wire, even in the DMZ).
I think I ran into the problem you mention in point 8 of that post, wherein after a short period of time the Netgear would just lose its Internet connectivity; I guess it was probably blocking the DHCP renewal packets. I followed your advice and set the IP address static and everything has been fine for 30 minutes now. Hooray!
My question is this: since the IP address I've set the Netgear to is actually the public IP address the 2Wire is assigned by AT&T, and it's not a static address, is that address likely to change regularly? I assume when that happens, my connectivity will break pretty hard. Do I need to get a static IP from AT&T? Do they even offer those to residential customers?
11-16-2011 07:32:03 AM - edited 11-16-2011 07:33:19 AM
If your IP address happens to change, then yes, it will break your connectivity and you'll have to reconfigure the NetGear.
However, it is known that on the U-Verse system, IP addresses normally do not ever change, unless the 2Wire RG is replaced or (sometimes) if it's factory reset.
I have been running a web server at home on a U-Verse IP address for over a year, and the IP address has not changed.
You can indeed purchace a block of 5 static IP addresses if you want, but those have to be assigned by the 2Wire. The 2Wire also has no facility to insert a static route, so you can't use those static IP addresses behind your router -- you can only use one of them on your NetGear's WAN interface. The other 4 would go unused.
12-07-2011 11:22:07 AM
Is this the easiest way to set my router up behind the RG? I want to have as many functions as I can from my Router which is the Asus RT-N56U
12-07-2011 06:37:46 PM
12-08-2011 06:11:30 PM
Hi Joe, I am thinking you can help with my issue. Here is what I've got:
Uverse 2Wire 3800HGV-B
Netgear WNDR3400 (brand new!)
LG N2A2DD2 NAS (fairly new!)
My Netgear was just hooked up the other day and seemed to realize what was going on and automatically assigned itself a new sub net (10.0.0.1). The 2Wire is still 192.168.1.254. Everything seemed to work just fine....networked all my computers, printers and have access to my LG within the network.
Now one of the reasons I put the new router behind the 2Wire was to get access to the LG from outside the network. The LG has software that helps to set it up but it is telling me that I need to setup port forwarding on my router. I tried this when I had the 2Wire only but couldn't get it to work since 2Wire doesn't support UPnp. So, I bought this new router, set up port forwarding for all the ports that LG says I need open, and it still fails to connect on all three test items: Web (HTTP, HTTPS), FTP Port, & Media Server. I followed all your instructions on Post #2 as well and rebooted the Netgear multiple times and still cannot get it to pass.
I want to first make sure I've got everything setup correctly on the 2Wire and Netgear before contacting LG about how to get this to work and thought you might be able to help. Thanks!
12-09-2011 06:22:16 AM
After that, you need to plug the LG NAS into the LAN side of the NetGear router and then configure it. That part I can't help you too much with, because I own neither of those units. However, if the NetGear is UPnP compliant, the LG should be able to tell the NetGear to open the proper ports on it's firewall. You will have to look at the LG and NetGear manuals to determine how to configure this and how to verify that it's working.
12-09-2011 10:25:46 PM
I'm running the 3800HGV-B with a Netgear WNDR3700v2 router and followed all the steps in post #2 and my router is not getting the public IP. It keeps getting it from the RG of 192.168.x.x and the private network is getting 10.0.0.x. I rebooted both devices one at a time and still not getting the publis IP on the Netgear.
12-12-2011 07:04:27 PM
Great post and feedback. I have read through all of your instructions however I am still a bit 'fuzzy' as to which configuration will suit me best.
I want to use my ASUS RT-N56U for everything, not just an access point. I want to turn 'wireless off' the RG and only use the RG for TV and my internet feed to my router. So to be even more clear, I want nothing connected to my RG except for the router to receive the internet from it in order to provide it to a single network both LAN and WAN on my router. Does that make sense?
This also includes firewall functions as well.
Should I follow post 2 and just disable everything on the RG i.e. wireless, lan, wan? Will I still have to have 2 subnets in order for this to work properly?
Your feedback is invaulable. Thank you.
12-12-2011 07:37:14 PM
Yes, you still need 2 subnets (one for the RG's LAN, e.g. 192.168.1.0/24, and one for your computer's LAN, e.g. 192.168.2.0/24). If you do not have two subnets, you will not be able to reach the RG's web interface from your computers.
01-02-2012 06:23:51 PM
There are some routers that have issues with the DHCP renewal process from the 2Wire router. To correct this, open a firewall port on your D-Link to accept all inbound traffic from any IP address on UDP port 68.
It appears that I've got one of these routers. Outlook on any computer connected to the LAN is loosing connection to Exchange Server every 10 minutes, resulting in Outlook freezing for several seconds while the connection is being restored. This never happped with just the 2Wire router.
I've followed the instructions in post #2 to set up my router behind the 2Wire. I set up the port forwarding on my router as follows:
Port Forward settings:
Port from = 68
Port to = 68
Protocol = UDP
IP Address forwarded to = static LAN address (for me 192.168.1.1)
Is this the right way to set this up? It doesn't change the Outlook problems I'm having.
Thanks so much for your help with this!
01-02-2012 08:11:15 PM
As far as the IP address, I'm not sure if setting it to the LAN address will work. It really should be set for the WAN address, but that's dynamic, so your firewall may not allow that.
What router is this (manufacturer and model)?
01-02-2012 08:38:40 PM - edited 01-02-2012 08:50:54 PM
The router is a Linksys WRT54GL with DD-WRT v24-sp2 installed.
It did let me enter the WAN address, and I changed the "from" to 67, and the "to" remains 68.
But that didn't change the Outlook behavior, unfortunately. Still disconnecting every 10 minutes.
01-02-2012 09:03:39 PM
See the following link:
01-03-2012 09:36:58 AM
Moved for better exposure
01-14-2012 01:47:36 PM
01-14-2012 04:45:27 PM
Since all you really need to do is get wireless working correctly, there is no need to actually do router-behind-router.as in post #2.
I would purchase an 802.11n router, and set it up as in post #13, and turn off the wireless in the 2Wire RG.
01-14-2012 06:22:24 PM
01-15-2012 05:43:05 PM
Like just about everyone else, I want to use my own Linksys wireless router to take advantage of the N-wireless speeds. Before the switch to ATT, we connected a desktop, 2 laptops, printer, xbox/wii wirelessly and a drobo NAS via wire. Nothing really comes to mind that I'd need to connect to the ATT device. All that said, which directions would you recommend I follow. Will I have any trouble accessing data off the NAS if everything is connected to my router?
Thanks for the help on here. Seems like your the only person out there with clear understanding of this mess...
01-15-2012 06:57:58 PM - edited 01-15-2012 06:58:14 PM
Yep, post #13 should do nicely for you. Plug your NAS into one of the LAN ports on your router.
In general, the only reasons you might need to use post #2 instead of post #13:
• You want to control ports on your firewall using your router rather than the 2Wire.
• You have a device or application that needs UPnP (like some gaming systems)
• You need parental controls, QOS, or VPN functions that only your router can do.
If all you want is more reliable wireless, or 802.11n (faster) wireless, you don't need post #2, you only need post #13.