PAP2T vs RT31P2

[voip123]

I'm heading off to bed in a few minutes, so I can try this tomorrow. I will have to re-enable DHCP on the RT so the laptop gets an IP.

My config (roughly) is:
Motorola SB5120 Cable modem -> Linksys WRT54GL (Tomato) -> Linksys RT31P2

The cable modem assigns a public IP to the WRT. The WRT then assigns an internal IP (172.20.0.101) to the RT.

The LAN addresses on the RT are 192.168.15.x, so when enabling DHCP on the RT, the laptop gets a 192.168.15.x address (not 172.20.0.x address like you mentioned above). For DNS, I didn't assign to 192.168.15.1. I believe that's the default when NAT is enabled. When a laptop connects wirelessly to the RT, the default gateway and DNS are 172.20.0.1 (the WRT IP).

I have enabled remote administration on the RT, so I can access it via a laptop with a 172.20.0.x address.

Is there anything I didn't address?

/c

Now try this:

type this in your browser: http://192.168.15.1. If it asks for userID and password, use this:
UserId = admin
Password = admin

Can you access?

[ctaranto]

Now try this:

type this in your browser: http://192.168.15.1. If it asks for userID and password, use this:
UserId = admin
Password = admin

Can you access?

If I am using a laptop connected to the WRT54G, I need to use http://172.20.0.101:<port> to access the RT's GUI (remote administration I guess is what it's called). If I had a laptop connected to the RT (which I will never do since it's not wireless), I'm sure that the IP you provided will work.

The admin/admin won't work (any longer). I changed the password.

My setup is done (for now). I put the RT in the DMZ for it to stay online (port range forwarding wasn't enough apparently).

A lot of (my) confusion was because of my boneheadedness of reseting the RT early in the process, which wiped out the provisioning string required for VOIPo. I think I had the setup done right early on, but it wasn't getting Phone 1 lit, so I kept changing settings hoping it would work, which resulted in lots of questions here.

-Craig