Latest snapsot wireless bridged as well as static not working
-
/tmp/ath0_setup.sh gives
#!/bin/sh # pfSense wireless configuration script. # enable shell debugging set -x /bin/ps awwuxx | grep hostapd | grep ath0 | awk '{ print $2 }' | xargs kill /sbin/ifconfig ath0 down /sbin/ifconfig ath0 mode '11g' /sbin/ifconfig ath0 channel '11' /sbin/ifconfig ath0 -mediaopt turbo /sbin/ifconfig ath0 ssid '1mbps Blazing' /sbin/ifconfig ath0 -hidessid /sbin/ifconfig ath0 -mediaopt adhoc /sbin/ifconfig ath0 protmode 'rtscts' /sbin/ifconfig ath0 mode 11g pureg /sbin/ifconfig ath0 -apbridge /sbin/ifconfig ath0 -wme /sbin/ifconfig ath0 authmode open wepmode off /sbin/ifconfig ath0 txpower '99' /sbin/ifconfig ath0 mediaopt hostap /sbin/ifconfig ath0 mtu 1500 /sbin/ifconfig ath0 up /usr/sbin/hostapd -B /var/etc/hostapd_ath0.confand /tmp/bridge0_config gives
/sbin/ifconfig bridge0 destroy /sbin/ifconfig bridge0 create /sbin/ifconfig ath0 mtu 1500 /sbin/ifconfig vr0 mtu 1500 /sbin/ifconfig ath0 up /sbin/ifconfig vr0 up /sbin/ifconfig bridge0 addm ath0 addm vr0 up -
Once the bridge is successfully created and wireless is working, are both the LAN interface and wireless interface supposed to be in promiscuous mode?
Thats what my ifconfig shows on a working system.
Also, in the GUI, when I go to Status/Interfaces, LAN and ATH are both listed as learning in Bridge0
-
anybody knows what happened to the "install embedded kernel" option in the LiveCD installer? I caqn't find it in 7.3
-
@onhel:
Once the bridge is successfully created and wireless is working, are both the LAN interface and wireless interface supposed to be in promiscuous mode?
Yes.
-
So it looks like from xbipin's output results that even though the mtu is being set correctly with both interfaces and the bridge, the problem is that lan and ath are just not going into promiscuous mode.
What if they manually enable promiscuous mode:
ifconfig vr0 promisc
ifconfig ath0 promisc -
here is what it says in my ath0_setup.sh on 1.2.3 (7.2)
#!/bin/sh # pfSense wireless configuration script. # enable shell debugging set -x /bin/ps awwuxx | grep hostapd | grep ath0 | awk '{ print $2 }' | xargs kill # Enable ATH distance settings /sbin/athctrl.sh -i ath0 -d '30' /sbin/ifconfig ath0 down /sbin/ifconfig ath0 mode '11g' /sbin/ifconfig ath0 channel '6' /sbin/ifconfig ath0 -mediaopt turbo /sbin/ifconfig ath0 ssid 'blackhole' /sbin/ifconfig ath0 -hidessid /sbin/ifconfig ath0 -mediaopt adhoc /sbin/ifconfig ath0 protmode 'rtscts' /sbin/ifconfig ath0 mode 11g pureg /sbin/ifconfig ath0 -apbridge /sbin/ifconfig ath0 -wme /sbin/ifconfig ath0 authmode open wepmode off /sbin/ifconfig ath0 txpower '85' /sbin/ifconfig ath0 mediaopt hostap ath0_setup.sh: unmodified: line 1again, just running those ifconfig commands didn't help. had to disable/enable wireless interface
-
tried putting them in promiscuous mode but still doesn't work
-
again, just running those ifconfig commands didn't help. had to disable/enable wireless interface
Disabling and enabling does nothing different from running the contents of ath0_setup.sh and then bridge0_config. You have to run both though.
-
tried putting wireless standalone without the bridge but with dhcp on it but still the same, atleast the older versions used to work with wireless without the bridge to the lan.
-
tried putting wireless standalone without the bridge but with dhcp on it but still the same, atleast the older versions used to work with wireless without the bridge to the lan.
Can you post your status.php? I can't replicate any problems with 7 different ath cards, bridged or not. Going to need more info.
-
Disabling and enabling does nothing different from running the contents of ath0_setup.sh and then bridge0_config. You have to run both though.
I don'tknow what it does but it helps ;)
-
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.
-
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
-
@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
-
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.
-
@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.
-
At least we're down to a one click fix
;D
-
@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.
-
Please, keep as posted on the progress :)
-
@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
