Re: Kernel IP routing bug

2000-06-24 Thread Tomi Manninen
On Sat, 24 Jun 2000, Robin Gilks wrote: > On Thu, 22 Jun 2000, you wrote: > > > > The reason it doesn't work is because TCP/IP does not work that > > way. TCP/IP is based on the assumption that every computer on a > > network segment (NOT subnet) can hear all of the other computers > > on the

Re: Kernel IP routing bug

2000-06-24 Thread Robin Gilks
On Thu, 22 Jun 2000, you wrote: [snip] > 2) somewhere in one of the networking HOWTOs is a way to > assign two IP numbers to the same network port. arrange the > subnetting and IP numbers so that all the machines that one of > your remote machines is on the same subnet as one of the IP #s, >

Re: Kernel IP routing bug

2000-06-24 Thread Robin Gilks
On Thu, 22 Jun 2000, you wrote: > > The reason it doesn't work is because TCP/IP does not work that > way. TCP/IP is based on the assumption that every computer on a > network segment (NOT subnet) can hear all of the other computers > on the same segment. It worked fine up to 2.0 series kerne

Re: Kernel IP routing bug

2000-06-24 Thread Richard Adams
On Thu, 22 Jun 2000, [EMAIL PROTECTED] wrote about, Re: Kernel IP routing bug: > The reason it doesn't work is because TCP/IP does not work that > way. TCP/IP is based on the assumption that every computer on a > network segment (NOT subnet) can hear all of the other computers

Re: Kernel IP routing bug

2000-06-22 Thread gray
On 20 Jun 00, at 0:15, Richard Adams wrote: > On Mon, 19 Jun 2000, Robin Gilks wrote about, Kernel IP routing bug: > > Greeting all > > > > Has anyone found a fix yet for the routing bug in 2.2 kernels that I > > highlighted about 5 months ago? > > > >

Kernel IP routing bug?

2000-06-20 Thread kb2shu
Message-Id: 2681_kb2shu From: kb2shu@kb2shu.#sca.ca.usa.noam To: [EMAIL PROTECTED] Saw this on another list, not sure if it will help. - Forwarded message - >From [EMAIL PROTECTED] Tue Jun 20 10:21:54 2000 Received: from delphi.wagate.com [204.137.132.198] by kb2shu.ampr.org (TNOS2.3

Re: Kernel IP routing bug

2000-06-20 Thread Robin Gilks
On Tue, 20 Jun 2000, you wrote: > > Are we talking along the same lines.??? > Hi Richard Yup - thats the one. Been bugging me for months not to mention using an extra port up to avoid in & out on the same interface (seperate TX & RX ports). I spent a long time looking into the code but didn't

Re: Kernel IP routing bug

2000-06-20 Thread Arno Verhoeven
Tomi Manninen OH2BNS wrote: > > The solution is for someone to dig in the kernel networking code and find > out what is going on. I once did that but as the networking code is rather > confusing and the bug doesn't currently affect me, I soon lost interest. > > The other solution is to wait for

Re: Kernel IP routing bug

2000-06-20 Thread Tomi Manninen OH2BNS
On Tue, 20 Jun 2000, Arno Verhoeven wrote: > Robin Gilks wrote: > > > > Has anyone found a fix yet for the routing bug in 2.2 kernels that I > > highlighted about 5 months ago? > > Funny... Last weekend I saw the very same thing on our packet radio > node. I was just about to send a question ab

Re: Kernel IP routing bug

2000-06-20 Thread Arno Verhoeven
Robin Gilks wrote: > > Greeting all > > Has anyone found a fix yet for the routing bug in 2.2 kernels that I > highlighted about 5 months ago? > > At the time there was a lot of prattle about netmasks (total waste of space) > and such where a simple point-to-point route could not be established

Re: Kernel IP routing bug

2000-06-19 Thread Richard Adams
On Mon, 19 Jun 2000, Robin Gilks wrote about, Kernel IP routing bug: > Greeting all > > Has anyone found a fix yet for the routing bug in 2.2 kernels that I > highlighted about 5 months ago? > > At the time there was a lot of prattle about netmasks (total waste of space)

Kernel IP routing bug

2000-06-19 Thread Robin Gilks
Greeting all Has anyone found a fix yet for the routing bug in 2.2 kernels that I highlighted about 5 months ago? At the time there was a lot of prattle about netmasks (total waste of space) and such where a simple point-to-point route could not be established, never mind a subnet. Summary A p