My testsetup is this
V.35 Interface Ethernet Roaring
Penguin
TARGET BOARD =============== LINUX PC1=========== LINUX PC2 (PPPoE
Server)
(Proprietary PPPoE Client)
The Linux PC1 establishes the PPPoE Session and then sends a message
to the
TARGET BOARD to start PPP negotioation. The PPP packets received by
the LINUX PC1 are added with the PPPoE header and are given to LINUX
PC2.
The connection is established successfully and data is also going thro
it fine.
After some random time, the PPPD in LINUX PC2 ie., the server is
Terminating by signal 15, and hence sending a PADT to LINUX PC1.
From where is the PPPD getting the SIGTERM signal in the server?. The
client is not sending anything wrong.? I am using PPPD 2.4.1 in the
server and the Linux Kernel 2.4.18.
Thanks
Vanitha
]Hi All,
]My testsetup is this
How can we know? Perhaps you have aliens beaming rays at your computer?
Seriously, enable debugging on the pppd in the various machines and show
us the output of the logs Perhaps they contain a clue.
I am having the "debug" option to the /etc/ppp/options file. I am
getting other messages like "ipcp up","local ip address.."..etc., in
the /var/log/messages. After that there is only this message
Terminated with signal 15. Are there any other options to enable the
log..??
> I am having the "debug" option to the /etc/ppp/options file. I am
> getting other messages like "ipcp up","local ip address.."..etc., in
> the /var/log/messages. After that there is only this message
> Terminated with signal 15. Are there any other options to enable the
> log..??
You need to post exact (cut-and-paste) copies of the logs before anyone
might be able to diagnose the problem. A narrative won't cut it,
especially one as sparse as the one above.
--
Clifford Kite Email: "echo xvgr_yv...@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* In my book, the first poster to resort to personal abuse in a Usenet
debate loses by default. - Rod Smith */
]un...@string.physics.ubc.ca (Bill Unruh) wrote in message news:<c132g7$p8q$1...@string.physics.ubc.ca>...
You need to tell the system where to send the debug messages.
Put
daemon.*;local2.* /var/log/daemonlog
into /etc/syslog.conf and then do
killall -1 syslogd
^^ do not forget the -1
Then look in /var/log/daemonlog for the messages, or post them here.
Here is the log that i got in /var/log/daemonlog. There is no error
statement before the "Terminating on signal 15" message
eb 23 10:13:34 localhost pppoe-server[2171]: Session 2 created for
client 00:60:e0:01:af:f5 (192.168.0.11) on eth1 using Service-Name ''
Feb 23 10:13:34 localhost pppd[2171]: pppd 2.4.1 started by root, uid
0
Feb 23 10:13:34 localhost pppd[2171]: using channel 8
Feb 23 10:13:34 localhost pppd[2171]: Connect: <--> /dev/pts/5
Feb 23 10:13:34 localhost pppd[2171]: rcvd [LCP ConfReq id=0x1
<asyncmap 0x0> <magic 0x266da3f7> <mrru 1500>]
Feb 23 10:13:34 localhost pppd[2171]: sent [LCP ConfReq id=0x1 <magic
0xd7190ece> <mrru 1500> <endpoint [MAC:00:60:e0:01:83:4a]>]
Feb 23 10:13:34 localhost pppd[2171]: sent [LCP ConfRej id=0x1
<asyncmap 0x0>]
Feb 23 10:13:34 localhost pppd[2171]: rcvd [LCP ConfAck id=0x1 <magic
0xd7190ece> <mrru 1500> <endpoint [MAC:00:60:e0:01:83:4a]>]
Feb 23 10:13:34 localhost pppd[2171]: rcvd [LCP ConfReq id=0x2 <magic
0x266da3f7> <mrru 1500>]
Feb 23 10:13:34 localhost pppd[2171]: sent [LCP ConfAck id=0x2 <magic
0x266da3f7> <mrru 1500>]
Feb 23 10:13:34 localhost pppd[2171]: Using interface ppp1
Feb 23 10:13:34 localhost pppd[2171]: New bundle ppp1 created
Feb 23 10:13:34 localhost pppd[2171]: sent [IPCP ConfReq id=0x1 <addr
10.0.0.1>]
Feb 23 10:13:34 localhost pppd[2171]: rcvd [IPCP ConfReq id=0x1 <addr
0.0.0.0>]
Feb 23 10:13:34 localhost pppd[2171]: sent [IPCP ConfNak id=0x1 <addr
192.168.0.11>]
Feb 23 10:13:34 localhost pppd[2171]: rcvd [IPCP ConfAck id=0x1 <addr
10.0.0.1>]
Feb 23 10:13:34 localhost pppd[2171]: rcvd [IPCP ConfReq id=0x2 <addr
192.168.0.11>]
Feb 23 10:13:34 localhost pppd[2171]: sent [IPCP ConfAck id=0x2 <addr
192.168.0.11>]
Feb 23 10:13:34 localhost pppd[2171]: not replacing existing default
route to eth0 [128.0.2.2]
Feb 23 10:13:34 localhost pppd[2171]: local IP address 10.0.0.1
Feb 23 10:13:34 localhost pppd[2171]: remote IP address 192.168.0.11
Feb 23 10:13:34 localhost pppd[2171]: Script /etc/ppp/ip-up started
(pid 2181)
Feb 23 10:13:34 localhost pppd[2171]: Script /etc/ppp/ip-up finished
(pid 2181), status = 0x0
Feb 23 10:23:34 localhost pppd[2171]: Terminating on signal 15.
Feb 23 10:23:34 localhost pppd[2171]: Script /etc/ppp/ip-down started
(pid 2316)
Feb 23 10:23:34 localhost pppd[2171]: sent [LCP TermReq id=0x2 "User
request"]
Feb 23 10:23:35 localhost pppd[2171]: Script /etc/ppp/ip-down finished
(pid 2316), status = 0x0
Feb 23 10:23:38 localhost pppd[2171]: sent [LCP TermReq id=0x3 "User
request"]
Feb 23 10:23:41 localhost pppd[2171]: Connection terminated.
Feb 23 10:23:41 localhost pppd[2171]: Connect time 10.0 minutes.
Feb 23 10:23:41 localhost pppd[2171]: Sent 2765350 bytes, received 30
bytes.
Feb 23 10:23:41 localhost pppd[2171]: Waiting for 1 child processes...
Feb 23 10:23:41 localhost pppd[2171]: script /usr/sbin/pppoe -n -I
eth1 -e 2:00:60:e0:01:af:f5 -S '', pid 2172
Feb 23 10:23:41 localhost pppoe[2172]: read (asyncReadFromPPP):
Session 2: Input/output error
Feb 23 10:23:41 localhost pppd[2171]: Script /usr/sbin/pppoe -n -I
eth1 -e 2:00:60:e0:01:af:f5 -S '' finished (pid 2172), status = 0x1
Feb 23 10:23:41 localhost pppd[2171]: Exit.
Feb 23 10:23:41 localhost pppoe-server[2155]: Session 2 closed for
client 00:60:e0:01:af:f5 (192.168.0.11) on eth1
Feb 23 10:23:41 localhost pppoe-server[2155]: Sent PADT
> Here is the log that i got in /var/log/daemonlog. There is no error
> statement before the "Terminating on signal 15" message
> Feb 23 10:13:34 localhost pppoe-server[2171]: Session 2 created for
I saw nothing amiss in the preceding log messages, except that you
appear to be trying doing MP over Ethernet, the PPP interface is ppp1
rather than ppp0, and the "Session 2" seems to imply that another
PPPoE session already exists - which might account for ppp0 not being
available, if there's only one link in the MP bundle.
Your over-all setup is very unusual, at least to me (and perhaps to
others as well since at the time I posted this there were no other
replies). However, I freely admit that I don't have an in-depth
understanding of MP, especially MP over Ethernet.
> Feb 23 10:13:34 localhost pppd[2171]: Script /etc/ppp/ip-up finished
> (pid 2181), status = 0x0
> Feb 23 10:23:34 localhost pppd[2171]: Terminating on signal 15.
> Feb 23 10:23:34 localhost pppd[2171]: Script /etc/ppp/ip-down started
> (pid 2316)
> Feb 23 10:23:34 localhost pppd[2171]: sent [LCP TermReq id=0x2 "User
> request"]
> Feb 23 10:23:35 localhost pppd[2171]: Script /etc/ppp/ip-down finished
> (pid 2316), status = 0x0
> Feb 23 10:23:38 localhost pppd[2171]: sent [LCP TermReq id=0x3 "User
> request"]
> Feb 23 10:23:41 localhost pppd[2171]: Connection terminated.
This looks like someone or some process terminated pppd with a SIGTERM.
It's a clean shutdown, not a modem hangup. My first thought is to ask
if there's a cron job running that could be doing something to cause
the shutdown.
> Feb 23 10:23:41 localhost pppd[2171]: Connect time 10.0 minutes.
In your first post you said the time to termination was random. Is
the 10.0 minute connect time just an improbable event?
> Feb 23 10:23:41 localhost pppd[2171]: Sent 2765350 bytes, received 30
> bytes.
How you can send that many bytes and received only 30 is beyond my ken.
> Feb 23 10:23:41 localhost pppd[2171]: Waiting for 1 child processes...
> Feb 23 10:23:41 localhost pppd[2171]: script /usr/sbin/pppoe -n -I
> eth1 -e 2:00:60:e0:01:af:f5 -S '', pid 2172
> Feb 23 10:23:41 localhost pppoe[2172]: read (asyncReadFromPPP):
> Session 2: Input/output error
Apparently pppoe wasn't expecting the pppd termination.
> Feb 23 10:23:41 localhost pppd[2171]: Script /usr/sbin/pppoe -n -I
> eth1 -e 2:00:60:e0:01:af:f5 -S '' finished (pid 2172), status = 0x1
> Feb 23 10:23:41 localhost pppd[2171]: Exit.
> Feb 23 10:23:41 localhost pppoe-server[2155]: Session 2 closed for
> client 00:60:e0:01:af:f5 (192.168.0.11) on eth1
> Feb 23 10:23:41 localhost pppoe-server[2155]: Sent PADT
At this point, all I can say is "Good Luck!"
-- Clifford Kite Email: "echo xvgr_yv...@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Slogan appropriate for a certain well-known software company:
FAILURE IS NOT AN OPTION - it is built into the operating system
and comes bundled with the software. And it attracts maggots. */
]Vanitha <van...@agilis.st.com.sg> wrote:
]> Here is the log that i got in /var/log/daemonlog. There is no error
]> statement before the "Terminating on signal 15" message
]> Feb 23 10:13:34 localhost pppoe-server[2171]: Session 2 created for
]> client 00:60:e0:01:af:f5 (192.168.0.11) on eth1 using Service-Name ''
]> Feb 23 10:13:34 localhost pppd[2171]: pppd 2.4.1 started by root, uid
]> 0
]> Feb 23 10:13:34 localhost pppd[2171]: using channel 8
]> Feb 23 10:13:34 localhost pppd[2171]: Connect: <--> /dev/pts/5
]> Feb 23 10:13:34 localhost pppd[2171]: rcvd [LCP ConfReq id=0x1
]> <asyncmap 0x0> <magic 0x266da3f7> <mrru 1500>]
]> Feb 23 10:13:34 localhost pppd[2171]: sent [LCP ConfReq id=0x1 <magic
]> 0xd7190ece> <mrru 1500> <endpoint [MAC:00:60:e0:01:83:4a]>]
]> Feb 23 10:13:34 localhost pppd[2171]: sent [LCP ConfRej id=0x1
]> <asyncmap 0x0>]
?? This looks like a non-standard implimentation of pppd. ppd does not
reject asyncmap 0
> ?? This looks like a non-standard implimentation of pppd. ppd does not
> reject asyncmap 0
It does when configured with the default-asyncmap option. That works
both ways, with pppd rejecting any attempt by the peer to negotiate ACCM.
--
Clifford Kite Email: "echo xvgr_yv...@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Those who can't write, write manuals. */