…just verified the whole setup and figured out that the bge NICs are not availlable after I switched of ACPI in /boot/device.hints regardless which version is installed (even 1.2 shows this).
So I won't disable ACPI and install 1.2.2 without gmirror waiting for the next stable release 1.2.3.

Does anybody had the same issue when disabling ACPI?

Checked it out this morning and the fxp0 is one of the added cards. But since the WAN was working when the problem happened and the OPT1 and LAN both use the xl driver then it shouldn't be driver related, right?

I confirmed with the person on site that the LAN connectivity was still working when the OPT1 lost connection to the internet.

Any other ideas?

Nat-t was added, and I've been having issues with a tunnel to a older Draytek Vigor 2900 which I can't get working anymore with 1.2.3.

I think the added nat-t support has triggered this. I'll need to check to make sure.

It needs to be possible to disable it on a per-tunnel basis.

Thank you for the useful info. I'll give it a try!

Max

Hi,

I investigated this problem a bit futher:

apparently when I lose my internet connection (I'm still connected to my AP at this point), it's my DNS that doesn't work anymore. DNS settings for my client are dynamically assigned by DHCP on my pfsense box.  An ipconfig /all showed me that the DNS server is 192.168.6.0 (shouldn't this be 192.168.6.1?). In the DHCP server settings in pfsense I left the DNS entry blank.

I did a ping to a website from one of my stations that has a wired network connection, and I received answers. When I lost internet connection (again my connection to the AP was ok) I did the same ping and my wireless client couldn't resolve the DNS name. I tried to ping base on the IP address of the website and I received answers. Also surfing based on that IP proved to work.

The strange thing is when I switch of my wireless nic and reconnect the problem is gone (for some time). So it would seem this is a client side issue. However I have 5 different wireless clients and they all have the same problem since I switched to 1.2.3.

I'm running the snapshot from 25feb at the moment.

Best regards,
Jan

That is to be expected (but not desired) for snapshots.   It's on my extremely long list to fix.

It sounds like out of state traffic getting blocked, as the version of pf in 1.2.1 and newer is more strict than previous versions, but that should only affect scenarios that can't be statefully filtered, such as with static routes and asymmetric routing. Try to check "Bypass rules for traffic on same interface" (paraphrasing from memory, you'll find it) under System -> Advanced.

Doesn't really show anything useful, what's the other end logging?

I can confirm this as well. Updated from 1.2.1-rc? to 1.2.3-PRERELEASE-TESTING-VERSION built on Thu Feb 19 21:52:48 EST 2009.

The package was not installed before the upgrade, nor was it present in the installed packages list after.

@cmb:

@john.grange:

Ok I did some research and in some cases yes it might be due to the asymmetric routing, does that mean if I have a route through a VPN server that does not have the firewall as the gateway I can not do any packet filtering?

Not for those networks. Check "Bypass firewall rules for traffic on the same interface " under System -> Advanced.

I have this selected but still same issue.

Thanks

All of my attempts to update an Alix box via the embedded update have resulted in the box being unbootable. My hunch is it has something with temp being a md of very limited size. I could take the same image (1 GB resized 1.2.2), change the platform to pfSense from embedded, reboot, and update using a full update.

My logs come and go, I had it logging firewall stuff (deny wireless users access to firewall config page-it blocks, but no logging -yes I double checked that I had it enabled)
Yet before I did a reboot It looged fine so it seems that its a hit and miss for me.

pfSense is a great project and I love it. thank you all for the free program and support (especcially the programmers and debuggers- i know what a pain it can be)