Getting network up

Justin Knierim justin at jrknierim.de
Sat Jul 17 05:31:41 PDT 2004


Hello everyone,

I built a belfs system (2004-07-07) on a remote server, and am having 
trouble getting the network up, which is of course a big problem being a 
remote server!  The system has 2 built in network cards, with eth0 being 
the one connected to the switch.  lspci in suse shows them as:

01:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)

I use the same 2.6.7 kernel for suse and lfs, in Suse it works, in lfs 
not.  The IP is static, no gateway (direct internet connection) and I 
have the two dns servers entered in /etc/resolv.conf.  Really exact same 
configuration for IP, etc. as the suse system.  The network card driver 
is built in, no module.

When the lfs system starts, the kernel seems to find the network card 
and that it is connected...

Jul 11 10:34:29 ds80-237-204-39 kernel: loop: loaded (max 8 devices)
Jul 11 10:34:29 ds80-237-204-39 kernel: 8139too Fast Ethernet driver 0.9.27
Jul 11 10:34:29 ds80-237-204-39 kernel: eth0: RealTek RTL8139 at 
0xe0814000, 00:0e:2e:08:39:d1, IRQ 17
Jul 11 10:34:29 ds80-237-204-39 kernel: eth0:  Identified 8139 chip type 
'RTL-8100B/8139D'
Jul 11 10:34:29 ds80-237-204-39 kernel: eth1: RealTek RTL8139 at 
0xe0816000, 00:e0:4c:ca:16:21, IRQ 19
Jul 11 10:34:29 ds80-237-204-39 kernel: eth1:  Identified 8139 chip type 
'RTL-8100B/8139D'
Jul 11 10:34:29 ds80-237-204-39 kernel: Uniform Multi-Platform E-IDE 
driver Revision: 7.00alpha2
....
Jul 11 10:34:29 ds80-237-204-39 kernel: input: AT Translated Set 2 
keyboard on isa0060/serio0
Jul 11 10:34:29 ds80-237-204-39 kernel: NET: Registered protocol family 2
Jul 11 10:34:29 ds80-237-204-39 kernel: IP: routing cache hash table of 
4096 buckets, 32Kbytes
Jul 11 10:34:29 ds80-237-204-39 kernel: TCP: Hash tables configured 
(established 32768 bind 65536)
Jul 11 10:34:29 ds80-237-204-39 kernel: Initializing IPsec netlink socket
Jul 11 10:34:29 ds80-237-204-39 kernel: NET: Registered protocol family 1
Jul 11 10:34:29 ds80-237-204-39 kernel: NET: Registered protocol family 15
Jul 11 10:34:29 ds80-237-204-39 kernel: kjournald starting.  Commit 
interval 5 seconds
Jul 11 10:34:29 ds80-237-204-39 kernel: EXT3-fs: mounted filesystem with 
ordered data mode.
Jul 11 10:34:29 ds80-237-204-39 kernel: VFS: Mounted root (ext3 
filesystem) readonly.
Jul 11 10:34:29 ds80-237-204-39 kernel: Freeing unused kernel memory: 
140k freed
Jul 11 10:34:29 ds80-237-204-39 kernel: Adding 650592k swap on 
/dev/hda5.  Priority:1 extents:1
Jul 11 10:34:29 ds80-237-204-39 kernel: EXT3 FS on hda6, internal journal
Jul 11 10:34:29 ds80-237-204-39 kernel: eth0: link up, 100Mbps, 
full-duplex, lpa 0x41E1
Jul 11 10:34:30 ds80-237-204-39 kernel: NET: Registered protocol family 10
Jul 11 10:34:30 ds80-237-204-39 kernel: Disabled Privacy Extensions on 
device c037eb00(lo)
Jul 11 10:34:30 ds80-237-204-39 kernel: IPv6 over IPv4 tunneling driver
Jul 11 10:34:41 ds80-237-204-39 kernel: eth0: no IPv6 routers present
Jul 17 13:33:43 ds80-237-204-39 kernel: input: AT Translated Set 2 
keyboard on isa0060/serio0

But when the system is started, I cannot ping or ssh into it.  Ssh won't 
start on the server anyways, as I can see in the log, since the network 
is not up.  Nothing else besides the kernel messages in any other log 
files.  Could I have something with tcpip or something setup wrong?  I 
do not have a firewall configured.  I have also tried dumping udev and 
hotplug, and creating all /dev devices with MAKEDEV.  Nothing new.

I appreciate any help getting this devil working!  Thanks!

-- 
Justin R. Knierim
lfs at jrknierim dot de




More information about the lfs-support mailing list