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

    Routing between two pfsense boxes via wireless bridge

    Scheduled Pinned Locked Moved Routing and Multi WAN
    14 Posts 3 Posters 6.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 Offline
      drummer_adair
      last edited by

      Thanks danswartz, I had not thought about that. I will set this up and get back with results.

      Adair

      1 Reply Last reply Reply Quote 0
      • D Offline
        drummer_adair
        last edited by

        I'm waiting for the other end of the link to get connected back up correctly to fully test.

        But a ping from my wireless device back to my desktop was failing, I fired up wireshark and saw that the ping was reaching my desktop but my desktop was not responding…...Yep you guessed it, bone head move. Windows firewall was blocking the pings. I turned if off and can ping my desktop thru my router from my wireless bridge.
        This tells me that PF is setup correctly and should mean everything will work ok once the link is back up.

        Damn windows!

        I will test and post back a final outcome.

        Next time I will test pinging hostes other than windows devices!

        Thanks,
        Adair

        1 Reply Last reply Reply Quote 0
        • D Offline
          danswartz
          last edited by

          good to hear!  everything i was seeing looked 'impossible' :)

          1 Reply Last reply Reply Quote 0
          • D Offline
            drummer_adair
            last edited by

            @danswartz:

            good to hear!  everything i was seeing looked 'impossible' :)

            Why do you say 'impossible'?

            1 Reply Last reply Reply Quote 0
            • D Offline
              danswartz
              last edited by

              I mean it all looked correct - i couldn't see how you could be pinging the LAN IP of  the pfsense but not the host, given what the rules and such looked like.

              1 Reply Last reply Reply Quote 0
              • D Offline
                drummer_adair
                last edited by

                Now I have everything setup just like before and when I try to ping the a host on the other LAN I get a TTL expired in transit..
                Trace routing shows the ip address of the OPT interface of my router.
                From either side I can ping the bridge IP's and bridge interface but not the LAN router or any host IP's.

                this is beginning to get really frustrating.

                Adair

                1 Reply Last reply Reply Quote 0
                • D Offline
                  danswartz
                  last edited by

                  What I wanted to see was the results of a wireshark trace on the host on the remote LAN when you try pinging…

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    drummer_adair
                    last edited by

                    That's just it, I can't even get as far as I was getting before.
                    Before I could ping the LAN interface of the each others router but not a host on the LAN (because of the windows firewall)
                    I'll still do some captures with wireshark later.

                    Thanks,
                    Adair

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      drummer_adair
                      last edited by

                      This is old but I now have this working. (it's actually been working for awhile, just didn't think to update the thread)

                      I had two major problems the entire time I was trying to get this working

                      First with the Ubiquity Bullets you have to put them in Client/Server WDS mode in order for them to do layer two bridging. DOH!

                      Second, at someone in a midst all the testing I screwed my my static route to the other subnet.

                      What I needed was LAN  192.168.2.0/24 via 172.16.10.2.
                      172.16.10.2 being the pfsense routers opt interface on the other side of the bridge.

                      Somehow I had put 172.16.10.3 (my routers opt interface address)

                      Getting the bullets our of a semi/mini nat mode and putting the correct routing statement on each pfsense box fixed everything right up!

                      1 Reply Last reply Reply Quote 0
                      • D Offline
                        danswartz
                        last edited by

                        Cool.

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