[oclug] problem with wvdial
Normand Fisher
fishern at ncf.ca
Mon Jun 23 09:05:15 EDT 2003
I wish it was that simple (getting the program to complain) but what I have is wvdial going thru what appears a perfectly normal script that seems to just stop with the following lines (on a terminal window):
> > Entering PPP mode.
> > Async interface address is unnumbered (Ethernet0)
> > Your IP address is 216.191.233.211. MTU is 1500 bytes
> > Header compression will match your system.
> > --> Looks like a welcome message.
> > --> Starting pppd at Thu Jun 19 21:07:11 2003
> > --> pid of pppd: 854
and it sits there, nothing else happens. I have tried with both wvdial and the script provided by NCF (ppp-ncf) with both giving me the exact same "lack" of result.
I've used text connections to ncf for at least ten years from all sort of operating system (Slackware vintage 1992, all flavours of Windows, OS2, Coherent Unix(on a 286!) as well as on another machine running RH9. Only in this Debian Woody distribution do I face this problem. Could be that I missed a step in the installation or ???. The rest of Woody seems to behave somewhat normally but I have to learn more about it.
Normand
----- Original Message -----
From: "Brenda J. Butler" <bjb at istop.com>
Date: Sunday, June 22, 2003 10:57 pm
Subject: Re: [oclug] problem with wvdial
> On Fri, Jun 20, 2003 at 08:50:19PM -0400, Normand Fisher wrote:
> > With some help on the irc channel yesterday, I finally found
> > what appears as a proper way to establish a dial-up connection.
> > In fact it really looks like I did connect (copy of message below).
> > However, I cannot activate any program such as ksirc or konqueror.
> > Looks like they don't know that there is a connection!
>
> When you say, "you can't activate", do you mean, "the apps start up
> but complain that they can't connect"?
>
> If so, perhaps you have to set your nameserver.
>
> Find out the nameserver from your isp, and put that in
> /etc/resolv.conflike this:
>
> nameserver a.b.c.d
>
> If your isp gave you several nameservers, put them all in, each
> on a separate line. Your isp might have given you ip addresses
> for "DNS servers", those are nameservers. (The a.b.c.d above
> represents an ip address.)
>
> If this isn't it, then ask again, but please include your
> linux distro (as segg mentions) and also please describe the
> problem you're having in more detail (see my "do you mean...?",
> above). If appropriate, include the exace error message.
>
> If you're feeling adventurous, you could also plug the error
> message straight into a Google search and see what comes up.
> Sometimes that works and sometimes it doesn't so don't feel
> shy to ask the list again.
>
> When segg says "try ping", he means to try pinging your isp.
> My pppd log gives something like this when I connect:
>
> Jun 22 22:26:55 seal pppd[31806]: local IP address m.n.c.d
> Jun 22 22:26:55 seal pppd[31806]: remote IP address m.n.c.1
> Jun 22 22:26:55 seal pppd[31806]: primary DNS address m.n.o.p
> Jun 22 22:26:55 seal pppd[31806]: secondary DNS address m.n.o.q
>
> (Notice how my isp is telling me what the DNS server addresses is
> right when I connect, I could actually automate the setting of the
> resolv.conf from this information.)
>
>
> You should try to ping the "remote IP address",
> the result should look like:
>
> bjb at tazmaniandevil /tmp 1130 $ ping m.n.c.1
> PING m.n.c.1 (m.n.c.1): 56 data bytes
> 64 bytes from m.n.c.1: icmp_seq=0 ttl=254 time=41.7 ms
> 64 bytes from m.n.c.1: icmp_seq=1 ttl=254 time=36.7 ms
> 64 bytes from m.n.c.1: icmp_seq=2 ttl=254 time=49.6 ms
> 64 bytes from m.n.c.1: icmp_seq=3 ttl=254 time=33.2 ms
> 64 bytes from m.n.c.1: icmp_seq=4 ttl=254 time=50.3 ms
>
>
> That means there is an IP connection between my machine and the
> isp machine that is connected to the other end of my phone line.
> Press Ctl-C to exit from ping, it will give you some stats
> on how many packets were sent/received:
>
> ...
> 64 bytes from m.n.c.1: icmp_seq=40 ttl=254 time=50.1 ms
> 64 bytes from m.n.c.1: icmp_seq=41 ttl=254 time=31.9 ms
>
> --- m.n.c.1 ping statistics ---
> 42 packets transmitted, 40 packets received, 4% packet loss
> round-trip min/avg/max = 29.9/37.9/96.3 ms
> bjb at tazmaniandevil /tmp 1131 $
>
> This ping command is a basic connectivity check, to see if
> you have an IP connection going. It will help to determine
> where next to look.
>
> You wouldn't mess with nameservers till ping was working, for
> instance.
>
> > I am obviuosly missing something but I can't find what to do
> > next. Help would be appreciated as to where to start looking.
> > Thanks
> > Normand
> >
> > Transcript:
> > ...
> > Entering PPP mode.
> > Async interface address is unnumbered (Ethernet0)
> > Your IP address is 216.191.233.211. MTU is 1500 bytes
> > Header compression will match your system.
> > --> Looks like a welcome message.
> > --> Starting pppd at Thu Jun 19 21:07:11 2003
> > --> pid of pppd: 854
> >
> > --
> > OCLUG general discussion list
> > OCLUG at lists.oclug.on.ca
> > http://www.oclug.on.ca/mailman/listinfo/oclug
> ---end quoted text---
>
> --
> bjb at istop dot com
> Welcome to the GNU age! http://www.gnu.org
> 5F82 9855 E247 1F8A 49CD 053E FB03 E77F 2A19 D707
> --
> OCLUG general discussion list
> OCLUG at lists.oclug.on.ca
> http://www.oclug.on.ca/mailman/listinfo/oclug
>
More information about the OCLUG
mailing list