[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [SLUG] Problems configuring woody for cable

This one time, at band camp, Adam Bogacki said:
> Sorry,
> 	I did not include the 'ifconfig' readout.
> 	It was copied by hand onto notepad and again into M$ Outlook so
> human error might be expected. The upside is that, as I understand it,
> it points to only one error.
> Tux:/home/adam# ifconfig
> Eth0	Link encap:Ethernet HWaddr 00:A0:CC:D9:E2:48
> 	Inet addr: Bcast: Mask:
> 	RX packets:68 errors:1 dropped:0overrun:0 frame:0
> 	TX packets:21 errors:0 dropped:0overrun:0 carrier:0
> 	Collisions:0 txqueuelen:100
> 	RX bytes:4530 (4.4 KiB) TX bytes:2491 (2.4 KiB)
> 	Interrupt:11 Base address:0xa400
> Lo	Link encap:Local Loopback
> 	Inetaddr: Mask:
> 	RX packets:956 errors:0 dropped:0overrun:0 frame:0
> 	TX packets:956 errors:0 dropped:0overrun:0 carrier:0
> 	Collisions:0 txqueuelen:100
> 	RX bytes:58251 (56.8 KiB) TX bytes:58251 (56.8 KiB)
> My /etc/resolv.conf is
> 'search paradise.net.nz
> nameserver
>            '
> which confuses me - where did that DNS come from ?
> my IP is
>               Localhost
>   Tux
>   Tux loghost

It looks like at some point this box has been on a LAN?  I am operating
on the assumption that you are not currently on a LAN, but have a
standalone box connected to a cable modem or other such device.  If I am
wrong, then apply this advice to whatever NIC is attached to the cable
modem, and we'll get back to the other one.

Try this:

Comment out any entries in /etc/networks - This controls entries for
known networks, and you are ony on one: the cable one.

Comment out all eth0 lines in /etc/network/interfaces - these are all
apparently for a LAN.

Add a stanza like:

auto eth0
iface eth0 inet static
    gateway 203.x.x.x (whatever it is)

man interfaces for details of each of these, and double check my netmask
and network settings - I'm just filling it in as I go.

/etc/resolv.conf looks fine, uncomment the search line - this controls
who you query for DNS, and the 'search' directive is part of that for
many ISP's.  man resolv.conf for all the details.

Then, /etc/init.d/network restart.  Try pinging your gateway by IP, then
try pinging anybody else (I usually use www.debian.org ||,
but whatever)  If you get successful pings by IP, then you have a net
connection.  If you also get successful pings by name, then DNS is
working, and you're set.

I think netconf has not done it's job well in this case, and just ended
up putting some entries in the right place and not doing the right thing
in others.  If you feel like you answered everything right, and it still
fell down, file a bug report.

|  Stephen Gran                  | Happiness adds and multiplies as we     |
|  steve@lobefin.net             | divide it with others.                  |
|  http://www.lobefin.net/~steve |                                         |

Attachment: pgpt4GoHl1mzm.pgp
Description: PGP signature

Reply to: