On May 19, Alexander Verbovetsky <[EMAIL PROTECTED]> wrote:
> >"call no-auth" is meaningless, unless you have an /etc/ppp/peers/no-auth
> >file. Do you?
> Yes, I have. Now I simply put `noauth' into /etc/ppp/peers/provider instead
> of
> `call no-auth'.
>
> It seems, using the call option breaks
"call no-auth" is meaningless, unless you have an /etc/ppp/peers/no-auth
file. Do you?
Yes, I have. Now I simply put `noauth' into /etc/ppp/peers/provider instead
of
`call no-auth'.
It seems, using the call option breaks the initialization of the tdb database.
Regards,
Alex
--
To UNSUBSCRIBE, emai
On May 18, Alexander Verbovetsky <[EMAIL PROTECTED]> wrote:
> Indeed, the segfault vanishes with `call no-auth' removed.
"call no-auth" is meaningless, unless you have an /etc/ppp/peers/no-auth
file. Do you?
--
ciao,
Marco
signature.asc
Description: Digital signature
On Sun, 13 May 2005, Tomas Jura wrote:
So may be this bug is related to nested config file call.
Indeed, the segfault vanishes with `call no-auth' removed.
Moreover, with 2.4.2+20040428-6 version the pon command produced a message
tdb_store failed: Invalid tdb context
(but worked fine nevertheless)
Please attach /etc/ppp/peers/provider
user "[EMAIL PROTECTED]"
plugin rp-pppoe.so
eth0
noipdefault
defaultroute
persist
noaccomp
default-asyncmap
nopcomp
noccp
novj
(I suppose that you did not modify /etc/ppp/options).
diff options.dpkg options
35c35,36
< auth
---
#auth
call no-auth
340a342,348
#
On May 08, Alexander Verbovetsky <[EMAIL PROTECTED]> wrote:
> #0 0x08074fd2 in tdb_store (tdb=0x0, key={dptr = 0x8090f20 "", dsize = 0},
It crashes because the TDB database has not been initialised, but I do
not know why. Please attach /etc/ppp/peers/provider (I suppose that you
did not modify /
What happens if you delete /var/run/ppp*.tdb?
Segfaults.
If it still segfaults, please get a new stack trace from an unstripped
binary (http://www.bofh.it/~md/debian/pppd.unstripped.gz).
Core was generated by `/usr/sbin/pppd call provider'.
Program terminated with signal 11, Segmentation fault.
Rea
On May 08, Alexander Verbovetsky <[EMAIL PROTECTED]> wrote:
> #0 0x08074fd2 in tdb_store ()
What happens if you delete /var/run/ppp*.tdb?
If it still segfaults, please get a new stack trace from an unstripped
binary (http://www.bofh.it/~md/debian/pppd.unstripped.gz).
--
ciao,
Marco
signature.
Are you getting a kernel oops too?
I think no.
If not, please get a stack trace from pppd ("gdb pppd" "run call provider").
I'm not sure, I generated core by "pppd call provider" and then
gdb /usr/sbin/pppd core
(gdb) bt
#0 0x08074fd2 in tdb_store ()
#1 0x08051b80 in unlock_db ()
#2 0x08061a11 i
Package: ppp
Version: 2.4.3-20050321+2
Severity: important
With kernel-mode pppoe, the `pon' command exits with the "Segmentation fault"
message.
Kernel 2.4.27 patched with
kernel-patch-debian-2.4.27 (2.4.27-9)
kernel-patch-2.4-lowlatency (20041204)
kernel-patch-2.4-preempt (20040321-3)
Version 2.4
10 matches
Mail list logo
