LAN GUI not accessible!
-
This is getting complex! Not helped by the fact that I have sent a few PMs with ForensicGeek so that info isn't available here. ::) Let's keep things public.
The fact that the gateway is showing as down is not good and probably explains why routing is not happening. The gateway status is monitored by pfSense pinging the gateway address so it implies either the gateway is not responding to pings or it can't reply for some reason like a bad route. What is the gateway address? I assume it's a machine on your Uni network. If it's running IDS/IPS it may have objected to the constant pings and stopped replying.
A few things are unclear to me reading back through the thread. So for the sake of clarity:
You are using a single physical host machine and pfSense (and others) exist as VMs running in VirtualBox, yes? You seem to have used the term 'virtual box' where I would expect to see 'virtual machine' which is confusing (to me ;)).
I'm not sure where or how you are testing that things are 'working'. Are you testing from a VM behind pfSense?I have only used virtual box a few times but on each of those occasions the thing that tripped me up was assigning the correct network adapter type for host communication. As I recall the nomenclature used did not make it obvious and the docs were also unclear.
Steve
-
Unless I misunderstood, its working for him now.
-
Yes but I fail to see how adding a DNS entry to one of the VMs will have fixed the pfSense gateway issue. Also 192.168.1.1 should have worked as a DNS server for that VM anyway, unless the WAN gateway is not a DNS server. In which case what is it providing for DNS via DHCP on the WAN?
I agree that there seems to be something more here. We shall see. ;)P.S. W00t! 10K posts. ;D
Steve
-
[[quote]P.S. W00t! 10K posts. ;D
So are you trying to post all over just to catch JimP? -
Do your fingers hurt? ;D
-
Just kind of happened. ;)
Steve
