I'm using Fedora 12 on a box with 2 separate NICs in different subnets. The problem is that after a reboot, both NICs always show up as eth0 when you left click on the networking icon on the top right. I have to manually change one of them to eth1 & then things start working.
DEVICE=eth0
HWADDR=(mac address)
BOOTPROTO=none
TYPE=Ethernet
ONBOOT=yes
[Code]....
I have a Proliant DL 120 G5 with CentOS 5.4 and I have installed a Brodcom Corporation Netxtrem BCM 5722 Gigabit Ethernet PCI. So I have two interfaces: eth0 broadcom eth1 Intel The eth1 works, instead eth0 don't work. I can ping itself and 127.0.0.1 but I can't ping the gateway. The results of netstat -nr is:
[code]....
I just finished installing Fedora 12 on a rack mount server. I was modifying the /etc/sysconfig/network-scripts/ifcfg-eth0 file to use a static IP address, but now nothing works. The device does not boot on start up or anything.Currently, ifcfg-eth0 looks like:
Quote:
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none[code].....
The eth0 device does not start on boot; the server does not get the IP address, is not reachable over the network, and will not connect to the internet....
I am trying to sort out some issues following an upgrade from F12.
I have eth0 as the connection I want to use. Prior to the upgrade, this connection was enabled and active at boot.
Now, for some reason after the upgrade it has to be manually enabled at every boot - even though when I go the Network tool, Ethernet Device > General tab - "Activate device when computer starts" is checked.
At every boot time it is inactive.
In all the ifcft-eth0 files, the ONBOOT parameter is set to "yes".
im trying to setup eth0 with subdevice eth0.0 and eth0.99 to come up at boot
eth0 is dhcp clint
eth0:0 is static ip
eth0.99 is 802.1q vlan interface
/etc/network/interfaces
Code:
auto lo
[Code]....
I have a server that provides the access to the net. It has 3 nics 2 Realtek 100mb and a ne2000 isa 10mb card for the net. I ran an update from a working configuration on Fedora 9 to Fedora 10 with yum upgrade. Fedora 10 does not find the the ne2000 at boot time. After booting I can modprobe ne and the nic is found in a new network restart call. Has something changed how modules are loaded before udev runs?
Then there is the problem that nics are assigned the wrong interfaces(eth*). I have configured it in sysconfig with the files ifcfg-eth(0-2). I do not run NetworkManager. Has something changed in the configuration how the interfaces are assigned to the nics via the mac addresses?
I have tried to change the net profile of udev but since the ne2000 is not found at boot time but had no success. And one of the Realtek nics is not found at some times.
I've just installed Fedora 10 to basically work as a NAS for another machine - but also serve a couple of web pages. After having alot of issues with network manager (with it changing the subnet so nothing would work), I'm now almost there:
I have two network cards connected in the server:
1) eth0 connects to a switch that ultimately connects it to the net (on a 10.0.0.* network)
2) eth1 connects directly into another server for backups (192.168.0.* network).
Now when I setup eth0, I get network access can ping/ update/ surf the net - absolutely no problems, but when I connect eth1 in - the net dies and nothing works, I can ping devices on both the 10.0.* and 192.168.* networks, just nothing past the gateway. I presume this is either a route or DNS issue, but am unsure about where its falling foul - both the resolv.conf file looks fine as do the ifcfg-ethx scripts.
I have a program that attaches to an interface. I can run two copies of the program on two systems (each running one instance), connect it to a switch, say 1.1.1.1 & 1.1.2.1. In this configuration two instances of the program can communicate and everything is fine.Now, to reduce cost, it want to use only one system with two nics connected to the same switch, running two instances of the above program, each instance attached to two interfaces respectively on the system. I have the following settings:
eth1 Link encap:Ethernet HWaddr XXXXXXXXXXXXXXX
inet addr:1.1.1.1 Bcast:1.1.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[code]....
However I cannot ping one from the other.
Neither "ping -I eth1 1.1.2.1" nor "ping -I eth2 1.1.1.1" works.
i have a Server, which has 2 nics installed. Each of those is connected to a router, which is connected to internet. On the server, i have apache, maillserver and im-server running. On the other hand, also squid, dansguardian and clam are running. so now: via eth0 i would like to have just the traffic, which is requested from outside (the big bad internet..) to my server (apache, mail, etc). via eth1 i would like to have all OUTGOING (also to the big bad internet) from the server, which is requested by a internal client. And of course all requests to my own server
both nics shall route their traffic to their own router. For better comprehension please consult the enclosed graph. Until now, i did not find a good solution, the default route is set to the traffic from eth0, if not, no external request will find back to a client do you have a idea how to handle this the easiest way?
I want to connect my modem straight to my fedora 13 box, using it as a firewall, and I want to use my wireless card to set up an ad-hoc to give internet to the windows computers in my house. My router has been messing up and I am trying to create a quick fix until I can solve the problem.
My eth0 has internet connectivity but when I use the brctl command to try to create a bridge it doesn't let me add my wireless card, wlan0, and also I lose internet while my eth0 is in a bridge. I am fairly new to Linux.
5.10 Breezy configured as machine controller. Works great eth0 is a fixed IP to communicate with controller comms board. Not easy at all to alter - the comms board is hard coded to listen on eth0 for commands.
I can use eth1 as the default gateway and ping google.com, etc. But when I now attempt to communicate with the controller with netcat, e.g.
Code: echo !HH | nc 192.168.1.6 80
I obviously never get an answer since the request is passed via eth1. Using the -g option with netcat doesn't work either. I had a look at iptables but it doesn't seem to be able to do what I want. How I can still use eth0 as my communication port to the controller whilst eth1 is the default gateway?
I have two servers on a vlan at my datacentre/colocation and previously both servers had public IPs on their eth0 interfaces. The servers are HP ProLiant DL360s - one is a G4 and one is a G5 The newer G5 is now the LAMP server and the G4 has been retired and I want to repurpose it as an iSCSI target using openfiler freenas or similar.
My G5 has public/static IPs lashed to the eth0 physical interface and the eth1 is not configured to do anything yet. The G4 will have both interfaces available - perhaps one for ssh access from one of my static public IPs and the other to be a private IP on the local vlan. Here is what I am trying to get my head around...
The G5
eth0 - Public IP - full LAMP services on two or three virtual interfaces
eth1 - Private IP 192.168.0.1
The G4
eth0 - Public IP for ssh
eth1 - Private IP 192.168.0.2
Because my traffic between eth1 on these boxes is via private IPs on the local private vlan it doesn't add to my quota for bandwidth. How do I go about configuring the routing and gateways and other aspects of this so that I can run a private IP space network between the eth1s and still serve the outside world from the eth0s...
I am afraid that if I assign the private IPs to the eth1 interfaces the routing may either not work or interfere with the access to the production internet facing interfaces (eth0s).
I have just upgraded a CentOS 5.2 box to Centos 5.3
I did have a bridged networking setup for Virtualbox which worked well. eth0 was bridged with br0. br0 boot protocol was DHCP and it sent its DHCP_HOSTNAME to the windows DHCP servers.
since the upgrade the br0 does not get an address but the eth0 does. I found that the scripts in /etc/sysconfig/network-scripts/ifcfg-* are getting rewritten.
I figure I may not need to have a bridge any more so I stripped that out to try to get a simple network setup working. I now just have eth0. I edited /etc/sysconfig/network-scripts/ifcfg-eth0 so that it looked like this,
~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Attansic Technology Corp. L1 Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
[Code].....
I'm running a dual boot Ubuntu 10.04/Backtrack 4 (Ubuntu 8.10) system. I can get internet in the BT4 side but not in the Lucid side. In Lucid I can ping my router, and the network manager says I'm good to go, but I can't get to any web sites. It all started when I tried to put my laptop on another network by mimicking the settings of a computer I had just unplugged from the network. MAC address and all.
ifconfig eth0:
Code:
eth0 Link encap:Ethernet HWaddr 00:1f:16:ba:4c:8c
inet addr:10.136.9.147 Bcast:10.136.9.159 Mask:255.255.255.240
inet6 addr: fe80::21f:16ff:feba:4c8c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[code]....
Sometimes (but not every time), when booting my Dell Inspiron 530, eth0 will not come up right away. I can boot and log in to Gnome, and the NetworkManager applet shows that the ethernet cable is unplugged. After sitting for 5-10 minutes, it will link up and everything works. If I unplug the network cable and plug it back in, it comes right up. But once it's linked, it works fine and never disconnects after that. I've tried switching to a different port on my switch and a new ethernet cable. So I suspect it's some sort of weird kernel problem. I checked /var/log/messages and the only thing that looks weird is:
Oct 17 07:51:49 obi-wan kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
Oct 17 07:51:49 obi-wan kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation.
Oct 17 07:51:49 obi-wan kernel: e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level,
[Code].....
But I have a second Inspiron 530 that has the same entry and it works fine. Has anybody seen a problem like this? I've looked around and so far can't find out the exact issue. I've upgraded NetworkManager to the latest version for FC10
I have been working on a network problem and have found what the actual problem is. For some reason on boot the netmask for my eth0 is set to be 255.255.255.255 In the network GUI application it is set correctly to 255.255.255.0
I looked in the following files and it is set there correctly too.
/etc/sysconfig/networking/devices/ifcfg-eth0
/etc/sysconfig/networking/profile/default/ifcfg-eth0
/etc/sysconfig/networking-scripts/ifcfg-eth0
If I check the box to "controlled by network-manager" the eth0 interface is started at boot but with a netmask of 255.255.255.255. If I uncheck this box then the interface does not come up at boot and I have to go to the GIU application to start it. It still comes up with the netmask of 255.255.255.255
I have to use ifconfig to set it to the right netmask and then everything works until I reboot.
"ifconfig eth0 192.168.1.65 netmask 255.255.255.0"
How do I get this to work properly? I need it to come up with the correct netmask.
I downloaded Fedora 10 32bit and put it on a Dell Dimension 8200 to save it from the recycle bin. Everything seems to work except I cannot get an IP addr. Roadrunner is my ISP using a cable modem and a Linksys Instant Broadband Series Etherfast Cable/DSL router model BEFSR41. In system-config-network, the nic shows inactive. If I activate it a window opens saying "determining IP information for eth0". After a short time the message adds the word "failed". Using a Windows PC on the same network, I can look at the DHCP connections on the Linksys and I see the MAC addr for the PC running Fedora.
From the OS installation, /etc/sysconfig/networking/devices/ifcfg-eth0 has following:
DEVICE=eth0
HWADDR=00:80:ad:d1:88:c9
ONBOOT=yes
[Code]....
I'm guessing this is a r8169 problem. This worked for a while after upgrading to fc13 (from fc12)
I'm not able to get off the local network with eth0. I can though with eth1. Both interfaces are connected to the same switch and have the same network, gateway, and dns server addresses.
The odd part is I am able to ping eth0 from off the LAN and get a reply.
Wireshark capture is attached.
I can't start eth0 and have read thru many of the threads on this and can't figure it out. What does this message mean?
Code:
[jeff@chladni ~]$ ifup eth0
Active connection state: activating
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/13
[Code]....
i install kernel rpm after i boot that kernel network not working kernel name : kernel-rt-trace-2.6.24.7-132.el5.centos.i686 [URL] error "Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring."
View 1 Replies View RelatedI just installed Fedora 10. I entered my static network info in Network Configuration. When rebooting, the eth0 says Inactive. I've read many articles about this problem on earlier versions and tried many of the suggestion, but have not found a definite way of solving this. Is there a better way or a workaround to get this machine on the network?
View 6 Replies View RelatedI use my T61 both wireless and in the dock, where I switch to the wired connection. After the latest round of updates, I seem to have lost the ability to switch to the wired network. When I turn the laptop on, I see it connect to the wireless network, but when I left click on the tray icon under Wired Network is says Device not managed.I have not made any changes to anything in the last couple weeks, besides some updates. How do I go about getting the wired network back in there?I tried to add eth0 back into System - Preferences - Network Connections, but whenever I try and add eth0, but it still says Device not managed.
View 2 Replies View RelatedI am unable to connect to the internet in fedora (XP connects fine) I normally use wifi, but have also checked the wired connection.
View 10 Replies View RelatedI'm using Fedora 14 with gnome as my GUI.As you know , there's gui tool which manages network adapter , either wireless or wired.After every login into fedora , I should click on network manager icon on taskbar and choose System eth0 to establish and enable eth0. I want it to be done automatically.
Previously , I used opensuse 11.4.It has a tool in yast which allows you to choose how to configure your network adapters , traditional or knetworkmanager mode.I can't find this like tool in gnome on fedora.
how I can configure network adapters to start or not during startup?
my eth0 connection is not automatically connected when fedora starts. I checked " activate device when windows starts" in network configuration. still it is not auto connecting and after connection the network icon is not changing to connected status although it is connected.
View 4 Replies View RelatedI am trying to setup linux box as router.
What i am trying to do is:
1. I am trying to setup NIC via network not NetworkManager
2. I have assigned the ip to both NIC with #ifconfig eth0 192.168.1.1
3. #Ifconfig shows my nic and ip
4. restart the service network .
5. #ifconfig shows nothing. NO NIC card
I dont want the network manager coz i dont want to install the gui on router and network manager works only in gui mode. ( i think my this understanding is correct)
I tried to configure the NIC with Network Manager
When ever i restart the network service i have no out put from ifconfig
I tried to configure the NIC with #setup command as well and select the dhcp option
I can not find any ifcfg-eth0 in /etc/sysconfig/networking-scripts/
I try to generate a server client code. What i try to do is sending video streams from eth0 and eth1 to the other server programs' eth0 and eth1. In order to do that, i decided to use SO_BINDTODEVICE. But the code is not working. Am i misunderstood the usage of SO_BINDTODEVICE.
1-Defining two ports
2-Defining two sockets
3-Assigning host ips on them
[code]....
I've a desktop running Fedora 10 connected to the Internet via LAN. There's 3 network controllers in the desktop. One integrated to the motherboard and two additional. I would like to connect other computers (two laptops, one running fc9 and the other Window$ XP) to the Internet via the desktop. I googled the question and found out that I need to adjust thing called 'NAT'.
For that purpose I did the following:
iptables -t nat -A POSTROUTING -s 192.168.2.0/24 -j SNAT --to-source 192.168.*.*
where 192.168.*.* - is desktop' IP address. I want to use 192.168.2.0/24 as a network for laptops. I activated one of devices (eth1), gave it IP address:
ifconfig eth1 192.168.2.0/24
and connected f9 laptop to it.
On the laptop I activated eth0 with the same IP. The problem is: it doesn't work. I can't ping anything from the laptop except its own address (192.168.2.0).
I have two network devices :
1. Intel Corporation 82574L Gigabit Network Conncection (Currently eth0, Mac=00:0e:8c:ab:c6:b1)
2. National Semiconductor Corporation DP83815 (Currently eth1, Mac=00:0e:8c:8a:70:62)
I want to change them so that the "Intel" become eth1 device and the "National" become the eth0 device.
I already tried these steps :
1. I disabled the Network Manager and enabled network
2. Edit the /etc/udev/rules.d/70-persistent-net.rules like this
Quote:
3. Change the /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth1 MAC addresses.
4. Reboot
5. After it bootup the Fedora can't recognize the devices, if I do ifconfig -a it shows "eth0_rename with FF:FF:FF:FF:FF:FF mac address".
I'm running fc10 x64 - latest updates. First I could never get wake on lan to work - spent days working on that one. Now, when I restart after a hibernate my eth0 is not re-enabled or recognized anymore. About to give up on Fedora.
I've tried service network restart.
I've tried unplugging cable and plugging back in.
I've tried init.d/networkmanager restart.
Only reboot works.
I've spent so much time trying to configure Fedore Core 10 for a Dynamips server and it's just not ready on some of the essential things like this hibernate problem and also wake on lan.