On 2010-03-08, Siju George <sgeorge...@gmail.com> wrote: > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33152 > priority: 0 > groups: lo > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:11:d8:01:23:45 > priority: 0 > media: Ethernet autoselect (100baseTX full-duplex) > status: active > inet6 fe80::211:d8ff:fe01:2345%vr0 prefixlen 64 scopeid 0x1 > enc0: flags=0<> mtu 1536 > priority: 0 > pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492 > priority: 0 > dev: vr0 state: session > sid: 0x211 PADI retries: 0 PADR retries: 0 time: 00:00:05 > sppp: phase terminate authproto pap authname "username" > groups: pppoe egress > inet6 fe80::211:d8ff:fe01:2345%pppoe0 -> prefixlen 64 scopeid 0x4 > inet 0.0.0.0 --> 0.0.0.1 netmask 0xffffffff > pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33152 > priority: 0 > groups: pflog > > where do I look to see why the phase was terminated as stated in > > sppp: phase terminate authproto pap authname "username" > > can get any info from /var/log/messages
you can try something like "tcpdump -n -vvv -i vr0 -s 1500". (vr0 == parent interface for pppoe0). or "ifconfig pppoe0 debug" might elicit more information (look in dmesg/messages, use ifconfig pppoe0 -debug to go back to normal).
