I run Celeron Coopermine ( Socket 370 ) 1000MHz… But one hour ago, I found that CPU fan have failure. Radiator was overheated and fan stops.  ( I do not have spare cpu fan for such old socket ) In that case, I decided to move on a "new" platform - Dell CPU Pentium 4 2.4GHz with 2GB RAM For now everything works fine, even with 2.1-RELEASE (i386) ( on new PC ) thanks a lot Jack

Have you tried this? set hw.clflush_disable=1 boot https://doc.pfsense.org/index.php/Boot_Troubleshooting#Vendor-Specific_Issues

SOLVED….The Motorola cable modem configuration was reloaded and upgraded from 3.3.1 to 3.5.8 and finally replaced with a Ubee DDW3611.  Replacing the modem solved the problem with the intermittent incoming/ARP issues. So the Pro 1000VT is now working.  I never determined why the firewall ARP replies wouldn't satisfy the old modem.  It might have been a CM issue or MSO problem that was cleared by replacing the modem. Thanks for all the help.

Curious to what "all" your refer to that talk about 2 lan interfaces with 1 wan interface..  its a router/firewall - your going to want 2 interfaces or how do you route between anything ;)  Or firewall between anything? ;) You could have 3 sure, you could have 6, etc.  Where you have multiple WAN, and multiple LAN, etc. If you put a gateway on the interface then pfsense would treat that as a WAN interface - so this would be connected to whatever network you have a gateway to get to other networks (internet normally)  Your lan interface as pfsense would see it would be where your clients connect that want to get through to the networks on the other side of pfsense, ie pfsense's wan. Sure you could use a captive portal to let them out or not, etc.

wow many many thx mate this now enlighten me.

Check your DNS settings also (System > General) and make sure you don't have something there tied to the LAN interface

This was a very frustrating bug. Thanks to every here for sorting it out. @phil.davis: /etc/rc.update_bogons.sh IPv4: egrep -v "^192.168.0.0/16|^172.16.0.0/12|^10.0.0.0/8" /tmp/bogons > /etc/bogons IPv6: egrep -iv "^fc00::/7" /tmp/bogonsv6 > /etc/bogonsv6 http://tools.ietf.org/html/rfc5735 0.0.0.0/8 - Addresses in this block refer to source hosts on "this" network.  Address 0.0.0.0/32 may be used as a source address for this host on this network; other addresses within 0.0.0.0/8 may be used to refer to specified hosts on this network ([RFC1122], Section 3.2.1.3). Protocols like DHCP (where the source [client] is trying to find out its IP address) need to put something in the source IP field. 0.0.0.0 is a good choice. So, there is an argument that 0.0.0.0/8 (or at least some of it) is "link-local" IPv4 address space. So it is not appropriate to consider it "bogon", as it is used legitimately on any local link by whatever protocol has the need.

I'm really unsure then which IP is being used… The issue may be around the wireless adapter I'm using. It's a RNX-N600UBE using the RT3572 chipset plugged-in via USB. It's using the run driver which I load through the boot.conf file I'll disable it and see if the crashes still occur.

What VM software are you attempting to use? What host OS on the computer? What is your goal with this, just to use pfsense to protect and give VPN access to one computer? Are there other computers on the network?

There was a time during 2.1 development when the list showed all addresses (including really external ones) and at that time the Filter [All|Local|Remote] dropdown was added so the user could choose what to display. Then, for whatever reason in some forum discussion… the behaviour was changed back to displaying just local addresses. But I suspect that a "local address" is one on a directly-connected network. I am not familiar with the previous behaviour, but I guess it used to show entries for other bits of private address space that were behind another router on LAN, or across a VPN link or...? I think the ability to show all, regardless of being direct-connected, private intranet or public internet, then filter it, was good. I think it was the "rate" source/binary that has to be modified so it actually spits out all the data. Then the PHP can filter for display as selected by the user.

Then you may need pkg_add, but you would not touch or change anything in the GUI to add those.

It looks like that is actually a sysctl rather than a loader tunable, as such you should be able to add it to the table in System: Advanced: System Tunables: This will mean it gets added to the config file and will survive a firmware update. Steve

I have an ath0 WiFi running inside an Alix2D13 on 2.1-RELEASE at a remote site. It ran various 2.1-RCn and was updated remotely a few times and it has been working. The settings (with SSID and password changed) are in the attached. At that site the power goes off a lot, and it comes back [both power and WiFi :) ] Maybe that will give you some confidence? [image: WiFiA.png] [image: WiFiA.png_thumb] [image: WiFiB.png] [image: WiFiB.png_thumb] [image: WiFiC.png] [image: WiFiC.png_thumb] [image: WiFiD.png] [image: WiFiD.png_thumb]

Hmm… Trying to mount root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted <118>Configuring crash dumps... <118>Using /dev/ad4s1b for dump device. <118>Mounting filesystems... WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck <118>mount: <118>/dev/ad4s1a <118>: <118>Operation not permitted <118>** /dev/ad4s1a <118>** Last Mounted on / <118>** Root file system <118>** Phase 1 - Check Blocks and Sizes <118>PARTIALLY TRUNCATED INODE I=37000242 <118>SALVAGE? yes

Well, today I'm still having the same problem after the clean install and so I tried the sugested solutions withought luck. One thin I noticied is that when the wan interface falls the "Gateway Monitoring Daemon" also stops and could not be started, on the log it says "ALARM: WAN_PPPOE(192.168.153.1) *** down ***" then the problem is that the router can't bring up the wan after a failure. Wel I don't have the necesary knowledge to know what's happening so…..

Aah, very good question. That motherboard has the idiotic Marvell controller, which doesn't work even under windows. I don't know of the top of my head, which SATA ports I have used, but I would guess I connected the HDD to the SATA3 Marvell port… The following output perhaps confirms that? (mind you, I'm running in IDE mode at the moment) $ atacontrol list ATA channel 0:     Master:  ad0 <hitachi hts542580k9sa00="" bbbzc3hp="">SATA revision 1.x     Slave:      no device present ATA channel 1:     Master:      no device present     Slave:      no device present ATA channel 2:     Master: acd0 <tsstcorp cddvdw="" sh-222ab="" sb01="">SATA revision 1.x     Slave:      no device present ATA channel 3:     Master:      no device present     Slave:      no device present</tsstcorp></hitachi>

You just need to assign/configure the WAN, to be able to login in to the Web Interface from the WAN side, and finish the configuration… i have done this way to use a PCI-E Wlan  Card as LAN...