Re: restrict implicit binding to interfaces
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Thu, 30 Oct 2008 03:21:43 -0700 (PDT)
On Oct 29, 8:11 pm, Maxwell Lol <nos...@xxxxxxxxxxx> wrote:
You seem to be under the misconception that addresses belong to
interfaces.
ifconfig(1) associates addresses to interfaces.
Right, and then that address belongs to the machine.
whole. When you bind to an address, you accept packets sent to that
address regardless of what interface they arrive on.
If you configure an interface to one address, it's won't accept
packets addressed to other (unicast) addresses.
Yes, it will. IP would not work if that was the case, you could never
have a functional router.
Some systems allow you to create a second address on the same
interface using a 'virtual interface.'
Unless you put the interface into promiscuous mode using a network sniffer.
You are completely confused. Promiscuous mode is a level 2 thing. It
has nothing whatsoever to do with IP addresses.
Otherwise, it
would be impossible to set up a functional router.
Usually interfaces are connected to different networks.
And usually traffic to any particular IP address flows over many
different networks.
DS
.
- Follow-Ups:
- Re: restrict implicit binding to interfaces
- From: Rick Jones
- Re: restrict implicit binding to interfaces
- References:
- restrict implicit binding to interfaces
- From: Wolfgang Draxinger
- Re: restrict implicit binding to interfaces
- From: David Schwartz
- Re: restrict implicit binding to interfaces
- From: Maxwell Lol
- restrict implicit binding to interfaces
- Prev by Date: Re: restrict implicit binding to interfaces
- Next by Date: Re: BIND -- can't register nameserver
- Previous by thread: Re: restrict implicit binding to interfaces
- Next by thread: Re: restrict implicit binding to interfaces
- Index(es):
Relevant Pages
|