Hi, I've recently acquired a new router that will hopefully will able to distribute a connection across my house unlike the shitty router we receive from Ogero. However, I am encountering difficulties in finding a way to make the Thomson from ogero act only as a modem so that my new router (EA6900) can do the the whole wireless part by itself. I know I can set the new Linksys into bridge mode but that would not be ideal since I would be losing many of the features I spent the money on this router for. Please if any of you has any idea on how to make the Thomson act only as a modem it would be greatly appreciated! thanks!
Thomson TG585 v7 as Modem Only?
What kind of difficulties are you encountering? It should be a straight forward process.
I have no idea how to do it and google was not much help, bridge mode on the thomson apparently is not the solution.InVader wroteWhat kind of difficulties are you encountering? It should be a straight forward process.
What exactly isn't working?
You don't need to bridge the pppoe connection. You can disable wireless on the modem, and then connect the new router through the WAN port to the modem. And that's it.
IMPORTANT: make sure that you are using 2 different subnets on the modem and on the router, so that traffic can get routed correctly.
For example my modem's Lan IP is 192.168.0.1, it automatically assigns (DHCP) an IP to the WAN side of my router in the same subnet 192.168.0.xxx. And the Lan side IP on my router is set to 192.168.5.1 and it assigns (DHCP) client IPs in the 192.168.5.xxx subnet.
For both, modem and router, the subnet mask is 255.255.255.0
You don't need to bridge the pppoe connection. You can disable wireless on the modem, and then connect the new router through the WAN port to the modem. And that's it.
IMPORTANT: make sure that you are using 2 different subnets on the modem and on the router, so that traffic can get routed correctly.
For example my modem's Lan IP is 192.168.0.1, it automatically assigns (DHCP) an IP to the WAN side of my router in the same subnet 192.168.0.xxx. And the Lan side IP on my router is set to 192.168.5.1 and it assigns (DHCP) client IPs in the 192.168.5.xxx subnet.
For both, modem and router, the subnet mask is 255.255.255.0
trent wroteWhat exactly isn't working?
You don't need to bridge the pppoe connection. You can disable wireless on the modem, and then connect the new router through the WAN port to the modem. And that's it.
IMPORTANT: make sure that you are using 2 different subnets on the modem and on the router, so that traffic can get routed correctly.
For example my modem's Lan IP is 192.168.0.1, it automatically assigns (DHCP) an IP to the WAN side of my router in the same subnet 192.168.0.xxx. And the Lan side IP on my router is set to 192.168.5.1 and it assigns (DHCP) client IPs in the 192.168.5.xxx subnet.
For both, modem and router, the subnet mask is 255.255.255.0
I was told it wasnt this easy since DHCP couldnt be active on both devices, also port forwarding, double nat etc would make it hard to set up the network reliably. I'm no professional so I might be very wrong, will be home in 2 hours and try the simple plug in method you told me to use.
- Edited
Port forwarding might be an issue. I never tried it because I don't need it. So that's something to look into.
Double Nat traversals not an issue, for me. I just have an extra (unnecessary) hop.
DHCP is also not an issue because you're running it on 2 different networks in the setup I described above (Net1 (0.x) between modem and router, Net2 (5.x) between router and all clients). Yes it's true you don't want 2 DHCPs on the same network, it's just not the case here. (NOTE: you can disable DHCP on the modem since it's not really needed, and set the router's WAN IP manually, just make sure it's in the modem's subnet)
The only remaining thing to double check is DNS settings. The modem will likely serve as a DNS server to the router, and the router as a DNS server to clients. You can avoid this double DNS layer by entering your ISP's DNS servers directly into the router's settings. (NOTE: you will also need to do this if you disable DHCP on the modem)
Double Nat traversals not an issue, for me. I just have an extra (unnecessary) hop.
DHCP is also not an issue because you're running it on 2 different networks in the setup I described above (Net1 (0.x) between modem and router, Net2 (5.x) between router and all clients). Yes it's true you don't want 2 DHCPs on the same network, it's just not the case here. (NOTE: you can disable DHCP on the modem since it's not really needed, and set the router's WAN IP manually, just make sure it's in the modem's subnet)
The only remaining thing to double check is DNS settings. The modem will likely serve as a DNS server to the router, and the router as a DNS server to clients. You can avoid this double DNS layer by entering your ISP's DNS servers directly into the router's settings. (NOTE: you will also need to do this if you disable DHCP on the modem)
You don't need any port forwarding or similar stuff on the modem. Just configure it as a bridge and you won't even see such options.
Disable its DHCP if possible and assign it to a different subnet as trent posted previously.
Disable its DHCP if possible and assign it to a different subnet as trent posted previously.
Did try the thomson in bridge mode but it would just not ask me for my dsl account or connect to the internet at all. Will be trying trent's method now. Wish me luck!InVader wroteYou don't need any port forwarding or similar stuff on the modem. Just configure it as a bridge and you won't even see such options.
Disable its DHCP if possible and assign it to a different subnet as trent posted previously.
You have to let the Linksys router make the internet connection (pppoe). This is the setup I have right now.ezzet wroteDid try the thomson in bridge mode but it would just not ask me for my dsl account or connect to the internet at all. Will be trying trent's method now. Wish me luck!InVader wroteYou don't need any port forwarding or similar stuff on the modem. Just configure it as a bridge and you won't even see such options.
Disable its DHCP if possible and assign it to a different subnet as trent posted previously.
Sorry I misunderstood earlier. I thought the Thomson modem had some known issue with Bridge mode.ezzet wroteDid try the thomson in bridge mode but it would just not ask me for my dsl account or connect to the internet at all. Will be trying trent's method now. Wish me luck!InVader wroteYou don't need any port forwarding or similar stuff on the modem. Just configure it as a bridge and you won't even see such options.
Disable its DHCP if possible and assign it to a different subnet as trent posted previously.
As InVader mentioned above. For bridge mode to work both the modem and router have to be setup for it. On the router, somewhere on the WAN settings page you can select the type of WAN connection. Choose PPPOE, you'll probably then get some additional settings fields where you'll be able to enter your DSL account information.
- Edited
Thompson will act as a modem and will connect to the adsl
The linksys will act as a wireless router
Stop dhcp and wireless on the thompson then connect it from lan to the wan of the new router
Put a static ip from the subnet of the Thompson,turn dhcp on the new router with different subnet setup the wireless settings and voila you have internet
The linksys will act as a wireless router
Stop dhcp and wireless on the thompson then connect it from lan to the wan of the new router
Put a static ip from the subnet of the Thompson,turn dhcp on the new router with different subnet setup the wireless settings and voila you have internet
Yeah you should disable dhcp on the secondary router.
Made it work with this! Thank you all so much I never would have though this was even possible!InVader wroteYou have to let the Linksys router make the internet connection (pppoe). This is the setup I have right now.ezzet wroteDid try the thomson in bridge mode but it would just not ask me for my dsl account or connect to the internet at all. Will be trying trent's method now. Wish me luck!InVader wroteYou don't need any port forwarding or similar stuff on the modem. Just configure it as a bridge and you won't even see such options.
Disable its DHCP if possible and assign it to a different subnet as trent posted previously.