problem w/ network setup in debian

[Barnaby W. Füi]

ok i got this mostly figured out now, from help on irc. but i STILL cant connect.

here is my /etc/network/interfaces:

# We always want the loopback interface. (This is commented out in case
# you're configuring it by hand elsewhere, like in /etc/init.d/network. If
# you're not, you need this line)

iface lo inet loopback

# An example ethernet card setup: (broadcast and gateway are optional)

iface eth0 inet static
address x.x.x.x
# network 192.168.0.0 (not on a lan)
netmask 255.255.255.128
# broadcast 192.168.0.255
gateway 65.3.241.129


and here is my /etc/resolv.conf:

domain moline1.il.home.com
nameserver 24.2.218.33
nameserver 24.2.218.34

all of these are correct, the same settings i use in windows and the same ones i used in redhat, and they worked in those.

i wasnt sure how to restart the network stuff after i modified the files, i looked for the pid and did a kill -HUP, that didnt work so i just rebooted and after rebooting it still didnt work.

 

[Barnaby W. Füi]

bump for update

 

[Barnaby W. Füi]

ok so it turns out that i think something is wrong with interfaces. when i do a ifconfig -a i get:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

those addresses obiously are not right.

so, now the question becomes: what is wrong with my interfaces file?

 

[pedrog]

What I know about this is not much, but I'm also on a cable modem with debian. Here is my file

auto lo eth0
iface lo inet loopback

# (network, broadcast and gateway are optional)

iface eth0 inet static
address xx.xxx.xxx.xxx
netmask 255.255.255.0
network xx.xxx.xxx.0
broadcast xx.xxx.xxx.255
gateway xx.xxx.xxx.1

I think that

/etc/init.d/networking restart

should restart the networking stuff.

 

[n0cmonkey]

<< ok so it turns out that i think something is wrong with interfaces. when i do a ifconfig -a i get:

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

those addresses obiously are not right.

so, now the question becomes: what is wrong with my interfaces file? >>



lo is loopback. You have not setup eth0 (your network card. Or so it appears.

 

[Barnaby W. Füi]

<<
iface eth0 inet static
address x.x.x.x
# network 192.168.0.0 (not on a lan)
netmask 255.255.255.128
# broadcast 192.168.0.255
gateway 65.3.241.129
>>



??? what about that ^^^^^ i thought it is set up???

 

[n0cmonkey]

<<

<<
iface eth0 inet static
address x.x.x.x
# network 192.168.0.0 (not on a lan)
netmask 255.255.255.128
# broadcast 192.168.0.255
gateway 65.3.241.129
>>



??? what about that ^^^^^ i thought it is set up??? >>



Not if there is no driver setup for it.

 

[Barnaby W. Füi]

ah! i thought the driver was in the kernel. when i installed debian, there were NO linksys cards on the list...wtf?

 

[n0cmonkey]

<< ah! i thought the driver was in the kernel. when i installed debian, there were NO linksys cards on the list...wtf? >>



tulip driver.

 

[pedrog]

so for a test....

echo "alias eth0 tulip" >> /etc/modules.conf
insmod tulip
/etc/init.d/networking restart

or.......................

Debian provides a script to setup this file also (make a back up your old one first)

/usr/sbin/modconf

I think that it's similar to the script that runs during the install.

 

[Barnaby W. Füi]

excuse my retardedness, but can you explain your post a little more, i dont want to do something if i dont really know what i'm doing.

thx

 

[Nothinman]

First type 'modprobe tulip' that will load the tulip driver and if it works, you should be able to type 'ifup eth0' and be on the network.

Just add the line 'tulip' to /etc/modules to get Debian to load the module at bootup.

 

[pedrog]

The reason that your eth0 isn't showing up may be that the kernel doesn't know to load the driver module for it.

These are ways of loading that module. Nothingman's instructions look simplest....