PAP2T vs RT31P2

[ctaranto]

Any reason why I was sent an RT31P2 vs a PAP2T? I have a PAP2T with my existing VoicePulse service. I had a RT31P2 with Vonage years ago.

Any ideas which one has better voice quality, less echoing, etc? Or are they identical internally, but the RT31P2 also is a 3 port router?

Thanks,

-Craig

[usa2k]

Without a support request, you are always most likely to get the RT31P2.

I've never used one, so I cannot comment on quality.
I've been thinking of buying one to evaluate.

[voip123]

I more prefer PAP2T.

I am currently using PAP2T unlocked with another VOIP provider.

[mikeb]

I also had a PAP2T with my former VoicePulse service. Then I received the RT31P2 from Voipo. I haven't noticed any difference in reliability or voice quality. The one thing I do like is that the RT31P2 and my wireless router are both Linksys units. They stack nicely on top of each other. ;) Although, I did add some foam extensions to the legs of the top unit to create more airflow between them.

[VOIPoTim]

The RT31P2 is the primary device shipped most of the time.

As our inventory changes, we do occasionally send out PAP2s or other Linksys devices, but we can't accept any special requests for device models.

All devices that we send out are 100% supported for all VOIPo features and functionality and are fully managed by VOIPo.

[usa2k]

... but we can't accept any special requests for device models.

In the good old days you guys had more time to spoil us :D

[ctaranto]

Update 1/6/2010: Most of the issues noted below were due to me resetting the RT31P2 adapter using the little red button in the back. That made it lose the required provisioning information needed to connect to the VOIPo servers. Most of you will not need to go through this, but it does show what a helpful bunch of users are on this forum.

See http://forums.voipo.com/showthread.php?t=1919 for how I currently have my network set up.

-------

Great info.

Question about hooking the RT31P2 with another router (WRT54G running Tomato) in front of it.

With VoicePulse, I had a PAP2T. Simply connect a LAN port on the WRT54G to the "Internet" port (the only Ether port on it), and it worked. It got an internal IP address on the same subnet as the WRT, and all was great.

With the RT31P2, do I need to connect the LAN port of the WRT54G to the WAN port of the RT31P2? Or can I get away with using the LAN port?

I greatly prefer the WRT54G being first in line since all wireless devices connect to it and I use it for QOS.

I did connect the RT31P2 via WAN port. I don't have a "line 1" light lit. And because it's on a different subnet, I can't access it without hardwiring a PC to it.

Thoughts?

Thanks,

-Craig

[voip123]

Great info.

Question about hooking the RT31P2 with another router (WRT54G running Tomato) in front of it.

With VoicePulse, I had a PAP2T. Simply connect a LAN port on the WRT54G to the "Internet" port (the only Ether port on it), and it worked. It got an internal IP address on the same subnet as the WRT, and all was great.

With the RT31P2, do I need to connect the LAN port of the WRT54G to the WAN port of the RT31P2? Or can I get away with using the LAN port?

I greatly prefer the WRT54G being first in line since all wireless devices connect to it and I use it for QOS.

I did connect the RT31P2 via WAN port. I don't have a "line 1" light lit. And because it's on a different subnet, I can't access it without hardwiring a PC to it.

Thoughts?

Thanks,

-Craig

This is my setup:

DSL Modem -> Linsys WRT54GS wireless router -> VOIPo RT31P2 Adapter

Linsys WRT54GS = 192.168.1.1

VOIPo RT31P2 = 192.168.1.188, VOIPo suggested the IP should be outside the range of the WRT54GS.

I have 2 PCs connect to the RT31P2 , the IPs are: 192.168.15.100 and 192.168.15.101. Both of them are static. The default getway on RT31P2 is 192.168.15.1. You can leave the DHCP enable, it will handle the IP for you automatically.

Hope this helps.

[Russell]

Great info.

Question about hooking the RT31P2 with another router (WRT54G running Tomato) in front of it.

With the RT31P2, do I need to connect the LAN port of the WRT54G to the WAN port of the RT31P2?
-Craig

That's what you do.

And, that's the way I've got mine setup. WAN of RT31P2 to LAN of my other router which is connected to the UVerse RG box.

I have both a RT31P2 and a PAP2T and frankly I can't tell the difference in voice quality.

[ctaranto]

This is my setup:

DSL Modem -> Linsys WRT54GS wireless router -> VOIPo RT31P2 Adapter

Linsys WRT54GS = 192.168.1.1

VOIPo RT31P2 = 192.168.1.188, VOIPo suggested the IP should be outside the range of the WRT54GS.

I have 2 PCs connect to the RT31P2 , the IPs are: 192.168.15.100 and 192.168.15.101. Both of them are static. The default getway on RT31P2 is 192.168.15.1. You can leave the DHCP enable, it will handle the IP for you automatically.

Hope this helps.

How did you connect the WRT to the RT? From the WRT LAN, did you connect to the RT WAN or RT LAN?

Thanks,

-Craig

[sr98user]

It should be from the WRT LAN to RT WAN. Otherwise you will have problems with multiple DHCP servers running on the LAN.

[voip123]

How did you connect the WRT to the RT? From the WRT LAN, did you connect to the RT WAN or RT LAN?

Thanks,

-Craig

One cable from prot1 on WRT54GS to the "internet" port on the RT31P2. You can use anyone port of the 4 ports (WRT54GS only has 4 ports). But you MUST use the "internet" port on the RT31P2. It is also important you have to assign correct IP on the RT31P2 or leave the DHCP enable.

[ctaranto]

Thanks. I had it set up that way, and I wasn't getting Phone 1 lit up. The RT administration was only available when a computer was plugged into the RT.

I found this on a vonage forum (who also uses an RT):
http://www.vonage-forum.com/ftopic4206.html

In there, it states:
The best thing to do if you are already using a router is to disable the vonage adaptor's ability to function as a router and just use it as a switch. To accomplish this you can follow the below directions.

1. Disable NAT and DCHP on the vonage adaptor.
2. From the line coming out of your router plug into lan jack 1 in the back of the vonage router.
2. If you have a computer plugged into the vonage adaptor plug it into lan jack 2 on the vonage adaptor.
3. Take the lan jack 3 on the vonage adaptor and plug it into the wan jack of the vonage adaptor.

This will give you the functionality of VOIP by turning the vonage adaptor into just another switch on your network.


So, I've done that.

My WRT is 172.20.0.1
I gave the RT a LAN address of 172.20.0.5
I gave the RT a WAN address of 172.20.0.3 (via static DHCP on the WRT)
I turned off DHCP on the RT
I turned off NAT on the RT
I plugged a wire from the WRT to the RT LAN
I plugged a wire from the RT LAN to the RT WAN

I can access the RT from a wireless connect on the WRT.
In the Status/Router and Status/Local Network pages on the RT, all are as expected.
On the front of the RT, LAN1, LAN3, and WAN (Internet) lights are lit.

I still do not have Phone 1 lit.

-Craig

[MisterEd]

How did you connect the WRT to the RT? From the WRT LAN, did you connect to the RT WAN or RT LAN?

Thanks,

-Craig

Like you said: LAN from your existing router to WAN on the Voipo router.

[chpalmer]

To access the RT31P2 from its WAN port...

Hook a computer to one of its LAN ports.

Go to http://192.168.15.1/Management.htm

Enable if its not already, Remote Administration:

Leave the Administration Port at 8080

On the WAN side of the router... log in with the IP of your RT31P2 WAN port...

http://(rt31p2 ip):8080




Ive found the pap2 has the dtmf falsing but have never had it on the RT31P2 yet...

[ctaranto]

Thanks for that suggestion.

I think I need my head examined. Maybe it's because I woke up early this morning and not thinking straight.

I changed my setup (again).

Cable modem -> WRT -> RT

WRT is 172.20.0.1
RT is 192.168.15.1

Connected WRT LAN to RT WAN

On the Internet Setup page, should I have "Obtain IP automatically"? If so, should it get a 172.20.0.x address?

[voip123]

Thanks. I had it set up that way, and I wasn't getting Phone 1 lit up. The RT administration was only available when a computer was plugged into the RT.

I found this on a vonage forum (who also uses an RT):
http://www.vonage-forum.com/ftopic4206.html

In there, it states:
The best thing to do if you are already using a router is to disable the vonage adaptor's ability to function as a router and just use it as a switch. To accomplish this you can follow the below directions.

1. Disable NAT and DCHP on the vonage adaptor.
2. From the line coming out of your router plug into lan jack 1 in the back of the vonage router.
2. If you have a computer plugged into the vonage adaptor plug it into lan jack 2 on the vonage adaptor.
3. Take the lan jack 3 on the vonage adaptor and plug it into the wan jack of the vonage adaptor.

This will give you the functionality of VOIP by turning the vonage adaptor into just another switch on your network.


So, I've done that.

My WRT is 172.20.0.1
I gave the RT a LAN address of 172.20.0.5
I gave the RT a WAN address of 172.20.0.3 (via static DHCP on the WRT)
I turned off DHCP on the RT
I turned off NAT on the RT
I plugged a wire from the WRT to the RT LAN
I plugged a wire from the RT LAN to the RT WAN

I can access the RT from a wireless connect on the WRT.
In the Status/Router and Status/Local Network pages on the RT, all are as expected.
On the front of the RT, LAN1, LAN3, and WAN (Internet) lights are lit.

I still do not have Phone 1 lit.

-Craig

Access to your WRT router:
Click on the status tab (the right most on the top), and then "Local network", and then click on the "DHCP Client Table" button.

Post here, tell us what you get?

[chpalmer]

WRT is 172.20.0.1
RT is 192.168.15.1

Connected WRT LAN to RT WAN

On the Internet Setup page, should I have "Obtain IP automatically"? If so, should it get a 172.20.0.x address?

Yes it would.

Up to you whether or not you use DHCP but finding the unit to sign into would be easier if it were static...

[voip123]

Thanks for that suggestion.

I think I need my head examined. Maybe it's because I woke up early this morning and not thinking straight.

I changed my setup (again).

Cable modem -> WRT -> RT

WRT is 172.20.0.1
RT is 192.168.15.1

Connected WRT LAN to RT WAN

On the Internet Setup page, should I have "Obtain IP automatically"? If so, should it get a 172.20.0.x address?

It is not going to work based on what the IPs.

Change you RT IP to 172.20.0.118. It should work.

192.168.15.1 is default gateway of the RT. It is not in the network of the IP 172.20.0.1 belongs to.

[ctaranto]

Access to your WRT router:
Click on the status tab (the right most on the top), and then "Local network", and then click on the "DHCP Client Table" button.

Post here, tell us what you get?

I'm running Tomato, so I don't know what info you're asking for.

Do you want the Static DHCP list, or the list of connected devices?

/c

[ctaranto]

It is not going to work based on what the IPs.

Change you RT IP to 172.20.0.118. It should work.

192.168.15.1 is default gateway of the RT. It is not in the network of the IP 172.20.0.1 belongs to.

So on Setup/Basic Setup, the "Local IP Address" should be a 172.20.0.x?

And Internet Setup should be "Obtain an IP automatically"?

I can put the RT into the 172.20.0.x range when it's connected to the WRT in a LAN to WAN connection?

Thanks,

/c

[ctaranto]

I have remote management working. I have set static DHCP in the WRT to give the RT WAN a 172.20.0.103 address.

I have the Local IP on the RT set at 172.20.0.118.

When I'm hard wired to the RT, I have to manually give the laptop a 172.20.0.104 address. I use a netmask of 255.255.255.0, and gateway and DNS of 172.20.0.118.

I can't ping 172.20.0.1 from that laptop. This is probably why I'm not connecting to the VOIPo servers.

I tried enabling DHCP on the RT, but the laptop never gets an address (I started the IPs at 200 (outside what the DHCP the WRT provides).

What am I missing?

Thanks,

/c

[voip123]

I'm running Tomato, so I don't know what info you're asking for.

Do you want the Static DHCP list, or the list of connected devices?

/c

Check out the attachment RT31P2.pdf. Can you setup your RT just like that?

[voip123]

I have remote management working. I have set static DHCP in the WRT to give the RT WAN a 172.20.0.103 address.

I have the Local IP on the RT set at 172.20.0.118.

When I'm hard wired to the RT, I have to manually give the laptop a 172.20.0.104 address. I use a netmask of 255.255.255.0, and gateway and DNS of 172.20.0.104.

I can't ping 172.20.0.1 from that laptop. This is probably why I'm not connecting to the VOIPo servers.

I tried enabling DHCP on the RT, but the laptop never gets an address (I started the IPs at 200 (outside what the DHCP the WRT provides).

What am I missing?

Thanks,

/c

1) you can only assign EITHER DHCP OR STATIC. You can not do both at the same time.

2) DNS is wrong. If you are using AT&T Yahoo DSL, you should use:
DNS1: 68.94.156.1
DNs2: 1561.164.8.201

[ctaranto]

Check out the attachment RT31P2.pdf. Can you setup your RT just like that?

I changed the setting to match the pdf. But the laptop isn't getting an IP from the RT.

/c

[ctaranto]

1) you can only assign EITHER DHCP OR STATIC. You can not do both at the same time.

2) DNS is wrong. If you are using AT&T Yahoo DSL, you should use:
DNS1: 68.94.156.1
DNs2: 1561.164.8.201

I know it's DHCP or Static. In the WRT, I can assign "Static DHCP", meaning it gives the same IP address every time based on a MAC address.

I'm using Comcast. I got the DNS values from the WRT and put them into the RT.

/c

[voip123]

I changed the setting to match the pdf. But the laptop isn't getting an IP from the RT.

/c

How do you setup your laptop? DHCP or STATIC?

Open a dos command prompt:

run the command: ipconfig /all

post here.

[ctaranto]

How do you setup your laptop? DHCP or STATIC?

Open a dos command prompt:

run the command: ipconfig /all

post here.

I have two laptops. One is running XP, but only has wireless (no driver for the internal wired port). The other is running Ubuntu. It's set up for DHCP (and works fine at work).

/c

[ctaranto]

Gimme a few mins. I have an old laptop sitting around that has XP and a working ether port (i hope). Booting it now...

/c

[voip123]

I have two laptops. One is running XP, but only has wireless (no driver for the internal wired port). The other is running Ubuntu. It's set up for DHCP (and works fine at work).

/c

Let's first forget about the liunx machine, focus on the XP one. Just connect the XP one to RT. then run the ipconfig /all.

[ctaranto]

Let's first forget about the liunx machine, focus on the XP one. Just connect the XP one to RT. then run the ipconfig /all.

The RT, not being wireless, can't be connected to it. There isn't a driver for the wired port on the laptop. The other (3rd) laptop is booted. Trying now...

/c

[ctaranto]

The XP laptop isn't getting an IP, either.

ipconfig /all shows

dhcp enabled: Yes
autoconfiguration enabled: Yes
IP Address: 0.0.0.0
Subnet: 0.0.0.0
Default gateway: <blank>
DHCP Server: 255.255.255.255

/c

[voip123]

the rt, not being wireless, can't be connected to it. There isn't a driver for the wired port on the laptop. The other (3rd) laptop is booted. Trying now...

/c

you must use cable to connect laptop and rt

[ctaranto]

Found the problem. I had turned NAT off in my experiment with the "vonage" setup I posted earlier. I turned it back on, and now DHCP works.

The laptop hardwired to the RT can now see the internet.

Now, to get Phone 1 lit up...

/c

[ctaranto]

Do I forward ports from the WRT to the 192 or 172 address?

/c

[voip123]

Found the problem. I had turned NAT off in my experiment with the "vonage" setup I posted earlier. I turned it back on, and now DHCP works.

The laptop hardwired to the RT can now see the internet.

Now, to get Phone 1 lit up...

/c

Glad you make it work.

[ctaranto]

Glad you make it work.

Thanks for all the help. You guys are great.

/c

[Russell]

Thanks for that suggestion.

I think I need my head examined. Maybe it's because I woke up early this morning and not thinking straight.

I changed my setup (again).

Cable modem -> WRT -> RT

WRT is 172.20.0.1
RT is 192.168.15.1

Connected WRT LAN to RT WAN

On the Internet Setup page, should I have "Obtain IP automatically"? If so, should it get a 172.20.0.x address?

Each router has a LAN side and a WAN side. The RT's 192.168.15.1 is the address on the LAN side. Yes, you need to "Obtain IP automatically" for the RT and setup the WRT to do DHCP. The RT's WAN address will be in the same subnet as the WRT's LAN side. In future posts specify whether you're listing a WAN or a LAN address for the device, which will be helpful to us readers. And, yes, your Cable modem -> WRT -> RT config is correct.

[Russell]

Do I forward ports from the WRT to the 192 or 172 address?

/c
If you need to forward ports you'd you'll be forwarding from the WRT to whatever address the WRT has assigned the RT (i.e. the RT's WAN address). Also see my previous post.

[ctaranto]

If you need to forward ports you'd you'll be forwarding from the WRT to whatever address the WRT has assigned the RT (i.e. the RT's WAN address). Also see my previous post.

Under voip123's recommendation, I statically set the WAN side of the RT to 172.20.0.118, so I forwarded that IP in the WRT.

I still don't have Phone 1 lit up. I filed a support ticket last night about this but haven't heard back. Maybe support doesn't work on the weekends?

Thanks again...

-Craig

[Russell]

Under voip123's recommendation, I statically set the WAN side of the RT to 172.20.0.118, so I forwarded that IP in the WRT.

I still don't have Phone 1 lit up. I filed a support ticket last night about this but haven't heard back. Maybe support doesn't work on the weekends?

Thanks again...

-Craig
To be honest, I've don't remember all the details and what you've tried from your postings in this long thread.

If get your RT to obtain an IP address automatically and directly attach it to the cable modem does Line 1 light up? If yes, I'd say the problem is at your end; if no, it's possibly not at your end.

[MisterEd]

Can you please clarify something. You have a working XP computer that can get on the internet, right? WHAT IP ADDRESS is that COMPUTER getting from your WRT? Forget the Voipo device for the moment. You keep saying 172. Most Linksys WRT routers DHCP scope is in the 192.168 range. Just look at your internet functioning XP COMPUTER not your router.

Right click on Nework Places
LEFT CLICK on PROPERTIES
Right Click on LOCAL AREA CONNECTION
LEFT click on STATUS
Then click on the SUPPORT TAB on top.

What is that IP?

[MisterEd]

Here is even an easier test:

Make sure your VOIPO is set back to DHCP on the WAN side.
Power off your cable/dsl modem.
REMOVE your WRT.

Plug the cable that went into your WRT into the VOIPO WAN port. DON'T ATTACH ANYTHING ELSE.

All you have now is CABLE MODEM into VOIPO WAN port. No computers, no phones.

Power up CABLE MODEM
Power up VOIPO

Does your phone work?

If not, bad Voipo
If so misconfigured WRT router

(This is all assuming you didn't mess up the WAN settings on the Voipo device).

[ctaranto]

Here is even an easier test:

Make sure your VOIPO is set back to DHCP on the WAN side.
Power off your cable/dsl modem.
REMOVE your WRT.

Plug the cable that went into your WRT into the VOIPO WAN port. DON'T ATTACH ANYTHING ELSE.

All you have now is CABLE MODEM into VOIPO WAN port. No computers, no phones.

Power up CABLE MODEM
Power up VOIPO

Does your phone work?

If not, bad Voipo
If so misconfigured WRT router

(This is all assuming you didn't mess up the WAN settings on the Voipo device).

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

[chpalmer]

pass= voipoadmin ?

[ctaranto]

pass= voipoadmin ?

Tried that on the advice of support and it didn't work (but thanks!).

Problem solved. Apparently hitting the "reset" button on the RT resets the provisioning, so the RT wasn't provisioning properly. Support gave me the right settings, I put it in, and viola. Everything works, and Phone 1 is lit.

Now I can go back and try to optimize the network in my environment.

Thanks to all of you for chipping in and helping me out. I hope I can return the favor to a new member soon.

-Craig

[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.

[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... ;)

[MisterEd]

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.

Yes, I realize that, but the thread read like "who's on first and what's on second" and I didn't see anywhere where he changed the router default (and have no idea WHY anyone does that on the LAN side as it makes no difference) but obviously he did. Also I now see he is plugging his laptop into the VOIPO device which gave him the 192 address which confused me as well. The thread had my head spinning with WRT RT WRT RT :). I prefer "voipo device" and "WRT router" just for clarity (I did tech support training for an ISP and we preached clarity as the key with end users) :).

Anyway, I should have kept my mouth, er, keyboard, shut. :)

[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