New vmware install, nothing works



  • First off, with VMWare, I was under the impression that it would still work as an actual router. Is this correct? If not, then that solves everything.

    Anyway, I have a PFsense set up in VMWare on a Debian box. Still working on getting debian fully configured, but that's another story.
    So I install PFSense. It boots fine in VMWare, but that's where the problems start.

    I've got 3 NICs. One onboard ethernet (eth0), one PCI-E ethernet (eth1) , and one PCI wireless (eth2).
    Eth0 is currently set as WAN, and it works (IP being reported is 192.168.1.2, which is assigned by an actual router).
    Eth1 is set to 10.0.0.1, dhcp enabled, starting address 10.0.0.2, ending address 10.0.0.9.
    Eth2 isn't set up, at all. Not even on Debian. (But this shouldn't matter, right?)

    When I plug this machine in to eth1, nothing happens. It's Win7, tried both static and dynamic, but I can't access anything.

    What did I do wrong? :(



  • Does Debian have control of eth1? Is it appropriately configured in Debian to pass DHCP traffic to pfSense?

    All your interface names are Linux style rather than FreeBSD/pfSense (unless FreeBSD uses different style interface names when its running as a guest) so its not clear to me where you have configured what you say you have configured.

    I don't have any experience of running pfSense as a guest, but  would presume you would need to do some sort of configuration of the NICs in the host to say what sort of access you want the guests to have to the system NICs (e.g. is a NIC for exclusive use of a host or a guest? if a nic is shared by host and guest does the host route or bridge to the guest? etc).



  • oh uh. I'm still a newb so I don't really know much about what I'm doing. I've only managed to get this far due to tons of googling :(

    eth0 is configured on debian, so I assume by control, you mean something along the lines of does it work on debian. So, yes. I have it set as a static IP though (192.168.1.15) so ssh and whatnot is easier to use. So far that is the only NIC I've set up on debian for any sort of use (eth1 is detected when I run ifconfig, but eth2 is not.)
    I'm not sure how I would go about passing DHCP traffic to pfSense though.

    When I say configured, I basically mean it works. I can get online on my debian box using eth0, but again that's the only one I've even touched so far. In pfSense, I just have eth0 as WAN, eth1 as NIC, and eth2 as opt1, but that's as far in the configuration as I've gotten.

    As far as setting permissions, I'm not entirely sure how to do that either. VMWare currently isn't running as root, so access might be an issue. Debian doesn't allow you to use root except in command line, and I'm not sure how to run VMWare in command line, so I have to log in as a regular user to run it.

    So essentially what you're saying here is that in order for this to work, the internet comes in through Eth0 on Debian. Debian then passes traffic to Eth0 on pfSense. pfSense then distributes packets accordingly through eth1, but Debian needs to be configured to pass traffic onto the connected pc's?

    PS.
    ifconfig results from debian (cleaned up a bit)

    eth0     inet addr:192.168.1.15  Bcast:192.168.1.255  Mask:255.255.255.0
    
    eth1    
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
    
    vmnet1  inet addr:172.16.228.1  Bcast:172.16.228.255  Mask:255.255.255.0
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
    
    vmnet8  inet addr:172.16.131.1  Bcast:172.16.131.255  Mask:255.255.255.0
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
    

    aaand I've found out that if I browse to 172.16.131.1, or 172.16.228.1, I can access my apache website.. But only in debian.

    more edits:
    Bridge. I need to set up a bridge? Between eth0 and one of the vmnet's?



  • I don't know what vm hosting packing you are using. I suggest that the documentation for that package is the appropriate place to be asking those questions.

    I've had an interest in VirtualBox for some time. The VirtualBox manual can be downloaded from http://download.virtualbox.org/virtualbox/3.0.8/UserManual.pdf In there (particularly sections 3.7.7 and 6) you will find some discussion of the issues of using NICs in guest virtual machines and what sorts of things need to be configured in virtualbox to enable networking in guest virtual machines. This might be useful reading to give you an idea of what you will need to configure in whatever host VM package you are using.



  • I'm using VMWare, it doesn't have much documentation for the type of thing I'm trying to accomplish here. The only thing I can really find is how to install pfSense using vmware on Windows. That would probably be a lot easier, but I was enjoying the new challenge of debian. Only problem is there aren't very many helpful resources..

    Maybe if I outline what I'm trying to accomplish here, it would make more sense.

    I essentially want to set up a fileserver that has torrent capabilities, but can also replace my wireless router.

    What it looks like:
    Modem => Debian (hosting pfSense, for the router functions) => Switch => PC1/2/???

    I know, I know, internet facing server is bad. But honestly, the computer I'm currently on was running Vista for 2+ years without a router/firewall and minimal AV software.

    So Debian will have Samba for the network, rTorrent/ruTorrent for downloading torrents (webgui is a must, as it's essentially going to be the seedbox), and I was hoping I could use pfSense in VMWare for a more stable internet experience (Current router is crap, often stops all traffic for 5-10 seconds, disconnects internet, etc etc.. All routers I've ever had have done this, so I'm just tired of them and would really, really like to set one up that doesn't rely on less than 16kb of ram).


Log in to reply