The problem isn't at the firewall (where indeed I can use rules to block
access), the problem is at the client. If the client is on a normal
network with outside access but also on this closed network then if
there is a gateway offered on the closed network then the client tries
to use that interface to access the internet which is not what I want.
I guess I'll just have to use something else as the dhcp server on that
network.
Thanks
Will
On 16/11/2012 03:18, Zach Underwood wrote:
If you would like to block access out of the subnet just use the firewall.
Zach Underwood
http://zachunderwood.me
On Nov 15, 2012 10:16 PM, "Chris Buechler" <[email protected]
<mailto:[email protected]>> wrote:
On Thu, Nov 15, 2012 at 11:04 AM, Will Wagner
<[email protected] <mailto:[email protected]>> wrote:
> Hello,
>
> I have a pfsense box working well with multiple interfaces. One
of the
> interfaces is an internal network for which there should be no
access
> outside the gateway.
>
> I want to configure pfSense to be a DHCP server on that
interface but I
> don't want it to specify any gateway in the options. If I leave
the gateway
> field blank then the interface address on pfsense is used, and
the UI will
> only allow me to enter an alternative IP address within the range.
>
> How can I make the DHCP server omit option 3 in the DHCP offer?
Short of changing the source code, you can't omit it.
_______________________________________________
List mailing list
[email protected] <mailto:[email protected]>
http://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
