blad w stosie tcp/ip ?

[Paweł Sikora]

On Thursday 29 of April 2004 23:20, Arkadiusz Miskiewicz wrote:
> Dnia czw 29. kwietnia 2004 23:02, Paweł Sikora napisał:
> > sprawdzilem to na freebsd i tam wszystko dziala tak jak
> > imho  powinno, czyli 10.0.0.2 nie widzi gatewaya 149.156.0.1.
> > natomiast w linuksie 10.0.0.2 widzi 149.156.0.1 za nim jeszcze
> > zostanie znatowany i uzyska dostep do sieci zewnetrznej.
> >
> > czy ta luka w arpie nie powinna byc zalatana?
>
> To nie luka tylko feature.
>
> net.ipv4.conf.all.arp_filter=1 spróbuj.

ani 0, ani 1 (wedle tego co ponizej) nie zapewni takiej funkcjonalnosci
jaka oferuje *bsd, a ktora jest zapisana w opisie protokolu arp.

arp_filter - BOOLEAN
        1 - Allows you to have multiple network interfaces on the same
        subnet, and have the ARPs for each interface be answered
        based on whether or not the kernel would route a packet from
        the ARP'd IP out that interface (therefore you must use source
        based routing for this to work). In other words it allows control
        of which cards (usually 1) will respond to an arp request.

        0 - (default) The kernel can respond to arp requests with addresses
        from other interfaces. This may seem wrong but it usually makes
        sense, because it increases the chance of successful communication.
        IP addresses are owned by the complete host on Linux, not by
        particular interfaces. Only for more complex setups like load-
        balancing, does this behaviour cause problems.

        arp_filter for the interface will be enabled if at least one of
        conf/{all,interface}/arp_filter is set to TRUE,
        it will be disabled otherwise

proxy_arp - BOOLEAN
        Do proxy arp.
        proxy_arp for the interface will be enabled if at least one of
        conf/{all,interface}/proxy_arp is set to TRUE,
        it will be disabled otherwise

-- 
If you think of MS-DOS as mono, and Windows as stereo,
  then Linux is Dolby Digital and all the music is free...