bump  :-[

The picture also also handy for:

Easy identification of a system, e.g. picture of the building its in, or the rack, or a graphic depiction of its name. Fun, but not entirely useless. (If you named your firewall after a character from a myth/novel/comic/tv/movie, why not have a picture of it?) A large image warning other admins to not touch a production unit or they'll be <insert creative="" punishment="" here="">. A company logo, or customer logo

As for it spilling outside the widget, that's probably just a CSS issue in that particular theme if the others are all OK. It might be worth opening a bug report for that if others can reproduce it.</insert>

This is most likely the same issue I had. Try the patch from this thread: http://forum.pfsense.org/index.php/topic,56367.msg301169.html#msg301169

I have problem with the Beta 2.1 dated 5/22 It would block my web also .. had to remove it. I did find out that I could go to the keyboard for the pfsense and redo the LAN IP Option #2 and then I would have net for few seconds or minute.. long enough to get the PFSENSE firewall page up and disable snort.

I got it to work in 1 beta 2.1 after I did find /* | grep -i snort | xargs rm -rv to remove it all and reinstalled it making sure the option to save settings was unchecked first

going to try in 2.1 RC see if I can get running

I'm using an Embedded version with ALIX, same problem! Sometimes the Web GUI only back to normal with a restart (11 option).

@drzoidberg33:

I am having a similar issue with todays snapshot. I have a multiwan setup, with 2.0.3 I can just deselect the "Default gateway" option on both interfaces but I cannot do this on 2.1. This results in my failover rules to fail as it always defaults to one of the gateways.

Is there a new way of doing WAN failover or is this a bug? To reproduce you just need to have two gateways and then try to untick "Default gateway" on both of them.

I found the "Allow default gateway switching" in Advance Setup -> Misc. This seems to have fixed the problem with the failover rules.

Thanks, patch works for me. However I don't recall this happening on 2.0.3.

Maybe you can add a serial to usb adapter. When building Pfsense routers I try to choose motherboards that have a serial port just for situations like this.

Opps, typing error, that pfSense 2.0.X-RELEASE  ;D

Using command vmstat -i, show irq16: ste0. ste0 use for TP-Link 10/100M Network Card (IT-P), This interface is functioning.

I, try to disabling unused devices and see the result tomorrow.

Thank you.

Could we have an option to turn off IPv6 support?
pfSense does not handle IPv6 DNSSEC queries if they get fragmented (i.e. when using a tunnel broker for IPv6 access):

May 24 13:54:27 vpn pf: 00:01:05.283725 rule 5/0(match): block in on gif0: (hlim 59, next-header Fragment (44) payload length: 1240) 2001:500:1b::1 > 2001:xxxx:xxxx:xxxx::2: frag (0x82af3ff7:0|1232) 53 > 39396: 34110*- 7/0/1 info. DNSKEY[|domain] May 24 13:54:27 vpn pf: 00:00:00.000123 rule 5/0(match): block in on gif0: (hlim 59, next-header Fragment (44) payload length: 413) 2001:500:1b::1 > 2001:xxxx:xxxx:xxxx::2: frag (0x82af3ff7:1232|405)

btw, the first line looks odd in when you view it in the web gui. It only shows 53 and 39396 as source and destination, not the IPs.

Thanks for the reply, I was getting nervous I wasn't going to hear back.

I had not enabled DHCP spoofing. I tried enabling it with both the virtio drivers and e1000 drivers and that didn't help the situation. Below is a copy of my NIC configurations in SmartOS for pfSense VMs:

pf1

[  {    "interface": "net0",    "mac": "82:cb:d4:bd:cd:65",    "nic_tag": "external",    "gateway": "76.x.xx.193",    "primary": true,    "ip": "76.x.xx.195",    "netmask": "255.255.255.248",    "model": "e1000",    "allow_dhcp_spoofing": true,    "allow_ip_spoofing": true,    "allow_unfiltered_promisc": true  },  {    "interface": "net1",    "mac": "e2:9d:bf:c3:3e:1e",    "nic_tag": "admin",    "ip": "10.0.0.2",    "netmask": "255.0.0.0",    "model": "e1000",    "allow_dhcp_spoofing": true,    "allow_ip_spoofing": true,    "allow_unfiltered_promisc": true  } ]

pf2

   {      "interface": "net0",      "mac": "32:9a:35:c7:e2:8b",      "nic_tag": "admin",      "gateway": "76.x.x.193",      "primary": true,      "ip": "76.x.x.196",      "netmask": "255.255.255.248",      "model": "e1000",      "allow_dhcp_spoofing": true,      "allow_ip_spoofing": true,      "allow_unfiltered_promisc": true    },    {      "interface": "net1",      "mac": "62:f1:0c:32:7c:07",      "nic_tag": "internal",      "ip": "10.0.0.3",      "netmask": "255.0.0.0",      "model": "e1000",      "allow_dhcp_spoofing": true,      "allow_ip_spoofing": true,      "allow_unfiltered_promisc": true    }

On a related note, one can check the pfsense git repository and if there are only updates to pfSense php / bash scripts i.e. no new binaries, one can use GIT to sync to the latest code. That procedure typically takes only a few seconds, even on slow links.

http://doc.pfsense.org/index.php/Updating_pfSense_code_between_snapshots

That's how I update my pfsense 2.1 several times every day.

Please post the output of pfSense shell commands```
ifconfig ; pciconf -l -v

PERHAPS your LAN interface is running at 1Gbps and there isn't quite enough PCI bus bandwidth for both interfaces, the NIC reports an error and the driver cycles the link to recover. I wonder what would happen if you forced the LAN interface to 100Mbps. Perhaps enabling flow control on the link would help but the FreeBSD man page gives no clue on how to enable flow control or read its state.

I have the same issue, and have for a long time, always figured it was something about my modem (this is a test site for my ISP, so lucky me gets to deal with multi-gateway setups…) but this is the second time something slightly different has happened and I decided to check here to see that I am not the only one with this issue.

1: WAN Gateway goes down
2: PFSense WAN side looses address
3: Wan Gateway comes back up
4: PFSense keeps rebooting the WAN NIC over and over for no reason at all.

Now, I have a Dell 1550, not using any extra add-on nic, 4GB RAM, 73GB SCSI disk.   I also use SQUID on this install, eventually if I let this issue go on long enough something with one of the packages freaks out, and consumes disk space...  Remember, this is only the second time this issue in particular has happened to me in regards of disk space, the WAN down is almost a daily thing.  You may think, oh, a log file is consuming a GB or so of extra data, no, when the system finally gets to a point, it will go from ~15% of used disk space to 90% or more of used space in a matter of hours (only took my 8 hours of sleeping today).  At this point, packages fail to launch, and the only thing working anymore honestly is the GUI, I am essentially forced into a re-install as I can't find what has consumed all the disk space.

One thing I have noticed, when my WAN goes down due to a link outage for any period of time, I tend to get a crash report, but can't send the crash report in, because the link is down, upon a reboot, well, I don't see options to send crash reports in...  Not even sure if those are checked on anyways. xD

Sys Log

May 22 00:52:07 kernel: arpresolve: can't allocate llinfo for 100.73.71.217 May 22 00:52:06 dhcp6c[46100]: check_exit: exiting May 22 00:52:05 php: : Accept router advertisements on interface fxp0 May 22 00:52:05 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf fxp0 > /tmp/fxp0_output 2> /tmp/fxp0_error_output' returned exit code '15', the output was '' May 22 00:52:05 php: : DEVD Ethernet detached event for wan May 22 00:52:05 check_reload_status: Linkup starting fxp0 May 22 00:52:05 kernel: fxp0: link state changed to UP May 22 00:52:04 kernel: arpresolve: can't allocate llinfo for 100.73.71.217 May 22 00:52:03 kernel: fxp0: link state changed to DOWN May 22 00:52:03 check_reload_status: Linkup starting fxp0 May 22 00:52:03 dhcp6c[46058]: client6_init: skip opening control port May 22 00:52:03 dhcp6c[46058]: client6_init: failed initialize control message authentication May 22 00:52:03 dhcp6c[46058]: dhcp6_ctl_authinit: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory May 22 00:52:03 dhcp6c[45512]: check_exit: exiting May 22 00:52:03 dhcp6c[45242]: client6_init: skip opening control port May 22 00:52:03 dhcp6c[45242]: client6_init: failed initialize control message authentication May 22 00:52:03 dhcp6c[45242]: dhcp6_ctl_authinit: failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory May 22 00:52:03 php: : HOTPLUG: Configuring interface wan May 22 00:52:03 kernel: arpresolve: can't allocate llinfo for 100.73.71.217 May 22 00:52:03 php: : DEVD Ethernet attached event for wan May 22 00:52:01 dhcp6c[33259]: client6_recvadvert: XID mismatch May 22 00:52:01 php: : Accept router advertisements on interface fxp0 May 22 00:52:01 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf fxp0 > /tmp/fxp0_output 2> /tmp/fxp0_error_output' returned exit code '15', the output was '' May 22 00:52:01 kernel: arpresolve: can't allocate llinfo for 100.73.71.217 May 22 00:52:01 php: : DEVD Ethernet detached event for wan May 22 00:52:00 kernel: fxp0: link state changed to UP May 22 00:52:00 check_reload_status: Linkup starting fxp0 May 22 00:52:00 dhcp6c[33259]: client6_recvadvert: XID mismatch

booting from a USB drive probably?
http://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_from_USB

jigglywiggly probably the interface you are on is not reporting correctly the bandwidth.
Which error you see and what type of interface you have?

Normally it would be better to put you wan bandwidth there since that will make code better for your interface.

Yes, but this is different case…
There are a lot of reports lately about FXP NICs and not all of them have bad hardware...
For bad HW I don`t need to call ISP, I can determine that by myself...