Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Latest snapsot wireless bridged as well as static not working

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    140 Posts 12 Posters 76.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      timd
      last edited by

      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>

      1 Reply Last reply Reply Quote 0
      • X
        xbipin
        last edited by

        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

        1 Reply Last reply Reply Quote 0
        • T
          timd
          last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • W
            wallabybob
            last edited by

            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?

            1 Reply Last reply Reply Quote 0
            • X
              xbipin
              last edited by

              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> 
              
              1 Reply Last reply Reply Quote 0
              • X
                xbipin
                last edited by

                any1 tested the latest snapshots for wireless functionality?

                1 Reply Last reply Reply Quote 0
                • C
                  covex
                  last edited by

                  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.

                  1 Reply Last reply Reply Quote 0
                  • X
                    xbipin
                    last edited by

                    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

                    1 Reply Last reply Reply Quote 0
                    • M
                      matrix200
                      last edited by

                      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.

                      Current network "hardware" :
                      Running 2.2RC in Virtualbox 4.2.16.

                      Retired:
                      ALIX2C2 , 4 gigabyte disk cf card running 2.0 (official release).

                      1 Reply Last reply Reply Quote 0
                      • AhnHELA
                        AhnHEL
                        last edited by

                        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

                        AhnHEL (Angel)

                        1 Reply Last reply Reply Quote 0
                        • X
                          xbipin
                          last edited by

                          @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?

                          1 Reply Last reply Reply Quote 0
                          • M
                            matrix200
                            last edited by

                            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.

                            Current network "hardware" :
                            Running 2.2RC in Virtualbox 4.2.16.

                            Retired:
                            ALIX2C2 , 4 gigabyte disk cf card running 2.0 (official release).

                            1 Reply Last reply Reply Quote 0
                            • X
                              xbipin
                              last edited by

                              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

                              1 Reply Last reply Reply Quote 0
                              • D
                                DeCex
                                last edited by

                                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.

                                1 Reply Last reply Reply Quote 0
                                • X
                                  xbipin
                                  last edited by

                                  i guess its not a wireless issue but its a bridge issue and dhcp isnt able to give out ip to wireless clients

                                  1.JPG
                                  1.JPG_thumb

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    DeCex
                                    last edited by

                                    Here´my firewall rules

                                    1 for LAN
                                    1 for OPT1

                                    LAN.png
                                    LAN.png_thumb
                                    OPT1.png
                                    OPT1.png_thumb

                                    1 Reply Last reply Reply Quote 0
                                    • X
                                      xbipin
                                      last edited by

                                      its the same rules i got, mayb if u read in older posts ull see that all the debug has been done and config is all perfect and firewall is also not blocking any dhcp packets but its just that dhcp isnt replying properly or something like that

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        matrix200
                                        last edited by

                                        I think it is not a firewall issue at all because in my setup I don't have dhcp and just have my laptop with an ip in my lan subnet and unless I do the bridging from lan to wifi interface , I simply can't access it (ping , telnet etc).
                                        Sounds like bridging/routing issue to me.

                                        Current network "hardware" :
                                        Running 2.2RC in Virtualbox 4.2.16.

                                        Retired:
                                        ALIX2C2 , 4 gigabyte disk cf card running 2.0 (official release).

                                        1 Reply Last reply Reply Quote 0
                                        • jimpJ
                                          jimp Rebel Alliance Developer Netgate
                                          last edited by

                                          I would probably also help to see the output of "ifconfig -a" and also a copy of the rules for the wireless interface for both those who say it works, and those who say it doesn't.

                                          Perhaps there is some telling difference between the two.

                                          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                                          Need help fast? Netgate Global Support!

                                          Do not Chat/PM for help!

                                          1 Reply Last reply Reply Quote 0
                                          • X
                                            xbipin
                                            last edited by

                                            doesnt work for me now doesnt even with static ips on wireless bridged to lan

                                            $ ifconfig -a
                                            vr0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
                                            	options=2809 <rxcsum,vlan_mtu,wol_ucast,wol_magic>ether 00:0d:b9:13:47:84
                                            	inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
                                            	inet6 fe80::20d:b9ff:fe13:4784%vr0 prefixlen 64 scopeid 0x1 
                                            	media: Ethernet autoselect (100baseTX <full-duplex>)
                                            	status: active
                                            vr1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                                            	options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether 00:0d:b9:13:47:85
                                            	inet6 fe80::20d:b9ff:fe13:4785%vr1 prefixlen 64 scopeid 0x2 
                                            	media: Ethernet autoselect (100baseTX <full-duplex>)
                                            	status: active
                                            vr2: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500
                                            	options=280b <rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic>ether 00:0d:b9:13:47:86
                                            	media: Ethernet autoselect (none)
                                            	status: no carrier
                                            ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 2290
                                            	ether 00:0b:6b:2c:d4:61
                                            	inet6 fe80::20b:6bff:fe2c:d461%ath0 prefixlen 64 scopeid 0x4 
                                            	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
                                            	ssid "1mbps Blazing" channel 11 (2462 Mhz 11g) bssid 00:0b:6b:2c:d4:61
                                            	authmode WPA2/802.11i privacy MIXED deftxkey 2 TKIP 2:128-bit
                                            	txpower 31.5 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250
                                            	roam:rssi11g 7 roam:rate11g 5 pureg protmode RTSCTS burst dtimperiod 1
                                            pfsync0: flags=41 <up,running>metric 0 mtu 1460
                                            	pfsync: syncdev: lo0 syncpeer: 224.0.0.240 maxupd: 128
                                            enc0: flags=0<> metric 0 mtu 1536
                                            lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
                                            	inet 127.0.0.1 netmask 0xff000000 
                                            	inet6 ::1 prefixlen 128 
                                            	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7 
                                            pflog0: flags=100 <promisc>metric 0 mtu 33204
                                            ng0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
                                            	inet6 fe80::20d:b9ff:fe13:4784%ng0 prefixlen 64 scopeid 0x9 
                                            	inet 92.99.242.71 --> 195.229.252.44 netmask 0xffffffff 
                                            bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                                            	ether aa:44:2b:7b:c5:65
                                            	id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
                                            	maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
                                            	root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
                                            	member: vr0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 1 priority 128 path cost 200000
                                            	member: ath0 flags=143 <learning,discover,autoedge,autoptp>ifmaxaddr 0 port 4 priority 128 path cost 370370</learning,discover,autoedge,autoptp></learning,discover,autoedge,autoptp></up,broadcast,running,simplex,multicast></up,pointopoint,running,noarp,simplex,multicast></promisc></up,loopback,running,multicast></up,running></hostap></up,broadcast,running,promisc,simplex,multicast></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></broadcast,simplex,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></rxcsum,vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,promisc,simplex,multicast> 
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.