Latest snapsot wireless bridged as well as static not working

xbipin

i have mailed u with the access, plz do so asap coz i dont know how long the lease on the ip is going to be from the isp

covex

@cmb:

One (or more) of you who can replicate problems, can I get remote access into your firewall? Then let me know when the problem occurs so I can log into the box and see what's happening. If you can replicate this problem and will let me into your firewall, please email me (cmb at pfsense dot org) and reference this forum thread.

email sent, please come in :) my ip is not changing

AhnHEL

ok, funny thing.

Once booted, enter GUI and go to Interfaces/LAN

Uncheck or Check Disable the Userland FTP-Proxy application

Hit Save and then Apply.

Bridge is working with proper MTU!

I reproduced this 3 times, test on yours please.

cmb

@onhel:

ok, funny thing.

Once booted, enter GUI and go to Interfaces/LAN

Uncheck or Check Disable the Userland FTP-Proxy application

Hit Save and then Apply.

Bridge is working with proper MTU!

I reproduced this 3 times, test on yours please.

That'll do the same thing as just clicking Save without changing anything.

Pretty sure I have a lead on the cause of this issue, it's some sort of FreeBSD bug, looking for a solution.

AhnHEL

At least we're down to a one click fix

;D

jimp

@onhel:

At least we're down to a one click fix

;D

In the tests I've done on this little WRAP I have next to me, saving is what reset it to 2290 :) Not quite what I'd call a fix yet…

A FreeBSD bug in hostapd is the likely culprit, as cmb said we're all hoping for a fix.

covex

Please, keep as posted on the progress :)

xbipin

@onhel:

ok, funny thing.

Once booted, enter GUI and go to Interfaces/LAN

Uncheck or Check Disable the Userland FTP-Proxy application

Hit Save and then Apply.

Bridge is working with proper MTU!

I reproduced this 3 times, test on yours please.

i cant believe this, the solution is this simple, i just tried it and within less than 30 secs it started working like there was no problem at all

cmb

@xbipin:

i cant believe this, the solution is this simple, i just tried it and within less than 30 secs it started working like there was no problem at all

It's not really that simple. That doesn't do anything differently from manually running the commands I noted earlier in the thread. It will make it work for a bit, but it won't stay working.

xbipin

actually when i tried manually those commands it never used to work but currently at least its running fine for the past like 15mins, lets see how long it lasts

covex

Confirmed, this… workaround :) works. I have stable wireless connection for more then 2 hours now.

xbipin

i can confirm it to work now in stable state for more than 24 hours, im on the 31st may 2009 1.2.3 7.2 base snapshot

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.