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

    Access DSL Modem through PPPoE – no longer works in 2.0_RC3

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 2 Posters 2.5k 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.
    • bmeeksB Offline
      bmeeks
      last edited by

      Under pfSense 1.2.3 I was running the setup described in http://forum.pfsense.org/index.php/topic,22330.msg115472.html#msg115472.  This process uses a DSL modem in Bridge Mode and consists of configuring an IP Alias for the firewall's WAN interface in the DSL modem's private LAN range (192.168.1.0/24 in my case).  I used 192.168.1.2 for the alias on the firewall's WAN and 192.168.1.1 on the DSL modem's LAN side.  My real LAN behind the firewall lies in the 192.168.10.0/24 block.

      A couple of firewall rules to permit traffic and an Outbound NAT setup are also required.  The AON rule is first in the NAT chain and takes anything from 192.168.10.0/24 destined for 192.168.1.0/24 and NATs it to be from 192.168.1.2.  The last step was to execute the command ifconfig to set the alias on the WAN interface from the shell (or by including that shell command in the config.xml).  This all worked fine in pfSense 1.2.3 and I could browse to my DSL modem's LAN-side web interface to view stats and configure/restart the modem as necessary.  All of these steps are described along with screenshots in the linked thread.

      When I upgraded to pfSense 2.0-RC3, this configuration ceased to work.  I cannot access the DSL modem from my LAN.  The packets time out.  I see them hit the firewall inbound and get passed by my rule, but that's it.  Oddly, from the shell on the firewall itself I can ping the modem's LAN-side IP of 192.168.1.1 and get a response.  Anyone have an idea what might have changed to pfSense 2.0 to break this setup?  It's like maybe the NAT rules are not processing in the order I think they are ???

      1 Reply Last reply Reply Quote 0
      • M Offline
        Metu69salemi
        last edited by

        Have you read this

        1 Reply Last reply Reply Quote 0
        • bmeeksB Offline
          bmeeks
          last edited by

          @Metu69salemi:

          Have you read this

          I had not seen that.  Thank you very much for the reference.  It should resolve my issue.  It seems I need to work on my pfSense documenation search skills… :D

          1 Reply Last reply Reply Quote 0
          • M Offline
            Metu69salemi
            last edited by

            @bmeeks:

            It seems I need to work on my pfSense documenation search skills… :D

            you're not only one ;)

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