I do not know why it seems to have a tunnel to itself. I do not see that in the setup.  I did finally get traffic to the 10.25.22.0 subnet and now the phone traffic is traveling thru the IPSec tunnel to the 10.25.18.0 subnet to the pbx server. I had to reboot both systems and something kicked in and now I can access the phones webgui and the phones registered with the server.

What does the systemlog say when you try to connect?

Thanks. It seems problem with my CentOS server, because when I tried to setup a Windows workstation with the IP address I stated on the OPT1 and connect it to the switch coonnected to the OPT1 interface it works. But when I tried connecting my CentOS it does not work. But at least I know that pfsense is working and my configuration is good. Now I have to deal with my CentOS server. It's kind of puzzle because when I tried to connect my CentOS server directly to my ISP switch it works, but if I connect it to the switch connected to the OPT1 interface it does not work.  ???

He means using a cellular data broadband card (like G3 or GSM) as a WAN connection. This was kicked around a while ago and there was a bounty open. The parts are slowly coming together, but I haven't heard details of a successful setup yet. It could be very handy for a backup connection when options are limited or for temporary setups (eg- construction site).

So how was your experience?

This is extremely common on modern networks as a result of Path MTU Discovery. Most TCP packets on modern networks will have the DF bit set. For example run a tcpdump -v on your network and you'll find that pretty much every TCP packet has the DF bit set. The problem is almost certainly something else.

My suggestion would be to create an opt1 interface on the pfsense box.  Call it 10.10.0.1, make your access point 10.10.0.2 or something like that.  In my experience, this setup will work with Squid transparent proxy bound to both the LAN and OPT1 interfaces.  Also, traffic between them should pass unless you block it with a rule.  If you need them bridged, that should work too.

How about this old age saying…. If it ain't broke don't fix it.

I´ve changed the kern.ipc.nmbclusters from "0" to "32768" and works fine. thanks at all, Paulo Coimbra

I have the same problem with pfsense and Comcast. I have to reboot my modem, usually works. If not sometimes reassigning the WLAN/LANS works. Best of luck.

@0tt0: @jigglywiggly: So I am a pfsense noob obviously, and I have a question why is pfsense running port 80 over the web, I want my web server running on that port. Also I port forwarded other ports and they don't work, like they respond but they arn't doing their functions like SSH, RDP, VNC. I am totally lost. Also openDNS doesn't seem to be working, it's set under the DNS, but it's not working… I am starting to dislike pfsense. The most obvious choice of port for something to be reached by a web browser is port 80, the default port for http. Otherwise you'd have to append port number to the URL when browsing, so that's the most natural way to start with for a default installation. Otherwise other people would ask the opposite question instead.. Should you want to use another port for various reasons just change it. And you probably want https anyway. Port forwarding is quite straight forward in pfSense I think. First go to "NAT" tab and enter the data and make sure it auto-adds a FW rule. Apply changes. Done. (Can't help thinking of Gordon Ramsey's way of saying it, writing that "recipe" LOL). Maybe also reset states to be sure. If you can't get that to work you may have chosen incorrect protocol or something, double check it. I'm also running OpenDNS and it's working perfectly. You should not be using "Allow DNS server list to be overridden by DHCP/PPP on WAN" obviously. You probably want to stick to it and learn how to get it to work, pfSense is probably one of the most advanced open source firewall packages in existence. When a product is so flexible and has so many options and features there's always some risk of doing things incorrectly in the beginning. Cheers, Thanks for the advice, specifically about getting OpenDNS to work. I had the check box checked that said "Allow DNS server list to be overridden by DHCP/PPP on WAN" removing it worked nicely. Danke.

Ok I sort of understand. But this brings me to antoher quesiton why wont my forwarded ports work :P I'll create another thread to ask that.