| krollah |
08-05-2009 01:00 PM |
penggy / ubuntu / aol / tun - connection created but not active
Hello LQ. After a few days of scouring this and several other forums, I've finally decided to post. I've found a lot of posts out there about penggy, aol, wvdial, gnome-ppp, etc etc etc, but nothing that fits my situation. I've found myself in a position where I need to be able to connect to AOL through Linux from the command line. Penggy seems like the way to go, and is ALMOST working. Let me first show my current config:
Code:
root@amtrak-laptop:/usr/local/etc/penggy# lsusb
Bus 008 Device 004: ID 0803:3095 Zoom Telephonics, Inc.
The device above is a Zoom USB modem that is at /dev/ttyACM0
Code:
/usr/local/etc/penggy# cat aol-secrets
## Secrets for aol authentication
## screen_name secret
##
#dark s3kr3t
aolscreenname password
Code:
/usr/local/etc/penggy#cat phonetab
18584100080
Code:
/usr/local/etc/penggy# grep -v ^# penggy.cfg | grep .
screen_name = aolscreenname
debug_level = 10
modem_device = /dev/ttyACM0
Ok, so when I connect, everything looks good:
Code:
Using /dev/ttyACM0 device...
Device /dev/ttyACM0 opened
Dialing provider...
Sending: ATZ
Received line : OK
Dialing 18584100080
Sending: ATDT18584100080
Received line : CONNECT 115200
Connection at 115200b/s done.
Executing chat script (/usr/local/share/penggy/chat/aolnet.scm)...
Script: String 'UQKT2' matched
Script: String 'login' matched
Script: Send 'aol '
Script: String 'Password' matched
Script: Send 'aol '
Script: String 'Connected' matched
Script: Chat success
Chat success, connected...
P3 - output raw dump:
0000: Z.Q.4... ..m..... | 5aaa5100347f7fa3 038b6d0010000000
0010: ....%n.M ........ | 050f0000256eb24d c00014c008050000
0020: ........ ........ | 0000040a00000100 040003ffff000000
0030: ........ .. | 00010000fffe0000 170d
FDO - Token 'SD' registered.
buffer - 58 bytes sended
buffer - 32 bytes received
P3 - Received an ACK packet
P3 - 1 packets acknowledged, remainder=0
P3 - Received a DATA packet:
P3 - input raw dump:
0000: Z.q..... SD...h.. | 5aae710b00107f20 5344eb83b3680000
0010: . | 0d
Loging into provider as 'myscreenname'
P3 - output raw dump:
0000: Z:/.V... Dd...... | 5a3a2f0056107fa0 4464001600010001
0010: ........ ........ | 0a0400000001010b 040000000503010a
0020: myscreen ........ | 64356e6f726d616e 2020011d00011d00
0030: ........ ..passwo | 010a040000000203 010766316e673372
0040: s....... ........ | 73011d00010a0400 000010010b040000
0050: ........ .... | 0001011d00011d00 0002000d
FDO - Token 'SD' unregistered.
FDO - Token 'At' registered.
FDO - Token 'AT' registered.
FDO - Token 'at' registered.
buffer - 92 bytes sended
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 13 bytes received
P3 - Received a DATA packet:
P3 - input raw dump:
0000: ZypM.... at...... | 5a79704d00117f20 617401100fa02001
0010: %...../T ..$....S | 258514ff00192f54 010224209f860253
0020: Nh@'.".. ...../T. | 4e684027e2229514 ff0019200c2f5403
0030: .$....SN h@g$.... | 0424209f8602534e 68406724209f8602
0040: Sn...K.. $.@.@G.. | 536e2015204b0402 2408408740472002
0050: ... | 20020d
buffer - 32 bytes received
buffer - 4 bytes received
P3 - Received a DATA packet:
P3 - input raw dump:
0000: Z.d..... At..^..A | 5a8d641e00121020 4174040f5e200141
0010: ),...... .......! | 292ca10000000000 800500000000c121
0020: .... | 1d20020d
FDO - Login confirm received
FDO - Token 'At' unregistered.
FDO - Token 'At' registered.
P3 - output raw dump:
0000: Z.l..... ya...... | 5abc6c000e1111a0 79610701010c0101
0010: .... | 0d01010d
FDO - Token 'ya' registered.
P3 - 1 packets acknowledged, remainder=1
buffer - 20 bytes sended
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 32 bytes received
P3 - Received a DATA packet:
P3 - input raw dump:
0000: Z0.z.... At.._..- | 5a30c57a00131020 4174040f5f20012d
0010: ..V..-?. .V...d." | 11205600002d3f01 2056010420640d22
0020: ...[Comp te.non.v | bd00055b436f6d70 7465206e6f6e2076
0030: alide..P our.plus | 616c6964652e2050 6f757220706c7573
0040: .d'infor mations, | 206427696e666f72 6d6174696f6e732c
0050: .appelez .le.1077 | 20617070656c657a 206c652031303737
0060: .(temps. d'attent | 202874656d707320 6427617474656e74
0070: e.gratui t.depui. | 6520677261747569 742064657075690d
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 27 bytes received
P3 - Received a DATA packet:
P3 - input raw dump:
0000: Z.#u.... At.._..b | 5aa6237500141020 4174040f5f000662
0010: s.une.li gne.Neuf | 7320756e65206c69 676e65204e657566
0020: .Box,.pu is.tarif | 20426f782c207075 6973207461726966
0030: .d'un.ap pel.loca | 206427756e206170 70656c206c6f6361
0040: l.depuis .une.lig | 6c20646570756973 20756e65206c6967
0050: ne.fixe. en.Franc | 6e65206669786520 656e204672616e63
0060: e.m.trop olitaine | 65206de974726f70 6f6c697461696e65
0070: )...}... ... | 292ee2207d010003 20020d
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 32 bytes received
buffer - 5 bytes received
P3 - Received a DATA packet:
P3 - input raw dump:
0000: Z.U_.... ya...... | 5ace555f00151120 79610701000304ac
0010: .S...... ........ | 83530d0201020101 000404cdbc929105
0020: .....cli ent-83-1 | 0205dc0a14636c69 656e742d38332d31
0030: 3.aol.co m....... | 332e616f6c2e636f 6d0c051ccdbc9290
0040: ........ ........ | 0c0413cdbc200c04 18cdbc0d0c041398
0050: ........ ........ | a3c00c041498a3f0 0c0414cdbcc00c04
0060: .@.`. | 13400c600d
IP address: 172.131.83.13
DNS server: 205.188.146.145
MTU: 1500
Hostname: client-83-13.aol.com
Domain: aol.com
Subnet: 205.188.146.144/255.255.255.240
Subnet: 205.188.32.0/255.255.224.0
Subnet: 205.188.13.0/255.255.255.0
Subnet: 152.163.192.0/255.255.224.0
Subnet: 152.163.240.0/255.255.240.0
Subnet: 205.188.192.0/255.255.240.0
Subnet: 64.12.96.0/255.255.224.0
Launching /usr/local/etc/penggy/ip-up
FDO - Token 'yc' registered.
IP tunnel is working.
So at this point everything seems great:
output of ifconfig:
Code:
eth0 Link encap:Ethernet HWaddr 00:1f:16:57:4d:30
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:252 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3184 (3.1 KB) TX bytes:3184 (3.1 KB)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:172.131.169.91 P-t-P:172.131.169.91 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:368 (368.0 B)
wlan0 Link encap:Ethernet HWaddr 00:23:4e:0f:ab:f2
inet addr:192.168.1.102 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::223:4eff:fe0f:abf2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:181 errors:0 dropped:0 overruns:0 frame:0
TX packets:249 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32153 (32.1 KB) TX bytes:57935 (57.9 KB)
wmaster0 Link encap:UNSPEC HWaddr 00-23-4E-0F-AB-F2-62-66-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
so the tun0 connection is created and is assigned an IP address.
and the routes created:
Code:
root@amtrak-laptop:/usr/local/etc/penggy# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
172.133.79.224 * 255.255.255.255 UH 0 0 0 tun0
root@amtrak-laptop:/usr/local/etc/penggy#
resolv.conf:
Code:
# This file has been automaticly generated by penggy
# A backup of your old configuration has been made in /etc/resolv.peng
# It will be restored when connection is down
domain aol.com
search aol.com
nameserver 205.188.146.145
so the DNS is set correctly too.. however, when I try to ping google, it just hangs (a ping straight to google's IP, or to my own DNS IP behaves the same):
Code:
root@amtrak-laptop:/usr/local/etc/penggy# ping www.google.com
^C
compare that to when i try to ping google when penggy isn't running:
Code:
ping www.google.com
ping: unknown host www.google.com
ping 74.125.127.99
connect: Network is unreachable
and here is the debug output from penggy while the ping is running:
Code:
IP TUNNEL - Sending a small packet
P3 - output raw dump:
0000: Z2..C... yc.<E..< | 5a32a900431715a0 7963003c4500003c
0010: ..@.@..( ..?..... | f1e540004011fc28 ac833fd1cdbc9291
0020: .!.5.(". uU...... | 8c210035002822a8 7555010000010000
0030: .....www .google. | 0000000003777777 06676f6f676c6503
0040: com..... . | 636f6d0000010001 0d
buffer - 73 bytes sended
engine - Timed out
P3 - timeout notified
buffer - 9 bytes sended
engine - Timed out
buffer - 46 bytes received
IP TUNNEL - Sending a small packet
P3 - output raw dump:
0000: Z...5... yc..E... | 5a96c000351815a0 7963002e4500002e
0010: >/@.@..^ ...f@.h" | 3e2f40004006925e c0a80166400c6822
0020: .|.iC..F ....P... | d97c146943e97f46 eee41fe45018f9b0
0030: a...*..M ... | 61a800002a05004d 00000d
buffer - 59 bytes sended
engine - Timed out
engine - Timed out
buffer - 60 bytes received
so you can see the packets going out, and you can see that something is received, but that's it! a few things that seem interesting to me are the messages in the penggy output that say "engine - Timed out" and "P3 - timeout notified" - maybe someone can clarify what they mean? i've also played around with running pengy with my other ethernet cards enabled/disabled with no luck... it seems to me that the problem has to do with getting tun/tap to work properly, but i'm not sure what that even entails. if anyone has any info, please let me know!
also of note is that i have tried using wvdial and gnome-ppp, but have run into several other problems... penggy seems to be the closest to working. |
