On 27 Feb 01 at 20:51, J.R. de Jong wrote:
> > > Are you sure you are running this configuration? What says
> > > cat /proc/net/ipx* ? Kernel should not forward anything if you have only
> > > one frame configured... There are some IPX forwarding fixes in 2.4.2-acX,
> > > btw.
Hi Arnaldo,
I have some questions... I have IPX router specification here on
screen and on page 56 it says:
==
The router places the address of the network segment on which packet arrived
into the next available Network Number field. The offset of this
field is easily calculated as 4*n bytes past the end of the IPX header,
where n is the value of the Transport Control field.
==
Code in ac4 stores outgoing interface number here, if I parsed code
correctly... This has another fatal side effect: it is propagated even
back to interface on which type 20 packet arrived, so now even machines
with one interface are network killers :-( (if you have one windows
and twenty such linuxes, each netbios broadcast is seen 21 times on network;
on other side it has nice effect that these linuxes ignore netbios broadcasts
routed by other linuxes).
Either store intrfc->if_netnum into packet before loop with '/* That aren't
in the list */', or do explicit check for ifcs != intrfc. But storing number
before looks better - code in ipxrtr_route_skb() does not know receiving
interface anyway, and you want same number in all copies.
I hope that I missed something obvious. If not, then peoples in larger
networks should add some '&& 0' into pprop code to disable it.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
P.S.: IPX router specification & NLSP 1.1 specification are available at
http://developer.novell.com/devres/langrp/specs.htm.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
