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

    Wifi and LAN on same subnet (SOLVED)

    Scheduled Pinned Locked Moved Wireless
    45 Posts 4 Posters 26.8k 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.
    • R Offline
      Rickinfl
      last edited by

      Ok Removed

      9. System > Advanced > System Tuneables > net.link.bridge.pfil_member > Changed from 1 to 0

      1 Reply Last reply Reply Quote 0
      • R Offline
        Rickinfl
        last edited by

        Ok.. I'm back :(  But with just a little issue.

        From my computer I can Ping another Computer. I can ping a WiFi, phone, laptop, etc. 
        From my laptop I can ping my Computer, But can't ping any WiFi

        Basically WiFi to WiFi I can't ping. I need this to work because I connect my Phone to a WiFi Device and it can't see it.

        Not sure what to do here.

        1 Reply Last reply Reply Quote 0
        • DerelictD Offline
          Derelict LAYER 8 Netgate
          last edited by

          Probably wifi isolation.

          “Intra-BSS Communication

          If you check Allow intra-BSS communication, wireless clients will be able to see each other directly, instead of routing all traffic through the AP. If clients will only need access to the Internet, it is typically safer to uncheck this. ”

          Excerpt From: Jim Pingle. “pfSense-2.1-book.epub.” iBooks. https://itunes.apple.com/WebObjects/MZStore.woa/wa/viewBook?id=3AC70C08837752AA49E641D5CEB871FE

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • R Offline
            Rickinfl
            last edited by

            That was it!! Working!

            Thanks Again!

            Updated HowTo

            Interfaces > WiFi > Allow intra-BSS communication > Check Box. < For WiFi devices to talk to each other

            1 Reply Last reply Reply Quote 0
            • B Offline
              BananaMan
              last edited by

              Credit goes to Rickinfl for this solution.

              What I have here is based upon what Rickinfl has typed up, but I've changed things up just a bit and added a few steps.  I kept getting locked out when changing settings on the LAN IP, but finally got it figured out.  This works for 2.2.6.

              I'm posting because I thought it may be helpful for those trying to bridge the LAN and WIFI so they're on the same subnet.  Hope this helps.

              Bridging Wifi to LAN Interface

              1- Set up wizard - set the initial LAN IP address to be higher than the final LAN IP, and set the netmask to /30.
              For example, if you want the LAN IP to be 192.168.1.1, set the IP for the LAN to be 192.168.1.50 /30  during this step.
              2- Interfaces > Assign > Add (it will be auto-named Opt1)
              3- Click on Opt1 to set up Wifi Settings
              3.1 Rename to Wifi
              3.2 Enable interface
              3.3 Under “Network-Specific Wireless Configuration” Set mode to “Access Point”
              3.4 Set channel to Operate on
              3.5 Select WIFI name and passphrase
              3.6 Check “Allow intra-BSS Communication”
              3.7 Check “Enable WME”
              4- Interfaces > Assign > Bridges > Create a Bridge [+ Add] >  Selected LAN and Wifi as the interfaces on this bridge > Save
              5- Interfaces > Add new Interface [+ Add] > Opt2 > Set Network port = Bridge > Save
              6- From Interfaces, click on Opt2 to change options
              6.1 Enable Interface
              6.2 Rename to “Bridge”
              6.3 IPv4 Configuration Type = Static IPv4 >
              6.4 IPv4 address = acutual desired IP address of LAN  [must set netmask to 30 for now - will change to 24 later] (example above would be 192.168.1.1)
              6.5 Save
              7- Services > DHCP Server > Turn on DHCP for Bridge > Enabled > Set Range (range with a /30 netmask will be small)
              8- Disable DHCP on LAN and WiFi (if they are enabled)
              9- Firewall > Rules > Added New Rule > Interface > LAN > Source = Protocol = ANY > Bridge Net > Reset to ANY.
              10- Firewall > Rules > Added New Rule > Interface > WiFi > Source = Bridge Net > Protocol = ANY > Rest set to ANY.
              11- Firewall > Rules > Added New Rule > Interface > Bridge > Source = Bridge Net > Protocol = ANY > Rest set to ANY.
              12- From “Interfaces” set the IPv4 Configuration Type for both LAN and Wifi to None.
              13- Router is now reachable by the Bridge IP address (192.168.1.1) and the LAN and WIFI are bridged.
              14- Log into router by Bridge IP and change the netmask to /24
              15- Change DHCP scope options

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