Navigation

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

    No Access from WiFi to WAN

    Wireless
    2
    3
    1001
    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.
    • P
      petzi last edited by

      Hello,

      I'm using a alix 2d13 board with an CM9 (atheros) mini-pcie WiFi Card. My LAN seems to be configured correctly so far - I can go into the internet/WAN.I'm using pfsense 2.1.

      But my WiFi AP (Standalone) doesn't work - I did follow http://www.interspective.net/2012/07/one-pfsense-wireless-config-to-rule.html imo.

      If I connect to the WiWi network by SSID, my (Android 4x, brand new LG F5) phone gathers a IP (it shows connected status), but from pfsense host I can't get a ping to the phone, nor I can go into the internet by phone. On Phone I can see "Registration not possible", unable to setup a stable connection (free translated). Note, only Access from WiFi clients to WAN shall be allowed.

      My WiFi Interface:

      I like to have more than 4 networks and hosts, hence static IPv4 255.255.255.240/28.

      My DNS Settings are:

      and my Rules for the WiFi:

      Here one can see the leases, but it's offline

      Probably the reason we I can't ping the phone from pfsense host (by ssh).

      What did I got wrong here?

      The goal is later to add 2nd WLAN on the same card with VPN and LAN access, also a captive portal for guests. Any hints on this?

      Thanks!

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

        255.255.255.240 is not a valid private IP address. This will cause a lot of problems.  I would stick to 10.x.x.x/8 or 172.16.x.x/12, 192.168.x.x/24 addresses.

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

          @podilarius:

          255.255.255.240 is not a valid private IP address. This will cause a lot of problems.  I would stick to 10.x.x.x/8 or 172.16.x.x/12, 192.168.x.x/24 addresses.

          ah, thank you - this solved my access problem! I have 192.168.255.1/24 now.

          Thanks

          1 Reply Last reply Reply Quote 0
          • First post
            Last post