Latest snapsot wireless bridged as well as static not working



  • latest snapsot, wireless gone down, doesnt work in bridged as well as static mode, not giving out ip address at all inspite of dhcp server configured properly.

    its just that in both static as well as bridged mode it doesnt give out ip addresses so i think its an issue with DHCL



  • no1 to confirm wireless bridge on embedded on alix not functioning, basically works but dhcp having issues so doesnt give ip address at all and on manually configuring it also doesnt communicate



  • 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

    tcpdump.txt



  • 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

    filter.txt



  • 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

    dump.txt



  • 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.


  • Administrator

    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



  • @Sloth:

    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 2009

    works perfectly fine, wireless, dhcp, dns, wireless to lan bridge



  • @xbipin:

    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:

    @Sloth:

    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



  • @n1ko:

    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


  • Administrator

    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.


  • Administrator

    Try to install the RC1 snapshot linked on the latest blog entry:

    http://blog.pfsense.org/?p=428



  • It seems that my new NC10 can connect jus fine, but my other devices (that used to work, Wii and e90) still cant connect after the first connection.

    If theres something changed in rules or maybe a bug fixed that would have affected those could someone give a ruleset that allows all lan-wlan traffic so that basicly there would be no filtering etc. between them. I only want to extend my wire network with wlan.



  • UPDATE: I swapped my ralink (rt2560f) card to an atheros (cant remember the exact chipset but same tp-link card that many has been using). All my problems went away! So it seems that my problems were with the ralink drivers.



  • There is definatly something hardware specific going on here.

    I had my 1.2.3 working at home with only intermittent problems connecting with wireless (dhcp problem as others specified).  With a later version of 1.2.3 this did not happen often and a reboot fixed it.

    On upgrading the ALix board from the old firewall 2D1 to the slightly more powerful 2D3 no matter how many reboots given Wireless would not hand out DHCP.  This was done using the same flash card so config and OS was identical.  I also tried rolling back and forward and while i didnt try all versions of 1.2.3 RC-1 released none of them worked.

    There is something hardware specific about this.



  • @timd:

    There is something hardware specific about this.

    What hardware are you using?


Locked
 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy