[HELP] pfsense virtual appliance install on virtualbox took over my home router
-
Use the router IP address, not the bogus FQDN invented by Netgear.
-
Use the router IP address, not the bogus FQDN invented by Netgear.
Is that 192.168.1.1 ? because that was what it usually is AND that was what it was pre pfsense install/calamity :(
-
Well, then connect the router directly to PC and change it to something else… The router should be configured as bridge anyway, any routing there just brings mess into your network.
-
Well, then connect the router directly to PC and change it to something else… The router should be configured as bridge anyway, any routing there just brings mess into your network.
The router is already connected directly to my host Windows system. Also is it possible to change pfsense LAN to something else instead of changing my router IP? I will prefer that because as i said..i want to use pfsense only within virtualbox and nothing more….i do not want it to interfere with my hoem network whatsoever...i just want it within virtualbox environment and that alone...to manage the VMs within
Thanks
-
I don't understand what's the point of the pfsense existence there. Of course it is possible to change the LAN IP.
-
I don't understand what's the point of the pfsense existence there. Of course it is possible to change the LAN IP.
As a test environment to test pfsense features?
My planned use of pfsense is in a production environment to manage my servers in a colocation setup…but want to test out certain things and be comfortable with it first.Is that a good use?
-
@uberwebguru:
As a test environment to test pfsense features?
My planned use of pfsense is in a production environment to manage my servers in a colocation setup…but want to test out certain things and be comfortable with it first.As a test environment, your virtualbox networking is completely misconfigured, otherwise this would never have happened as the virtual networks would have no access to the physical LAN.
-
@uberwebguru:
As a test environment to test pfsense features?
My planned use of pfsense is in a production environment to manage my servers in a colocation setup…but want to test out certain things and be comfortable with it first.As a test environment, your virtualbox networking is completely misconfigured, otherwise this would never have happened as the virtual networks would have no access to the physical LAN.
Well that is what i am trying to figure out…what is misconfigured and how to fix it...also remember i installed the pfsense virtual appliance for the virtualbox and it was ready to run..and i setup bridge networking for the pfsense (maybe this is where the mistake is?)...so what step did i mess up?
-
The virtual appliance is designed to provide real firewall/routing for real use. So yes, it is ready to run, just not for what you are doing. Configuring Virtualbox is rather offtopic for this forum.
-
The virtual appliance is designed to provide real firewall/routing for real use. So yes, it is ready to run, just not for what you are doing. Configuring Virtualbox is rather offtopic for this forum.
Ok looks like i am thinking something different here
So if indeed pfsense on virtualbox will control my whole network…so it will act as the new router?What happens to the wifi of the router?
Also will i still be able to manage things with my regular netgear router?
One added thing...is there a way to list all connected devices in pfsense? Tried searching for this in the web GUI and couldn't find it
-
The point is to virtualize the HW. Instead of using a physical router, you use a VM. IOW, you are just complicating things fairly heavily with the virtual machine. With no information about the virtual/physical network configuration, not possible to provide any advise. Suggest to Google pfsense + virtualbox.
-
The point is to virtualize the HW. Instead of using a physical router, you use a VM. IOW, you are just complicating things fairly heavily with the virtual machine. With no information about the virtual/physical network configuration, not possible to provide any advise. Suggest to Google pfsense + virtualbox.
Ok you keep skipping certain questions i keep asking
Alright so will i be able to manage the netgear router interface? because it is the one that controls the pfsense isn't it?
Also in pfsense is there a way to use connected network devices in the web GUI? -
Sigh. If you want to test something in purely virtualized environment, then you should configure your virtualized environment in a way that it does NOT affect your physical network. Bridging is certainly NOT the way to go here for this purpose. As for your Netgear router, already told you that it will just cause mess to have two routers in your network in this way. It should not need to be managed in any way. It would serve purely as an AP/bridge. Not a router. No need to manage anything there. If you need to manage something there, then obviously is CANNOT have the same IP as your pfsense LAN.
As for "connected devices", the question does not make much sense. What information you want?
-
Sigh. If you want to test something in purely virtualized environment, then you should configure your virtualized environment in a way that it does NOT affect your physical network. Bridging is certainly NOT the way to go here for this purpose.
So what do i need to do to only have pfsense in a virtualized environment only? Also did you not just say that is not possible and that pfsense is for real use?
As for "connected devices", the question does not make much sense. What information you want?
On the netgear router web GUI..i can see all connected devices in the network…i can see who is connected to the network....PC...phone...printer etc
Can pfsense do same?
-
1/ Read the virtualbox documentation and some networking basics.
2/ You still did not tell us what are you trying to do with that information and what "connected" means. -
1/ Read the virtualbox documentation and some networking basics.
2/ You still did not tell us what are you trying to do with that information and what "connected" means.Any information is good information whether needed or not
connected means devices in the network..host devices having ip addresses in the network..that is what connected mean…as the name implies...i also gave exmaple of devices that can be connected to a network...this is when the pfsense is the router of the network.The netgear router was able to do this so if the pfsense will be the router then i expect to be able to see a feature like this...something important to have really
-
Eh. Does not go anywhere. See Diagnostics - ARP table (or NDP table). If that is not what you want, then kindly explain what information you want or don't ask awfully generic questions without being able to specify any purpose. If it's important you should be able to tell what's important.
-
Eh. Does not go anywhere. See Diagnostics - ARP table (or NDP table). If that is not what you want, then kindly explain what information you want or don't ask awfully generic questions without being able to specify any purpose. If it's important you should be able to tell what's important.
Anyways back to my purpose..i want to use pfsense so that it can manage the network within virtualbox only and not my home network…i want the router to manage my home network and pfsense manage the virtualbox network
Is this possible?
If yes..then what do i do or what steps do i follow to make this setup?Thanks.
-
still need help…can anyone please help?
-
I don't use the pfsense VM. I have twice before created my own from the 2.01 and 2.02 versions.
The purpose for me was to use the openvpn functions and the PPTP functions, which I can report work very well in VMware.The thing to be careful of, which might effect this install is DHCP.
If done incorrectly a pfsense VM will cause conflict if its trying to assign DHCP on the same domain as another DHCP server (like the one built into you home router) and that might cause the behaviour you described. I always configured my pfsense VM wan port to pick up DHCP from the router. I also had to set the VM WAN port to BRIDGED and replicate the physical characteristics of host so that it was grabbing an IP just like any other computer on the LAN, assigning that to the pfsense VM's WAN and then being sure that none of the subnets I configure for PPTP, openvpn or lan in the VM conflict with the home router. Set up like that, it works fine.
Since then, I have built quite a few physical boxes, so I don't need the VM anymore, but it always worked well.