<![CDATA[Internal gateway]]>After all this years with network stuff at home i still have problems understanding what the gateway does.

It was always like that, that the router/modem is the gateway.
But i have pfSense running in Hyper-V and setting pfSense as gateway is a problem.
If i have to reboot Hyper-V then i can't access it anymore because there is the "Network Location Awareness Service".
Since pfSense is not running when Hyper-V starts, the NIC is set to public and you can't access the machine anymore trough remote desktop.

So at social.technet.microsoft.com somebody said to set a network device as gateway.

Does that mean the default gateway does not need to be pfsense/router?
Can you set all the PCs, Tabs, Phones, TVs, access points to something else?

]]>https://forum.netgate.com/topic/111855/internal-gatewayRSS for NodeSat, 11 Apr 2026 18:26:04 GMTMon, 20 Feb 2017 14:57:03 GMT60<![CDATA[Reply to Internal gateway on Mon, 20 Feb 2017 19:00:38 GMT]]>No, there is no need to restart it, it will immediately restart itself on its own.

]]>https://forum.netgate.com/post/681191https://forum.netgate.com/post/681191Mon, 20 Feb 2017 19:00:38 GMT<![CDATA[Reply to Internal gateway on Mon, 20 Feb 2017 15:08:57 GMT]]>Ok, then i have to figure out how to do it in Powershell.
But

net stop nlasvc /yes

only stops the service? I have to restart it after that?

So the gateway for all devices in the LAN should be pfSense?

]]>https://forum.netgate.com/post/681133https://forum.netgate.com/post/681133Mon, 20 Feb 2017 15:08:57 GMT<![CDATA[Reply to Internal gateway on Mon, 20 Feb 2017 15:00:16 GMT]]>
  • You can set the location to private via GPO
  • You can run a scheduled task that to
    • 
net stop nlasvc /yes

    a couple of minutes after boot, when the pfSense VM is up and running.

    Both of the above a whole lot better than messing with gateways.

    ]]>    https://forum.netgate.com/post/681131https://forum.netgate.com/post/681131Mon, 20 Feb 2017 15:00:16 GMT