This is a discussion on slack, help with simple ppp dialup within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> I'm just trying to get a simple desktop dialup setup working. I haven't set up any LAN. I'd like ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I'm just trying to get a simple desktop dialup setup working. I haven't set up any LAN. I'd like to be able to use ppp-on/off as a regular user, but for now I just want to get it working for root. I'm running a stock Slack 9.1 install with bare.i. I've run netconfig and told it I just want to setup a loopback connection (for "modem or no net"). I've run pppsetup and given it the usual input. I can run ppp-on as root and get my external modem to dialup and connect. /var/log/messages tells me: CONNECT -- got it Serial connection established. Using interface ppp0 Connect: ppp0 <--> /dev/modem Once connected, If I try to ping the one dns IP in my /etc/resolv.conf, I get: connect: Network is unreachable If I try to ping something else ping www.osnews.com I get ping: unknown host www.osnews.com Trying to traceroute the IP of my DNS listed in /etc/resolv.conf traceroute: findsaddr: Can't find interface Running 'ifconfig -a' lists eth0, lo, and ppp0. In the ppp0 section, there's no "inet" or "UP" lines present like there are in the lo section. Some more (possibly relevant) info from my config files: /etc/resolv.conf: search my_isp.net nameserver 123.456.789.123 /etc/host.conf: order hosts, bind multi on /etc/hosts: 127.0.0.1 localhost 127.0.0.1 me.example.net me /etc/networks: loopback 127.0.0.0 localnet 127.0.0.0 /etc/nsswitch.conf: # [snip] Everything says "files" except hosts: files dns Also, /etc/ppp/options mentions: defaultroute noipdefault Further -- once connected, "netstat -rn" output only lists that one line starting with 127.0.0.1 for the lo interface. That's the same as when I'm *not* connected. Maybe something to do with defaultroute? Any help is appreciated. If there's a trick here, I'll notify the relevant developers of it. Thanks. |
| |||
| John Gabriele wrote: > I'm just trying to get a simple desktop dialup setup working. Hmm... I also just remembered that I have a network card installed (and being recognized by the kernel -- dmesg mentions eth0: NatSemi [snip]) but I'm currently not using it for anything... Could there be some configuring going on (that I don't know about) that is making some wrong assumption based on the fact that the ethernet card is present? |
| |||
| On Tue, 20 Apr 2004 16:24:45 -0400, John Gabriele <john3gz@bestwebz.net> wrote: > Maybe something to do with defaultroute? Have you tried: route del default Just try it before calling ppp. Sebastian -- http://www.hpfsc.de/ - die Seite rund um: Assembler, Bundeswehr, TFT LCDs, Halle/Saale, Fahrradtouren, Neuseeland, Wanderstaat Mauma, Raumschiff USS Nathan, Enemy Room, MLCAD Tutorial |
| |||
| On 2004-04-20, John wrote: > I can run ppp-on as root and get my external modem to dialup and connect. > /var/log/messages tells me: > > CONNECT > -- got it > Serial connection established. > Using interface ppp0 > Connect: ppp0 <--> /dev/modem the serial device connection is ok. the problem is that the internal and external dynamic ip addresses are not established. that is how most dial isp's operate, you sent your username and password using pap authentication and the isp will only give you a ip address once you are verified. check /etc/ppp/pppsetup.txt this has info about your configuration and pap. (further info in /usr/doc/pppsetup.) the /etc/ppp/pap-secrets file simply requires- <dial-up-username> * <dial-up-password> > Once connected, If I try to ping the one dns IP in my /etc/resolv.conf, > I get: > > connect: Network is unreachable network is unreachable because no ip addresses internal (you) and external (the isp) are set. In the options file put- name <dial-up-username> example- > Also, /etc/ppp/options mentions: > defaultroute > noipdefault name "rick" > Further -- once connected, "netstat -rn" output only lists that one line > starting with 127.0.0.1 for the lo interface. That's the same as when I'm > *not* connected. no ppp ip address. hth, keith. |
| |||
| On 2004-04-21, Otako wrote: the /etc/ppp/pap-secrets file simply requires- > ><dial-up-username> * <dial-up-password> > In the options file put- > name "dial-up-username" just to clarify things. /etc/ppp/pap-secrets is the pap authentication file. the purpose of name <dial-up-username> in the /etc/ppp/options file is that it is a "pointer" to your "identity" in the paps-secret file that ppp requires for sending to the isp. so a pap-secrets file may be correct but if there is no name in the options file ppp will not send any username or password. |
| |||
| On Tue, 20 Apr 2004 16:24:45 -0400, John Gabriele <john3gz@bestwebz.net> wrote: >I'm just trying to get a simple desktop dialup setup working. I haven't set >up any LAN. I'd like to be able to use ppp-on/off as a regular user, but for >now I just want to get it working for root. I'm running a stock Slack 9.1 >install with bare.i. > >I've run netconfig and told it I just want to setup a loopback connection >(for "modem or no net"). > >I've run pppsetup and given it the usual input. > >I can run ppp-on as root and get my external modem to dialup and connect. >/var/log/messages tells me: > > CONNECT > -- got it > Serial connection established. > Using interface ppp0 > Connect: ppp0 <--> /dev/modem > > >Once connected, If I try to ping the one dns IP in my /etc/resolv.conf, >I get: > > connect: Network is unreachable >Any help is appreciated. If there's a trick here, I'll notify the relevant >developers of it. Thanks. I had a similar problem getting my dialup ppp going. It was my firewall. When the ppp0 gets established, the firewall needs to be restarted to allow the ppp0 interface. The whole thing is usually done in the /etc/ppp/ip-up script. Do you have a firewall going? If so, stop it and see if you can connect with ppp0. -- I'm not really a human, but I play one on earth. http://zentara.net/japh.html |
| |||
| zentara wrote: > On Tue, 20 Apr 2004 16:24:45 -0400, John Gabriele <john3gz@bestwebz.net> > wrote: > > >>I'm just trying to get a simple desktop dialup setup working. I haven't set >>up any LAN. I'd like to be able to use ppp-on/off as a regular user, but for >>now I just want to get it working for root. I'm running a stock Slack 9.1 >>install with bare.i. >> >> [snip] > > I had a similar problem getting my dialup ppp going. It was my firewall. > When the ppp0 gets established, the firewall needs to be restarted to > allow the ppp0 interface. The whole thing is usually done in the > /etc/ppp/ip-up script. > > > Do you have a firewall going? If so, stop it and see if you can connect > with ppp0. > Thanks for the reply zentara. No. I've got no /etc/rc.d/rc.firewall script, and rc.ip_forward isn't even executable. |
| |||
| Otako wrote: > On 2004-04-21, Otako wrote: > the /etc/ppp/pap-secrets file simply requires- > >><dial-up-username> * <dial-up-password> > > >>In the options file put- > > >>name "dial-up-username" > > > just to clarify things. > > /etc/ppp/pap-secrets is the pap authentication file. > > > the purpose of name <dial-up-username> in the /etc/ppp/options > file is that it is a "pointer" to your "identity" in the > paps-secret file that ppp requires for sending to the isp. > > so a pap-secrets file may be correct but if there is no name > in the options file ppp will not send any username or password. > Thanks for the replies Otako. What you just wrote seems weird -- I mean, I wonder why there's duplication of data there? Though, yes, I had my dial-up-username both in the options file and in the pap-secrets file. What's also weird is, as a test I intentionally misspelled my dialup username in /etc/ppp/options, and I get the same output from /var/log/messages as before. Also, I just noticed in /etc/ppp/pppsetup.txt (sic): | | ATENTION: I couldn't find 'PPP' in the kernel or as a module. | You'll need 'PPP' in the kernel or as a module to make a PPP connection. | I guess this is just because I've got hotplug set up (comes installed and enabled with Slack 9.1). Before running ppp-go, "lsmod | grep ppp" doesn't list anything. While ppp-go is connecting, lsmod shows: ppp_generic xxx 1 (autoclean) slhc xxx 0 (autoclean) [generic] After ppp-go has me connected, it shows: ppp_async xxx 1 (autoclean) ppp_generic xxx 3 (autoclean) [ppp_async] slhc xxx 0 (autoclean) [ppp_generic] |
| |||
| Sebastian Stein wrote: > On Tue, 20 Apr 2004 16:24:45 -0400, John Gabriele <john3gz@bestwebz.net> wrote: > >>Maybe something to do with defaultroute? > > > Have you tried: > > route del default > > Just try it before calling ppp. > > Sebastian Thanks Sebastian, but that command replies: SIOCDELRT: No such process ---J --- if attempting to reply via email, remove zees --- |