Re: How I hooked up VOIPo
Quote:
Originally Posted by
ctaranto
With modem -> router -> ATA, how does one get single NAT? Turning NAT off on the RT makes it not get Phone 1 lit.
And where are my "4 NATs"? Not knowing what happens internally, I believe that having the RT entirely on the 172.20.0 network, it's not doing NAT at all. I thought NAT happens when going from 172 to 192, or public to private.
-Craig
Assuming your modem is bridged, there's only one IP change from your public IP through your DHCP router to ATA ......thus single NAT.
If your ATA is attached directly to a bridged modem, there's no NAT at all since the ATA is seeing your public IP. Only the device's attached to the LAN port of the RT31P2 experience NAT.
My apologies, it looks like there is less than 4 NAT's since you turned off the DHCP server in the RT31P2. I'd have to study your setup a little closer to get a better idea of how many NAT's are going on.
There's still a problem somewhere in your setup if you are having to go to this trouble.
Re: How I hooked up VOIPo
Quote:
Originally Posted by
tritch
Assuming your modem is bridged, there's only one IP change from your public IP through your DHCP router to ATA ......thus single NAT.
If your ATA is attached directly to a bridged modem, there's no NAT at all since the ATA is seeing your public IP. Only the device's attached to the LAN port of the RT31P2 experience NAT.
My apologies, it looks like there is less than 4 NAT's since you turned off the DHCP server in the RT31P2. I'd have to study your setup a little closer to get a better idea of how many NAT's are going on.
There's still a problem somewhere in your setup if you are having to go to this trouble.
Having the ATA directly attached to the modem is a no-go. The RT is an insecure device - it's firewall, in a single word, sucks. When I had it directly connected, a run of ShieldsUp at grc.com showed ports were closed, not stealth. And a few ports were open.
Having the ATA behind the WRT caused reauth issues when the WRT was directly connected to the WAN port of the RT.
Which brings me to the topology in the first post of this thread.
-Craig
Re: How I hooked up VOIPo
This is strange..
I have my ATA always behind the router...firewall off..NAT on..no port forwarding and no STUN and don't experience these problems..
Re: How I hooked up VOIPo
Quote:
Originally Posted by
burris
This is strange..
I have my ATA always behind the router...firewall off..NAT on..no port forwarding and no STUN and don't experience these problems..
Firewall off on the router? That may explain a bit. I refuse to run my network that way.
Take a look at grc.com, go to ShieldsUp, and run a common port scan.
-Craig
Re: How I hooked up VOIPo
Not to start anything here but... http://web.archive.org/web/200412121.../grcsucks.com/
Is the Wan of the RT31P2 using dhcp to get its address by chance?
Your WRT has nothing in the "gateway" portion of its DHCP server according to your post. This should be its lan address. 172.20.0.1
Id also turn off dns forwarder if its on. I believe some routers have problems passing dns queries between the "client" and the internet when the forwarder is on... worth testing anyway.
Re: How I hooked up VOIPo
Quote:
Originally Posted by
ctaranto
Having the ATA directly attached to the modem is a no-go. The RT is an insecure device - it's firewall, in a single word, sucks. When I had it directly connected, a run of ShieldsUp at grc.com showed ports were closed, not stealth. And a few ports were open.
Exactly, that's the way the RT31P2 should behave ahead of your router.....allowing it to work more openly with the Internet.
In this scenario, your router is still providing the SPI firewall and protecting your internal network. Why do you really care about the RT's poor firewall ability which is upstream of your router. If the ATA was that insecure or easily hackable, Voipo would not prefer that you hook it up that way to begin with. However, Voipo does prefer it this way just to avoid SPI/NAT issues it encounters with some of its customers.
Quote:
Originally Posted by
ctaranto
Having the ATA behind the WRT caused reauth issues when the WRT was directly connected to the WAN port of the RT.
Once again, the fact you are having issues with it hooked up this way is indicative of something else being wrong. No one should have to hook up this way in your topology to get to work correctly.
I took another look at your setup and you have at least double NAT or more going on. Per your topology, your router's DHCP is enabled with a starting IP pool address of 172.20.0.100, but I noticed your LAN and WAN IP's on the RT is 172.20.0.2 and 172.20.0.3 respectively. This tells me that more NAT is going on in the picture here because if you truly had the RT's DHCP server disabled then the LAN ports on the RT would act like a switch instead of a router and pull it's IP addresses from your WRT IP pool.
If it's working good for you this way, I really can't knock it too bad.;)
Re: How I hooked up VOIPo
Quote:
Originally Posted by
tritch
Exactly, that's the way the RT31P2 should behave ahead of your router.....allowing it to work more openly with the Internet.
In this scenario, your router is still providing the SPI firewall and protecting your internal network. Why do you really care about the RT's poor firewall ability which is upstream of your router. If the ATA was that insecure or easily hackable, Voipo would not prefer that you hook it up that way to begin with. However, Voipo does prefer it this way just to avoid SPI/NAT issues it encounters with some of its customers.
If insecure and "more openly" is synonymous, then I don't want it. :) VOIPo only needs certain ports. It shouldn't be THAT open. I actually prefer having a PAP2T, which HAS to be behind a router (that's what I had with VoicePulse). I want to mimic the topology that I had, with my WRT first in line. I also like to measure bandwidth usage and with the RT first, I can't do that.
Quote:
Originally Posted by
tritch
Once again, the fact you are having issues with it hooked up this way is indicative of something else being wrong. No one should have to hook up this way in your topology to get to work correctly.
Maybe dd-wrt and hooking it up to the WAN is good enough. I never tried that. But I far prefer Tomato, and thus far, it's working.
Quote:
Originally Posted by
tritch
I took another look at your setup and you have at least double NAT or more going on. Per your topology, your router's DHCP is enabled with a starting IP pool address of 172.20.0.100, but I noticed your LAN and WAN IP's on the RT is 172.20.0.2 and 172.20.0.3 respectively. This tells me that more NAT is going on in the picture here because if you truly had the RT's DHCP server disabled then the LAN ports on the RT would act like a switch instead of a router and pull it's IP addresses from your WRT IP pool.
The WRT's DHCP pool is .100. The RT isn't getting it's IPs from the WRT (I put them in statically), so .2 and .3 were chosen. Because an IP is outside of the DHCP realm (but inside the subnet mask), that causes NAT to be used? I didn't believe that was the case. I believe the way I've hooked it up, the RT *IS* a switch now. The only thing is the WAN port needs to be used because all voice communications goes out the WAN. DHCP is turned off on the RT, and nothing else is connected to it. I can also directly log into the RT via 172.20.0.2 (without any port numbers) while wireless connected to the WRT.
Are you suggesting that if I statically set the IPs of the RT to inside the DHCP range, I'll reduce a NAT? That doesn't quite make sense to me, but again, I'm not a network guy.
I believe (or believed) that by connecting directly to the LAN port, and putting the LAN and WAN in the same subnet, I'm *reducing* a NAT.
Quote:
Originally Posted by
tritch
If it's working good for you this way, I really can't knock it too bad.;)
I'm enjoying this conversation (please don't take it as an argument). :)
-Craig
Re: How I hooked up VOIPo
Quote:
Originally Posted by
ctaranto
If insecure and "more openly" is synonymous, then I don't want it. VOIPo only needs certain ports. It shouldn't be THAT open. I actually prefer having a PAP2T, which HAS to be behind a router (that's what I had with VoicePulse). I want to mimic the topology that I had, with my WRT first in line. I also like to measure bandwidth usage and with the RT first, I can't do that.
I don't have this setup either, but it is preferred by Voipo. It must be secure enough, otherwise you'd be hearing of more ATA's being attacked or hacked.
Quote:
Originally Posted by
ctaranto
The WRT's DHCP pool is .100. The RT isn't getting it's IPs from the WRT (I put them in statically), so .2 and .3 were chosen. Because an IP is outside of the DHCP realm (but inside the subnet mask), that causes NAT to be used? I didn't believe that was the case. I believe the way I've hooked it up, the RT *IS* a switch now. The only thing is the WAN port needs to be used because all voice communications goes out the WAN. DHCP is turned off on the RT, and nothing else is connected to it. I can also directly log into the RT via 172.20.0.2 (without any port numbers) while wireless connected to the WRT.
Ok, I stand corrected. I missed the fact you statically assigned the IP's on the RT with the same subnet.
Router setup:
IP: 172.20.0.1
Subnet: 255.255.255.0
Gateway: 0.0.0.0
DHCP enabled: starting IP pool of 172.20.0.100
RT LAN:
IP: 172.20.0.2
Subnet: 255.255.255.0
Gateway: 172.20.0.1
RT WAN:
IP: 172.20.0.3
Subnet: 255.255.255.0
Gateway: 172.20.0.1
LAN and WAN ports on the RT are set with static IP's which are on the same subnet as the router and do not automatically obtain IP's from the WRT. The RT is acting like a switch as you mentioned, so there's only a single NAT between your public IP and your RT which is good.
I do see a problem as chpalmer pointed out in his post. Your WRT's gateway should be 172.20.0.1 not 0.0.0.0 It's possible when you had the RT's WAN hooked up to the WRT's LAN that the router assigned this gateway to the RT as well. I'm assuming of course that you had the RT automatically obtain its IP address from the WRT's IP pool when you tried it before. You might want to see if that was the problem. If this resolves the issue, then you would want to reserve or assign a static IP for the RT in the router.
Re: How I hooked up VOIPo
Quote:
Originally Posted by
tritch
I don't have this setup either, but it is preferred by Voipo. It must be secure enough, otherwise you'd be hearing of more ATA's being attacked or hacked.
There were many things I didn't like about the RT being first. A few of them are:
1. The feeling I was insecure by ports not being "stealth"
2. Relying on the RT to handle all NAT. If it's NAT abilities aren't good (and it's hard to find info on this), then when using many bittorrent clients, I will see a performance hit.
3. The QoS setup in the RT is no where near as good as a WRT running Tomato.
Quote:
Originally Posted by
tritch
I do see a problem as chpalmer pointed out in his post. Your WRT's gateway should be 172.20.0.1 not 0.0.0.0 It's possible when you had the RT's WAN hooked up to the WRT's LAN that the router assigned this gateway to the RT as well. I'm assuming of course that you had the RT automatically obtain its IP address from the WRT's IP pool when you tried it before. You might want to see if that was the problem. If this resolves the issue, then you would want to reserve or assign a static IP for the RT in the router.
Interesting that the Tomato firmware doesn't even offer a "gateway" for the Router IP (maybe it assumes the Router IP as the gateway?). I don't know the effect of this setting in dd-wrt in the current topology vs. hooking directly into the WAN. I also didn't try dd-wrt and hooking directly into the WAN.
Thanks,
-Craig
