next »

[cmb]

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:

Code:

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.

[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]

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]

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.

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.

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]

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