@wallabybob: If by "default DNS" you mean the DNS your ISP assigns then the most effective way (assuming your WAN link gets an IP address by DHCP) is to check the box. If your WAN link doesn't get its IP address by DHCP and you want your ISP's DNS server then contact the ISP to get the DNS servers address(es) (may be in ISP configuration help page) and then specify the DNS server(s) by System -> General Setup DNS Servers. If you are asking how to set this when you only have WAN access to pfSense and can't ssh in, then sorry, I don't know. You haven't specified if you want LAN systems to use the pfSense DNS forwarder (I presume you do) or you want the "default" DNS to be propagated to the LAN clients. Yeah default dns I mean the one my ISP assigns. And yes I use the DNS forwarder. And yeah I only have lan access to the web gui.

@Cry: You can only have a single default gateway, and that's always going to be on your external interface.  What you want to do is to configure static routes to your internal networks. k - what i ended up doing was giving the wan interface an ip and set the gateway on that to the one i wanted to set lan interface to.

If you mean access to the web interface, it's been covered (lots) before, but… Add a firewall rule destination WAN address port 443 (you have switched to https, right?) Better still is to limit the source to an alias containing all the ips/networks you connect from.

@kamil.maciejewski: Yes, I know this all, but the problem is, that this is a production area, it needs to work all the time and, what's even worse - I'm only part time working in this company, so i need to be able to change the settings remote. I'll separate the networks when it will work without any problems. For now I can only create new subnet and start moving IP's there. If it only fix the network lost problem I'm not quite sure you get it: What you are doing is wrong and will not work properly. Nothing anyone can tell you will make it work properly other than correctly wiring the network to separate switches. Edit: Locked thread.

wrong forum.

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.