On Mon, Aug 29, 2016 at 10:39 AM, Alfredo Tapia Sabogal <[email protected]> wrote: > I virtualize a pfsense on my laptop i want to access to internet i believe > that i have to create some rules firewall or nats rules to access from my > lan ip address to my wan ip address how can i aproach that? > > Alfredo Tapia Sabogal > > El ago. 29, 2016 10:34 AM, "WebDawg" <[email protected]> escribió: > >> On Mon, Aug 29, 2016 at 9:31 AM, Alfredo Tapia Sabogal >> <[email protected]> wrote: >> > So if my laptop will be on my lan site 172.16.30.10 /24 and my wan is >> > 192.168.0.x >> > How i create a rule on the firewall or nat to access internet? >> > >> > Regards >> > >> > Alfredo Tapia Sabogal >> > >> >> >> So you have a virtualized instance of pfSense on your laptop and you >> are trying to connect through it? >> >> Is this a separate laptop or is this the system you are currently >> using as a desktop? >> >> Or are you turning a laptop into a router? >> _______________________________________________
You are not giving very many details and it is going to be hard to help you if you do not take the time to explain your setup more. If you want to run a virtualized instance of pfsense locally on a system you have some work to do. Your best bet for the wan connection is to create a bridge for the interface that connects to the internet/wan and add one of the virtualized interfaces to it. You would then configure pfSense to pull the address or what ever you want it to do. I do not know how to configure virtualbox to create another interface on your system so your local system can connect through it. I think you are going to need another bridge interface that you pass through though your virtualization system and set it as the LAN interface inside your virtualized pfSense. You would then tell your system to pull a DHCP address from an interface attached to that bridge. I do not know why you would choose to do this except for lack of resources or experimentation. I have done things like this and while all this is possible sometimes it is not worth it. If you want, explain your main purpose and why you chose to locally virtualize a pfSense system on your desktop and possibly we can see clearer why and possibly give you some better advice. I know little about virtualbox and I do not know about the limitations of its bridging (layer 2) and routing (layer 3) system. Also unless you choose paravirtualized drivers for your pfSense virtualized instance you are creating bottle necks that you may not want. The HVM nic drivers use the CPU of the system to do translation on packets and such. You may also run into a FreeBSD where you need to enable the full packet. Depending on what you already have setup, this may not be an easy task and you may be better off grabbing ANY system and setting up pfSense on it. Also it seems that you do not have experience using pfsense or your chosen virtualization networking stack. You are creating some steep hills which you need to climb, but hills can be fun too and I am just letting you know what you have to deal with. _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
