Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl
Craig White wrote:

On Sun, 2008-09-28 at 22:53 +0800, [EMAIL PROTECTED] wrote:
  

Dear All,

I just have the problem of Destination Host Unreachable from eth1
( ping to other same network segment internal machine ) as the
following setting :

[EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=no
[EMAIL PROTECTED] network-scripts]#

[EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
DEVICE=eth1
BOOTPROTO=static
BROADCAST=192.168.0.255
IPADDR=192.168.0.254
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes
[EMAIL PROTECTED] network-scripts]#

[EMAIL PROTECTED] network-scripts]# cat ../network
NETWORKING=yes
HOSTNAME=svr1
[EMAIL PROTECTED] network-scripts]#

So, what is the problem of the current setting ?



looks OK except that I would recommend that you use a FQDN
in /etc/sysconfig/network and not just a name... i.e. srv1.mynetwork.com

obviously /dev/eth0 is not going to be loaded at boot time - but that
may be your intentions.

  

BTW, what different between modify ifcfg-eth? and running the tools of
system-config-network ?



shouldn't be any difference as either should modify the
same /etc/sysconfig/network-scripts/ifcfg-ethX file

system-config-network does have the ability to also edit your 'hosts'
file (/etc/hosts), you dns resolution configuration (/etc/resolv.conf)
at one session.

Craig

  

Hello,

How can we enable and verify the Network Interface working with full
duplex mode ?

Thanks

Edward.
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl
Aldo Foot wrote:

On Sun, Sep 28, 2008 at 7:53 AM,  [EMAIL PROTECTED] wrote:
  

Dear All,

I just have the problem of Destination Host Unreachable from eth1 ( ping
to other same network segment internal machine ) as the following setting :

[EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=no
[EMAIL PROTECTED] network-scripts]#

[EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
DEVICE=eth1
BOOTPROTO=static
BROADCAST=192.168.0.255
IPADDR=192.168.0.254
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes
[EMAIL PROTECTED] network-scripts]#

[EMAIL PROTECTED] network-scripts]# cat ../network
NETWORKING=yes
HOSTNAME=svr1
[EMAIL PROTECTED] network-scripts]#

So, what is the problem of the current setting ?

BTW, what different between modify ifcfg-eth? and running the tools of
system-config-network ?



The system-config-network is just a GUI to make it easier to configure
the devices.

What kind of network devices do you have? are they PCI cards or
attached to the motherboard?

~af
  

/etc/modprobe.conf :
aliases eth0 8139too
aliases eth1 r8169

For 8139too driver, it is a network interface PCI card ( 10/100M half
duplex )...
For r8169 driver, it is attached to the motherboard ( ASUS Desktop
Barebone : P2-P5945GCX, 1.0G )...

The System is FC8...

So, any more help for me ?

Thanks !

Edward.
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [Fwd: Config Network Setting]

2008-09-29 Thread Les Mikesell

[EMAIL PROTECTED] wrote:




I just have the problem of Destination Host Unreachable from eth1
( ping to other same network segment internal machine ) as the
following setting :

[EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=no
[EMAIL PROTECTED] network-scripts]#

[EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
DEVICE=eth1
BOOTPROTO=static
BROADCAST=192.168.0.255
IPADDR=192.168.0.254
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes
[EMAIL PROTECTED] network-scripts]#

[EMAIL PROTECTED] network-scripts]# cat ../network
NETWORKING=yes
HOSTNAME=svr1
[EMAIL PROTECTED] network-scripts]#

So, what is the problem of the current setting ?
   



looks OK except that I would recommend that you use a FQDN
in /etc/sysconfig/network and not just a name... i.e. srv1.mynetwork.com

obviously /dev/eth0 is not going to be loaded at boot time - but that
may be your intentions.

 


BTW, what different between modify ifcfg-eth? and running the tools of
system-config-network ?
   



shouldn't be any difference as either should modify the
same /etc/sysconfig/network-scripts/ifcfg-ethX file

system-config-network does have the ability to also edit your 'hosts'
file (/etc/hosts), you dns resolution configuration (/etc/resolv.conf)
at one session.

Craig

 


Hello,

How can we enable and verify the Network Interface working with full
duplex mode ?



Run ethtool to display the current settings.  You can also include 
ETHTOOL_OPTS in your ifcfg-ethX file to force a setting but if the other 
end of the connection is set to autonegotiate both ends must negotiate - 
and current equipment usually gets it right.


--
  Les Mikesell
[EMAIL PROTECTED]

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl
Les Mikesell wrote:

 [EMAIL PROTECTED] wrote:



 I just have the problem of Destination Host Unreachable from eth1
 ( ping to other same network segment internal machine ) as the
 following setting :

 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
 DEVICE=eth0
 BOOTPROTO=dhcp
 ONBOOT=no
 [EMAIL PROTECTED] network-scripts]#

 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
 DEVICE=eth1
 BOOTPROTO=static
 BROADCAST=192.168.0.255
 IPADDR=192.168.0.254
 NETMASK=255.255.255.0
 NETWORK=192.168.0.0
 ONBOOT=yes
 [EMAIL PROTECTED] network-scripts]#

 [EMAIL PROTECTED] network-scripts]# cat ../network
 NETWORKING=yes
 HOSTNAME=svr1
 [EMAIL PROTECTED] network-scripts]#

 So, what is the problem of the current setting ?

 
 looks OK except that I would recommend that you use a FQDN
 in /etc/sysconfig/network and not just a name... i.e.
 srv1.mynetwork.com

 obviously /dev/eth0 is not going to be loaded at boot time - but that
 may be your intentions.
 


 BTW, what different between modify ifcfg-eth? and running the tools of
 system-config-network ?

 
 shouldn't be any difference as either should modify the
 same /etc/sysconfig/network-scripts/ifcfg-ethX file

 system-config-network does have the ability to also edit your 'hosts'
 file (/etc/hosts), you dns resolution configuration (/etc/resolv.conf)
 at one session.

 Craig



 Hello,

 How can we enable and verify the Network Interface working with full
 duplex mode ?


 Run ethtool to display the current settings. You can also include
 ETHTOOL_OPTS in your ifcfg-ethX file to force a setting but if the
 other end of the connection is set to autonegotiate both ends must
 negotiate - and current equipment usually gets it right.

Hello,

How to enable the NIC with full duplex mode by using option
ETHTOOL_OPTS in ifcfg-ethx file ?
Is there sample config for reference ?

Thanks !

Edward.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl


Les Mikesell wrote:

 [EMAIL PROTECTED] wrote:



 I just have the problem of Destination Host Unreachable from eth1
 ( ping to other same network segment internal machine ) as the
 following setting :

 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
 DEVICE=eth0
 BOOTPROTO=dhcp
 ONBOOT=no
 [EMAIL PROTECTED] network-scripts]#

 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
 DEVICE=eth1
 BOOTPROTO=static
 BROADCAST=192.168.0.255
 IPADDR=192.168.0.254
 NETMASK=255.255.255.0
 NETWORK=192.168.0.0
 ONBOOT=yes
 [EMAIL PROTECTED] network-scripts]#

 [EMAIL PROTECTED] network-scripts]# cat ../network
 NETWORKING=yes
 HOSTNAME=svr1
 [EMAIL PROTECTED] network-scripts]#

 So, what is the problem of the current setting ?

 
 looks OK except that I would recommend that you use a FQDN
 in /etc/sysconfig/network and not just a name... i.e.
 srv1.mynetwork.com

 obviously /dev/eth0 is not going to be loaded at boot time - but that
 may be your intentions.
 


 BTW, what different between modify ifcfg-eth? and running the tools of
 system-config-network ?

 
 shouldn't be any difference as either should modify the
 same /etc/sysconfig/network-scripts/ifcfg-ethX file

 system-config-network does have the ability to also edit your 'hosts'
 file (/etc/hosts), you dns resolution configuration (/etc/resolv.conf)
 at one session.

 Craig



 Hello,

 How can we enable and verify the Network Interface working with full
 duplex mode ?


 Run ethtool to display the current settings. You can also include
 ETHTOOL_OPTS in your ifcfg-ethX file to force a setting but if the
 other end of the connection is set to autonegotiate both ends must
 negotiate - and current equipment usually gets it right.

Dear All,

I just found a message for /var/log/messages :
kernel : udev: renamed network interface eth0 to eth1

So, how to solve this problem ?

Thanks !

Edward.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-29 Thread Aldo Foot
On Mon, Sep 29, 2008 at 7:05 AM,  [EMAIL PROTECTED] wrote:
 Dear All,

 I just found a message for /var/log/messages :
 kernel : udev: renamed network interface eth0 to eth1

 So, how to solve this problem ?

In a previous reply you said:
 For 8139too driver, it is a network interface PCI card
  For r8169 driver, it is attached to the motherboard 

I have seen before that the OS will change the device if you have a PCI and
a built-in NIC. If you unplug the PCI NIC, the built-in NIC becomes
eth0. With the
PCI NIC plugged in, the built-in NIC becomes eth1 and the PCI becomes eth0.
Try unplugging the PCI NIC to check whether this is the case with your
machine; take note of the MAC address with the ifconfig command to track
which one is which.

I have not understood why this happens though. Maybe someone can shed some
light here.
~af

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl


Aldo Foot wrote:

On Mon, Sep 29, 2008 at 7:05 AM,  [EMAIL PROTECTED] wrote:
  

Dear All,

I just found a message for /var/log/messages :
kernel : udev: renamed network interface eth0 to eth1

So, how to solve this problem ?



In a previous reply you said:
 For 8139too driver, it is a network interface PCI card
  For r8169 driver, it is attached to the motherboard 

I have seen before that the OS will change the device if you have a PCI and
a built-in NIC. If you unplug the PCI NIC, the built-in NIC becomes
eth0. With the
PCI NIC plugged in, the built-in NIC becomes eth1 and the PCI becomes eth0.
Try unplugging the PCI NIC to check whether this is the case with your
machine; take note of the MAC address with the ifconfig command to track
which one is which.

I have not understood why this happens though. Maybe someone can shed some
light here.
~af

  

Hello,

Is this problem in FC8 System only ?
So, have you tried to find doc though the net ?

Thanks !

Edward.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [Fwd: Config Network Setting]

2008-09-29 Thread Aldo Foot
On Mon, Sep 29, 2008 at 9:46 AM,  [EMAIL PROTECTED] wrote:


 Aldo Foot wrote:

 On Mon, Sep 29, 2008 at 7:05 AM,  [EMAIL PROTECTED] wrote:


 Dear All,

 I just found a message for /var/log/messages :
 kernel : udev: renamed network interface eth0 to eth1

 So, how to solve this problem ?


 In a previous reply you said:
  For 8139too driver, it is a network interface PCI card
   For r8169 driver, it is attached to the motherboard 

 I have seen before that the OS will change the device if you have a PCI and
 a built-in NIC. If you unplug the PCI NIC, the built-in NIC becomes
 eth0. With the
 PCI NIC plugged in, the built-in NIC becomes eth1 and the PCI becomes eth0.
 Try unplugging the PCI NIC to check whether this is the case with your
 machine; take note of the MAC address with the ifconfig command to track
 which one is which.

 I have not understood why this happens though. Maybe someone can shed some
 light here.
 ~af



 Hello,

 Is this problem in FC8 System only ?
 So, have you tried to find doc though the net ?


disclamer
I have not done this and I don't know whether that is accurate.
/disclaimer

I did some reading. It appears that udev does the device switching. But
if desired, the devices can be tied to a specific mac address.

See this old thread --notice what they say about /etc/modprobe.conf.
http://www.redhat.com/archives/k12osn/2005-September/msg00354.html

Read this Debian related page:  http://www.debianhelp.co.uk/udev.htm

I don't now whether the problem is with F8 only. I haven't tried all
the flavors.
~af

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl


Aldo Foot wrote:

On Mon, Sep 29, 2008 at 9:46 AM,  [EMAIL PROTECTED] wrote:
  

Aldo Foot wrote:

On Mon, Sep 29, 2008 at 7:05 AM,  [EMAIL PROTECTED] wrote:


Dear All,

I just found a message for /var/log/messages :
kernel : udev: renamed network interface eth0 to eth1

So, how to solve this problem ?


In a previous reply you said:
 For 8139too driver, it is a network interface PCI card
  For r8169 driver, it is attached to the motherboard 

I have seen before that the OS will change the device if you have a PCI and
a built-in NIC. If you unplug the PCI NIC, the built-in NIC becomes
eth0. With the
PCI NIC plugged in, the built-in NIC becomes eth1 and the PCI becomes eth0.
Try unplugging the PCI NIC to check whether this is the case with your
machine; take note of the MAC address with the ifconfig command to track
which one is which.

I have not understood why this happens though. Maybe someone can shed some
light here.
~af



Hello,

Is this problem in FC8 System only ?
So, have you tried to find doc though the net ?




disclamer
I have not done this and I don't know whether that is accurate.
/disclaimer

I did some reading. It appears that udev does the device switching. But
if desired, the devices can be tied to a specific mac address.

See this old thread --notice what they say about /etc/modprobe.conf.
http://www.redhat.com/archives/k12osn/2005-September/msg00354.html

Read this Debian related page:  http://www.debianhelp.co.uk/udev.htm

I don't now whether the problem is with F8 only. I haven't tried all
the flavors.
~af
  

Hello,

How can we disable the udev for switching the device with FC8 System ?

Thanks !

Edward.



-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [Fwd: Config Network Setting]

2008-09-29 Thread edwardspl



Aldo Foot wrote:

On Mon, Sep 29, 2008 at 9:46 AM,  [EMAIL PROTECTED] wrote:
  

Aldo Foot wrote:

On Mon, Sep 29, 2008 at 7:05 AM,  [EMAIL PROTECTED] wrote:


Dear All,

I just found a message for /var/log/messages :
kernel : udev: renamed network interface eth0 to eth1

So, how to solve this problem ?


In a previous reply you said:
 For 8139too driver, it is a network interface PCI card
  For r8169 driver, it is attached to the motherboard 

I have seen before that the OS will change the device if you have a PCI and
a built-in NIC. If you unplug the PCI NIC, the built-in NIC becomes
eth0. With the
PCI NIC plugged in, the built-in NIC becomes eth1 and the PCI becomes eth0.
Try unplugging the PCI NIC to check whether this is the case with your
machine; take note of the MAC address with the ifconfig command to track
which one is which.

I have not understood why this happens though. Maybe someone can shed some
light here.
~af



Hello,

Is this problem in FC8 System only ?
So, have you tried to find doc though the net ?




disclamer
I have not done this and I don't know whether that is accurate.
/disclaimer

I did some reading. It appears that udev does the device switching. But
if desired, the devices can be tied to a specific mac address.

See this old thread --notice what they say about /etc/modprobe.conf.
http://www.redhat.com/archives/k12osn/2005-September/msg00354.html

Read this Debian related page:  http://www.debianhelp.co.uk/udev.htm

I don't now whether the problem is with F8 only. I haven't tried all
the flavors.
~af
  


Hello,

If disbale the onboard lan and install another INC, then, is there still
the problem ?

Thanks !

Edward.
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [Fwd: Config Network Setting]

2008-09-28 Thread Craig White
On Sun, 2008-09-28 at 22:53 +0800, [EMAIL PROTECTED] wrote:
 Dear All,
 
 I just have the problem of Destination Host Unreachable from eth1
 ( ping to other same network segment internal machine ) as the
 following setting :
 
 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
 DEVICE=eth0
 BOOTPROTO=dhcp
 ONBOOT=no
 [EMAIL PROTECTED] network-scripts]#
 
 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
 DEVICE=eth1
 BOOTPROTO=static
 BROADCAST=192.168.0.255
 IPADDR=192.168.0.254
 NETMASK=255.255.255.0
 NETWORK=192.168.0.0
 ONBOOT=yes
 [EMAIL PROTECTED] network-scripts]#
 
 [EMAIL PROTECTED] network-scripts]# cat ../network
 NETWORKING=yes
 HOSTNAME=svr1
 [EMAIL PROTECTED] network-scripts]#
 
 So, what is the problem of the current setting ?

looks OK except that I would recommend that you use a FQDN
in /etc/sysconfig/network and not just a name... i.e. srv1.mynetwork.com

obviously /dev/eth0 is not going to be loaded at boot time - but that
may be your intentions.

 
 BTW, what different between modify ifcfg-eth? and running the tools of
 system-config-network ?

shouldn't be any difference as either should modify the
same /etc/sysconfig/network-scripts/ifcfg-ethX file

system-config-network does have the ability to also edit your 'hosts'
file (/etc/hosts), you dns resolution configuration (/etc/resolv.conf)
at one session.

Craig


-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-28 Thread Aldo Foot
On Sun, Sep 28, 2008 at 7:53 AM,  [EMAIL PROTECTED] wrote:
 Dear All,

 I just have the problem of Destination Host Unreachable from eth1 ( ping
 to other same network segment internal machine ) as the following setting :

 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth0
 DEVICE=eth0
 BOOTPROTO=dhcp
 ONBOOT=no
 [EMAIL PROTECTED] network-scripts]#

 [EMAIL PROTECTED] network-scripts]# cat ifcfg-eth1
 DEVICE=eth1
 BOOTPROTO=static
 BROADCAST=192.168.0.255
 IPADDR=192.168.0.254
 NETMASK=255.255.255.0
 NETWORK=192.168.0.0
 ONBOOT=yes
 [EMAIL PROTECTED] network-scripts]#

 [EMAIL PROTECTED] network-scripts]# cat ../network
 NETWORKING=yes
 HOSTNAME=svr1
 [EMAIL PROTECTED] network-scripts]#

 So, what is the problem of the current setting ?

 BTW, what different between modify ifcfg-eth? and running the tools of
 system-config-network ?

The system-config-network is just a GUI to make it easier to configure
the devices.

What kind of network devices do you have? are they PCI cards or
attached to the motherboard?

~af

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


[Fwd: Config Network Setting]

2008-09-27 Thread edwardspl
Dear All,

After modify the config files, I can't restart the network controll by
using /etc/rc.d/init.d/network restart...

Thanks !

Edward.

 Original Message 
Subject:Config Network Setting
Date:   Sat, 27 Sep 2008 14:43:32 +0800
From:   [EMAIL PROTECTED]
Reply-To:   Community assistance, encouragement, and advice for using
Fedora. fedora-list@redhat.com
To: fedora-list@redhat.com fedora-list@redhat.com



Dear All,

Mine is FC8 System...
So, if I want to modify the config of controller card, then I need to
edit the following files ?
/etc/sysconifg/network-scripts/ifcfg-eth?
/etc/modprobe.conf

And what else other profile also need to be modified ?

Thanks !

Edward.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

__ NOD32 3475 (20080926) Information __

This message was checked by NOD32 antivirus system.
http://www.nod32.com.hk




-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: [Fwd: Config Network Setting]

2008-09-27 Thread Craig White
On Sat, 2008-09-27 at 15:08 +0800, [EMAIL PROTECTED] wrote:
 Dear All,
 
 After modify the config files, I can't restart the network controll by
 using /etc/rc.d/init.d/network restart...
 
 Thanks !
 
 Edward.
 
  Original Message  
   Subject: 
 Config Network Setting
  Date: 
 Sat, 27 Sep 2008 14:43:32 +0800
  From: 
 [EMAIL PROTECTED]
  Reply-To: 
 Community assistance,
 encouragement, and advice for using
 Fedora. fedora-list@redhat.com
To: 
 fedora-list@redhat.com
 fedora-list@redhat.com
 
 
 Dear All,
 
 Mine is FC8 System...
 So, if I want to modify the config of controller card, then I need to
 edit the following files ?
 /etc/sysconifg/network-scripts/ifcfg-eth?
 /etc/modprobe.conf
 
 And what else other profile also need to be modified ?
 

crystal ball cloudy...

why did you modify /etc/modprobe.conf?

what is error in /var/log/messages?

what is output of...
cat /etc/sysconfig/network-scripts/ifcfg-eth*
cat /etc/modprobe.conf

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Re: [Fwd: Config Network Setting]

2008-09-27 Thread Aldo Foot
On Sat, Sep 27, 2008 at 12:08 AM,  [EMAIL PROTECTED] wrote:
 Mine is FC8 System...
 So, if I want to modify the config of controller card, then I need to
 edit the following files ?
 /etc/sysconifg/network-scripts/ifcfg-eth?
 /etc/modprobe.conf

 And what else other profile also need to be modified ?



 /etc/modprobe.conf has nothing to do with your network settings.

First ---  look here
http://docs.fedoraproject.org/install-guide/f8/en_US/ch-networkconfig.html

Then --- As root launch /usr/sbin/system-config-network and configure your
netcard, which by default is eth0.

~af

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines