HELP!!! linksys wireless router and TSTT paradyne modem

[TheApprentice]

Whoa Slaming....
That tidbit slipped my mind...

You sure know ur networking

[Jarrox]

Hey does anyone know how to configure the paradyne/wrtg54g so hat the linksis does the nat? i already did the ppp ip extension thing and the linksis is getting the 190.x.x.x on the wan side from tstt but the clients cant browse

is the linksis supposed to be in router mode or gateway?

P.S i'm using dd-wrt on the linksys

[keith77]

Any updates on this one.. I am having the same problem..

[Preston786]

Having both router and modem with the same IP is asking for trouble. Best practice is to unplug one device, configure its IP to something else and then reconnect.

Just do what awesome says chg it to 192.168.2.2 or sumn leave TSTT modem as 1.1

[Spazosaurus]

Hmmm just now seeing the replies on this thread.

U mean just putting the modem and router on different subnets solved the problem.

I'm no networking guru by any means but i'm pretty sure that configuring them as different hosts is all you need, i.e 1.1 for the modem and 1.2 for your wireless router and there's no need to configure them on entirely different subnets.

Please correct me if im wrong.

[W1nTry]

Once a device (regardless of what it is) is capable of 'routing', you need to have a different subnet. A routed device cannot have the same subnet on the same 'device'. I use ' ' because there are virtual routers and routing tables that allow for this. In any event, the rule still remains the same. Since both a modem and a wireless router are 'routed' devices, they cannot exist in the same address space.

[Spazosaurus]

Interesting. I have both my modem and router on the same subnet and havent had any issues whatsoever.

[W1nTry]

Basically its like this, your modem will have a private scheme (unless your flow then its different), so lets say you have 192.168.1.x/24 on your modem, that's your private scheme which is NATed onto a public IP like 190.92.45.56. You then have your router's WAN port connected on the 192.168.1.x scheme a well.
So if your modem is 192.168.1.1, your wireless router WAN port will also be a 192.168.1.2 (for eg).
Your wireless router in turn has a LAN and WLAN side, which it will most likely distribute DHCP for, generally you SHOULD NOT have a 192.168.1.x scheme on the LAN/WLAN of the wireless router as well because then the router will have the same subnets on 2 different interfaces. This is a NO NO in the greater routing world, in actuality a cisco, juniper, 3com, etc router will not even LET you put the same IP scheme on 2 interfaces of the same router.
Now that being said i've seen where this MAY work. Some wireless routers will take the DHCP scheme from say your modem and for the most part it will work. If this is the case let me introduce where it will NOT work.
Say you have PCs connected to a switch on the TSTT modem. And you are browsing wirelessly from the wirless router. You will NOT be able to reach file shares of the PCs connected directly to the TSTT modem because if your IP on the wireless/router LAN ports is 192.168.1.10 and you're trying to access 192.168.1.6 on the TSTT modem, how does the router differentiate between the internal scheme and the external?
Answer, it can't
There is 1 more case where this will work, but i'll not get into that, involves having the wireless router give out DHCP and connecting the TSTT LAN to the WLAN AND WAN... etc.

[Spazosaurus]

I've always let TSTT router handle routing and instead of plugging into the WAN port of my wireless router, just use one of the LAN ports, in which case technically the wireless router is acting as just a switch and AP. Also I disable the DHCP server on the (now AP) and rely on TSTT's to do it.

I guess this is why I havent had a problem.

Thanks for explaining that though, i'll box around with bringing back my wireless router as a router.

[Arcmanov]

When I had BLINK, I did just that, and used my wi-fi router as switch/AP.
Made things a whole lot simpler by letting the BLINK modem do 'all' the routing/DHCP.

[W1nTry]

If you're WAP has an AP mode, AP mode is the way to go. There really is no need to do double NAT. Many businesses mistake the need for a wireless ROUTER when its a wireless ACCESS POINT they really need. For Flow connections a router was necessary because theyd distribute public addresses whereas TSTT modems distribute private.

[Fkacn_tt]

What you are trying to do its kind of simple and difficult, you have too disable networking from automatic typo static, then enter the ip address, gateway, dns from the paradyne modem. directly connect to the adsl router and record all the info I listed and enter it in the wet window like I explained above.

[Saxito Pau]

If you're WAP has an AP mode, AP mode is the way to go. There really is no need to do double NAT. Many businesses mistake the need for a wireless ROUTER when its a wireless ACCESS POINT they really need. For Flow connections a router was necessary because theyd distribute public addresses whereas TSTT modems distribute private.

Really? I'm surprised that people prefer to use the DHCP in the modem itself. I personally never liked it and usually use the router DHCP for my cases. The only exception is at "that" place

In once office adding the router solved the issue of the DHCP in the Blink modem not always working.

I'd like more elaboration.