U-verse for BUSINESS? : 2Wire 3600HGV bridge mode? or another AT&T supported VDSL modem? [ Edited ]

[SomeJoe7777 ACE - Geek]

wesmac,

Yes, the IP addressing and DHCP are probably the problem.

Refer to post #13 in this thread for the proper procedure to make a wireless access point work on the 2Wire's network. Basically, you need to turn off DHCP on the DIR-857, and assign it a static IP address within the 2Wire's subnet.

[wesmac75]

Awesome!  Of course, there is still an issue.  I can't figure a way to make my router's static IP outside of the DHCP range.  On the RG, it's a pop up menu that won't give choices outside the DHCP range.  Any help?

When I get that set, I can manually program my dir 857 to a different LAN static IP.  Then I can disconnect the 857's wan/internet port and plug the RG into a lan/lan connection.

Am I making sense?

[SomeJoe7777 ACE - Geek]

You do not need to set the static IP for the DIR-857 through the 2Wire RG's menus. Just set it on the DIR-857 yourself. The 2Wire RG will eventually realize that the DIR-857 is using a static IP.

I believe the default DHCP range for the 2Wire is 192.168.1.64 through 192.168.1.254. Set the DIR-857 outside this range. (For example: use 192.168.1.10).

Remember that you're setting the LAN address of the DIR-857 to this IP address, not the WAN address. The WAN in this case is not used.

[wesmac75]

Done, all is running correctly.  No real change from before unfortunately!  The 3TB WD drive will not show up in the DLink program Shareport Plus or from within the DLink IP Interface.  I really thought the subnet trick would work.  Do you happen to know any suggestions for having a networked hard drive?  Via Win7?

Seriously, great advice.  I read a lot of forums.  Your advice and clarity is the best I have seen Some Joe7777.  Nicely done.

[SomeJoe7777 ACE - Geek]

You should be able to get the NAS to show up -- check the configuration of the NAS carefully (or reset it to factory defaults), and assign it a static IP address as well (use 192.168.1.20).

[wesmac75]

It's technically not NAS.  It's a USB 3.0 external.  The DIR 857 has USB 3.0, but it won't recognize this drive.

Bummin'

[SomeJoe7777 ACE - Geek]

Oh, I see. The DIR-857 has a feature where you can just plug in a USB drive and it becomes a file server for that drive.

In this case, I'm 99% sure the problem is that the drive is 3TB. Drives exceeding 2TB must use a GPT partition table or otherwise have to have some type of sector remapping mechanism within the drive controller in order to be used. I almost guarantee that the DIR-857 does not have this capability, so it's not able to use the drive.

[wesmac75]

OK thanks.  So disappointing.  I fell for their advertising.  "any USB device"  I should have known better.

Thanks for your help!  I posted your message on the DIR 857 support page I have been posting on.

http://forums.dlink.com/index.php?topic=48434.0

[aaearon]

First off props for all the support/info you've provided for this thread. I'm going to ask a question I think I already know the answer to but I'm hoping I will be surprised.

My current set up is just the 2wire RG. Since I live in an apartment and I cannot run Ethernet in the walls and my S/O finds it unacceptable to have Ethernet running across the apartment, I am using the two set top boxes as bridges (I have switches that filter out the IGMP multicast connected to the Ethernet ports of the set top boxes and have devices connected to those switches. This actually works pretty well.)  I'm wanting to use a router running DD-WRT to do all my work and turn my RG into a simple modem like in post #2.

Heres the deal though: I want to use the DD-WRT router to hand out DHCP and I need the DD-WRT router because I need to be able to add static routes to another router (pfsense that is infront of my lab network) Is this possible? If I do like in post #2, my RG is running 192.168.1.x and my DD-WRT router would be on 192.168.2.x however since all devices are using set top boxes as bridges, I don't see any way to get them on the 192.168.2.x network and off of 192.168.1.x and I still cant do static routes with the limitation of the 2wire RG. I'm thinking what I will basically need to do is

-keep RG IP as 192.168.1.254 and do the information as outlined in post #2

-set DD-WRT router IP as 192.168.1.1

-disable DHCP on the RG (I don't think this is possible. Hope I am wrong)
-enable DHCP on the DD-WRT

What does everyone think?

[SomeJoe7777 ACE - Geek]

You cannot disable DHCP on the RG, because the STBs require it.

Your two switches that you have hanging off the STB Ethernet ports -- what make/model are they? If they're smart switches that support VLANs, we might be able to make this work.

[aaearon]

They are simple NETGEAR GS108's so I am pretty sure they don't. What I think I will end up doing is ordering powerline ethernet adapters and do post #2. RG -> DD-WRT -> Powerline adapters that I will connect the switches that are currently hanging off the STBs currently.

[Computer-Joe]

---

aaearon wrote:

First off props for all the support/info you've provided for this thread. I'm going to ask a question I think I already know the answer to but I'm hoping I will be surprised.

My current set up is just the 2wire RG. Since I live in an apartment and I cannot run Ethernet in the walls and my S/O finds it unacceptable to have Ethernet running across the apartment, I am using the two set top boxes as bridges (I have switches that filter out the IGMP multicast connected to the Ethernet ports of the set top boxes and have devices connected to those switches. This actually works pretty well.)  I'm wanting to use a router running DD-WRT to do all my work and turn my RG into a simple modem like in post #2.

Heres the deal though: I want to use the DD-WRT router to hand out DHCP and I need the DD-WRT router because I need to be able to add static routes to another router (pfsense that is infront of my lab network) Is this possible? If I do like in post #2, my RG is running 192.168.1.x and my DD-WRT router would be on 192.168.2.x however since all devices are using set top boxes as bridges, I don't see any way to get them on the 192.168.2.x network and off of 192.168.1.x and I still cant do static routes with the limitation of the 2wire RG. I'm thinking what I will basically need to do is

-keep RG IP as 192.168.1.254 and do the information as outlined in post #2

-set DD-WRT router IP as 192.168.1.1

-disable DHCP on the RG (I don't think this is possible. Hope I am wrong)
-enable DHCP on the DD-WRT

What does everyone think?

---

I don't think so. The STBs will not work if there is any kind of router between them and the RG (a switch is OK). No you can not disable DHCP on the RG.

This is what I would try. On your DDWRT router turn off DHCP, set it to use 192.168.1.2 as it's local address, set it up to be in the DMZ on the RG, and connect a cable from both a LAN port and the WAN port to LAN ports on the RG. Set up your clients (downstream from the STBs) to use DHCP for IP addresses from the RG, but hard code them to use the DDWRT router as their gateway and DNS server. Might work.

__________________________________________________________
How can you be in two places at once, when your not anywhere at all?
------------------------------------------------------------------------------------------------------
I really want to become a procrastinator, but I keep putting it off.
------------------------------------------------------------------------------------------------------
There are three kinds of people, those that can count, and those that can't.
------------------------------------------------------------------------------------
“Our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them." :Bertrand Russell

[SomeJoe7777 ACE - Geek]

CJ,

That's not going to work because the DD-WRT router will have the same subnet on both the LAN and the WAN. It can't route like that.

His idea to use powerline Ethernet adapters will work. He could also replace the NetGear GS108 switches with GS108T switches and configure VLANs.

[Computer-Joe]

---

SomeJoe7777 wrote:
CJ,

That's not going to work because the DD-WRT router will have the same subnet on both the LAN and the WAN. It can't route like that.

His idea to use powerline Ethernet adapters will work. He could also replace the NetGear GS108 switches with GS108T switches and configure VLANs.

---

Ah, I was figuring on the DDWRT router having the public IP on the WAN side from the DMZ on the RG thus only having one DHCP server, but parallel gateways. I guess if were to work you'd have to wait for the public IP to be assigned to the WAN side before plugging in the LAN to LAN cable.

__________________________________________________________
How can you be in two places at once, when your not anywhere at all?
------------------------------------------------------------------------------------------------------
I really want to become a procrastinator, but I keep putting it off.
------------------------------------------------------------------------------------------------------
There are three kinds of people, those that can count, and those that can't.
------------------------------------------------------------------------------------
“Our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them." :Bertrand Russell

[aaearon]

So the powerline adapters worked like everyone expected but it seems like the throughput on them is no good. I had everything set up and working fine but when the Apartment Captain (I saw this earlier in the thead and I am shamelessly stealing it) went to stream media, it seems like the powerline adapter wasn't good enough to stream 720p and she was not happy! That is a whole nother issue on its own. I reverted back to my original set up just using the residential gateway and no DD-WRT router.

Trying to decide if I want to 1) Throw in the towel, return the router and powerline adapters and just use logmein to RDP into boxes in my lab network giving up on my idea 2) mess with the powerline adapters and somehow improve the throughput or 3) try switches that support VLAN.

I just want some routes between networks

[SomeJoe7777 ACE - Geek]

Which power line adapters did you get? If you picked up some of the 85Mbps ones, they are known to work only marginally well.

The 200Mbps ones are based on a completely different chipset, and will work much better (not just throughput-wise, but they handle broadcast and multicast packets much better).

You might want to return the ones you have and try the 200Mbps ones from a reputable company.

If that doesn't work, you might only have to spend a little bit more money to get VLAN-capable switches. Post back if you want to try that and I'll point you to some examples.

[Jamienjeff]

My apologies. Don't mean to hijack the thread but I hope by asking these questions I can get an answer to summarize what is probably detailed in many prior posts. I have moderate router and networking knowledge and have found more than one answer to this question. Having just switched to Uverse from Comcast, I am in a similar position of having a router (linksys e4200) already configured: port forwarding to a server, plex media center streaming to offsite computers, dlink ip cameras to watch the kids. I also have a domain name from tzo which is updated by the ddns function of the router (presumably for when Comcast changes my ip address). I would like to keep the router as configured and only change the RG settings. The confusion comes from reading the various suggestions of how to do this and not understanding (despite all the reading) various terminologies which may or may not be being used interchangeably. 1. What's the difference between bridge mode, pass thru mode, rg as modem or putting the router in the RG's dmz? 2. One suggestion has been to check the "router behind router" box and let the rg do the work. Seems too simple. No? 3. Suggestions in post 2 of this thread. 4. Last comes from 2wire guide which suggests this is bridge mode: Bridge mode is used to configure devices on the LAN with a broadband IP . When the gateway is into bridge mode you can use a supplementary network or a third party router to handle the traffic. The gateway will only function as a direct connection to the phone line. Note By default, the gateway is configured in the routing mode. When routing is disabled, the NAT and the DHCP server are also disabled. Confirm with the ISP that the WAN protocol is compatible with bridging mode. 1. Navigate to Settings > Broadband > Link Configuration. Configure the following section of the Link Configuration page to enable the bridge mode and add supplementary networks: 2. Select the Use Broadband IPs on LAN check box. This enables bridge mode on the gateway. 3. Enter the subnet mask address in the Specify usable subnet mask text box. You must specify this address on the LAN devices or supplementary network devices while configuring the subnet mask. The recommended subnet mask address is 255.255.255.0. 4. Select the Auto Firewall Open check box. This disables the firewall of the gateway. Make sure that you select this option because the firewall must be disabled for the bridge mode to function. 5. Select the Use the built-in system MAC address radio button from the System MAC Address section to use the configured MAC address. OR Select the Override the built-in MAC address radio button from the System MAC Address section, and mention a MAC address of your choice in the Specify MAC address text box. 6. Leave the Upstream MTU value as is. This is the maximum size allowed on packets that are communicated between your network and your ISP . 7. Select the Add Additional Network check box to tail a router from the Local Ethernet port located at the back panel of the gateway. This adds a secondary network to the broadband WAN interface. 8. Enter the gateway address of the supplementary network device in the Router Address text box. This is the gateway address of the secondary subnet. 9. Enter the Subnet Mask address in the text box. This is the router mask of the secondary subnet. 10. Select the Auto Firewall Open check box to disable the firewall for all devices using addresses from this subnet. 11. Clear the Routing check box to ensure that the gateway does not assign IP addresses to LAN devices through DHCP . 12. Click Save. The bridge mode is enabled on the gateway, and LAN devices are configured to take the Broadband IP address. The service LED on the front panel of the device remains off when the gateway is in bridge mode. The supplementary network represented by the router is tailed to the gateway. Again, my apologies if this is elsewhere, despite my searching I've been unable to locate satisfactory answers. Thanks.

[SomeJoe7777 ACE - Geek]

Ignore the 2Wire's manual. That applies to the stock 2Wire firmware, which is not provided. AT&T's firmware is different and does not have the options that are detailed in the 2Wire's manual.

All other terms you cited are equivalent. The functionality of any AT&T gateway can be configured to allow your own router to function with the outside IP address. On the 2Wire gateways, it's called "DMZPlus". On the Motorola NVG510 gateway, it's called "passthrough".

Follow the steps in post 2 of this thread to configure this setup for 2Wire gateways. There is another thread somewhere on the forum (do a search) where someone has posted the equivalent steps for the NVG510 gateway.

[aaearon]

I put the powerline adapters back in play. They are the 200mbps jobbers. The throughput isn't great (on the best outlet combo I've found I get 3.75MB/sec) but seems to be good enough for HD playback. It also seems like sometimes I need to unplug them and plug them back in which is fairly annoying but maybe its just the price I have to pay and they will 'settle down' once I ahve everything going.

This weekend I plan to revert my setup back to RG -> DD-WRT -> pfsense. Think I may have overreacted when I swapped everything back last Sunday night after streaming was crawling. 

That being said, I will need to replace one of the switches so I am going to look for a 16port one that supports VLans

[SomeJoe7777 ACE - Geek]

Try the Dell PowerConnect 2816:

http://configure.us.dell.com/dellstore/config.aspx?oc=bccwfk1&model_id=powerconnect-2816&c=us&l=en&s...

Also check out the Netgear GS108T (only 8 port, but a bargain):

http://www.amazon.com/Netgear-GS108T-NAS-Prosafe-8-Port-Gigabit/dp/B003KP8VSK/ref=sr_1_1?s=electroni...

You can also look at the Netgear GS716T-200 (16 port, less expensive than the Dell switch), but I have not used this switch so I don't know if there are any firmware bugs in it:

http://www.amazon.com/GS716T-200-ProSafe%C2%AE-16-port-Gigabit-Switch/dp/B00358PJ28/ref=sr_1_1?ie=UT...

Do NOT under any circumstances try to use the Netgear GS1xxE switches -- they have several firmware bugs that prevent VLANs from working correctly.

[Jamienjeff]

Thanks for the quick reply. 

Followed post #2; since the LInksys e4200 router was preprogrammed with IP address of 192.168.1.1, I had to change the RG IP address.  Once I got them of the same network it worked.  Partially.  I am able to access the internet on all my devices connect via wired or wireless to the router (or the gateway for that matter). 

Issue I've noticed is the following:  all of the devices in my house, which I was able to connect to previously, are no longer accessible.  For example, I have 2 dlink cameras, media server, receiver, blu ray, all with fixed ip addresses that were previously accessible via port forwarding through the router.  The cameras are live in the sense that the light on the front indicates that they are on the wireless network (home network, SSID name, not the 2Wire network).  However, when I interrogate the router for all connected devices, none of them show.  I have powered them on and off and have refreshed the router.  What is most interesting is that if I type in the external ip address to the RG (I have verified by ipconfig that it is the external address my router has as well) xx.xxx.x.x: port number to the camera, I can access the cameras.  Yet, while connected on my intranet if I type 192.168.1.1: port number, I am unable to access the camera.  If I enter 192.168.1.x for the particular camera, I am unable to connect.  This problem is further compounded by the fact that mydlink.com which was typically able to access the cameras is unable to do so. 

As an aside, I have also verified that mydomainname.com (via tzo dns server) has the correct ip address - i.e. the router is able to connect with tzo.

Suggestions?

Next question relates to using the HD boxes from Uverse to access my server.  I assume to get from the gateway to the server I need to point to the external domain name first.  Correct?

Thanks!

[SomeJoe7777 ACE - Geek]

Go back and start over, follow post 2 again. Your router and the RG should NOT be on the same subnet. See also post #7 in this thread:

http://forums.att.com/t5/Residential-Gateway/U-verse-for-BUSINESS-2Wire-3600HGV-bridge-mode-or-anoth...

Your RG should be on 192.168.1.254/24, your Linksys should be on 192.168.2.1/24 (LAN), and DHCP for the WAN. When you configure the RG for DMZPlus, the Linksys will then pick up your external IP address on its WAN (the RG will hand it the external IP via DHCP).

After this, cameras should work locally using http://192.168.2.x. Cameras should work externally using http://<external ip address>:<port> or http://<dynamic DNS name>:<port>.

[Jamienjeff]

Got it.  I didn't quite get the difference in subnet.  The RG is handing the external IP without difficulty.  I can reset the RG back to 192.168.1.254 and then change the linksys to the 192.168.2.1.  I was hoping to avoid having to change the IP addresses of all of the devices in the house, but understand that I have to do it.

Thanks for the great advice.

JW

[Jamienjeff]

Not sure I have time to address this tonight. 

But, last night I changed the RG ip address via the settings-> LAN->DHCP to the 172.16.0.0/255.255.0.0 selection.  This changed my RG ip address to 172.16.0.1.  I then put the router back to the settings that worked for me - ip address 192.168.1.1 and was able to access the web and external IP handoff worked seamlessly.  However, with this setup I was unable access the other devices that were connected to the router - which for some reason were not visible (see my previous post).  Any explanation for that?  All devices have an ip address 192.168.1.x and are connected wirelessly to the router. 

Thanks for the education!

[Jamienjeff]

Argh! Re-ran post #2. (I left the dmz open to the router). Left RG at 192.168.1.254. Verified external ip. Rebooted router and changed ip to 192.168.2.1, understanding I would have to change all ip settings for devices (cameras, server, etc). Now, even though the rg lists the router and says the ip for the router is the external ip, the router cannot connect to the Internet. I've rebooted a bunch of times. No luck. Serves me right for starting this at night. Suggestions?

[SomeJoe7777 ACE - Geek]

Remember that when you change IP addressing schemes, every device on the network needs to be rebooted/reset because most devices cache the MAC address-to-IP address mappings.

Your post where you were changing the RG to 172.16.0.0/16 should work, and this would enable your router to use 192.168.1.1. Just do it in this order:

1. Change LAN range on RG to 172.16.0.0/16, reboot RG
2. Reset Linksys, ensure outside IP address stays as the external
3. Change Linksys LAN to 192.168.1.1/24
4. Reboot Linksys, reboot your computer you're using to manage the Linkys
5. Verify internet connectivity from your computer
6. Change static IPs on other devices, reset/reboot
7. For all other DHCP devices, reset/reboot

[Jamienjeff]

Thanks much.  Will give it a try.  I hadn't rebooted the RG - probably need to do that.

When I wrote the other night, I had the RG IP set to the 172.16.0.0/16 and the Linksys to 192.168.1.1 (external ip was passed seamlessly to the linksys).  Unfortunately, as mentioned, I was unable to access all the devices (cameras, server, etc) even though they had been re-booted as well and even though they indicated connected and I was able to connect via port forwarding through the external IP.

I think hoping to have everything work the way it was wishing for too much.  Will likely have to reset everything and start over.

HOpefully will have positive news tonight.

[Jamienjeff]

Progress report:

Set RG IP to 172.16.0.0/16.  IP of RG set to 172.16.0.1.  Couldn't reboot RG as wife was watching tv.

However, the external IP was 108.xxx.xx.xx.

Set the Linksys back to 192.168.1.1 and rebooted. 

External IP was passed successfully to Linksys and was able to connect to internet.  Success! 

Almost.

2 dlink cameras with fixed IP addresses (before switching from Comcast) show green led indicating they are connected to my wireless router.  However, the router does not show they are connected.

I cannot get to the cameras via 192.168.1.11 or .12 (their assigned IP addresses) even after re-booting both cameras.

I cannot get to the cameras via 192.168.1.1:81 or :82 (their assigned ports via port fowarding).  This all worked previously.

However, I CAN get to the cameras via external IP:81 or <mydomainname.com>:81 or :82.

Fascinating and frustrating.  Any ideas?  Would UPnP (active) have anything to do with this?

Thoughts?

[SomeJoe7777 ACE - Geek]

Your cameras are connected to the LAN ports on the Linksys, correct?

Attempt to ping the cameras from your computer. If you can't ping them, something is not hooked up right, or they don't have the IP addresses you think they do.

[Jamienjeff]

I should have clarified.  The cameras are wireless IP cameras.  I can ping them successfully. 

I cannot access them via their local IP address or via port forwarding through the router (e.g. 192.168.1.1:81).

I can get to them via <external IP>:81

Mydlink.com which establishes a link with the cameras says the cameras are offline.  I had trouble establishing this in the past due to having a server on the network that I wanted to be able to access via port 80).

Let me outline the entire network:

RG -> LInksys e4200 -> home wireless network (ipads, phones, wireless ip cameras)

      -> Linksys e4200 -> switch -> wired imac, readynas server, receiver, blu ray

The cameras and the server have dedicated, fixed IP while the receiver and blu ray are assigned via dhcp (by the router).

I'm not even bothering yet with the receiver, blu ray and server until I can prove I can get the wireless ip cameras to work.

Thanks very much for all of your help!