Jump to content
|Topic||Stats||Last action by|
|Cleveland crowd protests over 12-year-old shot by police||
|Coca Cola unveils milk that is more ‘nutritious’ and expensive than regular milk||
|Steam Sale (Exploration): Nov. 26 - Dec. 2||
|Duplicate Item Received - What else do I need to do?||
|Uploader brings up old windows style dialog without places||
Posted 01 June 2013 - 23:44
Posted 02 June 2013 - 03:54
Posted 02 June 2013 - 10:26
1)Well you need to allow access to the webgui from the WAN, normally that is not a good idea because the wan is normally the internet/hostile network. You are normally on the lan, private/safe side.
2) Set a static on it, via interfaces - change from dhcp to static.. Pretty straight forward. Do you need a picture?
3) Yeah - but they are double natting, unless you turn off nat on pfsense and just turn it into a firewall/router - but now its going to be a bit more difficult for you current router lan to know how to get to the pfsense lan.
For why do you want to do this? Normally the lan is secure, why should you need to isolate your vms from your lan?
If you did want to do that - then just make pfsense your actual internet router and have multiple segments where you have lan and vm segment, dmz, wireless -- you can have as many segments as you want - then pfsense can firewall between them all while doing nat to the public internet.. And you still accessing the webgui from a lan side interface.
Posted 02 June 2013 - 10:49
Posted 02 June 2013 - 19:55
Or we can go this vm route if you want - but its kind of a pointless step if you ask me.
Posted 03 June 2013 - 00:14
Posted 04 June 2013 - 21:22
Posted 05 June 2013 - 17:02
Posted 05 June 2013 - 22:32
Posted 06 June 2013 - 15:52
Posted 06 June 2013 - 22:33
Posted 07 June 2013 - 03:31
Posted 08 June 2013 - 11:40
Posted 08 June 2013 - 13:31
Posted 09 June 2013 - 18:09