[RP-PPPoE] pppoe:read (asyncReadFromPPP):: Input/output error

[Jolly Shah]

Yes the command "/usr/sbin/pppd pty 'pppoe -I ath0' noauth user test
password YOURPASSWORDHERE  debug" does not give any error but it
doesn't connect to server too.

below is the output for "ls -l /dev/ppp"

~ # ls -l /dev/ppp
crw-------    1 root     root     108,   0 Jan  1 00:07 /dev/ppp

I don't have strace..Tried the other one suggested by you and below
are the arguments being passed to pppd command.

~ # cat /tmp/pppd-args
pty /usr/sbin/pppoe -p /etc/ppp/pppoe.conf-pppoe.pid.pppoe -I ath0 -T
80 -U -m 1412 -D /tmp/pppoe-debug-141/pppoe-debug.txt-0 noipdefault
noauth default-asyncmap defaultroute hide-password nodetach mtu 1492
mru 1492 noaccomp nodeflate nopcomp novj novjccomp user test
lcp-echo-interval 20 lcp-echo-failure 3 debug

I will install strace and will try to debug with that.

--
Jolly Shah




On Fri, Jul 30, 2010 at 8:22 PM, Mike <mike-rppppoe at tiedyenetworks.com> wrote:
> Jolly Shah wrote:
>>
>> Thanks for the reply Mike.
>> Below are the observations:
>>
>> -> Yes ath0 is up and running
>> -> It has write access to pid file /etc/ppp/pppoe.conf-pppoe.pid.pppoe
>> -> /usr/sbin/pppoe -h gives help output
>> -> command "/usr/sbin/pppd pty 'pppoe -I ath0' noauth user test
>> password YOURPASSWORDHERE  debug" does not give any error.
>> -> pppoe modules are built in the kernel. So I cant see them in lsmod.
>> But they are present in the kernel otherwise it gives error saying
>> kernel support is missing for pppoe.
>>
>> I have attached the full debug log of pppoe-start command. It gives
>> "pppoe: read (asyncReadFromPPP): Session 7: Input/output error" after
>> session confirmation request.
>>
>
> Howdy,
>
>   Ok so the interesting thing then is that you were able to run "pppd pty
> pppoe...." by hand, with a much stripped down command line, and you stated
> here that you got no error. If that is really the case then your machine is
> otherwise healthy and this is an invocation problem. The root of the problem
> seems to be that pppd is aborting as soon as it's run (your last packet
> states 'RP-PPPoE: System call error: Bad file descriptor'), if indeed it's
> actually getting launched at all.
>
>   Questions:
>
>   What does ls -l /dev/ppp show?
>   Do you have local logging (like files in /var/log for example)? Do you see
> anything in it from pppd? What does it say?
>
>   Bonus debugging:
>
>   Do you have 'strace' available? Can you run 'strace -f -p <pid of
> rp-pppoe> 2> /some/temp/file'. Look for 'exec...' and see what cmd line args
> are being passed to pppd, and then a further exec... for pppoe and check
> those. You'll be looking for errors concerning open() and such most likely.
>
>   If you don't have strace available... is your filesystem writable? can you
> try the following:
>
>   mv /usr/sbin/pppd /usr/sbin/pppd.orig
>   cat > /usr/sbin/pppd <<EOF
>   #!/bin/sh
>   echo $* > /tmp/pppd-args
>   exec /usr/sbin/pppd.orig $*
>   EOF
>   chmod +x /usr/sbin/pppd
>
>   and then try a run and see what's in /tmp/pppd-args?
>
> Mike-
>
> _______________________________________________
> RP-PPPoE mailing list
> RP-PPPoE at lists.roaringpenguin.com
> http://lists.roaringpenguin.com/cgi-bin/mailman/listinfo/rp-pppoe
>



-- 
Jolly Shah