General question Fedora 5?

Well,
We having a working model, all that is except the external routing. I can ping the box but can’t ping out. Hopefully ifconfig will give you an idea, after further review it’s not “just fine”

[[root@hosta webmin-1.270]]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:B3:0A:85:97
inet addr:69.128.106.189 Bcast:69.128.106.191 Mask:255.255.255.248
inet6 addr: fe80::202:b3ff:fe0a:8597/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:22 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:20671 errors:0 dropped:0 overruns:0 frame:0
TX packets:20671 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:18501706 (17.6 MiB) TX bytes:18501706 (17.6 MiB)

Hey Dan,

So eth0 is definitely up. Strangely I’m only seeing collisions on this interface…and that aint right.

Could there be another device on your network with the same IP or MAC address?

What appears in the kernel log when you try to ping out? (This can be seen by typing "dmesg" at the command line.)

Good thing God gave me lots of hair!!

Here’s this:

/etc/sysconfig/network/ifconfig-eth0:
GATEWAY=69.128.106.185
BOOTPROTO=none
TYPE=Ethernet
HWADDR=00:02:B3:0A:85:97
DEVICE=eth0
MTU=""
NETMASK=255.255.255.248
BROADCAST=69.128.106.191
IPADDR=69.128.106.189
NETWORK=69.128.106.184
ONBOOT=yes

/resolv.conf:
search solvdns.net
nameserver 216.126.128.40
nameserver 4.2.2.1
nameserver 216.165.129.157

/network-scripts/ifconfig-eth0
GATEWAY=69.128.106.185
BOOTPROTO=none
TYPE=Ethernet
HWADDR=00:02:B3:0A:85:97
DEVICE=eth0
MTU=""
NETMASK=255.255.255.248
BROADCAST=69.128.106.191
IPADDR=69.128.106.189
NETWORK=69.128.106.184
ONBOOT=yes

When I manually changed BOOTPROTO to static on all occasions and rebooted It froze the boot at CUPS, NFS and such. I never did get it to route.

Just to check the card I reinstalled Slack 10.2 ( twice after realizing that GRUB was living in the MBR) I went right away to startx, opened Konquerer, tyoed in webmin.com and boom, webmin shows up. So the card isn’t fried.

I’ll give it one last gasp, trying to make sure that CUPS and NFS are not in it (who needs printing on a server??)

It was no go with the 4.2 server iso. Same problem. Thought I would try letting it install as a DHCP device but all that did was hang up the boot process.

I’m DLing the 3.7 server torrent and will give that a try. Otherwise it’s a bug and I’ll send in the motherboard and NIC info.

tapping fingers waiting for the Slack version…

OH,
How does one mount and access the CDROM or floppy in barebones centOS?

Hey Dan,

CUPS and NFS would only freeze (and not really freeze…they would timeout and eventually fail and the boot would continue after some period of time) if you don’t have any interfaces (i.e. not even loopback) or if they have been configured explicitly to use other non-loopback interfaces. I’m not sure how you’d end up in that situation. If they actually freeze the system then I’m pretty sure your hardware has some kind of pretty serious problem.

I think I’d still like to see the kernel log output. It seems like something serious is wrong on your box, and I don’t know that configuration is going to change that. dmesg might give you some clues about where things are going awry.

I did the mesg and got this eth related stuff

e100:Intel pro/100 driver 3.4.8-k2-napi
e100:eth0:e100_watchdog: linkup, 10 mps, halfduplex
eth0: no IPv6 router present

net: registering protcol family 2
IP: routing cache hash table of 4096 buckets, 64 Kbytes
TCP: hash tables configured (established 131072 bind 43690)
Initialized IPsec netlink socket
net: registering protcol family 1
net: registering protcol family 17

net: registering protcol family 10
Disabled privacy extensions on device xxxxxxxx (lo)
IPv6 over IPv4 tunneling driver

and then these divert statements:

divert: allocating diver_blk for eth0

divert: not allocating divert_blk for nonethernet device sit0

What is sit0??

The rest was standard fare boot items and probes

half duplex I’ve never seen but shouldn’t bother, I’m familiar with this IPv6 over IPv4 tunneling though.

LOL, freeze is the word for the impatient. The timeouts were incredibly long, in the area of 15-20 minutes if I could wait that long.

well, CentOS 3.7 server installed and pings outside the box. I ran your virtmin.sh. What is the username and password for webmin?

skip the last post :wink:

I have virtminPro up and running now and am fairly impressed, having been using Virtualmin for a few years now the extras deserve kudos.

As I’m tweaking I have to ask, do I want to try to upgrade to CentOS4? The most obvious thing I noticed on install of 3 was the user option to choose to run all traffic through eth0 ( had to actually select the device, though it was the only choice)

Still have no idea why CentOS 4 refused to route.

Not stop is throwing AWBS into the works. Anything I should know in advance?