Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have purchased TP Link ADSL router a while back when I was connecting to my first ISP via ADSL.

Now, I have changed the ISP to a cable company and am having trouble setting up the router to connect to the new Cable modem.

The internet works, but only in bridge mode, ie. my PC gets public IP, and isn't part of the network, (and hence can't be accessed by other PCs in the network) which is what I want - I want the router to have the NAT and the clients behind it to have access to the Internet, but with addresses.

The setup is pretty simple - from cable modem one network cable to router, from router another network cable to PC.

When I configure the router to use Encapsulation - Bridged (VC Mux), my PC gets the public IP and the Internet works. When I configure it to use Routed connection (either LLC or VC Mux) I do get the local IP but no internet (regardless of the NAT setting)

The router also has diagnostics, status, ping etc, but nothing I change in the PVC settings enables the Internet.

Is what I'm trying even possible? If so, how to do it? What am I missing?

share|improve this question
up vote 1 down vote accepted

No, you will need another wireless router.

The WAN side of the TP-Link's router is dedicated and internally connected to the ADSL modem and phone port, so you have no means to use the router's uplink capability. The Ethernet ports you do have access to are all for the LAN (local area network). If you could convert one of those RJ45 ports to WAN functionality, then you could use that TP-Link unit with a cable modem.

share|improve this answer
But how come that Internet works just fine when in bridged mode? (using only Ethernet ports) – veljkoz Feb 8 '12 at 8:50
Bridge mode essentially disables the TP-Link's router functionality. The four RJ45 Ethernet ports comprise a switch, so you effectively connect the cable modem to your PC. The PC ends up with the public IP address because there is no router to provide NAT and DHCP. This is the same result as connecting the PC directly to the cable modem. – sawdust Feb 8 '12 at 20:54
Thanks for the clarification... now that I think about it, it does make sense... – veljkoz Feb 9 '12 at 8:23

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .