Navigation

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

    How to access dsl modem from wan / lan

    General pfSense Questions
    6
    8
    4006
    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.
    • H
      hadi57 last edited by

      hi

      i set up my modem in bridge mode, i need to access it from wan / lan, for diagnostic purpose, any body can tel me how?

      help really apreciated

      hadi57

      1 Reply Last reply Reply Quote 0
      • GruensFroeschli
        GruensFroeschli last edited by

        http://faq.pfsense.com
        –> http://doc.pfsense.org/index.php/How_can_i_access_my_PPPoE_Modem_on_WAN

        1 Reply Last reply Reply Quote 0
        • H
          hadi57 last edited by

          thanks for the reply but i am getting the following error:

          Error: FTP Unable to get ftp://ftp.freebsd.org/FreeBSD/ports/i386/packages-7.0-release/Latest/redir.tbz: File unavailabe (e.g., file not found, no access)
          pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0release/Latest/red.tbz' by URL

          thanks in advance

          1 Reply Last reply Reply Quote 0
          • ?
            Guest last edited by

            Upgrade your pfSense image.  You're running an old version.

            1 Reply Last reply Reply Quote 0
            • X
              XIII last edited by

              I get the same error, running 1.2.2, when i invoke auto update it states i am up to date. previously, i was able to access the modem just by typing in the address…

              1 Reply Last reply Reply Quote 0
              • X
                XIII last edited by

                it wants to go to:
                ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0-release/Latest/redir.tbz
                but that path does not exist on the server
                you can go here:
                ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/
                there is no "packages-7.0-release" folder

                1 Reply Last reply Reply Quote 0
                • Cry Havok
                  Cry Havok last edited by

                  You'll need to move to the 1.2.3 RC.

                  1 Reply Last reply Reply Quote 0
                  • O
                    ollopa last edited by

                    Thought I'd reply to this because there was an extra caveat I ran into that might help others with the same problem.
                    In my setup, my WAN interface gets its IP address via DHCP, not PPPoE.  That means that I NAT on the WAN interface, and by default NAT is round-robin.  Adding an ip alias to the WAN interface allowed me to access my DSL modem's web interface, but pfSense started to round-robin NAT on my alias and I started losing connectivity.

                    It is possible to tell pf to NAT only on the main address and not aliases, but pfSense (1.2.x?) does not support the option.  Hopefully there will be GUI support for this option in the future.  Until then, here's how I did it and made it permanent (steps 1 and 4 are only needed on embedded installs):

                    1. mount filesystem as read-write:  mount -w /
                    2. vi /etc/inc/filter.inc
                      find the function filter_nat_rules_generate_if and change
                      $tgt = "($if)";
                      to
                      $tgt = "($if:0)";
                      3)save and exit vi
                      4)remount filesystem as read-only:  mount -r /

                    That changes the NAT rule from something like
                    nat on $wan from 192.168.1.0/24 to any -> (sis1)
                    to
                    nat on $wan from 192.168.1.0/24 to any -> (sis1:0)

                    It's the addition of :0 to the interface name that will tell PF to ignore aliases on the interface and NAT only on the main address.

                    Hopefully somebody else finds this useful.
                    Also, instead of setting up a port redirection on the pfSense router, I configured advanced outbound NAT in a similar way as described in this m0n0wall tutorial: Accessing a DSL or cable modem IP from inside the firewall

                    Seems to be working well.

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

                    Products

                    • Platform Overview
                    • TNSR
                    • pfSense Plus
                    • Appliances

                    Services

                    • Training
                    • Professional Services

                    Support

                    • Subscription Plans
                    • Contact Support
                    • Product Lifecycle
                    • Documentation

                    News

                    • Media Coverage
                    • Press
                    • Events

                    Resources

                    • Blog
                    • FAQ
                    • Find a Partner
                    • Resource Library
                    • Security Information

                    Company

                    • About Us
                    • Careers
                    • Partners
                    • Contact Us
                    • Legal
                    Our Mission

                    We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                    Subscribe to our Newsletter

                    Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                    © 2021 Rubicon Communications, LLC | Privacy Policy