Re: Unable to connect to the the ISP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Again some progress. I know this is a newbie blunder, but I entered my username and password as 'username' and 'password' instead of username and password. I still think it's worth mentioning in this mailing list for possible future mistakes of newbies such as myself. As a result of this important change in /etc/hostname.pppoe0, I managed to get a valid IP address from my provider. However, I still cannot access the inet via any service, be it ping, telnet, ftp or http. In the ifconfig the one-before-last line of pppoe0 shows inet AAA.AAA.AAA.AAA -- 0.0.0.1 netmask 0xff00 where AAA.AAA.AAA.AAA is my valid IP address. Do I need to enter a different gateway or is 0.0.0.1 good enough? Thanks, Amit. iD8DBQFG3ExpEzurR/yozRMRAn0uAKCsmNcDmeRSyH/0SXr15qIbJDQTgQCfW5dU sMLMPmkxsaLSQvMfrLGV/Ys= =LltP -END PGP SIGNATURE-
Re: Unable to connect to the the ISP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 With the help of Jonathon, I think I've made some progress. I changed /etc/hostname.pppoe0 to be the following: pppoedev fxp0 authproto pap authname 'MYAUTHNAME' authkey 'MYPASSWORD' !/sbin/ifconfig fxp0 up !/sbin/ifconfig \$if inet 0.0.0.0 http://0.0.0.0 0.0.0.1 http://0.0.0.1 netmask 0x mtu 1452 !/sbin/route add default 0.0.0.1 http://0.0.0.1 up and restarted the network. The output of ifconfig and dmesg are attached in separate files. As you can see, I still don't get a proper inet address, i.e. I'm still not connected. No error messages this time. I have a conjecture. Is it possible that my ISP does not require authentication and that the only thing that prevents me from connecting is the 'authproto pap' entry in /etc/hostname.pppoe0? Thanks, Amit. iD8DBQFG2wVLEzurR/yozRMRAr3EAJsESpewKNla+Cjx2QRZemrU2kjjiQCg/EUc tJcnEjK2ysnyUheGqKrOlSY= =9OT6 -END PGP SIGNATURE- [demime 1.01d removed an attachment of type text/x-log which had a name of dmesg.log] [demime 1.01d removed an attachment of type text/x-log which had a name of ifconfig.log] up [demime 1.01d removed an attachment of type application/pgp-signature which had a name of dmesg.log.sig] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of ifconfig.log.sig] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of hostname.fxp0.sig]
Re: Unable to connect to the the ISP
On Sat, 1 Sep 2007, Amit Finkler wrote: The contents of my /etc/hostname.fxp0 are: dhcp This should be just up. 1. How do I disable IPv6? You don't need to, I'm sure that's not the problem. Btw, I suggest you to try the kernel mode pppoe. It's really simple to set up and works like a charm. See pppoe(4). -- Antti Harri
Re: Unable to connect to the the ISP
On 2007/09/01 16:34, Amit Finkler wrote: The error message I get involves something about IPv6 format something about IPv6 format? you can do better than that. copy-and-paste.
Re: Unable to connect to the the ISP
2007/9/1, Amit Finkler [EMAIL PROTECTED]: 1. How do I disable IPv6? disable ipv6cp ppp(8) tells you more. Best Martin PS: Read http://www.catb.org/~esr/faqs/smart-questions.html
Re: Unable to connect to the the ISP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Henderson wrote: On 2007/09/01 16:34, Amit Finkler wrote: The error message I get involves something about IPv6 format something about IPv6 format? you can do better than that. copy-and-paste. Antti Harri wrote: On Sat, 1 Sep 2007, Amit Finkler wrote: The contents of my /etc/hostname.fxp0 are: dhcp This should be just up. 1. How do I disable IPv6? You don't need to, I'm sure that's not the problem. Btw, I suggest you to try the kernel mode pppoe. It's really simple to set up and works like a charm. See pppoe(4). OK, so I configured /etc/hostname.pppoe0 as described in pppoe(4): # The following line is all in one line inet 0.0.0.0 255.255.255.255 NONE pppoedev fxp0 authproto pap authname 'myUsername' authkey 'myPassword' up dest 0.0.0.1 !/sbin/route add default 0.0.0.1 and the corresponding ifconfig output is: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33224 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 rl0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0a:cd:10:2b:c5 media: Ethernet autoselect status: active fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0d:61:03:77:63 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet6 fe80::20d:61ff:fe03:7763%fxp0 prefixlen 64 scopeid 0x2 inet 10.0.0.2 netmask 0xff00 broadcast 10.255.255.255 pflog0: flags=0 mtu 33224 enc0: flags=0 mtu 1536 pppoe0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1492 dev: fxp0 state: initial sid: 0x0 PADI retries: 0 PADR retries: 0 groups: pppoe inet6 fe80::20a:cdff:fe10:2bc5%pppoe0 - prefixlen 64 scopeid 0x6 inet 0.0.0.0 -- 0.0.0.0 netmask 0x So I got rid of the nagging IPv6 message (nevermind what that was) but I still can't manage to connect. Amit. Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG2YCSEzurR/yozRMRAtBuAJ9Ytf4hwV/+RBnk/HkzzIspRLWYbgCfcMUH L0PatuQ/3xsXlE+TeNJ3Fq4= =WO8M -END PGP SIGNATURE-
Re: Unable to connect to the the ISP
On 2007/09/01 18:09, Amit Finkler wrote: pppoe0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1492 I don't know why, but this interface is not up.