On Thu, May 5, 2011 at 08:26, Joseph L. Casale
jcas...@activenetwerx.com wrote:
Is there a simple way to block access to a windows machine? I'm setting
up a network in a remote, far away location and will have little
physical control. I want to control/stop people from sticking a wifi
router and
In addition to this, and to controlling DHCP, as another poster mentioned,
there is an audit method that may take some time, but can be automated to some
degree.
It's an interesting use of TTLs I saw discussed on another list - you have to
keep track of the TTLs by the hosts on your network
In addition to this, and to controlling DHCP, as another poster mentioned,
there is an audit method that may take some time, but can be automated to some
degree.
It's an interesting use of TTLs I saw discussed on another list - you have to
keep track of the TTLs by the hosts on your network
Is there a simple way to block access to a windows machine? I'm setting
up a network in a remote, far away location and will have little
physical control. I want to control/stop people from sticking a wifi
router and connecting windows machines to the network.
The OS doesn't matter, the
To prevent 'automatic' configuration of routers, pfSense DHCP can be
configured trivially to only issue DHCP leases to known hosts (based on
mac address), but naturally it wouldn't prevent someone from manually
configuring IP settings or mac spoofing.
As J.C. said, it depends on how much
On Thu, May 5, 2011 at 11:56 AM, Karl Fife karlf...@gmail.com wrote:
To prevent 'automatic' configuration of routers, pfSense DHCP can be
configured trivially to only issue DHCP leases to known hosts (based on mac
address), but naturally it wouldn't prevent someone from manually
configuring
On 5/5/11 9:11 AM, Yehuda Katz wrote:
On Thu, May 5, 2011 at 11:56 AM, Karl Fife karlf...@gmail.com
mailto:karlf...@gmail.com wrote:
To prevent 'automatic' configuration of routers, pfSense DHCP can
be configured trivially to only issue DHCP leases to known hosts
(based on mac
