Latest snapsot wireless bridged as well as static not working

covex

I don't see any updates for 1.2.3 7.2 based after May 30th… ???

AhnHEL

I'm back on 7.1 builds. Clicking Save in Interfaces/LAN fixes the "wireless bridge MTU and promiscuous mode" bug in the 7.1 build as well. Besides, 7.1 builds are up to 1.2.3 RC2.

xbipin

i tried the 3rd june 1.2.3 7.1 but pppoe wont work so i went back to the 31st may 1.2.3 7.1 base release and work fine with the wireless workaround

covex

this is more of a firewall issue but it affects some how the wireless interface so I'm going to post it here :)
my firewall setup can be seen in attached files
when rules on the LAN interface setup first time everything works OK but after reboot I get this message in dmesg:

Configuring firewall...
ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled
ipfw:
rule 2: setsockopt(IP_FW_DEL)
:
Invalid argument
ipfw:
rule 3: setsockopt(IP_FW_DEL)
:
Invalid argument

when the router is up my wireless wont work. I'm getting dhcp ip address and all other info right but I can connect to the firewall or internet.
Looks like this error makes firewall do something to the wireless interface. Wireless is bridged to LAN

removing and recreating these rules would fix the problem.

lan.png_thumb

wan.png_thumb

wireless.png_thumb

ipsec.png_thumb

cmb

We were able to get the changing MTU issue that was causing the problem on the systems I saw resolved in FreeBSD, and have added that patch to our snapshots as of a couple days ago. Those of you who could replicate issues, please test the latest snapshot from here and report back.
http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/?C=M;O=D

xbipin

just downloaded and reflashed to pfSense-1.2.3-20090609-0445 and the wireless issue has been solved, works perfect now, so finally we r over with it, keep in mind 1.2.3 RC2 is FreeBSD 7.2 base now

cmb

@xbipin:

just downloaded and reflashed to pfSense-1.2.3-20090609-0445 and the wireless issue has been solved, works perfect now, so finally we r over with it, keep in mind 1.2.3 RC2 is FreeBSD 7.2 base now

Thanks for the report! That's good news, glad to see it seems to be fixed in FreeBSD now. Yes, 1.2.3 will be on FreeBSD 7.2 unless some major reason appears to not use it. Thus far it's been a painless change.

xbipin

how about making it on FreeBSD 8 and when can the nanobsd images be available for testing for embedded?

any plans of adding some basic packages to the embedded images to add some more functionality, eg: siproxd and other basic commonly used packages bcoz for home networking, there r not any specific features i use of pfsense other than traffic shaping and wireless.

cmb

@xbipin:

how about making it on FreeBSD 8

It was committed to FreeBSD by Sam Leffler so it's in 8. It was also MFCed to RELENG_7. We have the same patch on top of 7.2, because it won't get changed in RELENG_7_2.

@xbipin:

and when can the nanobsd images be available for testing for embedded?

You'll see there are nanobsd folders on the snapshot server now, we'll have images up soon.

@xbipin:

any plans of adding some basic packages to the embedded images to add some more functionality, eg: siproxd and other basic commonly used packages bcoz for home networking, there r not any specific features i use of pfsense other than traffic shaping and wireless.

siproxd is in embedded in 1.2.3. You can install many other packages if you want. http://doc.pfsense.org/index.php/Installing_packages_on_embedded

Packages and embedded will change in a yet to be determined way once we're switched to nanobsd embedded. We will be making all embedded suitable packages available in some fashion (easier than the above).

xbipin

one feature which has been talked about much under wireless but hasn't been implemented as yet is the option to select the transmit and receive antenna for wireless bcoz not all have 2 antennas and this has been discussed in the wireless forum and was also said it would be added in future releases but haven't seen it as yet. i tried running the below commands and restarting the box but then the wireless clients would connect but were not able to surf so then i have to click the save button on the wireless page and then everything comes to normal but then the below values change to default, rx=0 tx=1 div=1

sysctl dev.ath.0.txantenna=0
sysctl dev.ath.0.rxantenna=0
sysctl dev.ath.0.diversity=0

cmb

@xbipin:

one feature which has been talked about much under wireless but hasn't been implemented as yet is the option to select the transmit and receive antenna for wireless bcoz not all have 2 antennas and this has been discussed in the wireless forum and was also said it would be added in future releases but haven't seen it as yet. i tried running the below commands and restarting the box but then the wireless clients would connect but were not able to surf so then i have to click the save button on the wireless page and then everything comes to normal but then the below values change to default, rx=0 tx=1 div=1

sysctl dev.ath.0.txantenna=0
sysctl dev.ath.0.rxantenna=0
sysctl dev.ath.0.diversity=0

You can make feature requests at http://redmine.pfsense.org

xbipin

after the update, wireless seems fine but i guess surfing through lan and wireless has gone slow, packets dont pass through the firewall quick enough compared to the 7.1 base, overall internet performance has gone down for some reason, latency is high in voip calls and it seems something in the firewall is causing the delay

xbipin

still more glitches noticed, as soon as firewall is rebooted and then when wireless comes online, clients get connected and get an ip also from dhcp but wont be able to surf till the older workaround is performed, either clicking save in lan setup or wireless setup, MTU after reebot seems all fine but the workaround still needs to be performed and due to performance issues im reverting back to the 7.1 base with the snapshot that has the wireless issue

just restored to 7.1 base and now it can breath faster, definately something causing the slowness in the 7.2 base

covex

…as soon as firewall is rebooted and then when wireless comes online, clients get connected and get an ip also from dhcp but wont be able to surf till the older workaround is performed...

hm… looks like I have exactly the same symptoms. As I posted above, after reboot everything seems to be OK but no traffic goes through on wireless. I can't connect to the router or surf internet, but I can connect to my desktop, which is on the same LAN, using vnc no problem.
So, those errors that I'm getting in the firewall during reboot are not to blame...

Sloth

Can confirm that, on reboot with the 0609-2221 7.2 embedded build, I am also seeing no traffic over WiFi until the 'save config' fix. Having said that, once the WiFi fix is 'applied' I am having no other problems: I am able to saturate My WAN connection (10Mbit) with only 20% CPU usage, and latency to My VoIP provider is running at a steady 10-11ms. These figures are pretty much the same as for previous 7.1 builds, so it does not look like I am suffering the same performance problems as xbipin when running 7.2 based builds…
Jason.

pfSense image:
1.2.3-RC2 built on Tue Jun 9 21:29:11 EDT 2009 (pfSense-1.2.3-20090609-2221.img.gz embedded freeBSD 7.2)
Hardware:
Alix 2c3 BIOS 0.99h
Atheros 5212 based miniPCI card (Wistron CM9)

xbipin

its not that i cant use my complete wan bandwidth but the performance issue is when say u open multiple sites, most new ones that u havent opened that day or say for an hour or so, the initial connection to the site takes a slight bit longer, then again if u open up then it opens quick and even if u reload the page as fresh. i have kept my firewall on aggressive so mayb the reconnection of sites is a bit slower than the 7.1 base for some reason and also if there r no packets going through to WAN then sites take even longer to open and my network card blinks constantly as if still data is to be downloaded even if i load google which takes less than a second in normal cases and if i open up the pfsense site, take almost more than 15secs, i tried reconnecting to my WAN etc but still the same and then when i reverted back to 7.1, it got blazing fast again.

Sloth

xbipin,

Have just tried running My pfsense box with state table optimisation set to 'agressive'. Not noticed a massive slowdown, but CPU usage increased to 12% (from 2% when set to 'normal') while handling normal background WAN traffic (approx 200Kbit/s) and responsiveness of pfSense web interface seemed slower (could see page redraws). NB I'm on a very low latency Internet connection so re-establishing dropped TCP sessions is not so much of a hit, but I could see you having problems on a higher latency connection. I seem to remember reading on here somewhere the advice to run state table optimisation 'normal' unless you have a good reason to set it otherwise (I'm sure someone will hop on here and correct me or give further explaination though!).

NB2: changing the state table optimisation setting appears to break WiFi, requiring the 'save' fix to get it back again.

Jason.

pfSense image:
1.2.3-RC2 built on Tue Jun 9 21:29:11 EDT 2009 (pfSense-1.2.3-20090609-2221.img.gz embedded freeBSD 7.2)
Hardware:
Alix 2c3 BIOS 0.99h
Atheros 5212 based miniPCI card (Wistron CM9)

xbipin

just a while ago i tried pfSense-1.2.3-20090611-2116.img.gz but seems pppoe is broken so i tried pfSense-1.2.3-20090610-2204.img.gz and that works now and the internet slowness issue i had is gone all of a sudden but now the wireless, having proper MTU values also wont start and give ips to wireless clients, the save button click work around also doesnt seem to work now, let me mention that i have changed my wireless card to Compex WLM54AGP23 with the atheros 5413 chipset

sorry but wireless is fine but actually the restore section isnt working so it didnt import the firewall rules and that was the issue and i guess its still broken, gives some xml error

Sloth

Well, after a nearby lightening strike last night, I no longer have a working ALIX router >:( The strike took out My cable modem and fried the WAN port of the ALIX box. Interestingly I can still attach to ALIX via serial port and pfSense boots, but boot sequence does not even report existence of WAN interface, and once booted pfSense cannot pass traffic over 2 remaining ports (not surprising I guess as there was the distinctive smell of burnt chips after the strike suggesting that the damage was probably extensive!).

I'll probably spin up an old PC with pfSense as a stop-gap until I can source another ALIX board (anyone selling?), so unfortunately no more embedded testing for now…

Jason.

pfSense image:
1.2.3-RC2 built on Tue Jun 9 21:29:11 EDT 2009 (pfSense-1.2.3-20090609-2221.img.gz embedded freeBSD 7.2)
Hardware:
~~Alix 2c3 BIOS 0.99h~~ toast :(
Atheros 5212 based miniPCI card (Wistron CM9) waiting for a new home…......

covex

here is something else that I haven't seen before…
wireless completely unusable if it's set to turbo g/channel 6. Away from the router I get only 1Mbs/Low, when if I switch to channel 10 or 9 I get 54Mbps/Good
I've never seen this issue before I switched to 1.2.3 7.2 based :-\