F5F Stay Refreshed Power Users Networks I've successfully installed PFsense.

I've successfully installed PFsense.

I've successfully installed PFsense.

P
peterphph
Member
175
08-03-2023, 12:44 AM
#1
The setup looks reasonable. You're using PFSense's WAN adapter as a bridged connection and an internal network adapter for the Windows VM. Make sure the IP addresses match what you expect in your sandbox environment.
P
peterphph
08-03-2023, 12:44 AM #1

The setup looks reasonable. You're using PFSense's WAN adapter as a bridged connection and an internal network adapter for the Windows VM. Make sure the IP addresses match what you expect in your sandbox environment.

C
163
08-03-2023, 01:00 AM
#2
You're unsure about the purpose of the network setup. Are you aiming for a segment that connects only to the internet, leaving your local LAN inactive? Where is PF-Sense installed, and where should the isolated device be located? What function does this isolated machine serve?
C
Cookie0verDose
08-03-2023, 01:00 AM #2

You're unsure about the purpose of the network setup. Are you aiming for a segment that connects only to the internet, leaving your local LAN inactive? Where is PF-Sense installed, and where should the isolated device be located? What function does this isolated machine serve?

1
1Duduzim
Member
164
08-11-2023, 01:59 PM
#3
It's a kind of sandbox that hides the LAN while still allowing internet access. The O.S VM has its own address range compared to the host, which makes it seem functional. Link: https://forums.virtualbox.org/viewtopic....08#p468780
1
1Duduzim
08-11-2023, 01:59 PM #3

It's a kind of sandbox that hides the LAN while still allowing internet access. The O.S VM has its own address range compared to the host, which makes it seem functional. Link: https://forums.virtualbox.org/viewtopic....08#p468780

C
CrazyBessyCat
Posting Freak
912
08-19-2023, 03:25 PM
#4
I understand your feelings during this difficult period.
C
CrazyBessyCat
08-19-2023, 03:25 PM #4

I understand your feelings during this difficult period.

M
ManMallow
Member
223
08-29-2023, 04:33 AM
#5
In fact, I believed I had it sorted, but it’s not quite that simple. I’m now attempting to create a second interface so it can link to the internet in the same way as interface em1, which is already configured in the pfsense VM settings. Although I set it up correctly for the VM network, connecting my internal VM still isn’t working. Should I assign an IP address to 'Em2'? Yes, I think so. The instruction mentions entering the "WAN upstream gateway address," likely pointing to 10.0.0.127/24, but it keeps flagging it as not an IPv4 address. This seems confusing given em1 is already online.
M
ManMallow
08-29-2023, 04:33 AM #5

In fact, I believed I had it sorted, but it’s not quite that simple. I’m now attempting to create a second interface so it can link to the internet in the same way as interface em1, which is already configured in the pfsense VM settings. Although I set it up correctly for the VM network, connecting my internal VM still isn’t working. Should I assign an IP address to 'Em2'? Yes, I think so. The instruction mentions entering the "WAN upstream gateway address," likely pointing to 10.0.0.127/24, but it keeps flagging it as not an IPv4 address. This seems confusing given em1 is already online.

M
Mr_BookItYT
Member
125
08-29-2023, 11:38 AM
#6
It mentions leaving it blank for a LAN interface. It seems unclear what purpose you have with this second interface. This approach isn't typical; usually, separate LANs are handled by the main router, not one connected directly to the LAN.
M
Mr_BookItYT
08-29-2023, 11:38 AM #6

It mentions leaving it blank for a LAN interface. It seems unclear what purpose you have with this second interface. This approach isn't typical; usually, separate LANs are handled by the main router, not one connected directly to the LAN.

W
Wicket1635
Member
157
09-06-2023, 08:42 AM
#7
I realized it all along. I had been putting too much pressure on myself, but the answer was clear—right there, labeled "Lan". Now I’m working in a fully separate sandbox, just like they do for big systems.
W
Wicket1635
09-06-2023, 08:42 AM #7

I realized it all along. I had been putting too much pressure on myself, but the answer was clear—right there, labeled "Lan". Now I’m working in a fully separate sandbox, just like they do for big systems.

G
GodPlayer312
Member
60
09-07-2023, 09:47 PM
#8
As you mentioned, enterprise would likely keep all LANs on the router or firewall. Anything on the WAN side could potentially be reached unless you manage your NAT rules carefully. The default setup usually permits full access from the LAN to the WAN, so it blocks auto-configuration devices broadcasting to the LAN but won’t stop someone guessing your LAN IPs and connecting directly. NAT will forward those attempts automatically.
G
GodPlayer312
09-07-2023, 09:47 PM #8

As you mentioned, enterprise would likely keep all LANs on the router or firewall. Anything on the WAN side could potentially be reached unless you manage your NAT rules carefully. The default setup usually permits full access from the LAN to the WAN, so it blocks auto-configuration devices broadcasting to the LAN but won’t stop someone guessing your LAN IPs and connecting directly. NAT will forward those attempts automatically.