Re: ppp Routing problem

1999-05-25 Thread John Hasler
Mike Patterson writes: > I'm almost there, thanks to various people's help. The last problem I > have has the symptoms of a routing problem, but ifconfig and route say > differently. Here are the outputs. any clues? > # route > Kernel IP routing table > Destination Gateway Genmask

ppp Routing problem

1999-05-25 Thread Mike Patterson
I'm almost there, thanks to various people's help. The last problem I have has the symptoms of a routing problem, but ifconfig and route say differently. Here are the outputs. any clues? # route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface

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: Kernel 2.2.x: PPP routing problem?

1999-05-19 Thread Kris
In reply to Johnny Thompson: > I had the same problem.. IP masquerade isn't re-reading > the firewall rules after the link goes down. Creating a > null /etc/{wherever}ipmasqueradeislocatedinthisdirectory/ppp > .file. > > touch /etc/ipmasq/ppp .. That should solve your problem.. ;) > > If

Re: Kernel 2.2.x: PPP routing problem?

1999-05-19 Thread Sean
Like a dolt, I didn't even recognize this. I had the exact same problem that Kris has described, and after a reinstall, I noticed it went away "automagically". Of course, I don't have ipmasq installed this time. *doh!* BTW, HTML-mail SUCKS. :) Sean Johnny Thompson wrote: I had the same proble

Re: Kernel 2.2.x: PPP routing problem?

1999-05-19 Thread Johnny Thompson
I had the same problem.. IP masquerade isn't re-reading the firewall rules after the link goes down.  Creating a null /etc/{wherever}ipmasqueradeislocatedinthisdirectory/ppp file. touch /etc/ipmasq/ppp .. That should solve your problem.. ;)  If that doesn't work, uninstall ipmasq because you prob

Re: Kernel 2.2.x: PPP routing problem?

1999-05-18 Thread Kris
In reply to John Pearson: >These [Exim things in ps ax output] should run briefly when you start >your session, and then be gone. > >If they are still running it may be that there is a problem with exim's >setup that is preventing it from quitting in a timely manner, or it may >just be a further s

Re: Kernel 2.2.x: PPP routing problem?

1999-05-18 Thread Kris
{blush} You can tell I follow the digest now... darn. Apologies for the waste of bandwidth, but it's for archive continuity (and so people actually know wts(meg) I was going on about). Re-send, in reply to "Sean" <[EMAIL PROTECTED]>, with the correct subject: > Nope. inetd has been well and

Re: Kernel 2.2.x: PPP routing problem?

1999-05-17 Thread Pollywog
On 17-May-99 Sean wrote: > A quick kludge that might fix your problem (it fixed it on my machine under > hamm, and after I get done upgrading to slink, I'm going to try it there) is > to kill inetd. I think the problem revolves around the netbase script in > the /etc/init.d folder trying to use i

Re: Kernel 2.2.x: PPP routing problem?

1999-05-17 Thread Sean
A quick kludge that might fix your problem (it fixed it on my machine under hamm, and after I get done upgrading to slink, I'm going to try it there) is to kill inetd. I think the problem revolves around the netbase script in the /etc/init.d folder trying to use ifwadm(or something like that) inst

Re: Kernel 2.2.x: PPP routing problem?

1999-05-17 Thread Kris
At 19:35 16/05/1999 +, you wrote: >After I got everything installed, I >immediately downloaded, installed and ran apt-get, and promptly upgraded to >Slink, just as I had done when Slink first went stable. And now I can't use >any of the >2.0.x kernels AND have ppp work. I've tried everything

Re: Kernel 2.2.x: PPP routing problem?

1999-05-16 Thread John Hasler
Kris writes: > # cat /etc/resolv.conf > domain globalnet.co.uk # <- Tried with, without, > search globalnet.co.uk # <- and combinations of. > nameserver 194.126.82.5 > nameserver 194.126.86.9 The 'domain' and 'search' directives won't affect your problem (In fact they are rarely needed at all).

Re: Kernel 2.2.x: PPP routing problem?

1999-05-16 Thread Sean
Sean -Original Message- From: Kris <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Date: Sunday, May 16, 1999 10:58 AM Subject: Re: Kernel 2.2.x: PPP routing problem? >At 08:32 16/05/1999 +, you wrote: > >I have a working ppp on kernel 2.2.9. my pppd command

Re: Kernel 2.2.x: PPP routing problem?

1999-05-16 Thread Kris
At 08:32 16/05/1999 +, you wrote: >I have a working ppp on kernel 2.2.9. my pppd command is > >exec /usr/sbin/pppd /dev/ttyS0 115200 lock modem crtscts \ > asyncmap 0 defaultroute connect $DIALER_SCRIPT >pppd --version >(pppd version 2.3 patch level 5) > >egrep -v '#|^ *$' /etc/ppp/opt

Re: Kernel 2.2.x: PPP routing problem?

1999-05-16 Thread Kris
At 20:21 15/05/1999 +, you wrote: >Ppp is known to have problems with 2.2.X. Indeed it does. *thwap* >How about the far end of the ppp link? Nope; the only thing I can ping or otherwise communicate with is localhost & the dynamic IP which I'm assigned (from /var/log/ppp.log). >Option nam

Re: Kernel 2.2.x: PPP routing problem?

1999-05-15 Thread Wayne Topa
Subject: Kernel 2.2.x: PPP routing problem? Date: Sat, May 15, 1999 at 05:46:14PM +0100 In reply to:Kris Quoting Kris([EMAIL PROTECTED]): > Problem: PPP works fine under kernel 2.0.36; under 2.2.x it connects, but > it seems like no packets go in or out. tcpdump only show

Re: Kernel 2.2.x: PPP routing problem?

1999-05-15 Thread John Hasler
Kris writes: > Problem: PPP works fine under kernel 2.0.36; under 2.2.x it connects, but > it seems like no packets go in or out. Ppp is known to have problems with 2.2.X. > ...not _any_ remote IPs (including my nameservers). How about the far end of the ppp link? > -am and -vj make no differen

Kernel 2.2.x: PPP routing problem?

1999-05-15 Thread Kris
Problem: PPP works fine under kernel 2.0.36; under 2.2.x it connects, but it seems like no packets go in or out. tcpdump only shows what looks like things trying to get out, but not getting anything back (really technical, huh?). I can ping myself (localhost & local IP), but not _any_ remote IPs