On 11/29/11 10:06 AM, Ryan Rodrigue wrote:
You are correct that these are on different subnets. Your method of
double nattng should work, but isn't the bast way to do things.
Double natting usually causes problems.
It's ugly and best avoidable if possible, and it makes troubleshooting
NAT-broken protocols not much fun, but it generally doesn't cause any
problems.
_______________________________________________
I stand corrected. I guess I could have worded that more carefully.
It did work for me for a few months and then, perhaps something changed
on the vonage box or something I did ... Anyways, went back to
192.168.100.100 LAN ---pf--- WAN dhcp ===== modem
And everything works again. A couple of pieces of good news: It was not
the hardware/Alix embedded ot Supermicro Atom and it is not my 24 port
hp procurve switch. The reason I am happy it is not the switch is
because it is slated to go on a mission critical, remote project next month!
I can understand why pfSense would freak out over double natting. The
negative is that I'll have to futz with coddling the vonage box behind
the firewall to give it BW. There was a reason I went to double natting.
Mehma
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list