Going bonkers with r6300 and Uverse

[imported_browsing]

I had been using a lot of switches and the 2wire residential gateway that the Uverse came with to run my local area network which includes a home media server, along with a trendnet router as a wireless access point. I wanted to upgrade to 5ghz so I bought a fancy netgear R6300 but it insists on functioning as an independent router, requiring there to be a cable in the internet port as opposed to just the LAN ports like I used on the trendnet. It won't accept being part of the other network beyond internet access, it keeps switching its IP address to 10.0.0.1 and I've had no luck getting it to act as part of the existing 192.168etc... is there anything I can do? Can I get this thing to play nice with the Uverse somehow? What steps will I need to take? The way that the cabling is distributed in my house, I can't easily separate the different computers and media receivers from the uverse receivers to make things easier.

I've been fiddling with it for hours and I'm lost! Any suggestions or help would be appreciated.

 

[ScottMac]

Shut down the DHCP and firewall services on the new router (shut down all network services), then connect a LAN port of the new router to a LAN port on the RG.

Essentially, you're using your router as an access point, which only extends your existing wired network into the wireless domain.

 

[imported_browsing]

Thanks for the reply; that is exactly what I was hoping to do but I can't get it to pick up and use an IP address from my 2wire router. It refuses to even let me in to configure it if I don't have something plugged into the Internet port.

 

[TSDible]

Back when I had U-Verse, I set their gateway on its own subnet and then used my own router to do all the work. Essentially their hardware only acted as the modem. You may want to look in to doing something like that.

 

[imported_browsing]

Just a follow up -- the netgear genie program that the router comes with was trying to "fix" the connection constantly, making it impossible for me to edit the settings I needed to. There's an advanced section that is in the wireless menu on the GUI once you actually get into the router (which I had to go through their forwarding internal domain name instead of the normal 192.168.X.X -- you have to type routerlogin.net, pain in the...) that let me switch it to AP mode. After that, the sort of setup that I was originally trying for like ScottMac picked it up. It's still flaky in getting to the router settings but I don't care -- the wifi is secured and 3x faster than it was before. Thanks for all the help guys. It's definitely not ready for prime time from a firmware perspective. Fast though.

 

[makaira]

I am also going a little crazy getting the Netgear R6300 to work as a wireless access point on an existing network without control of the modem. The manual isn't very helpful either in this case.

I can configure the router from reset with a wireless connection from 192.168.1.* ip range, and give the machine an IP in 192.168.0.* range, disable DHCP etc etc, then but can't connect to it from LAN ports !?!. When I switch on "AP" (which assume is Access point), I can no longer get the web page up from either 192.168.1.1 (from wireless) or 192.168.0.228 (LAN) or the network address suggested, but the LAN now sees through the router even if the wireless doesn't...

If you configure it just the way Netgear suggests, you may be OK, but stepping off that well worn path is likely to be problematic. Makes old Netscreen Router appear simple.

Any hints gratefully received...