Latest snapsot wireless bridged as well as static not working

n1ko · Apr 25, 2009, 5:32 PM

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.

n1ko · Apr 26, 2009, 9:08 AM

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.

timd · Apr 27, 2009, 1:57 PM

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.

wallabybob · Apr 27, 2009, 8:34 PM

@timd:

There is something hardware specific about this.

What hardware are you using?

timd · Apr 28, 2009, 11:59 AM

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.

wallabybob · Apr 28, 2009, 12:32 PM

What about your wireless hardware? Is it the same as what you were using in the 2D1?

timd · Apr 29, 2009, 10:20 AM

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>

xbipin · Apr 29, 2009, 11:36 AM

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

timd · Apr 29, 2009, 12:58 PM

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.

wallabybob · Apr 29, 2009, 9:33 PM

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?

xbipin · Apr 30, 2009, 6:09 AM

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>

xbipin · May 13, 2009, 6:40 AM

any1 tested the latest snapshots for wireless functionality?

covex · May 15, 2009, 11:49 PM

I've updated yesterday from original rc1 release to the May 12th one. release from May 14th wouldn't event boot on my Alix 0_o.
After update wireless (bridged to LAN) went down and my laptop was showing limited or no connectivity message.
I had to kill the wireless interface and assigned it again. That fixed it and it works OK.
oh, and I'm running alix with atheros 5212.

xbipin · May 18, 2009, 8:41 AM

the snapshot server was down till now and now that its up, i tried the 18th may 7.1 base, 7.2 base of freebsd and m having same issues, wireless not get IP from DHCP when bridged with LAN, the second issue i saw with both the bsd versions of 1.2.3 was in system log there was an error saying couldn't not get the MTU of ath0 so using 1500 but then it couldn't bridge with LAN due to that wireless not being able to set its MTU value so the next line it said the same but now for vr1 which is the LAN interface

matrix200 · May 22, 2009, 2:38 PM

I also have bridging issues with the original 1.2.3RC1 build.
In my case if I only set bridging in the wireless interface it doesn't work (I don't use dhcp though and assign static ip's).
However if I set the bridging from the lan interface too it starts working!
This is annoying but I suppose I can live with that.

AhnHEL · May 22, 2009, 9:54 PM

I was having that same MTU issue as xbipin, mtu to the bridge interface was not set at 1500 when i ran the ifconfig command.

Using the below commands fixed it for me on my Alix 2c2

ifconfig vr0 mtu 1500
ifconfig ath0 mtu 1500
ifconfig bridge0 destroy
ifconfig bridge create

xbipin · May 23, 2009, 12:00 PM

@matrix200:

I also have bridging issues with the original 1.2.3RC1 build.
In my case if I only set bridging in the wireless interface it doesn't work (I don't use dhcp though and assign static ip's).
However if I set the bridging from the lan interface too it starts working!
This is annoying but I suppose I can live with that.

do u mean to say LAN bridged to WAN works but wireless bridged to LAN doesnt?

matrix200 · May 23, 2009, 9:35 PM

No,

What I am saying , it matters in which interface I set the bridging.
If I set the bridging in wireless interface (ath0 to lan) it doesn't work.
If I go to lan's interface and set there to bridget to ath0 then it works.
The thing is , this setting is not retained after reboot and I have to repeat this procedure everytime I want to reboot.
I also get the error message about wrong mtu when bridging but strangely enough the bridge works fine afterwards.

xbipin · May 24, 2009, 7:33 AM

i tried the following release
1.2.3-RC1
built on Sat May 23 03:47:37 EDT 2009

and still sad coz wireless bridged to LAN and wireless clients dont get ip address from DHCP running on LAN interface

DeCex · May 24, 2009, 9:51 AM

All works fine here;

OPT1 bridge to LAN

2 PC with with wireless connection
1 Wii gameconsole (wireless client)

If you goto the Status\Interface and look at the OPT1 option. What does it say? "associated" ?. I think i had this issue onces long ago and rememberd it was somethin to do with the OPT1 channel setting. Since im on WAG311T wifi card (Netgear) i hae channel 6 set (Turbo) and have no probelm at all.