networking problem with linux

Could you cut and paste the information posted about your network card at bootup?

No information is displayed really, that I have time to examine
at any rate - when I look for a boot log file I cannot find one
and do not know how to turn it on.....

I do know that the system seems to look load the device
eth0 okay....

Sorry, I am new to Linux.

I have also looked at the netstat and ifconfig and the adapter
seems to be working okay, just the network is unreachable.

I would appreciate any advice.... I really have tried playing with
things for many hours now - I have read the networking section
from the LINUX documentation project but still no joy..

Here is my config. Note, some lines may be broken.  Some options are for speed optimizations local to my network.  I have a server doing ip masqing with a cable modem. eth0 is the nic for the modem and eth1 is for the local network.

Nic

/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
/sbin/ifconfig eth0 x.x.x.x netmask 255.255.248.0 broadcast 24.1.199.255 mtu 1500
/sbin/ifconfig eth1 192.168.0.1 netmask 255.255.255.0 mtu 1500
/sbin/route add default gw 24.1.192.1 dev eth0 mss 1460 window 23360
echo 1 > /proc/sys/net/ipv4/ip_forward
/sbin/ipchains -A forward -j MASQ -s 192.168.0.0/24 -d 0.0.0.0/0

Nic,

I have tried all that you suggest from your config but when
I get to the line ifconfig eth0 X.X.X.X netmask 255.255.255.0 mtu

the reply I get is resoure not available

but when I type ifconfig eth0 it gives me all the information
about the card etc.

also when I add my default gateway it tells me host not
available - this I know is not true as I use this through
Windoze to access the net.

..... I am becoming even more confused!!

Anymore ideas.

 x.x.x.x stands for the ip of your machine that you are using.  Don't literally enter in "x.x.x.x"

  What I'd like you to do is the following:

  Make it so that your network doesn't configure on start up.  If you don't know how to do that, learn how to bring down the network completely.  In other words make it so that your network configuration is clean.  Then, type in the above lines, in respect to your configuration, one by one, and then verify that what you typed in works.  For example, after you add the gateway, see if you can ping it.  Oh, and one other thing, make sure you have added the necessary lines to /etc/networks, or in the config add a couple "route add -net" lines.  The resulting config would look like this, assuming one net card.

/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
/sbin/ifconfig eth0 x.x.x.x netmask 255.255.255.0
/sbin/route add -net x.x.x.0 netmask 255.255.255.0
/sbin/route add default gw x.x.x.x dev eth0

Remember to replace x.x.x.x with relavant values.
Also, your netmask might not match mine.

From the sounds of your responses leecronin it appears we should take a step back from try to configure the ethernet interface to see if the interface is actually being recognized by the kernel.  Three things I think you should do first before we really can suggest a course of action:
1.) If the directory /proc exists and contains files please cat /proc/pci and /proc/net/dev and output the results here so we can see them.  
2.) Output the results of the command "ifconfig" without any parameters with it.  This will show what interfaces the kernel currently recognizes and the status of those interfaces (ie. IP addresses bound to them, netmask, etc).
3.) Output the results of the command "route" without any parameters with it.  This will show the current entries in the routing table.  

Previous posters have indicated that you should have lines to setup the interfaces in your config files.  With Redhat most of that setup already exists.  This is why I'm suggesting we take a step back to determine if the interface is even recognized by the kernel.

From the sounds of your responses leecronin it appears we should take a step back from try to configure the ethernet interface to see if the interface is actually being recognized by the kernel.  Three things I think you should do first before we really can suggest a course of action:
1.) If the directory /proc exists and contains files please cat /proc/pci and /proc/net/dev and output the results here so we can see them.  
2.) Output the results of the command "ifconfig" without any parameters with it.  This will show what interfaces the kernel currently recognizes and the status of those interfaces (ie. IP addresses bound to them, netmask, etc).
3.) Output the results of the command "route" without any parameters with it.  This will show the current entries in the routing table.  

Previous posters have indicated that you should have lines to setup the interfaces in your config files.  With Redhat most of that setup already exists.  This is why I'm suggesting we take a step back to determine if the interface is even recognized by the kernel.

Sorry for the double post.  It didn't appear to complete the first time.

Hi nshup and Pops,

Please note I did not enter x.x.x.x but my IP address!
I just used x.x.x.x to represent it but I understant you may
think I literally used that!!

I am working on bringing the net down and restarting but
here are the PCI, DEV and ifconfig, route stuff below

I hope this helps point the way to the problem....

Roll on the day when windoze is removed from my HD!!

Cheers,

Lee

Here is the contents of

a) PCI

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Intel Unknown device (rev 3).
      Vendor id=8086. Device id=7190.
      Medium devsel.  Master Capable.  Latency=64.  
      Prefetchable 32 bit memory at 0xe4000000 [0xe4000008].
  Bus  0, device   1, function  0:
    PCI bridge: Intel Unknown device (rev 3).
      Vendor id=8086. Device id=7191.
      Medium devsel.  Master Capable.  Latency=64.  Min Gnt=136.
  Bus  0, device   4, function  0:
    ISA bridge: Intel 82371AB PIIX4 ISA (rev 2).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  No bursts.  
  Bus  0, device   4, function  1:
    IDE interface: Intel 82371AB PIIX4 IDE (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.  
      I/O at 0xd800 [0xd801].
  Bus  0, device   4, function  2:
    USB Controller: Intel 82371AB PIIX4 USB (rev 1).
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.  
      I/O at 0xd400 [0xd401].
  Bus  0, device   4, function  3:
    Bridge: Intel 82371AB PIIX4 ACPI (rev 2).
      Medium devsel.  Fast back-to-back capable.  
  Bus  0, device  10, function  0:
    Ethernet controller: 3Com 3C900 10b Combo (rev 0).
      Medium devsel.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xd000 [0xd001].
  Bus  0, device  11, function  0:
    Multimedia audio controller: Unknown vendor Unknown device (rev 5).
      Vendor id=1102. Device id=2.
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.  Min Gnt=2.Max Lat=20.
      I/O at 0xb800 [0xb801].
  Bus  0, device  11, function  1:
    Input device controller: Unknown vendor Unknown device (rev 5).
      Vendor id=1102. Device id=7002.
      Medium devsel.  Fast back-to-back capable.  Master Capable.  Latency=32.  
      I/O at 0xb400 [0xb401].
  Bus  1, device   0, function  0:
    VGA compatible controller: NVidia Unknown device (rev 17).
      Vendor id=10de. Device id=28.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=64.  Min Gnt=5.Max Lat=1.
      Non-prefetchable 32 bit memory at 0xe0000000 [0xe0000000].
      Prefetchable 32 bit memory at 0xe2000000 [0xe2000008].

b) /proc/net/dev

Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    5392      48    0    0    0     0          0         0     5392      48    0    0    0     0       0          0
  eth0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0

c) the info that ifconfig gives:

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

d) the info that route gives:

P routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.0       *               255.0.0.0       U     0      0        0 lo

Adjusted points to 150

Does the module load?  /sbin/lsmod, will give you a listing of modukes.

Since ifconfig doesn't show eth0 at all, you might not have brought it up for some reason.  What happens when you type "ifconfig eth0 up" ?

You might want to try the netconf tool.  It can be very useful for figuring this stuff out in the beginning.

when I type ifconfig eth0 up the whole system locks up and
I can do nothing!!!

netconf seems nice but still nothing works after I activate the changes.....

I am confused... I also am beginning to think it may
be a weird hardware problem.

Lee

Disregard the above comment, when I type
ifconfig eth0 IPVALUE  Netmask Value up
the system locks up...

but when I type ifconfig eth0 up

it says resources temporaliy anavailabe.....

????????

It does sound like a hardware problem.  What happens when you install the module using "insmod 3c95x".  After that, to an lsmod to see if it installed.

after I install the module using insmod 3c95x nothing happens
that I can see....

..... has anyone no idea?? I have place up a rather large
amount of config info yet I remain very confused.

IF someone could read the above information and comment
accordingly I would be very grateful.

Thanks

Lee

leecronin:  If you run 'ifconfig -a' does it show additional interfaces which are not eth0,  but perhaps xl0 or another device specific name?  if so,  you may want to make a symbolic link to that device for eth0.  I found that when the system fails to make a symbolic it can cause lots of wierd havoc. *I hope this helps out*

Vince

Do not feel bad, I am having the same problem and have spent weeks on it, and still have had no luck..
I have good cards, good cable etc.
Good Luck and when you get an answer maybe you can help me.

Mike

Thanks everyone for all your help... all of which
was sensible but I have sorted it out myself.

The network card, an old 3com combo was to blame
and chaning to an intel pro 100 did the trick...

..... now to get my sound blaster too work
and windoze will be gone FOREVER!
Bog off Bill Gates!!! (this is the view of this
author and not this organisation!!)

Cheers once again everyone.

Lee

So was it a bad card?

Hansendc

Well for windows no... the card worked....

....but for linux yes the card did not work.....

This was not because the card was bad, but because the PnP
options on the mother board were messed up by the card...
....so technically I would say it was a bad card....

..... I guess the points are yours.

Lee,

   Have you ever consider turning off PnP on the card, and give it a fixed setting (IRQ, IO, and MEM setting). Make sure you set the CMOS to assign the setting manually (for the slow where you plug you card in - I assume you BIOS allows this) After that make sure update your window setting as well.  If it worked under windows, then it should work under Linux as well.

   I have came across the same problem sometimes back, and by doing some manual setting on the card, I worked fine.

  The thing that I discovered is that, newer MB and BIOS and even OS (Windows), tend to "reconfigure" PnP devices automatically upon bootup.  And I doubt Linux does.

   Wish you the best of luck...


....and I believe it not about points eh:)

If hansendc doesn't answer this in a few days, I'll answer (you can drop the points to zero), so this shows up in the Previously Asked section.

Cool!  Glad to see you answered it, handsendc!