RE: Restricting ports/services to specific interfaces

Perhaps a different (and overly simplistic) way of looking at it would
be to assume that within a subnet, all devices can access all other
devices without going through a bridge or router.  If you have both
interfaces present in the same subnet, then it should make no difference
which interface is used and TCP/IP is just picking one, because it
should make no difference.  If this is not the case, then you really
would need two subnets.

Because DHCP needs to function before the clients TCP/IP stack is fully
initialized, it makes some sense that DNS, Telnet, and other IP
applications would function when DHCP would not.  Are your clients
drawing their default gateway information from DHCP?

Regards
Andy Nolen-Parkhouse

<snip>
Simon,

I believe I'm not explaining the problem very well - or perhaps subnets
is
the answer and I'm just not getting it.
</snip>