Koozali.org: home of the SME Server

4b6 and ppp: ppp0 not active

Patrick

4b6 and ppp: ppp0 not active
« on: April 14, 2000, 02:57:44 AM »
Hi all,

I'm going insain of the ppp0 not active messages.
what's wrong, is this a know error/bug?
the exact same settings worked with 3.1

noipdefault is on the options file but when I see pppd with ps x|more
then the option noipdefault issn't in row behind pppd.

I've put it in diald.conf, doesn't make any difference. And if the connection is made successfull it looks like a matter of luck.

help please;)

Patrick

Patrick

RE: 4b6 and ppp: ppp0 not active
« Reply #1 on: April 14, 2000, 04:12:25 AM »
This is so weird,

now I've setup e-smith 4b6 to dialin to another ISP and the ppp0 not active errors are completely gone.

Patrick

Charlie Brady

RE: 4b6 and ppp: ppp0 not active
« Reply #2 on: April 14, 2000, 04:56:04 AM »
Patrick wrote:

> I'm going insain of the ppp0 not active messages. what's
> wrong, is this a know error/bug? the exact same settings
> worked with 3.1

What particular ppp0 not active messages are they? Have you looked in the file /var/log/messages for detailed diagnostic messages?

> noipdefault is on the options file but when I see pppd with ps
> x|more then the option noipdefault issn't in row behind pppd.

The /etc/ppp/options file is read *in addition to* the command line parameters which you can see in the ps listing. You shouldn't expect to see it, and it will be active, so you don't need to worry about that.

> I've put it in diald.conf, doesn't make any difference.

You shouldn't expect it to.

> And if the connection is made successfull it looks like
> a matter of luck.

You'll need to see the detailed diagnostics to be able to fix it.

Charlie

Charlie Brady

RE: 4b6 and ppp: ppp0 not active
« Reply #3 on: April 14, 2000, 04:57:31 AM »
Patrick wrote:

> This is so weird,
>
> now I've setup e-smith 4b6 to dialin to another ISP and the
> ppp0 not active errors are completely gone.

Different ISPs and different access servers are configured differently - some, IMO, incorrectly. Find those log messages and I'll  try to explain the difference.

Charlie

Patrick

RE: 4b6 and ppp: ppp0 not active
« Reply #4 on: April 14, 2000, 04:34:23 PM »
Hi Charlie,

this is it;)

Apr 14 00:35:03 inetgw diald: diald startup succeeded
Apr 14 00:35:03 inetgw modprobe: can't locate module tap0
Apr 14 00:35:04 inetgw modprobe: can't locate module tap1
Apr 14 00:35:04 inetgw modprobe: can't locate module tap2
Apr 14 00:35:04 inetgw modprobe: can't locate module tap3
Apr 14 00:35:05 inetgw modprobe: can't locate module tap4
Apr 14 00:35:05 inetgw modprobe: can't locate module tap5
Apr 14 00:35:05 inetgw modprobe: can't locate module tap6
Apr 14 00:35:06 inetgw modprobe: can't locate module tap7
Apr 14 00:35:06 inetgw modprobe: can't locate module tap8
Apr 14 00:35:07 inetgw modprobe: can't locate module tap9
Apr 14 00:35:07 inetgw modprobe: can't locate module tap10
Apr 14 00:35:07 inetgw modprobe: can't locate module tap11
Apr 14 00:35:08 inetgw modprobe: can't locate module tap12
Apr 14 00:35:08 inetgw modprobe: can't locate module tap13
Apr 14 00:35:08 inetgw modprobe: can't locate module tap14
Apr 14 00:35:09 inetgw modprobe: can't locate module tap15
Apr 14 00:35:09 inetgw diald[1463]: start sl0: SIOCSIFMTU: Invalid argument
Apr 14 00:35:24 inetgw diald[1463]: Trigger: udp       212.48.60.7/1024       212.48.41.3/53
Apr 14 00:35:24 inetgw diald[1463]: Calling site 212.48.41.3
Apr 14 00:35:25 inetgw chat[1486]: abort on (BUSY)
Apr 14 00:35:25 inetgw chat[1486]: abort on (ERROR)
Apr 14 00:35:25 inetgw chat[1486]: abort on (NO CARRIER)
Apr 14 00:35:25 inetgw chat[1486]: abort on (NO DIALTONE)
Apr 14 00:35:25 inetgw chat[1486]: abort on (Invalid Login)
Apr 14 00:35:25 inetgw chat[1486]: abort on (Login incorrect)
Apr 14 00:35:25 inetgw chat[1486]: send (ATZ^M)
Apr 14 00:35:25 inetgw chat[1486]: expect (OK)
Apr 14 00:35:25 inetgw chat[1486]: ATZ^M^M
Apr 14 00:35:25 inetgw chat[1486]: OK
Apr 14 00:35:25 inetgw chat[1486]:  -- got it
Apr 14 00:35:25 inetgw chat[1486]: send (ATL0M0DT7500300^M)
Apr 14 00:35:25 inetgw chat[1486]: expect (CONNECT)
Apr 14 00:35:25 inetgw chat[1486]: ^M
Apr 14 00:35:48 inetgw chat[1486]: ATL0M0DT7500300^M^M
Apr 14 00:35:48 inetgw chat[1486]: CONNECT
Apr 14 00:35:48 inetgw chat[1486]:  -- got it
Apr 14 00:35:48 inetgw chat[1486]: send (^M)
Apr 14 00:35:48 inetgw diald[1463]: Connected to site 212.48.41.3
Apr 14 00:35:48 inetgw diald[1463]: Running pppd (pid = 1490).
Apr 14 00:35:49 inetgw pppd[1490]: pppd 2.3.11 started by root, uid 0
Apr 14 00:35:49 inetgw pppd[1490]: Using interface ppp0
Apr 14 00:35:49 inetgw pppd[1490]: Connect: ppp0 <--> /dev/ttyS0
Apr 14 00:35:49 inetgw pppd[1490]: Could not determine remote IP address
Apr 14 00:35:55 inetgw pppd[1490]: Connection terminated.
Apr 14 00:35:55 inetgw pppd[1490]: Connect time 0.0 minutes.
Apr 14 00:35:55 inetgw pppd[1490]: Sent 270 bytes, received 262 bytes.
Apr 14 00:35:55 inetgw pppd[1490]: Exit.
Apr 14 00:35:55 inetgw pppd[1431]: Using interface ppp-1073742908
Apr 14 00:35:55 inetgw pppd[1431]: Connect: ppp-1073742908 <--> /dev/ttyS0
Apr 14 00:35:56 inetgw diald[1463]: start sl0: SIOCSIFMTU: Invalid argument
Apr 14 00:35:56 inetgw diald[1463]: start sl0: SIOCADDRT: File exists
Apr 14 00:35:56 inetgw diald[1463]: stop ppp0: SIOCDELRT: No such process
Apr 14 00:35:56 inetgw kernel: ppp: ppp0 not active
Apr 14 00:35:56 inetgw modprobe: can't locate module ppp-1073742908
Apr 14 00:35:56 inetgw diald[1463]: stop ppp0: SIOCSIFFLAGS: Device not configured
Apr 14 00:35:56 inetgw pppd[1431]: ioctl(SIOCSIFMTU): No such device(19)
Apr 14 00:35:56 inetgw pppd[1431]: tcflush failed: Input/output error
Apr 14 00:35:57 inetgw pppd[1431]: Exit.
Apr 14 00:35:57 inetgw diald[1463]: Delaying 10 seconds before clear to dial.
Apr 14 00:36:07 inetgw diald[1463]: Calling site 212.48.41.3
Apr 14 00:36:08 inetgw chat[1505]: abort on (BUSY)
Apr 14 00:36:08 inetgw chat[1505]: abort on (ERROR)
Apr 14 00:36:08 inetgw chat[1505]: abort on (NO CARRIER)
Apr 14 00:36:08 inetgw chat[1505]: abort on (NO DIALTONE)
Apr 14 00:36:08 inetgw chat[1505]: abort on (Invalid Login)
Apr 14 00:36:08 inetgw chat[1505]: abort on (Login incorrect)
Apr 14 00:36:08 inetgw chat[1505]: send (ATZ^M)
Apr 14 00:36:08 inetgw chat[1505]: expect (OK)
Apr 14 00:36:08 inetgw chat[1505]: ATZ^M^M
Apr 14 00:36:08 inetgw chat[1505]: OK
Apr 14 00:36:08 inetgw chat[1505]:  -- got it
Apr 14 00:36:08 inetgw chat[1505]: send (ATL0M0DT7500300^M)
Apr 14 00:36:09 inetgw chat[1505]: expect (CONNECT)
Apr 14 00:36:09 inetgw chat[1505]: ^M
Apr 14 00:36:42 inetgw chat[1505]: ATL0M0DT7500300^M^M
Apr 14 00:36:42 inetgw chat[1505]: CONNECT
Apr 14 00:36:42 inetgw chat[1505]:  -- got it
Apr 14 00:36:42 inetgw chat[1505]: send (^M)
Apr 14 00:36:42 inetgw diald[1463]: Connected to site 212.48.41.3
Apr 14 00:36:42 inetgw diald[1463]: Running pppd (pid = 1511).
Apr 14 00:36:42 inetgw pppd[1511]: pppd 2.3.11 started by root, uid 0
Apr 14 00:36:42 inetgw pppd[1511]: Using interface ppp0
Apr 14 00:36:42 inetgw pppd[1511]: Connect: ppp0 <--> /dev/ttyS0
Apr 14 00:36:43 inetgw pppd[1511]: Could not determine remote IP address
Apr 14 00:36:49 inetgw pppd[1511]: Connection terminated.
Apr 14 00:36:49 inetgw pppd[1511]: Connect time 0.1 minutes.
Apr 14 00:36:49 inetgw pppd[1511]: Sent 271 bytes, received 254 bytes.
Apr 14 00:36:49 inetgw pppd[1511]: Exit.
Apr 14 00:36:49 inetgw diald[1463]: start sl0: SIOCSIFMTU: Invalid argument
Apr 14 00:36:49 inetgw diald[1463]: start sl0: SIOCADDRT: File exists
Apr 14 00:36:49 inetgw diald[1463]: stop ppp0: SIOCDELRT: No such process
Apr 14 00:36:49 inetgw kernel: ppp: ppp0 not active
Apr 14 00:36:49 inetgw diald[1463]: stop ppp0: SIOCSIFFLAGS: Device not configured


Now, this is the log from the successfull connection the the other ISP:

Apr 14 13:15:11 inetgw diald[391]: Trigger: udp       212.48.60.7/1024     195.241.48.33/53
Apr 14 13:15:11 inetgw diald[391]: Calling site 212.41.128.69
Apr 14 13:15:13 inetgw chat[1183]: abort on (BUSY)
Apr 14 13:15:13 inetgw chat[1183]: abort on (ERROR)
Apr 14 13:15:13 inetgw chat[1183]: abort on (NO CARRIER)
Apr 14 13:15:13 inetgw chat[1183]: abort on (NO DIALTONE)
Apr 14 13:15:13 inetgw chat[1183]: abort on (Invalid Login)
Apr 14 13:15:13 inetgw chat[1183]: abort on (Login incorrect)
Apr 14 13:15:13 inetgw chat[1183]: send (ATZ^M)
Apr 14 13:15:13 inetgw chat[1183]: expect (OK)
Apr 14 13:15:13 inetgw chat[1183]: ATZ^M^M
Apr 14 13:15:13 inetgw chat[1183]: OK
Apr 14 13:15:13 inetgw chat[1183]:  -- got it
Apr 14 13:15:13 inetgw chat[1183]: send (ATL0M0DT7001234^M)
Apr 14 13:15:13 inetgw chat[1183]: expect (CONNECT)
Apr 14 13:15:13 inetgw chat[1183]: ^M
Apr 14 13:15:41 inetgw chat[1183]: ATL0M0DT7001234^M^M
Apr 14 13:15:41 inetgw chat[1183]: CONNECT
Apr 14 13:15:41 inetgw chat[1183]:  -- got it
Apr 14 13:15:41 inetgw chat[1183]: send (^M)
Apr 14 13:15:41 inetgw diald[391]: Connected to site 212.41.128.69
Apr 14 13:15:41 inetgw diald[391]: Running pppd (pid = 1184).
Apr 14 13:15:42 inetgw kernel: PPP: version 2.3.7 (demand dialling)
Apr 14 13:15:42 inetgw kernel: PPP line discipline registered.
Apr 14 13:15:42 inetgw kernel: registered device ppp0
Apr 14 13:15:42 inetgw pppd[1184]: pppd 2.3.11 started by root, uid 0
Apr 14 13:15:42 inetgw pppd[1184]: Using interface ppp0
Apr 14 13:15:42 inetgw pppd[1184]: Connect: ppp0 <--> /dev/ttyS0
Apr 14 13:15:46 inetgw kernel: PPP BSD Compression module registered
Apr 14 13:15:46 inetgw kernel: PPP Deflate Compression module registered
Apr 14 13:15:46 inetgw pppd[1184]: local  IP address 195.241.233.220
Apr 14 13:15:46 inetgw pppd[1184]: remote IP address 212.41.128.68
Apr 14 13:15:46 inetgw diald[391]: New addresses: local 195.241.233.220, remote 212.41.128.68, broadcast 0.0.0.0
Apr 14 13:15:47 inetgw diald[391]: start ppp0: SIOCSIFMTU: Invalid argument
Apr 14 13:18:40 inetgw PAM-securetty[1281]: Couldn't open /etc/securetty
Apr 14 13:18:43 inetgw PAM_pwdb[1281]: (login) session opened for user root by (uid=0)
Apr 14 13:20:46 inetgw e-smith[1323]: Processing event: email-update


and that works great.

Charlie Brady

RE: 4b6 and ppp: ppp0 not active
« Reply #5 on: April 14, 2000, 07:00:22 PM »
Patrick wrote:

You'll notice the critical difference between:

> Apr 14 00:35:49 inetgw pppd[1490]: Connect: ppp0 <--> /dev/ttyS0
> Apr 14 00:35:49 inetgw pppd[1490]: Could not determine remote IP address
> Apr 14 00:35:55 inetgw pppd[1490]: Connection terminated.
> Apr 14 00:35:55 inetgw pppd[1490]: Connect time 0.0 minutes.

and

> Apr 14 13:15:42 inetgw pppd[1184]: Connect: ppp0 <--> /dev/ttyS0
> Apr 14 13:15:46 inetgw kernel: PPP BSD Compression module registered
> Apr 14 13:15:46 inetgw kernel: PPP Deflate Compression module registered
> Apr 14 13:15:46 inetgw pppd[1184]: local IP address 195.241.233.220
> Apr 14 13:15:46 inetgw pppd[1184]: remote IP address 212.41.128.68

The first ISP is not issuing you with an IP address. The only solution is that you will need to supply your own. If your ISP has assigned a permanent IP address, and told you about it, then
add it to the diald.conf template as "a.b.c.d:" - notice the trailing colon. And complain to your technical contact at your ISP about their PPP configuration.

Regards

Charlie

Patrick

RE: 4b6 and ppp: ppp0 not active
« Reply #6 on: April 15, 2000, 02:42:09 PM »
heh,

the weird thing is that this ISP doesn't give fixed IP addresses;)

Patrick
btw. I guess they use bad configuraties dial-in routers.
btw2. with e-smith 3.1 it did work, maybe luck? or did something change with r4

Charlie Brady

RE: 4b6 and ppp: ppp0 not active
« Reply #7 on: April 16, 2000, 06:03:59 PM »
Patrick wrote:

> btw2. with e-smith 3.1 it did work, maybe luck? or did
> something change with r4

The only thing that I am aware of is that the "ipdefault" option is added. Without  "noipdefault" option, some ISPs will allow a link to be setup with 192.168.x.x as the local address. This may work for some e-smith to ISP traffic, but can't work for any direct internet access.

It's a mystery. But if you are up and running, that's a good thing :-)

Charlie

Bart Koppers

RE: 4b6 and ppp: ppp0 not active
« Reply #8 on: April 26, 2000, 11:13:53 PM »
Have the same problem. This Dutch ISP (zonnet.nl) doesn't seem to provide
a serverside IP-address all of the time, just a clientside IP-address (don't ask me why...)
Subsequently, i found something in DejaNews, but haven't (yet) tried this myself however..

Add :10.1.1.1 on the pppd-options line in /etc/diald.conf
or use the file /etc/ppp/peers/zonnet (man pppd ...)

Probably have to change 0.0.0.0:0.0.0.0 to 0.0.0.0:10.1.1.1
in /etc/daild.conf too.
Or maybe both the pppd-options line and this one?

Now the serverside of the PPP link gets the address 10.1.1.1
Wonder if this really works. I will let you know if it does in my e-smith configuration.
(PS: dont forget to patch the /etc/e-smith/templates/etc/diald.conf file if it works)

Regards,
 
Bart