Latest snapsot wireless bridged as well as static not working
-
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) -
Had same problem however a reboot has fixed it and so far its still up. (at home so dont mind testing)
Along with all that at least my massive wireless in / out errors are gone so hopefully this can be fixed while retaining these drivers.
Along with that it appears the ammount of inturupt on the processor is down when pushing my 50meg virgin line to the limit which is nice.
-
I'm running 1.2.3-RC1 built on Mon Apr 13 16:35:28 EDT 2009 and I'm not having any trouble with LAN bridged with wireless. DHCP hands out IP addresses to laptops linked over wireless.
-
i just installed 1.2.3-RC1 built on Mon Apr 13 17:15:57 EDT 2009 and it doesnt work, rebooted also but still the same, in bridged mode doesnt give ip and also id ip defined manually still doesnt provide internet access. if put in standard wireless mode without lan bridge, then still doesnt give out ip using dhcp, only works if ip defined manually in client.
-
Do you have firewall rules allowing DHCP traffic on your wireless interface? There are a number of posts giving suitable rules.
-
with the following 2 rules it was working in older releases so i dont think thats the issue as the firewall doesnt block any such packets also
-
Wallybob: I also have an 'allow all' rule for the WiFi Interface (as noted in My post above this is a working config that is only borked by the most recent builds)
timd et al: what WiFi hardware are you running, and what flavour of pfSense - full or emebedded?
btw Since the recent important WiFi code update, and aside from the current issue, the performance and reliablility of WiFi connections has been excellent: My stand-alone Wireless AP is now gathering dust…
Reagards
Jason.
-
I am running full version, atheros wireless NIC.
sloth and xbipin: have you looked in the DHCP server log for signs that the DHCP server received a request from the wireless NIC? (See Status -> System logs and click on the DHCP tab. Note though that for received DHCP requests on a wireless NIC bridged with a wired NIC the log reports wired NIC rather than the wireless NIC.) Is there isny error reports in the DHCP log?
Is there any report in the Firewall log that suggests the firewall is blocking DHCP?
Does a tcpdump on the wireless interface show received DHCP packets?
-
the dhcp log doesnt show anything and the tcpdump gave the results present in the txt file
there is nothing in the system log or firewall log that suggests that something is blocking it -
So tcpdump on the wireless interface shows incoming DHCP packets but the DHCP server doesn't log generating a response to them.
I suspect the firewall is blocking them (check your DHCP enabling rules are active on the wireless NIC) or the DHCP server is rejecting them ad not reporting them. (Do you have DHCP restricted to handing out addresses ONLY to known MAC addresses and the source address in the tcpdump trace is not in the "known MAC address" list? )
-
Please also look for blocked DHCP requests in /var/log/filter.log (That where I found them logged when I reported a DHCP problem in August 2008.)
-
the wireless is bridged to LAN and DHCP server is enabled on LAN and give ip to known MAC is unticked which is by default so its supposed to give out ips and in the log i replaced the mac address of my wireless client to 00:23:6c:xx:xx:xx so in it the last 3 portions i have purposely changed
-
my filter log seems like this, its not blocking anything
-
So to summarise:
-
tcpdump shows dhcp requests received on the wireless NIC
-
the wireless NIC has firewall rules to allow DHCP traffic
-
the firewall filter log doesn't show DHCP requests blocked
-
the DHCP server log doesn't show any DHCP requests recognised.
I'd be suspicious that you have somehow got a firewall rule that quietly blocks the DHCP requests from the wireless NIC. I can't think of any other explanation that fits what you report. How about dumping the firewall rules and posting them: type the shell command pfctl -s rules -v.
-
-
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
