That is odd… I've never owned a netgear router.  I do have my wireless and wired turned on and both active but the 192.168.1.0 subnet is only visable on the wired side X-Link to the newly flashed router..... No routing required to get to the admin interface. I just entered the 192.168.1.1 address again and my browser attempts to connect to something  ??? but i know there is no 192.168.1.* devices on my network its been unplugged since last night.... Crazy.

Thanks for the kick :)

Looking at my regular router's state table:

tcp 192.168.1.1:80 <- 172.17.xx.xxx:51968 CLOSED:SYN_SENT
tcp 172.17.xx.xxx:51968 -> EXT_IP:1813 -> 192.168.1.1:80 SYN_SENT:CLOSED

Looks like someone's plugged something in to the wrong port! LOL

o yea man thank you

im tryed for firefox and works fine. :D

I went back and turned off "install emerging threats rules" and it seems to have reloaded the pfsense version of snort.conf. I turned them back on and it restarted cleanly. It would seem that after a rules update … it changes the snort.conf? Is this possible?

Podilarius

The last time this happened a builder VM needed to be restarted. I'll pass along the word.

@kevindd992002:

If I have an athlon 64 processor and enabled "virtualization" in the bios of my mobo, do I need to use Symmetic Multiprocessor Processing in the installation of pfsense 1.2.3 RC1?

Probably not. VT only helps with VMware, VirtualBox, and other Hypervisors. If it's not talking about VT, then you probably don't need it anyhow. If that is a feature like Hyperthreading, it really won't gain you much if anything (And may hurt). If you only have one CPU with one core, you can use either the SMP or UP kernel safely. SMP is the default in FreeBSD since 7.x, but there are still some edge cases where the SMP kernel has bugs that are not present in the UP kernel. YMMV

Also, if I update to the latest snapshot using the firmware updater of pfsense, will it retain the SMP feature enabled? Or do I have to re-enable it?

It should keep what you have. If you are in doubt, do a console update from URL and it will prompt you for the kernel choice.

In the latest snapshot page http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/updates/ which of "nanobsd" and "full update" will I choose?

If you are running a nanobsd embedded image, use those, if you are running a full install made from a livecd, use the full install.

And lastly, in this live installer page http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/livecd_installer/ , why do the files have an extension of .iso.gz and not .iso only? How will you burn an .iso.gz image in Windows? I thought those were for Linux?

It's just a compressed format like .zip, .rar, etc. You can use something like 7-zip to decompress it, then burn.

Thank you.

It definitely won't be in 1.2.x. 2.0 depends on if/when it gets into FreeBSD, probably not likely for 2.0 either. You need 3 static public IPs if you want stateful failover. You can do with two if you don't want to fail over and retain states.

Ok, tried it again with a different CF card and it worked.  The card that failed is good as far as I know.  I'll have to spend a little time with it to be sure.

Thanks!

This should be in now, in Dashboard 0.8.5.

This seems to be a known issue.  I had this problem a while ago, and found that many others had the same issue.  Hate saying it, but do a search and it's out there.  My solution was to install cron and set it up to auto start ntop every few minutes (followed a post a while ago).  Not an elegant solution, but works.  I'd say search for NTOP and CRON and you should be good to go.
  I think someone is going to have to start a bounty to get ntop updated to the latest version.

Aha, i had, by some unknown way (and trust me i tried to figure how) managed last sunday to get the brdige running .. and it did, untill tonight
The alix did not reboot in between, but same behaviour :
I can reach my servers on LAN fine, but i cannot ping nor traceroute to the pfsense LAN IP
Therefore, i have no access to the net .. since i cannot reach the gw …

Note :
Alix 2D3 (bios 0.99h)
Same snapshot as before
dhcpd is enabled on LAN
WLAN (OPT2, ath0) bridged to LAN (vr0)
WAN on vr2, static IP
PPTPD on WAN

Below is my ifconfig:

vr0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether 00:0d:b9:15:69:0c
inet 10.0.33.254 netmask 0xffffff00 broadcast 10.0.33.255
inet6 fe80::20d:b9ff:fe15:690c%vr0 prefixlen 64 scopeid 0x1
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vr1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether 00:0d:b9:15:69:0d
media: Ethernet autoselect (none)
status: no carrier
vr2: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether 00:0d:b9:15:69:0e
inet6 fe80::20d:b9ff:fe15:690e%vr2 prefixlen 64 scopeid 0x3
inet xxx.xxx.xxx.xxx netmask 0xffffff00 broadcast 82.235.179.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
ether 00:0b:6b:2d:e6:7e
inet6 fe80::20b:6bff:fe2d:e67e%ath0 prefixlen 64 scopeid 0x4
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
ssid Dune channel 3 (2422 Mhz 11g) bssid 00:0b:6b:2d:e6:7e
authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 3 TKIP 2:128-bit
TKIP 3:128-bit txpower 31.5 scanvalid 60 bgscan bgscanintvl 300
bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode RTSCTS burst
dtimperiod 1
pflog0: flags=100 <promisc>metric 0 mtu 33204
pfsync0: flags=41 <up,running>metric 0 mtu 1460
pfsync: syncdev: lo0 syncpeer: 224.0.0.240 maxupd: 128
enc0: flags=41 <up,running>metric 0 mtu 1536
lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
ether ee:c3:50:ff:1b:65
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: vr0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 1 priority 128 path cost 200000
member: ath0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 4 priority 128 path cost 370370
ng0: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng1: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng2: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng3: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng4: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng5: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng6: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng7: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng8: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng9: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng10: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng11: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng12: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng13: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng14: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng15: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500
ng16: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500</pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></learning,discover,autoedge,autoptp></learning,discover,autoedge,autoptp></up,broadcast,running,simplex,multicast></up,loopback,running,multicast></up,running></up,running></promisc></hostap></up,broadcast,running,promisc,simplex,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,simplex,multicast></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></broadcast,simplex,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,promisc,simplex,multicast>

I believe pf itself uses the GIANT LOCK, but the rest of the O/S will use both cpus for tasks unrelated directly to pf.

Search around in the wireless forum. From what I can determine high amounts of in errors on the interface don't necessarily mean there is a problem. A stuck beacon or the like is different, but if there doesn't seem to be a problem I wouldn't worry. I have several Alix boxes with ath cards that are running just fine- they all have huge amounts of in errors. It may well be that the ath driver does not mask 'normal' errors under some circumstances.

@iMicke:

I recently built my first pfsense box and I used a 1Gb Transcend Industrial compact flash. Unfortunately it was also too small for your 1Gb nanobsd images. According to the documentation it is C/H/S 1974/16/63..

You could still use the card with the 512MB image.

I just broke 90 days uptime with pfsense running on this board. Sadly, I'm going to have to take the router down for maintenance in the next few days as I'm having a dedicated 100 amp circuit run to my office. Why? Because I'm running running 14 computers on 1 20amp circuit which isn't really smart. ;) Hehe.

It actaully fixed it self after a reboot .

I had the same issue and discovered that disabling RX Checksum on the NICs enabled them to work again.

My devices are fxp0, fxp1 and fxp2.  To disable RX Checksum, I dropped to shell (8), then entered:

ifconfig fxp0 -rxcsum
ifconfig fxp1 -rxcsum
ifconfig fxp2 -rxcsum

Okay, my 4gig CF card is only showing 1.88 gig capacity and will not reformat to original size.  Is this due to the nano image and windows only seeing one partition?  Is there any way to restore the card to the original size or is it permanently smaller?  This probably has something to do with my updating problem.
jim

Im running this on a watchguard x700, and it seemed to do ok with monowall loaded previously.  Although, hardware can go bad in the blink of an eye.

I have managed to Image the CF 4 GB image [August 26] successfully on both Soekris 4401 & 5501 boxes. Unfortunately what worked for me was to use Parallels and a FreeBSD OS I have as a VM [7.2 Stable].

Tried again with instruction set from the WIKI in OS X , and images are not booting up. I will look to do another test once a newer 4GB image is released.

Anyone else having trouble in Mac OS X without using a VM solutions ?

Regards,