Latest snapsot wireless bridged as well as static not working
-
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
-
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.
-
-
Currently at home the ALix 2D3 which is similar to the 2D1 but includes USB ports, 256mb of memory rather than 128 and slightly higher clockspeed.
-
What about your wireless hardware? Is it the same as what you were using in the 2D1?
-
Yup Its an Atheros (same card all the time) : Heres info got from 1.2.2 currently running on it. ( Loads of In / Out errors but working. )
"dmesg | grep ath"
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
ath0: <atheros 5212="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
ath0: [ITHREAD]
ath0: using obsoleted if_watchdog interface
ath0: mac 10.5 phy 6.1 radio 6.3</atheros> -
i also have the atheros card and doesnt work on 1.2.3, not that it doesnt work at all but doesnt give out ip using dhcp, if ip is set in clients to manual then atleast it communicates. i tried everything
-
Yeah i'd like to add that while the DHCP doesnt work with wireless the actual wireless card is working properly for the first time with no interface in / out errors ect. All previous versions always left me with In / Out errors.
-
DHCP works fine on my atheros NIC.
Here's the kernel I'm running
uname -a
FreeBSD pfsense.example.org 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Mon Apr 13 15:59:41 EDT 2009 sullrich@RELENG_1_2-snapshots.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.7 i386
Here's how my interface is reported in the startup:
dmesg | grep ath
ath0: <atheros 5212="">mem 0xee000000-0xee00ffff irq 12 at device 8.0 on pci0
ath0: [ITHREAD]
ath0: WARNING: using obsoleted if_watchdog interface
ath0: Ethernet address: 00:19:e0:xx:xx:xx
ath0: mac 7.9 phy 4.5 radio 5.6</atheros>Your atheros is a more recent revision than mine?
-
i go the below atheros card working with the march release but not the latest one
$ dmesg | grep ath ath0: <atheros 5413="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: xx:xx:xx:xx:xx:xx ath0: mac 10.5 phy 6.1 radio 6.3 ath0: promiscuous mode enabled</atheros>
