Re: Why cant I get an internet connection
apt-get install pppoeconf
-or-
run pppoeconf, and then once its all setup, it should activate on boot.
'pon' and 'poff' should do it manually.
hope this helps,
-iridium
p.s. this works on my p3-600mhz vaio, running woody 3.0 (note: these ppoe
packages are default installed on their netinst CDs).
----- Original Message -----
From: "shaun bokowski" <sbokow@bellsouth.net>
To: <debian-laptop@lists.debian.org>
Sent: Tuesday, August 20, 2002 12:35 AM
Subject: Re: Why cant I get an internet connection
>
> ----- Original Message -----
> From: "Jeff" <jcoppock1@attbi.com>
> To: <debian-laptop@lists.debian.org>
> Sent: Monday, August 19, 2002 4:25 PM
> Subject: Re: Why cant I get an internet connection
>
>
> > shaun bokowski, 2002-Aug-19 18:07 -0700:
> > >
> > > ----- Original Message -----
> > > From: "Jeff" <jcoppock1@attbi.com>
> > > To: <debian-laptop@lists.debian.org>
> > > Sent: Sunday, August 18, 2002 11:06 PM
> > > Subject: Re: Why cant I get an internet connection
> > >
> > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Jeff" <jcoppock1@attbi.com>
> > > > > To: <debian-laptop@lists.debian.org>
> > > > > Sent: Sunday, August 18, 2002 8:28 AM
> > > > > Subject: Re: Why cant I get an internet connection
> > > > >
> > > > >
> > > > > --
> > > > > To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> > > > > with a subject of "unsubscribe". Trouble? Contact
> > > listmaster@lists.debian.org
> > > > >
> > > >
> > > > Sorry Shaun, I didn't see that you replied to the list and to me
> > > > directly too...jc
> > > >
> > > > --
> > > > Jeff Coppock Systems Engineer
> > > > Diggin' Debian Admin and User
> > >
> > > I am running pump not dhcpclient. pump (dhcp) and networking was
> configure
> > > at
> > > the beginning and I got on the internet. What should show in the
> > > /var/log/syslog file,
> > > what am I looking for that shows I really do have a connection. I
think
> that
> > > my network
> > > is not working.
> >
> > The syslog will show the details of the dhcp process, your system
> > getting it's IP configuration. That's all it'll show. If you're not
> > sure your network is working, check to make sure eth0 is configured
> > properly by checking "ifconfig eth0" as root, and then ping the
> > address shown:
> >
> > $ sudo ifconfig eth0
> > eth0 Link encap:Ethernet HWaddr 00:A0:C9:BC:78:C9
> > inet addr:192.168.0.116 Bcast:192.168.0.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1738 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:2296 errors:0 dropped:0 overruns:0 carrier:3
> > collisions:0 txqueuelen:100
> > RX bytes:823076 (803.7 KiB) TX bytes:292453 (285.5 KiB)
> > Interrupt:3 Base address:0x300
> >
> > $ ping -c 2 192.168.0.116
> > PING 192.168.0.116 (192.168.0.116): 56 data bytes
> > 64 bytes from 192.168.0.116: icmp_seq=0 ttl=64 time=0.5 ms
> > 64 bytes from 192.168.0.116: icmp_seq=1 ttl=64 time=0.4 ms
> >
> > If that works, then check to see if you received a default gateway
> > from dhcp:
> >
> > $ netstat -rn
> > Kernel IP routing table
> > Destination Gateway Genmask Flags MSS Window irtt Iface
> > 192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
> > 0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 eth0
> >
> > The "0.0.0.0" is the default gateway. See if you can ping it:
> >
> > $ ping -c 2 192.168.0.1
> > PING 192.168.0.1 (192.168.0.1): 56 data bytes
> > 64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.8 ms
> > 64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=1.2 ms
> >
> > Now, lets see if your DNS is working. First check to see if it got
> > configured:
> >
> > $ cat /etc/resolv.conf
> > search attbi.com
> > nameserver 216.148.227.68
> > nameserver 204.127.202.4
> >
> > Now see if you can reach one:
> >
> > $ ping -c 2 216.148.227.68
> > PING 216.148.227.68 (216.148.227.68): 56 data bytes
> > 64 bytes from 216.148.227.68: icmp_seq=0 ttl=54 time=100.8 ms
> > 64 bytes from 216.148.227.68: icmp_seq=1 ttl=54 time=79.6 ms
> >
> > Okay, next find out if it will resolve for you:
> >
> > $ nslookup -sil www.yahoo.com
> > Server: 216.148.227.68
> > Address: 216.148.227.68#53
> >
> > Non-authoritative answer:
> > www.yahoo.com canonical name = www.yahoo.akadns.net.
> > Name: www.yahoo.akadns.net
> > Address: 64.58.76.178
> > Name: www.yahoo.akadns.net
> > Address: 64.58.76.179
> > <snipped the rest>
> >
> > Try pinging one of the yahoo addresses. If that works, you're on the
> > internet. I'm assuming here that your service provider isn't
> > requiring you to use PPPoE/oA or the like. That would change the
> > interface you use for the above tests. It would be ppp0 instead.
> >
> > jc
> >
> >
> >
> > --
> > Jeff Coppock Systems Engineer
> > Diggin' Debian Admin and User
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
>
> Jeff,
>
> Everything was ok till I got to
>
> $ nslookup -sil www.yahoo.com
> Server: 216.148.227.68
> Address: 216.148.227.68#53
>
> I do
> user@hostname nslookup -sil www.yahoo.com
>
> bash: nslookup: command not found
>
> I ping both yahoo addresses and no luck.
>
> I am doing everything in # root or $ user as you print . My service
provider
> is using or requires PPPoE , no static ip.
>
> What could be it?
>
>
> --
> To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
Reply to: