routing problem - solved :-)

2002-01-17 Thread Klaus Neumann
Thanks folks! After I discovered linuxconf, and played a little with its network menu, I could suddenly connect to the internet. Any volunteer who would help me to exchange my SuSE router with Debian? Regards, Klaus

Kernel 2.2.x: PPP routing problem - solved!

1999-05-24 Thread Kris
To those who were (or weren't) having the same problem as me (PPP freezes in kernel 2.2), I found the answer after talking with Clifford Kite on comp.os.linux.networking (he didn't suggest it, though, he just prompted me to get on with the diagnosing): The modem UART type wasn't set right. On

Re: routing problem solved

1996-06-12 Thread Bruce Perens
The installation menu provides a prototype network number made from the logical AND of your IP address and your netmask. If the user types in the wrong netmask or overrides the prototype network number (which I think is what happened here), they can get an incorrect value. I'll have to look at this

Re: routing problem solved

1996-06-12 Thread Rick Hawkins
> : NETWORK=129.186.31.38 > > IPADDR as the same as the NETWORK address?? Strange, isn't it? err, forgot about this in the message i just sent. On these machines, i found that i had to use their own address as teh network address, rather than the .0 address; otherwise they wouldn't talk to anyt

Re: routing problem solved

1996-06-12 Thread Rick Hawkins
> The reason the last "route add -net ${NETWORK}" is not working is that it > is expecting a network address (ending in .0) and it is getting a host > address instead. In the above example, change the "NETWORK=129.186.31.38" > line to "NETWORK=129.186.31.0" and things should work. If this is i

Re: routing problem solved

1996-06-12 Thread Gerry Jensen
On Wed, 12 Jun 1996, Rick Hawkins wrote: > Under the beta releases with 1.3.9x, the following file is created: > > #! /bin/sh > ifconfig lo 127.0.0.1 > route add 127.0.0.1 > IPADDR=129.186.31.38 > NETMASK=255.255.255.0 > NETWORK=129.186.31.38 > BROADCAST=129.186.31.255 > GATEWAY=129.186.31.

routing problem solved

1996-06-12 Thread Rick Hawkins
OK, i've got it. but i think this means i've found a bug, or at least something that needs fixing. Under the beta releases with 1.3.9x, the following file is created: #! /bin/sh ifconfig lo 127.0.0.1 route add 127.0.0.1 IPADDR=129.186.31.38 NETMASK=255.255.255.0 NETWORK=129.186.31.38 BROAD