Re: lo on potato

1999-12-14 Thread Svante Signell
For me eth0 route seems to be set automatically by the kernel, but not lo. I'm using kernel 2.2.12. Marcin Kurc writes: > kernel 2.2.x does "route add -net" automatically. You dont need to specify > it. > The route can be changed by giving full syntax like you said. > > -> /usr/src/linux/Do

Re: lo on potato

1999-12-14 Thread Marcin Kurc
kernel 2.2.x does "route add -net" automatically. You dont need to specify it. The route can be changed by giving full syntax like you said. -> /usr/src/linux/Documentation On Tue, Dec 14, 1999 at 12:33:57AM +0100, Svante Signell wrote: > Yes, > > I had the same problem. The solution was to add

Re: lo on potato

1999-12-13 Thread Svante Signell
Yes, I had the same problem. The solution was to add netmask to the route command in /etc/init.d/network: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 dev lo Also netmask had to be added to my eth0 interface: /sbin/route add -net 192.168.x.y netmask 255.255.255.0 dev eth0 Maybe the new versi

lo on potato

1999-12-13 Thread Evan Moore
i have potato running on two boxes, but the lo interface will not come up, it complains about SIOCADDRT: invalid argument ?? The error is not showing up in syslog. Any1 else have this prob? thanks evan