On Monday 12 March 2007, Amos Shapira wrote:
> On 13/03/07, Oron Peled <[EMAIL PROTECTED]> wrote:
> > First, terminology: s/switching/forwarding/
> >
> > Either:
> > echo 0 > /proc/sys/net/ipv4/ip_forward
> > Or the equivalent:
> > sysctl -w net.ipv4.ip_forward=0
> >
> > Now you can send/receive packets from all your network interfaces
> > but there's no routing for packets among them.
>
> I think what the Shlomi was refering to is that the kernel will
> automatically "optimize away" the hardware layer because it knows that the
> address it sends to is actually its own.
>
> I'm not 100% sure he's right (it used to be that you had to have an
Who do you mean by "he"?
> additional routing entry to achieve that on old systems, and as far as I
> remember today's kernels are smart enough to do that automatically), but if
> he is - is there a way to prevent this?
>
> What puzzels me in the original question is:
> > level, so we can still use higher-level protocols such as TCP/IP?
>
> What did you mean by that? The question seemed to be at the IP/ethernet
> level until now, TCP should go wherever IP will boldly take it....
By TCP/IP I meant the entire protocol stack. Naturally if IP works then TCP
will work as well.
Regards,
Shlomi Fish
---------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Homepage: http://www.shlomifish.org/
Chuck Norris wrote a complete Perl 6 implementation in a day but then
destroyed all evidence with his bare hands, so no one will know his secrets.
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
