Hello, Yes, the system is pfsense 1.2.2 the rule for smtp was added to the wan interface (em1). pfctl -vvs rules reports this @62 block drop in log quick on em1 from bogons:50to any label "block bogon networks from wan"                      [ Evaluations: 369980    Packets: 557       Bytes: 27864       States: 0     ]                                      [ Inserted: uid 0 pid 48699 ] running /etc/rc.update_bogons.sh seems to solve the issue (outdated bogons definitions) thanks giuliano</bogons:50>

Sorted my problem, had to set MTU to 1400!

Hi guys, Well I've managed to sort the problem! it was the MTU! set it to 1400 and it works like a dream now. Thanks

I have 7 Polycom IP650's at one location behind a pfSense box.  We're not using Asterisk (using OnSip/Junction Networks) but I had the same problem.  I tried siproxd and couldn't get it to work.  After reading every post here concerning SIP (at least 3 times) I finally started with a fresh install and enabled Advanced Outbound NAT, made a rule for the VoIP VLAN out (separate interface from LAN), and rebooted.  Every phone came up and has been working great since.  I've never used Asterisk (been wanting to check it out in my "spare" time), but OnSip runs everything by RFC standards, no extra bells and whistles unless it's a standard.  I would "assume" that Asterisk works the same way. Of course, the great thing about standards is there are so many to choose from . . .  ;)

Faulty hardware.

We are not encrypting anything.  It's just regular ol PPPoE.

take it to someone who has a computer with a serial port, a friend or relative?

You have a rule allowing any OPT1 subnet traffic out, you also need to allow traffic from LAN to OPT1, that should require a second firewall rule.

I will have to mess with trying to find a way to block that ping.  I use VMware server and the way my server is configured pfSense has 100% unfiltered control over that network card and windows does not really even see it as a working card.  The MAC address is correct and I am still scratching my head over here :( The only thing that I could try is to match the hardware MAC (true mac address) with the virtual mac address since pfSense does not share the interface with any other OS.  But, seriously I want to choke the tech support people because it worked perfect until they changed the firmware to do something funky at startup… no fun :(

Ok, I've got it working.  It ended up not being a NAT issue after all, it was the way I was setting up my VLAN3 interface. In the "IP Configuration" section I had entered the pfSense WAN address in the "Gateway" field.  As it turns out I needed to leave that field blank to allow traffic in and out. See the attached image details… Thanks again for helping me out. [image: 6.jpg] [image: 6.jpg_thumb]

here we go again. the HDD in my pfsense pc died and so i had to do a clean installation. i've used the latest RC available on the homepage, and found myselfe encountering the same problem again. everytime the ADSL modem is restarted (it stays off for 1 minute), pfsense simply does not reconnect. even if i hit the "connect" button, it just won't conect. (using PPPoE) i must reboot the pfsense pc to get it to connect again. also tried several snapshots, all have the same problem. i am curently running: pfSense-Full-Update-1.2.3-20090918-0504 to work around the issue i am tryinto to setup a cronjob to reboot pfsense right after i restart the modem. not much success yet. :(

@jimp: Actually the network that out PPPoE rides over to customers is AT&T and locally here it works the same way for their customers, though it may vary by region. I'm in GA in the old Bellsouth territory, so that probably makes a difference. I remember when I had Qwest in Seattle they used PPPoE but routed the statics to you like a proper ISP should. I called 'em just to verify I wasn't going crazy…and I'm not.

2.0 supports interface grouping via lagg. http://www.freebsd.org/cgi/man.cgi?query=lagg&apropos=0&sektion=0&manpath=FreeBSD+7.2-RELEASE&format=html I would suggest grabbing an Alpha snapshot if you want to experiment with it. The underlying lagg features should be available in the 1.2.3 snaps, so you might be able to hack something together using the shell, scripts, or something. I haven't tried that, and it would be unsupported, but it might be an option if the 2.0 snaps seem too volatile for your needs.

@jimp: aeropilot is on the right track. The easiest way to turn a wireless router into a bridge is to turn off DHCP, change its LAN IP to something that doesn't conflict with pfSense, and then only plug into the LAN side, not the Internet/WAN port of the wireless router. Why risk bricking the wireless router by reflashing with a new OS when it's that easy? http://doc.pfsense.org/index.php/Use_an_existing_wireless_router_with_pfSense But my setting is WAN - > ADSL <wan>->(LAN) pfsense(Wireless Nic)  -> WRT54G(v5) -> (Wireless nic) Family member 1)Will it possible to connect pfsense to WRT54G through Wireless nic ?? 2)Shall i use ADSL modem as PPOE(dialup itself) to establish connection ? 3)Traffic will pass direct from ADSL through a LAN cable to Pfsense (Virtual instance) From pfSense to WRT54G is using a Wireless nic to make connect to WRT54G. How to define WAN and LAN IP from pfsense if my above configuration is possible. Is there any component which is redudant or missing in my configuration ?? I also using my pfsense (WinXP) to browse net will it possible ??</wan>

You'll either have to use the developer version that matches the version of pfSense you're using, or take the kernel modules from a matching FreeBSD kernel version.