Latest snapsot wireless bridged as well as static not working
-
see the txt file for dump
-
The rules dump includes
pass in quick on ath0 proto udp from any port 66 >< 69 to any port 66 >< 69 keep state label "USER_RULE: pass dhcp traffic"
[ Evaluations: 48 Packets: 211 Bytes: 69208 States: 0 ]
[ Inserted: uid 0 pid 3678 ]From the pfctl man page it appears this means 211 packets matched this rule.
I don't know what filter dhcpd uses to request incoming packets but probably most of those 211 packets should have gone to dhcpd but apparently didn't. Was dhcpd running? (Had it died?) -
dhcpd is running happily and hands out ips on the lan but doesnt on the wireless bridged to lan.
like i said the same config, without any changes works very well for releases in March or so and i was using it so far until i tried the 7th april and onwards snapshots and it has been down every since.
its just that in bridge or non bridge, dhcp doesnt hand out ips on the wireless interface at all.
-
Nothing jumped out at me as changing between March and April, but you might browse through the commits to see if you notice anything:
https://rcs.pfsense.org/projects/pfsense/repos/mainline/logs/RELENG_1_2
I didn't look through the tools/builder scripts, but sometimes changes there can affect the releases as well.
https://rcs.pfsense.org/projects/pfsense-tools
-
on some more testing i found out the following
wireless to lan bridge doesnt work but as i said even on standalone wireless as access point configured to give out ip using dhcp wasnt able to do that but after a lot of config change it some how gave out the ip using dhcp put the dns server should be 192.168.2.1 as that being the ip of the wireless but it used to give dns address of that listed under the system>general setup but the tick box is tick saying Allow DNS server list to be overridden by DHCP/PPP on WAN so basically something to do with that so i then removed the dns entries over there and kept the tick box ticked so then the dns server changed to 192.168.2.1 which is the ip of the wireless interface so i guess the bug is in that tick box, inspite of it being ticked it still gives the wireless clients the dns server written in the boxes above so keeping them clear seems to solve the dhcp in standard wireless mode.
ill do further testing by enabling wireless to lan bridge and report it further -
in standalone wireless mode its giving out ips but as soon as i switch it to bridge mode, then it still gives out ips but the ones that it used to give out when in standalone mode so the routing is wrong on it so nothing opens in the client and also everytime i do some changes the CPU usage jumps to 100% so i guess ill simply stick to the march release atleast its stable
-
I can confirm that Wireless bridging is Borked on My Alix box running builds 0416-2048 and 0417-2146. Devices are associating successfully, but no traffic is being passed to LAN (Wifi bridged -> LAN). Have rolled back to 0328-0054, retaining same config, which works just fine.
Hardware:
Alix 2c3 BIOS 0.99h
Atheros 5212 based miniPCI card (Wistron CM9)can u provide me with the file that u got , 0328-0054?
-
currently running :
1.2.3-PRERELEASE-TESTING-VERSION
built on Sat Mar 28 00:40:33 EDT 2009works perfectly fine, wireless, dhcp, dns, wireless to lan bridge
-
can u provide me with the file that u got , 0328-0054?
No problem, here ya go:
http://files.me.com/jason.pugh/oizgne
(link will only be active for next 7 days)BTW I have noticed looking at the embedded images that the image size jumps by about 1.2MB from the 0328-0054 build to the April builds with broken WiFi bridging. There are usually small fluctuations in size, but the big jump suggests that a large change might have been commited, or compile option changed?
[IDIOT DISCLAIMER]
As I have not been invoved in any serious dev work for a number of years now, please treat the above comment as speculation rather than fact!
[/IDIOT DISCLAIMER] -
thanks for the file, works perfectly fine.
i was checking the change log, maybe the difference in file size was maybe because of some driver update or new install, not sure though.
-
I suspect for the bulk of you this is user error, missing firewall rules that allow DHCP or something. Mine works perfectly fine and I know it works fine for numerous others and haven't personally seen a box where it didn't. Though this:
I can confirm that Wireless bridging is Borked on My Alix box running builds 0416-2048 and 0417-2146. Devices are associating successfully, but no traffic is being passed to LAN (Wifi bridged -> LAN). Have rolled back to 0328-0054, retaining same config, which works just fine.
sounds legit. Sloth: if I get you a few snapshots between 3/28 and 4/16 can you test to narrow down the change more closely? Nothing sticks out at me between those points.
-
cmb,
Yup, no problem testing a few snapshots around those dates if you can make them available. I was going to have a look at them Myself, but didn't get onto the download area before they had been removed - Doh! Just one problem though - I'm travelling from tomorrow am (European time), so would need the snapshots within the next couple of hours to stand a chance of getting them flashed and tested.
BTW I'm just about to try the RC…..
-
If this is an user error why did it occurr (without any changes) so suddenly after certain snapshot? And why is it fixed when reverting back to an older version?
Also for me this is occurring so that the DHCP works fine for one time and after the first connection it stops giving out ip's (or any other traffic for that matter). If I refresh the interface ( go to interfaces->wlan and push save) it again works for one time.
I am using RL2560, some people here are using atheros chipsets so it probably isnt driver related.
I have tried WPA2 and WPA (both and separaly). Previously I was using WPA only with G only mode.
EDIT: just flashed the new RC, same thing. Works for the first time (after boot or restarting interface) and after that nothing.
In system logs I see:
Apr 23 23:13:13 hostapd: ral0: STA <mac_here>WPA: group key handshake completed (WPA)
Apr 23 23:12:30 hostapd: ral0: STA <mac_here>WPA: group key handshake completed (WPA)
Apr 23 23:12:29 hostapd: ral0: STA <mac_here>WPA: pairwise key handshake completed (WPA)
Apr 23 23:12:29 hostapd: ral0: STA <mac_here>IEEE 802.11: associated</mac_here></mac_here></mac_here></mac_here> -
i certainly dont think its a user error coz i have been using the config ever since and nothing has changed in it, the rules r all fine etc and bytheway u guys can test between 28th march and 7th april coz i have tried 17th, 13th, 21st april and all r broken so to narrow it down, 28th march to 7th april so that makes it 9 snapshots for those 9 days
one more thing, when was it that the system page started showing 1.2.3 RC1 on a march release coz if im not wrong i was using such a march release and was working fine, i guess something even after 28th
-
If this is an user error why did it occurr (without any changes) so suddenly after certain snapshot? And why is it fixed when reverting back to an older version?
As I said, if you're one that can revert back to an earlier 1.2.3 snapshot and it's fixed, that's not the case.
I don't have many embedded snapshots for testing though to narrow it down. Lot of iso and full update files. Will see what I can find. Thanks for narrowing down the dates already.
-
I don't see any relevant changes between March 28 and April 7.
Those who are having this problem, try checking "Allow IPv6" under System -> Advanced. That change falls within this window, but there isn't any way that should have anything to do with this unless PF's inet6 does strange things. It isn't for me, and I seriously doubt if that's the case, but it's the only remotely relevant change I see in the 1.2 branch between those dates.
-
there is no option under system->advanced to enable or disable ipv6
-
Sure there is.
-
basically it doesnt appear in my current 28th march release, i completely forgot about it.
ill need to reinstall the latest firmware and give it a try.
-
Try to install the RC1 snapshot linked on the latest blog entry:
http://blog.pfsense.org/?p=428
