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 73.9k 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.
    • 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
                                • AhnHELA
                                  AhnHEL
                                  last edited by

                                  MTU on ath0 is 2290

                                  Is this proper?

                                  Ran the following commands in console to set all interfaces to 1500 mtu including bridge0 and thats how it started to work again for me.

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

                                  Change the vr0 above with your interface name for LAN

                                  $ ifconfig
                                  vr0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
                                  options=2809 <rxcsum,vlan_mtu,wol_ucast,wol_magic>ether xx:xx:xx:xx:xx:xx
                                  inet xxx.xxx.xxx.x netmask 0xfffffff0 broadcast xxx.xxx.xxx.xxx
                                  inet6 xxxx::xxxx:xxxx:xxxx:xxxx%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=284b <rxcsum,txcsum,vlan_mtu,polling,wol_ucast,wol_magic>ether xx:xx:xx:xx:xx:xx
                                  inet6 xxxx::xxxx:xxxx:xxxx:xxxx%vr1 prefixlen 64 scopeid 0x2
                                  inet xxx.xxx.xxx.xxx netmask 0xfffff000 broadcast 255.255.255.255
                                  media: Ethernet autoselect (100baseTX <full-duplex>)
                                  status: active
                                  ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
                                  ether xx:xx:xx:xx:xx:xx
                                  inet6 xxxx::xxxx:xxxx:xxxx:xxxx%ath0 prefixlen 64 scopeid 0x3
                                  media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>status: associated
                                  ssid Taino1 channel 11 (2462 Mhz 11g) bssid xx:xx:xx:xx:xx:xx
                                  authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 3 TKIP 2:128-bit
                                  TKIP 3:128-bit txpower 31.5 scanvalid 60 bgscan bgscanintvl 300
                                  bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode OFF burst
                                  -apbridge 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 0x6
                                  pflog0: flags=100 <promisc>metric 0 mtu 33204
                                  tun0: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                                  inet6 xxxx::xxxx:xxxx:xxxx:xxxx%tun0 prefixlen 64 scopeid 0x9
                                  inet xxx.xxx.xxx.xxx –> xxx.xxx.xxx.xxx netmask 0xffffffff
                                  Opened by PID 446
                                  tun1: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500
                                  inet6 xxxx::xxxx:xxxx:xxxx:xxxx%tun1 prefixlen 64 scopeid 0xa
                                  inet xxx.xxx.xxx.xxx --> xxx.xxx.xxx.xxx netmask 0xffffffff
                                  Opened by PID 453
                                  bridge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
                                  ether xx:xx:xx:xx:xx:xx
                                  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 3 priority 128 path cost 370370</learning,discover,autoedge,autoptp></learning,discover,autoedge,autoptp></up,broadcast,running,simplex,multicast></up,pointopoint,running,multicast></up,pointopoint,running,multicast></promisc></up,loopback,running,multicast></up,running></hostap></up,broadcast,running,promisc,simplex,multicast></full-duplex></rxcsum,txcsum,vlan_mtu,polling,wol_ucast,wol_magic></up,broadcast,running,simplex,multicast></full-duplex></rxcsum,vlan_mtu,wol_ucast,wol_magic></up,broadcast,running,promisc,simplex,multicast>

                                  AhnHEL (Angel)

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

                                    updated to the recent snapshot and the same thing again. dhcp wont work on the wireless. alix, atheros 5212, full install.
                                    ifconfig shows mtu of 2290 on ath0 and on bridge0
                                    also, after upgrade I'm getting error message invalid parameter while loading firewall rules 2 and 3.
                                    Here are those rules from config file (nothing was changed, this is how they are in config file):
                                    <rule><type>pass</type>
                                    <interface>optXXXX</interface>
                                    <max-src-nodes><max-src-states><statetimeout><statetype>keep state</statetype>
                                    <os><source>
                                    <any><destination><any></any></destination></any></os></statetimeout></max-src-states></max-src-nodes></rule>
                                    <rule><type>pass</type>
                                    <interface>opt2</interface>
                                    <max-src-nodes><max-src-states><statetimeout><statetype>keep state</statetype>
                                    <os><source>
                                    <any><destination><any></any></destination></any></os></statetimeout></max-src-states></max-src-nodes></rule>
                                    what these rules do? opt2 is my wireless.

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

                                      Did you run the ifconfig commands i listed above to see if that resolves your wireless problem?

                                      I'd reboot my Alix box and try again myself to see if the commands consistently resolve the issue but my Alix box is remote to my location and I cant afford the downtime if the commands dont help.

                                      AhnHEL (Angel)

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

                                        screenshot in your post, is it before you've recreated the bridge or after?
                                        your card is in promiscuous mode here

                                        ath0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500</up,broadcast,running,promisc,simplex,multicast>
                                        

                                        mine does not have it after I change mtu on it.

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

                                          Screenshot is taken after.

                                          Wont both vr0 and ath0 be in promiscuous mode because they are bridged?

                                          AhnHEL (Angel)

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

                                            I don't know what is going on!  ???
                                            My wireless works right now but vr1 (LAN) mtu is 1500, ath0 mtu is 2290 and bridge0 is 1500.
                                            The only thing I changed was switching from channel 6 to channel 10 in the wireless settings. I'm afraid to reboot my router now!  :)

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.