Re: pppd gateway/software suspend
On Mon, 22 Mar 2004, Alessandro Speranza wrote:
> On Mon, 22 Mar 2004, Daniel Pittman wrote:
>>
>> Two other things that may be helpful: if you post the routing table
>> *before* you dial out with ppp,
>
> all right, that's the whole story:
> I start from
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 127.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 127.0.0.1 0.0.0.0 UG 0 0 0 lo
Hrm. That routing table is in a bad way. You route the loopback address
via your Ethernet adapter, and have a default route gatewayed to
127.0.0.1, neither of which are even *close* to right.
[... dial up ...]
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.100.101 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
> 0.0.0.0 127.0.0.1 0.0.0.0 UG 0 0 0 lo
>
> I can't ping anybody but myself and the gateway.
That would be because your gateway is the local machine via loopback,
and Linux will respond to any *local* address regardless of with network
adapter the request comes across.
[...]
> now I'm up and running, like now. In fact, it might be useful to say,
> that I think I started getting these sort of problems after I
> installed and configured netenv, which I did because I move around in
> different network situations.
Well, my guess is that netenv is somehow screwed and is inserting the
*very* broken 'gateway via localhost' bit.
I suggest removing netenv and getting to the point where that default
route no longer shows up.
Once that is working, test the PPP stuff and I reckon it would work just
as you expect. :)
Personally, I use the 'mapping' feature of `ifupdown' to deal with
network location issues these days, and `whereami' before that; you may
want to look into them rather than netenv. I never had good luck, or
feelings, when using it.
[...]
>> and the output of running the same pppd
>> command, but with 'nodetatch' and 'debug' turned on.
>
> Hmmm...that I don't know how to do....I bring pppd up with wvdial, and
> my /etc/ppp/peers/wvdial file is just
>
> noauth
> name wvdial
> usepeerdns
> defaultroute
>
> I added the defaultroute by hand, but I don't know if that's any
> use....I'm really not a ppp expert and every time I try to bring up
> pppd with pon or with pppd call ... I seem to get nothing. That's why
> I like wvdial....bad?
Sure. Well, it's pretty easy to deal with the ppp thing. When you make
a call with wvdial, run ps xfwww as root, which should show you the full
command line that wvdial ran.
Once you know that, as root, you can run that command yourself, adding
those two words to the command line, like this:
] pppd call wvdial [whatever else] nodetech debug
That will make the call, but will not put pppd in the background, and
will show you information useful to debugging.
That said, I don't think it matters at this point; I look dubiously at
netenv and that 'gateway via 127.0.0.1' route...
Daniel
--
Crying loud, you're crawling on the floor
Just a beautiful baby, You're nothing more
-- Switchblade Symphony, _Clown_
Reply to: