Internal network issues between pfSense and Windows in VirtualBox
I have three virtual machines running on Virtual Box. First one is Linux (pfsense) that's acting as a router with two network adapters one bridged and one set to the internal network. The other two vms are Windows 7 that are only connected to the internal network.
Now here is the issue, the Windows 7 machines can see each other, and can communicate. But neither of them can see the pfsense vm. pfsense also can't see them. I've double checked the internal network settings, IPs, subnets everything is correct. But whenever I try to ping the pfsense vm I get the usual message, Destination Host: unreachable. I've disabled Firewalls on the Windows machines, hoping that would fix the issue, nothing.. I can access the internet with the pfsense machine via the Bridged Adapter.
Network Setup:
pfsense (first vm):
- First Adapter: Bridged, DHCP, Promiscuous Mode: Deny
- Second Adapter: Internal Network, Static (192.168.0.254), Promiscuous Mode: Allow VMs
Windows 7 (second vm)
- Second Adapter: Internal Network, Static (192.168.0.15), Promiscuous Mode: Allow VMs
Windows 7 (third vm)
- Second Adapter: Internal Network, Static (192.168.0.30), Promiscuous Mode: Allow VMs
Virtualbox Version: 4.3.20
windows networking virtualbox pfsense
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
migrated from serverfault.com Dec 27 '14 at 21:11
This question came from our site for system and network administrators.
|
show 2 more comments
I have three virtual machines running on Virtual Box. First one is Linux (pfsense) that's acting as a router with two network adapters one bridged and one set to the internal network. The other two vms are Windows 7 that are only connected to the internal network.
Now here is the issue, the Windows 7 machines can see each other, and can communicate. But neither of them can see the pfsense vm. pfsense also can't see them. I've double checked the internal network settings, IPs, subnets everything is correct. But whenever I try to ping the pfsense vm I get the usual message, Destination Host: unreachable. I've disabled Firewalls on the Windows machines, hoping that would fix the issue, nothing.. I can access the internet with the pfsense machine via the Bridged Adapter.
Network Setup:
pfsense (first vm):
- First Adapter: Bridged, DHCP, Promiscuous Mode: Deny
- Second Adapter: Internal Network, Static (192.168.0.254), Promiscuous Mode: Allow VMs
Windows 7 (second vm)
- Second Adapter: Internal Network, Static (192.168.0.15), Promiscuous Mode: Allow VMs
Windows 7 (third vm)
- Second Adapter: Internal Network, Static (192.168.0.30), Promiscuous Mode: Allow VMs
Virtualbox Version: 4.3.20
windows networking virtualbox pfsense
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
migrated from serverfault.com Dec 27 '14 at 21:11
This question came from our site for system and network administrators.
The most probable issue is that pfsense is denying ICMP requests by default. If you can change it to allow pinging, it could work.
– xR34P3Rx
Dec 27 '14 at 21:15
As far as I am aware, pfSense blocks only ICMP request from the outside. Windows treats it as in the pfsense vm doesn't exist, and the other way around. Yet they are on the same network....
– Dzoni
Dec 27 '14 at 21:19
Im assuming they're in the same subnet as well? 192.168.0.0/24?
– xR34P3Rx
Dec 27 '14 at 21:25
Using bridged on any of the clients might not what you need - you need three unique albeit simulated NICs and MACs before three simulated IPs?
– arch-abit
Dec 27 '14 at 21:25
@xR34P3Rx Yes they are all the same /24 on all machines. arch-abit I am using one bridged intergace only on the pfsense machine for the internet connection. I need to create another network, a virtual one, for some experiments. The network will have a Windows Server and a few Windows Clients, with a gateway that is the pfsense machine. Sorry for not clarifying earlier.
– Dzoni
Dec 27 '14 at 21:30
|
show 2 more comments
I have three virtual machines running on Virtual Box. First one is Linux (pfsense) that's acting as a router with two network adapters one bridged and one set to the internal network. The other two vms are Windows 7 that are only connected to the internal network.
Now here is the issue, the Windows 7 machines can see each other, and can communicate. But neither of them can see the pfsense vm. pfsense also can't see them. I've double checked the internal network settings, IPs, subnets everything is correct. But whenever I try to ping the pfsense vm I get the usual message, Destination Host: unreachable. I've disabled Firewalls on the Windows machines, hoping that would fix the issue, nothing.. I can access the internet with the pfsense machine via the Bridged Adapter.
Network Setup:
pfsense (first vm):
- First Adapter: Bridged, DHCP, Promiscuous Mode: Deny
- Second Adapter: Internal Network, Static (192.168.0.254), Promiscuous Mode: Allow VMs
Windows 7 (second vm)
- Second Adapter: Internal Network, Static (192.168.0.15), Promiscuous Mode: Allow VMs
Windows 7 (third vm)
- Second Adapter: Internal Network, Static (192.168.0.30), Promiscuous Mode: Allow VMs
Virtualbox Version: 4.3.20
windows networking virtualbox pfsense
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
I have three virtual machines running on Virtual Box. First one is Linux (pfsense) that's acting as a router with two network adapters one bridged and one set to the internal network. The other two vms are Windows 7 that are only connected to the internal network.
Now here is the issue, the Windows 7 machines can see each other, and can communicate. But neither of them can see the pfsense vm. pfsense also can't see them. I've double checked the internal network settings, IPs, subnets everything is correct. But whenever I try to ping the pfsense vm I get the usual message, Destination Host: unreachable. I've disabled Firewalls on the Windows machines, hoping that would fix the issue, nothing.. I can access the internet with the pfsense machine via the Bridged Adapter.
Network Setup:
pfsense (first vm):
- First Adapter: Bridged, DHCP, Promiscuous Mode: Deny
- Second Adapter: Internal Network, Static (192.168.0.254), Promiscuous Mode: Allow VMs
Windows 7 (second vm)
- Second Adapter: Internal Network, Static (192.168.0.15), Promiscuous Mode: Allow VMs
Windows 7 (third vm)
- Second Adapter: Internal Network, Static (192.168.0.30), Promiscuous Mode: Allow VMs
Virtualbox Version: 4.3.20
windows networking virtualbox pfsense
windows networking virtualbox pfsense
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
asked Dec 27 '14 at 21:09
DzoniDzoni
63110
63110
migrated from serverfault.com Dec 27 '14 at 21:11
This question came from our site for system and network administrators.
migrated from serverfault.com Dec 27 '14 at 21:11
This question came from our site for system and network administrators.
The most probable issue is that pfsense is denying ICMP requests by default. If you can change it to allow pinging, it could work.
– xR34P3Rx
Dec 27 '14 at 21:15
As far as I am aware, pfSense blocks only ICMP request from the outside. Windows treats it as in the pfsense vm doesn't exist, and the other way around. Yet they are on the same network....
– Dzoni
Dec 27 '14 at 21:19
Im assuming they're in the same subnet as well? 192.168.0.0/24?
– xR34P3Rx
Dec 27 '14 at 21:25
Using bridged on any of the clients might not what you need - you need three unique albeit simulated NICs and MACs before three simulated IPs?
– arch-abit
Dec 27 '14 at 21:25
@xR34P3Rx Yes they are all the same /24 on all machines. arch-abit I am using one bridged intergace only on the pfsense machine for the internet connection. I need to create another network, a virtual one, for some experiments. The network will have a Windows Server and a few Windows Clients, with a gateway that is the pfsense machine. Sorry for not clarifying earlier.
– Dzoni
Dec 27 '14 at 21:30
|
show 2 more comments
The most probable issue is that pfsense is denying ICMP requests by default. If you can change it to allow pinging, it could work.
– xR34P3Rx
Dec 27 '14 at 21:15
As far as I am aware, pfSense blocks only ICMP request from the outside. Windows treats it as in the pfsense vm doesn't exist, and the other way around. Yet they are on the same network....
– Dzoni
Dec 27 '14 at 21:19
Im assuming they're in the same subnet as well? 192.168.0.0/24?
– xR34P3Rx
Dec 27 '14 at 21:25
Using bridged on any of the clients might not what you need - you need three unique albeit simulated NICs and MACs before three simulated IPs?
– arch-abit
Dec 27 '14 at 21:25
@xR34P3Rx Yes they are all the same /24 on all machines. arch-abit I am using one bridged intergace only on the pfsense machine for the internet connection. I need to create another network, a virtual one, for some experiments. The network will have a Windows Server and a few Windows Clients, with a gateway that is the pfsense machine. Sorry for not clarifying earlier.
– Dzoni
Dec 27 '14 at 21:30
The most probable issue is that pfsense is denying ICMP requests by default. If you can change it to allow pinging, it could work.
– xR34P3Rx
Dec 27 '14 at 21:15
The most probable issue is that pfsense is denying ICMP requests by default. If you can change it to allow pinging, it could work.
– xR34P3Rx
Dec 27 '14 at 21:15
As far as I am aware, pfSense blocks only ICMP request from the outside. Windows treats it as in the pfsense vm doesn't exist, and the other way around. Yet they are on the same network....
– Dzoni
Dec 27 '14 at 21:19
As far as I am aware, pfSense blocks only ICMP request from the outside. Windows treats it as in the pfsense vm doesn't exist, and the other way around. Yet they are on the same network....
– Dzoni
Dec 27 '14 at 21:19
Im assuming they're in the same subnet as well? 192.168.0.0/24?
– xR34P3Rx
Dec 27 '14 at 21:25
Im assuming they're in the same subnet as well? 192.168.0.0/24?
– xR34P3Rx
Dec 27 '14 at 21:25
Using bridged on any of the clients might not what you need - you need three unique albeit simulated NICs and MACs before three simulated IPs?
– arch-abit
Dec 27 '14 at 21:25
Using bridged on any of the clients might not what you need - you need three unique albeit simulated NICs and MACs before three simulated IPs?
– arch-abit
Dec 27 '14 at 21:25
@xR34P3Rx Yes they are all the same /24 on all machines. arch-abit I am using one bridged intergace only on the pfsense machine for the internet connection. I need to create another network, a virtual one, for some experiments. The network will have a Windows Server and a few Windows Clients, with a gateway that is the pfsense machine. Sorry for not clarifying earlier.
– Dzoni
Dec 27 '14 at 21:30
@xR34P3Rx Yes they are all the same /24 on all machines. arch-abit I am using one bridged intergace only on the pfsense machine for the internet connection. I need to create another network, a virtual one, for some experiments. The network will have a Windows Server and a few Windows Clients, with a gateway that is the pfsense machine. Sorry for not clarifying earlier.
– Dzoni
Dec 27 '14 at 21:30
|
show 2 more comments
1 Answer
1
active
oldest
votes
The Bridged Adapter on the pfsense machine was causing issues. Changed the first adapter on the pfsense machine from Bridged to NAT and that fixed the issue.
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f857525%2finternal-network-issues-between-pfsense-and-windows-in-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Bridged Adapter on the pfsense machine was causing issues. Changed the first adapter on the pfsense machine from Bridged to NAT and that fixed the issue.
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
add a comment |
The Bridged Adapter on the pfsense machine was causing issues. Changed the first adapter on the pfsense machine from Bridged to NAT and that fixed the issue.
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
add a comment |
The Bridged Adapter on the pfsense machine was causing issues. Changed the first adapter on the pfsense machine from Bridged to NAT and that fixed the issue.
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
The Bridged Adapter on the pfsense machine was causing issues. Changed the first adapter on the pfsense machine from Bridged to NAT and that fixed the issue.
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
answered Dec 27 '14 at 22:09
DzoniDzoni
63110
63110
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f857525%2finternal-network-issues-between-pfsense-and-windows-in-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The most probable issue is that pfsense is denying ICMP requests by default. If you can change it to allow pinging, it could work.
– xR34P3Rx
Dec 27 '14 at 21:15
As far as I am aware, pfSense blocks only ICMP request from the outside. Windows treats it as in the pfsense vm doesn't exist, and the other way around. Yet they are on the same network....
– Dzoni
Dec 27 '14 at 21:19
Im assuming they're in the same subnet as well? 192.168.0.0/24?
– xR34P3Rx
Dec 27 '14 at 21:25
Using bridged on any of the clients might not what you need - you need three unique albeit simulated NICs and MACs before three simulated IPs?
– arch-abit
Dec 27 '14 at 21:25
@xR34P3Rx Yes they are all the same /24 on all machines. arch-abit I am using one bridged intergace only on the pfsense machine for the internet connection. I need to create another network, a virtual one, for some experiments. The network will have a Windows Server and a few Windows Clients, with a gateway that is the pfsense machine. Sorry for not clarifying earlier.
– Dzoni
Dec 27 '14 at 21:30