News: This forum is now permanently frozen.
Pages: [1]
Topic: Network interface setup in virtualbox  (Read 666 times)
« on: November 19, 2014, 08:36:12 »
dylanh724 *
Posts: 6

UPDATE: Ok, here's my new setup. I read that you have to have 2 network adapters, but read wrong and realized you need ONE physical adapter and ONE virtual one (2 total).

So here is my updated setup (currently trying PFSense, but in essence the same setup, must be shared code):

> DSL Cable + Router (combo from ISP)  @ (DMZ to; DHCP enabled)

>> Router @ (DHCP disabled, WiFi enabled)

>>> Server @ (Running virtualbox of pfsense)

>>>> PFSense @ (WAN) / (LAN, virtual)

I thought I should be able to access PFSense via, but it's timing out and pings are not working, either..

A few notable mentions:
> When I try to setup WAN to dhcp, the web server ends up being http://dhcp/ ..odd...
>> When I try to setup WAN, after IP+mask, it says "Enter the new WAN IPv4 upstream gateway address".. what IS this? Google doesn't have much.. must be a new addition (it's not in youtube tutorials). It requires it, it seems. I'm not sure what to put.

Ok too many guides are saying different things, and I've tried many combos, so I'm rather confused. First, my setup:

Windows 7 x64, using Virtualbox, running latest m0n0wall.
2 physical NIC cards: WiFi + physical connection . Say, server on and router
(physical goes to router, for now, but I can remove it if it's causing issues... I feel that issues should come LATER. If anything, I thought I should at least be able to access the web interface..)

In virtualbox, I have 2 network adapters: NAT (default settings) + Bridged Adapter (wifi adapter)

I installed to virtual HD >> interfaces, I set LAN to em0 and WAN to em1.

I set up m0n0wall LAN ip address to (option #2's setup),

Now I can ping (windows server), but I can't ping back (and the web config page times out), "destination host unreachable". I'll try a local address after this post and edit if something changes, but I really think it has something to do with my virtualbox network interfaces.

Every guide says something different, so I tried to desperately try random combinations Tongue

Again, still testing as I type this, and will edit progress. I hope it's just something stupid I missed.

PS -- I read something about setting a VB adapter to "host only"? If I did that, I'd have 3 adapters..?


Help Smiley Thanks mates
« Last Edit: November 19, 2014, 18:33:51 by dylanh724 »
« Reply #1 on: November 20, 2014, 07:08:05 »
dylanh724 *
Posts: 6

Hmm, no comments? Even a troll to say "WTF U DOING" would guide me showing I'm in the wrong direction Tongue
« Reply #2 on: November 21, 2014, 14:50:33 »
Lee Sharp *****
Posts: 517

You can go out but not back because of the firewall and NAT.  This is intended, and normally what is wanted.  What are you trying to do?
« Reply #3 on: November 26, 2014, 10:00:04 »
dylanh724 *
Posts: 6

I'm trying to make a captive portal like Starbucks style. Here is my revamped layout, super clean, with router info too (replace pfsense with m0n0, been testing both):

Clients can LAN, can ping, can even browse google (the 8.8.8.Cool, but can't browse any other site. Also pinging etc fails. Tracert to doesn't even reach m0n0... but tracert to goes thru m0n0, out to WAN, and replies successfully. What the heck?!

Before I turn on captive portal, I want them to be able to reach WAN ... It's cool if I break down the firewall so that I know they CAN get to WAN, THEN i'll turn on captive portal.
« Reply #4 on: November 27, 2014, 04:13:16 »
Lee Sharp *****
Posts: 517

Your DNS needs to be internal to start.  Set up and on m0n0wall and use the NDS forwarder for local DNS.  You need to resolve DNS to start to go to an IP address to trigger captive portal.
Pages: [1]
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines