PAP2T vs RT31P2

[voip123]

I've been talking with VOIPo support about this. I think it's a bad RT. Earlier today I put the RT directly connected to the cable modem (I first made the WAN on the RT DHCP so the cable modem could assign it a public IP). I unplugged both, plugged in the cable modem, waited for the 4 lights, plugged in the VOIPo. The Internet light on the VOIPo blinked like crazy (which is normal). But never got a Phone light to light up. Then after waiting for 30 mins, I tried to get back into the RT admin screen, and the password was changed and I can no longer get in. I then tried the Reset button for 30 seconds, and it didn't work. Connecting an XP laptop to the RT, getting a 192.168.15.100 IP, I could see the internet fine.

Thanks to all of you for the continued suggestions.

-Craig

Since you mentioned you connected the RT to modem directly. Can we do one more check?

After hookup everything, run the ipconfig /all

Post the output here.

[ctaranto]

Since you mentioned you connected the RT to modem directly. Can we do one more check?

After hookup everything, run the ipconfig /all

Post the output here.

Well, I put the RT directly on the cable modem to eliminate everything else. After getting Phone 1 lit up, I moved it back behind the WRT router, and it still works fine.

I have the WRT give the RT WAN a 172.20.0.101 address (using Static DHCP on the WRT, Obtain IP on the RT). The RT LAN is 192.168.15.1. I have turned DHCP off on the RT because I'm not going to be connecting anything to it and don't want unnecessary things running on it.

When I did have a laptop connected to the RT (and DHCP was enabled), I believe it provided:

IP: 192.168.15.100
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1

With that, I was able to see the RT, WRT, and internet.

I have unplugged the VoicePulse PAP2T, configured VoicePulse to always call my virtual number on VOIPo, and all is well.

/c

[voip123]

Well, I put the RT directly on the cable modem to eliminate everything else. After getting Phone 1 lit up, I moved it back behind the WRT router, and it still works fine.

I have the WRT give the RT WAN a 172.20.0.101 address (using Static DHCP on the WRT, Obtain IP on the RT). The RT LAN is 192.168.15.1. I have turned DHCP off on the RT because I'm not going to be connecting anything to it and don't want unnecessary things running on it.

When I did have a laptop connected to the RT (and DHCP was enabled), I believe it provided:

IP: 192.168.15.100
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1

With that, I was able to see the RT, WRT, and internet.

I have unplugged the VoicePulse PAP2T, configured VoicePulse to always call my virtual number on VOIPo, and all is well.

/c

OK. I can see your setting as below:
#1 comcast modem (correct?). The default gateway on the device is 172.20.0.1. Now leave the DHCP enable on this device.

#2 your RT. When you connect the RT to the #1 in any port. But you must connect the other end on RT into the <B>Internet</B> port.

#3 A XP machine that connects to the RT.

If you run the ipconfig /all on the XP, you should get something like this:
IP: 172.20.0.1XX
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1 <- I am not sure about this one. Did you assign this?

Now open a browser,and type: http://172.20.0.1XX, the one you got from the command ipconfig /all. You might try: http://172.20.0.1XX:8080 or http://172.20.0.1XX:9999, it depends on the port VOIPo sets for you.

See if you can access.

[ctaranto]

OK. I can see your setting as below:
#1 comcast modem (correct?). The default gateway on the device is 172.20.0.1. Now leave the DHCP enable on this device.

#2 your RT. When you connect the RT to the #1 in any port. But you must connect the other end on RT into the <B>Internet</B> port.

#3 A XP machine that connects to the RT.

If you run the ipconfig /all on the XP, you should get something like this:
IP: 172.20.0.1XX
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1 <- I am not sure about this one. Did you assign this?

Now open a browser,and type: http://172.20.0.1XX, the one you got from the command ipconfig /all. You might try: http://172.20.0.1XX:8080 or http://172.20.0.1XX:9999, it depends on the port VOIPo sets for you.

See if you can access.

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

[usa2k]

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

That sounds like a sensible configuration.

[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

[MisterEd]

OK. I can see your setting as below:
#1 comcast modem (correct?). The default gateway on the device is 172.20.0.1. Now leave the DHCP enable on this device.

#2 your RT. When you connect the RT to the #1 in any port. But you must connect the other end on RT into the <B>Internet</B> port.

#3 A XP machine that connects to the RT.

If you run the ipconfig /all on the XP, you should get something like this:
IP: 172.20.0.1XX
Subnet: 255.255.255.0
Gateway: 192.168.15.1
DNS: 192.168.15.1 <- I am not sure about this one. Did you assign this?

Now open a browser,and type: http://172.20.0.1XX, the one you got from the command ipconfig /all. You might try: http://172.20.0.1XX:8080 or http://172.20.0.1XX:9999, it depends on the port VOIPo sets for you.

See if you can access.

I've been following this thread and you have me confused. If I am missing something I apologize for "butting in."

Why would he be getting a 172.xx address off the LAN side of his WRT router to his (XP) computer. Unless he made changes the "normal" IP generated on the lan side would be in the private 192.168.x.xxx range. I've never seen a router (out of the box) generate a public IP on the LAN.

When I run IPCONFIG/ALL I get this (this is Win7):

• Connection-specific DNS Suffix . :
  Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
  Physical Address. . . . . . . . . : 00-xx-xx-xx-5F-9F
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  IPv4 Address. . . . . . . . . . . : 192.168.1.20
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.1.1

My Voipo device is getting 192.168.1.5 and to access it I use http://192.168.1.5
Again, if I am misunderstanding something I apologize.

[sr98user]

Why would he be getting a 172.xx address off the LAN side of his WRT router to his (XP) computer. Unless he made changes the "normal" IP generated on the lan side would be in the private 192.168.x.xxx range. I've never seen a router (out of the box) generate a public IP on the LAN.

172.16.0.0 - 172.31.0.0 are class B private networks. 192.168.x.x is class C and 10.0.0.0 is the Class A. All three are private subnets and are not routable on the internet.

Most of the routers are set to give a subnet in 192.168.x.x. I think the user must have changed it to the class B private address.

[chpalmer]

LAN on 172.31.125/24 here...