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

    2.1.4 Wireless AP Help

    Scheduled Pinned Locked Moved Wireless
    6 Posts 4 Posters 1.3k 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.
    • D
      DoyleChris
      last edited by

      Just got a Rosewill RNX-G300LX Wireless access card to put in my pfsense box to create a WAP. It has a Ralink RT2561 and Ralink RT2527

      I got it in the computer and it is seen by pfsense and i got most everything setup.
      But when i connect to it i get a IP from the Router but i cant get to the internet.
      Below is a picture of the Dashboard, Interfaces,Rules for Wireless, and Bridge.

      AccesspointRule.PNG
      AccesspointRule.PNG_thumb
      Bridge.PNG
      Bridge.PNG_thumb
      Dashboard.PNG
      Dashboard.PNG_thumb
      Interfaces.PNG
      Interfaces.PNG_thumb

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

        What IP are you pulling? Remember 169.254.x.x is auto config. You need to set an IP on that interface or bridge it to your lan. I never bridged an interface so maybe that is what that up arrow means? Can you ping the firewall? Can you see the firewall's mac address in your comuters arp table? (command: arp -a)

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

          I am pulling my lan addresses 192.168.1.***.

          Im trying to bridge to lan where wired works fine.

          I will try pining next.

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

            I cant ping pfsense thought the wireless but i can see the wireless card mac address on pfsense. I would really like help getting this to work.

            1 Reply Last reply Reply Quote 0
            • L
              Legion
              last edited by

              ping will require a new rule allowing ICMP. Your TCP rule won't pass it.

              Status -> System Logs -> Firewall will show ping being blocked.

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

                Maybe forget the bridging, which just adds complication, until you can get the thing working. Sometimes I wonder why people bother with bridging anyway. Is it so awful to have different IPs on different networks? Perhaps I am missing something.

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