SLES10SP3, eth1, dsl0 . how to UP debug for PPPoE ?

[skoltogyan]

WS------->[eth0_SLES10_eth1_dsl0]----->dlink_2500U_bridge_mode----------------->ISP

Server: SLES10SP3.
Device name: dsl0
Type: DSL

PPPmode=PPP over Ethernet
Ethernet card=eth1
Device Activation=At boot time

[CODE]# pwd
/etc/sysconfig/network/providers

cat provider1

ASKPASSWORD=‘no’
AUTODNS=‘no’
DEFAULTROUTE=‘yes’
DEMAND=‘no’
DSLSUPPORTED=‘yes’
IDLETIME=‘0’
IPADDR=’’
ISDNSUPPORTED=‘no’
MODEMSUPPORTED=‘no’
MODIFYDNS=‘no’
MODIFYIP=‘yes’
PASSWORD=‘XXXXXXXXX’
PHONE=’’
PROVIDER=‘Vega’
REMOTE_IPADDR=’’
USERNAME=‘adso46932’

cd …/

fil099srvlc:/etc/sysconfig/network #
fil099srvlc:/etc/sysconfig/network # cat ifcfg-dsl0
BOOTPROTO=‘none’
DEVICE=‘eth-id-00:16:76:b8:b6:02’
MODEM_IP=‘192.168.1.1’
NAME=‘DSL ’
PPPD_OPTIONS=‘nobsdcomp nodeflate’
PPPMODE=‘pppoe’
PROVIDER=‘provider1’
STARTMODE=‘auto’
UNIQUE=’’
USERCONTROL=‘no’
VPIVCI=’’
[/CODE]

How to activate a debugger and to receive more inorfmation for connection PPPoE ?

Serg

( Problem which I try to decide: PPP connection is broken off also itself not recovered . it occurs about 5. 7 times in a day)

[Jens-U]

Hi Serg,

WS------->[eth0_SLES10_eth1_dsl0]----->dlink_2500U_bridge_mode----------------->ISP
How to activate a debugger and to receive more inorfmation for connection PPPoE ?

depending on the depth of information you want to see, you could set pppd’s debug option (in the “options” file - SLES10SP3 is too outdated even for me, I don’t know if the file is /etc/ppp/options or located elsewhere ) or run a tcpdump on eth1.

Have you considered moving to a supported version of SLES, like SLES11SP3?

Regards,
Jens

[skoltogyan]

[QUOTE=jmozdzen;17291]Hi Serg,

WS------->[eth0_SLES10_eth1_dsl0]----->dlink_2500U_bridge_mode----------------->ISP
How to activate a debugger and to receive more inorfmation for connection PPPoE ?

depending on the depth of information you want to see, you could set pppd’s debug option (in the “options” file - SLES10SP3 is too outdated even for me, I don’t know if the file is /etc/ppp/options or located elsewhere ) or run a tcpdump on eth1.

Have you considered moving to a supported version of SLES, like SLES11SP3?

Regards,
Jens[/QUOTE]
There is no possibility of an upgrade from SLES10sp3 on SLES11SP3.
Reasons:

1. the subscription ended
2. the server is located far and to it access only on ssh on the Internet

[Jens-U]

Hi Serg,

There is no possibility of an upgrade from SLES10sp3 on SLES11SP3. [… reasons …]

I had already guessed there’d be good reasons.

If you need help with the pppd debug output, just let me know.

Regards,
Jens

[skoltogyan]

[QUOTE=jmozdzen;17300]Hi Serg,

There is no possibility of an upgrade from SLES10sp3 on SLES11SP3. [… reasons …]

I had already guessed there’d be good reasons.

If you need help with the pppd debug output, just let me know.

Regards,
Jens[/QUOTE]

Yes, i need help with the pppd debug output.
I will tell in other words: Sometimes the dsl0 interface disappears.
How it I find? - each 3 minutes of cron are launched by script: /root/bin/test
Here the script text :

fil099srvlc:/etc/ppp # cat /root/bin/test
RESULT=‘/var/log/resultmp’
ERRLOG=‘/var/log/ErrorInternet’
#PATTRN=’ 0% packet loss’
PATTRN=‘dsl0’

#/bin/ping 213.227.224.3 -c 1 > $RESULT
/sbin/ifconfig > $RESULT
/bin/cat $RESULT | /bin/grep -q “$PATTRN”
ERRST=$?
#echo “Result=$ERRST”
case $ERRST in
1)
echo " 1 1 1 1 1 1 1 1 " >> /var/log/messages
echo " 2 2 2 2 2 2 2 2 " >> /var/log/messages
echo “-BEGIN -0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0” >> $ERRLOG
/bin/date >> $ERRLOG
cat $RESULT >> $ERRLOG
/sbin/ifdown dsl0
/sbin/ifdown eth1

/sbin/rmmod dl2k

sleep 4

/sbin/modprobe dl2k

/sbin/ifup eth1
sleep 3
ifup dsl0
ifconfig dsl0 mtu 800

/root/ksr/rt

/bin/date >> $ERRLOG
echo "-------the END-------------------------------" >> $ERRLOG
echo " " >> $ERRLOG

esac

If there is no dsl0 interface, to restart it.
The reason - why disappears the dsl0 interface - isn’t clear.

Serg

[Jens-U]

Hi Serg,

The reason - why disappears the dsl0 interface - isn’t clear.

that’s why I suggested running pppd with debug turned on - it will tell you why the link was brought down, i.e. LCP time-outs, dropped physical links, authentication problems, link idle and so on.

From “man pppd”:

debug Enables connection debugging facilities. If this option is given, pppd will log the contents of all control packets sent or received in a readable form. The packets are logged through syslog with facility daemon and level debug. This information can be directed to a file by setting up /etc/syslog.conf appropriately (see syslog.conf(5)).

Regards,
Jens

[skoltogyan]

[QUOTE=jmozdzen;17303]Hi Serg,

The reason - why disappears the dsl0 interface - isn’t clear.

that’s why I suggested running pppd with debug turned on - it will tell you why the link was brought down, i.e. LCP time-outs, dropped physical links, authentication problems, link idle and so on.

From “man pppd”:

Regards,
Jens[/QUOTE]

Thank you.
This is right ? :

fil099srvlc:/srv/samba/vol1/common # cat /etc/ppp/options | grep -i debug

Increase debugging level (same as -d). The debug output is written

debug

Enable debugging code in the kernel-level PPP driver. The argument n

general debug messages, 2 to request that the contents of received

#kdebug n
kdebug 1
fil099srvlc:/srv/samba/vol1/common # cat /etc/ppp/options.pptp | grep -i debug
debug
fil099srvlc:/srv/samba/vol1/common #

?

[Jens-U]

[QUOTE=skoltogyan;17305]Thank you.
This is right ? :

?[/QUOTE]

The statement in /etc/ppp/options should be sufficient, the one in options.pptp not neccessary (you’re not running pptp, as far as I can tell) and setting kdebug sounds a bit overkill at the moment

You’ll need to have the pppd restarted for the changes to take effect. After that, your server’s syslog (/var/log/messages per default) should provide details of pppd’s link handling.

Regards,
Jens