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

    VBOX Environment: Enable SSH and GUI on WAN

    Scheduled Pinned Locked Moved Virtualization
    4 Posts 2 Posters 9.9k 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.
    • P
      ProjectRK
      last edited by

      Hi,

      This is my first post. First of all, yeah, its a bad practice for this one opening up a hole in a WAN interface. But this will be only for my VBOX test environment not for LIVE. This will be a test setup before I will implement it to a live. Back to my point, I'm having trouble accessing administratively my VM pfsense through WAN interface inside VBOX. But my VM pfsense can ping my router and out to the internet.

      Goal: I need to access administratively my vbox pfsense through WAN interface either by SSH or GUI .

      Host:
      OS: Ubuntu 14.04 x64
      VM: Virtualbox
      IP: 192.168.3.10

      Guest:
      OS: pfsense
      Ports: SSH 332 / GUI 333

      Interfaces:

      • em0 / WAN: NAT mode / Intel Pro 1000 MT Server NIC

      • IP: 192.168.0.5 /24

      • GW: 192.168.0.2 /24

      • em1 / LAN: Internal Network mode / Intel Pro 1000 MT Server NIC

      • IP: 192.168.1.1 /24

      My current VM forwarding is
      SSH: 127.0.0.1:1332 -> 192.168.0.5:332
      GUI: 127.0.0.1:1333 -> 192.168.0.5:333

      can anyone help me please?

      Thank you very much in advance

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        By default, WAN is set to block rfc1918 private addresses.  You need to create a VM on the LAN side and then use the VM to configure pfSense to not ignore private IPs on WAN.  There is a way you could shell in and then edit/remove the Block private networks rule, but I don't know it off the top of my head.

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

          @KOM:

          By default, WAN is set to block rfc1918 private addresses.  You need to create a VM on the LAN side and then use the VM to configure pfSense to not ignore private IPs on WAN.  There is a way you could shell in and then edit/remove the Block private networks rule, but I don't know it off the top of my head.

          Thank you very much for your suggestion, it really works in my VM, I could SSH through now. What I did, I uncheck RFC1918 in my WAN interface, then I open a port for it. Only left is the GUI, seems I can't access it.

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

            It's ok now, I managed to figure it out. I will post my solution eventually.

            Thank you for the help

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