Hi,
> 2) Add a field to the packet queue which holds the interface the packet
> was received on. This is ok, but means all input mechanisms (SLIP,
> loopback, PPP, ethernet) must do this, adding overhead. In addition, in
> systems which support dynamic interfaces (like Linux's IP aliasing), we
> can't guarantee that a pointer will work, because the interface may not
> exist anymore. This is, IMHO, the correct behavior.
>
> I am going to implement 2) for Linux, hopefully by the end of 7 days and
> 7 nights.
You know that the pointer is already there? Since the ip-firewalling in
Linux can be interface name based. The pointer is valid in linux, since
there are notifier calls if the table would change. Generally I think it is
not a good idea to accept packets only if they are addressed to the right
interface. I think it is much better to insert a firewalling rule if you
dont want to receive packets on the wrong interface. Then the choice is up
to the user without additional kerelbloat.
Greetings
Bernd
References:
|
|
