12-01-2003
I had this problem back when I was running red hat 7.3 . I worked at it a lot and no matter what it did it refused to activate eth0 for the home network. This problem was very common among the people I knew who were running 7.3. When I upgraded to 8.0 the problem had been rectified. Even though it should not have been a problem, for some reason 7.3 had odd quirks when run on a dual boot with windows, but when it was running on the box by itself it didnt experience any problems. For me, the inability to activate eth0 on a home network was one of those problems. I wish I had an easier answer for you but I am at a loss, I would suggest upgrading to Fedora Core 1.
9 More Discussions You Might Find Interesting
1. IP Networking
We have just moved offices and in the same week recieved a SUN box from another company site.
I'm attemting to connect this SUN box to the network, but i can't see it on the network.
I have modified the /etc/host file with the IP i want to attribute to the box, rebooted, but still nothing.... (1 Reply)
Discussion started by: colesy
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I was wondering if anyone could help me out with this problem. I have SCO 5.0.5 installed on a system that I am using 3c905b (3 Com) network card. This system is always powered on. After no certain time period this NIC doesn't work. I can't ping to this system from any other machine or vice... (5 Replies)
Discussion started by: Tinal
5 Replies
3. IP Networking
hi all,
Using kermit, i made serial dialup connetion between two PCs through telephone line and transfered files trough this line. The code appears as like this,
set modem type generic #Setting the modem type.
set modem data-compression on #Data compression on to speed up transfer.... (0 Replies)
Discussion started by: pcsaji
0 Replies
4. UNIX for Dummies Questions & Answers
I have a network connection problem in unix. I am trying to access to LAN in unix but unfortunately it doesn't work. For example, if I ping from Unix to windows it says 'the network is unreacable'. Also, I can't ping in windows to unix.
I would be glad if someone could help me.
Thanks.
... (5 Replies)
Discussion started by: fatihshen
5 Replies
5. Ubuntu
Hi,
I am using ubuntu 8.x. I am not not able connect to internet through broadband. i'm also using windows xp, there i don't have any problems.
Please tell me how access the internet on ubuntu 8.x through broadband.
Thanks,
Achhayya:) (4 Replies)
Discussion started by: achhayya
4 Replies
6. Solaris
Hello colleague,
Development department is deploying some applications on solaris machine but hence all connection goes down.
Our all network connection files are correct but we can't connect with our gw. Only we can ping localhost and assigned ip address.
I don't want to reboot for... (4 Replies)
Discussion started by: getrue
4 Replies
7. Linux
Hi, I installed linux Fedora on a virtual machine, but the network connection is not working. All firewalls are off. Any ideas what is the problem? I am using WiFi.
Thanks in advance!
Regards,
Atanas (2 Replies)
Discussion started by: apenkov
2 Replies
8. Solaris
hi,
I'm setting up a home lab and I am having problems keeping my connection open on putty. every time i leave it for about 10 seconds and come back I keep having to re-connect. I'm more of a AIX person and trying to get more fimilar with Sun but some of the commands I am trying to run to diag... (2 Replies)
Discussion started by: vpundit
2 Replies
9. Solaris
Hi,
Recently we faced awkward situation where we cannot connect to Oracle DB that hosted in Solaris server intermittently and it timeout eventually. The server seems fine. We can putty to server like normal but when try do prstat, it takes time and come out Please Wait.. for a while. When we go... (1 Reply)
Discussion started by: tharmendran
1 Replies
LEARN ABOUT DEBIAN
aoe-discover
aoe-discover(8) System Manager's Manual aoe-discover(8)
NAME
aoe-discover - tell aoe driver to discover AoE devices
SYNOPSIS
aoe-discover
DESCRIPTION
The aoe-discover command tells the aoe driver to discover ATA over Ethernet (AoE) devices on the network. All network interfaces will be
probed with a AoE config query broadcast.
If the aoe-interfaces command has limited the allowable network interfaces, only devices discovered via allowable interfaces will become
available. The default is to make available all AoE devices found on all accessible ethernet networks.
It's good to run the aoe-discover command after running aoe-interfaces.
EXAMPLE
In this example, the root user on a host named nai loads the aoe module with only eth0 allowable for AoE traffic. After remembering that
shelf 7 is on eth3, this sysadmin uses aoe-interfaces to add eth3 to the list of allowable network interfaces and then calls aoe-discover
to ask the aoe driver to look for new AoE devices.
nai:~# modprobe aoe aoe_iflist="eth0"
nai:~# aoe-stat
e10.9 eth0 up
nai:~# aoe-interfaces eth0 eth3
nai:~# aoe-discover
nai:~# aoe-stat
e7.0 eth3 up
e7.1 eth3 up
e7.2 eth3 up
e7.3 eth3 up
e7.4 eth3 up
e7.5 eth3 up
e7.6 eth3 up
e7.7 eth3 up
e7.8 eth3 up
e7.9 eth3 up
e10.9 eth0 up
SEE ALSO
aoe-interfaces(8), aoe-stat(8), aoetools(8).
AUTHOR
Ed L. Cashin (ecashin@coraid.com)
aoe-discover(8)