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

    Can't get an ip on my wlan

    Wireless
    3
    8
    1.1k
    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.
    • N
      notaduck
      last edited by

      Hello. i have tried to setup my wifi card http://www.pcworld.com/product/pg/1558988155/detail
      It is no problem to connect to the wifi but i wont handle out ip's  :'(

      This is how i have configured it

      wan re1
      lan re0
      wifi ath0
      bridge lan - wifi

      my firrewall rules is set to allow all lan on bridge,lan and wifi.
      But i cant fugire out what i should do to get an ip when i am accessing the wifi

      Selection_003.png
      Selection_004.png
      Selection_005.png
      Selection_006.png
      Selection_003.png_thumb
      Selection_004.png_thumb
      Selection_005.png_thumb
      Selection_006.png_thumb

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Why are you bridging this in the first place?

        1 Reply Last reply Reply Quote 0
        • N
          notaduck
          last edited by

          to get the two networks on same Lan.
          i have been looking around on some guides and others experiences and they are all bridging the network ?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            @notaduck:

            to get the two networks on same Lan.

            Uhm. Is there actually some reason why this is needed? (Everyone's doing it is not one.) The packets will route just fine between WLAN and LAN without any bridge in place.

            Looking at the screenshots, you just cannot decide what you want to do. WIFI - None/None - no wonder you cannot get any IP there. LAN - Static IPv4. Then bridge - again None/None, yet you assign it as interface?  If you really want to bridge, then you should only assign the bridge to LAN and configure the IP, DHCP and whatnot there. Any bridge member should be None/None. Plus play with the system tunables to move the packet filtering to bridge instead of members.

            1 Reply Last reply Reply Quote 0
            • P
              pLu
              last edited by

              Disable the Bridge0 interface but keep the bridge. You don't need any firewall rules on the bridge in a default configuration.

              Add this rule for DHCP on interface WIFI:

              
              Proto        	Source 		Port 	Destination 		Port
              IPv4 UDP	0.0.0.0 	68 	255.255.255.255 	67
              
              

              It has some drawbacks but is good enough at home. Or listen to doktornotor.

              1 Reply Last reply Reply Quote 0
              • N
                notaduck
                last edited by

                thanks for the help until now!
                i tried to connect a scrren to my pfsense system and i am getting these errors every time i apply or change somthing on ath0( wlan)
                http://s21.postimg.org/m6qfqitmu/pfsense.jpg

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  Yes. I would strongly suggest to stop bridging wireless and wired.

                  1 Reply Last reply Reply Quote 0
                  • P
                    pLu
                    last edited by

                    @notaduck:

                    i tried to connect a scrren to my pfsense system and i am getting these errors every time i apply or change somthing on ath0( wlan)
                    http://s21.postimg.org/m6qfqitmu/pfsense.jpg

                    You don't need a monitor for that, it's in the system log too. It's a common error that you'll just have to live with until they fix it in FreeBSD.

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