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

Access Draytek v120 in PPPoA to PPPoE bridge mode

Scheduled Pinned Locked Moved General pfSense Questions
9 Posts 4 Posters 6.6k 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.
  • R
    rhy7s
    last edited by Jan 27, 2011, 3:39 AM

    I would like to be able to see the configuration interface for the Draytek Vigor 120 when it's attached to the WAN interface in PPPoA to PPPoE bridge mode. I see there was a solution for tomato firmware here - does anyone know how I'd go about duplicating that functionality in pfSense?

    1 Reply Last reply Reply Quote 0
    • S
      SeventhSon
      last edited by Jan 27, 2011, 10:03 AM

      I'm not sure if i understand the question correct, but i think that you need a Virtual IP on the interface. Either you need Proxy ARP or IP Alias (if you are on 2.0).

      http://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses%3F

      1 Reply Last reply Reply Quote 0
      • R
        rhy7s
        last edited by Jan 27, 2011, 8:48 PM

        The Draytek passes the real external IP to the WAN interface but that means I can't access it via its private network address. I see that Proxy ARP notes "ProxyARP type IP addresses DO NOT work with the FTP Helper and addon packages such as squid" - do you know what other packages could be affected? I wouldn't want to be compromising FTP further anyway. Would I also have to allow access to RFC1918 networks elsewhere to be able to access the Draytek in front of the WAN interface.

        1 Reply Last reply Reply Quote 0
        • P
          ptt Rebel Alliance
          last edited by Jan 27, 2011, 9:23 PM

          If im not wrong with this you must be Ok: http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall

          1 Reply Last reply Reply Quote 0
          • R
            rhy7s
            last edited by Jan 29, 2011, 7:23 AM

            Thanks for that, will check it out when I get back in a few days.

            1 Reply Last reply Reply Quote 0
            • S
              stephenw10 Netgate Administrator
              last edited by Jan 29, 2011, 12:23 PM

              I use the instructions from here:

              http://doc.pfsense.org/index.php/How_can_i_access_my_PPPoE_Modem_on_WAN

              This works great in 1.2.3. Much easier! However it doesn't last across a reboot.
              I use the V120, execellent device.

              Steve

              1 Reply Last reply Reply Quote 0
              • R
                rhy7s
                last edited by Feb 7, 2011, 10:46 PM

                With the first method I can ping from the firewall to the modem but can't ping or access its web GUI from inside the network. With the second method, pkg_add can't find the package.

                1 Reply Last reply Reply Quote 0
                • S
                  stephenw10 Netgate Administrator
                  last edited by Feb 8, 2011, 1:38 AM Feb 8, 2011, 1:34 AM

                  That's because the package repo address has changed for release.
                  See my thread here for my workaround and more permanent solution.

                  The workaround is to specify the url:

                  pkg_add -r ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/redir.tbz
                  

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • R
                    rhy7s
                    last edited by Feb 8, 2011, 8:33 PM

                    That's great, thanks for that.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                      [[user:consent.lead]]
                      [[user:consent.not_received]]