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've lasted a lot longer than usual before resorting to asking around, but I've finally gone delightfully mad. I've been trying to access shares based on Windows 7 Ultimate with limited user access on said shares. I've managed to get into my XP machine, another mate's Vista machine and various Linux boxes with no issues, but that's only for shares that are accessible by everyone. The moment I try to get into a share that requires user credentials, I get "Error returning browse list: NT_STATUS_ACCESS_DENIED".If I try to access restricted shares (be it machine or folder) through Nautilus, I will get a user logon prompt, but it fails. Using smbclient results in just as little success, and now I'm munching through O'Reiley's Samba manual from '99, after realising that I need to basically learn Samba in its entirety to have a hope in hell at getting this to work. The trouble is though, every HOWTO and relevant forum post I get my hands on all seem to concentrate more on the server side of things, and usually servering from a linux box, not the other way around as I'm trying to.
The above Windows 7 machine won't even allow me to view its share contents, whereas the XP machine previously will allow me to browse, but won't allow me to access folders with restricted access. I'm pretty sure there aren't any major issues with the way the Windows 7 machine is setup, as it can be accessed with logon from my Xbox, Ubuntu machine, XP and Vista, with only Fedora having problems getting in as it constantly fails logon. What I'm trying to establish is, if Ubuntu can get in, is there something in my Fedora samba config I'm missing that's preventing me access? My thanks in advance to those of you who've been able to put up with me rambling.
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'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]....
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 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 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'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 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.
I've got a 64 bit home server system that was upgraded from FC2 to 7, 9, now 11. I've now got a weird situation where dns inquiries will not work when I reboot the machine, until i restart eth0. When I reboot, I can open firefox on the machine, put in the IP of my dsl router, and look at it's settings just fine. All other internet uses, whether it's yum,squid, or etc. comes back with the usual name server not found messages. I've got thenetwork setup to use the named on this server, ( the web's a tad bit slower when I set it up to use ISP's windows nameservers, go figure).
Anyway, a few years ago I set up the machine to use the network service to bring theseinterfaces up. (I believe this was because the early versions on Networkmanger had some issues. In an attempt to fix this issue I reset Networkmanger start at startup, and reset up eth0 and 1 to be controlled by it.I then got namserver1=XXX.XXX.XXX.XXX in resolve.conf at reboot..(yeah they were really X's, I'm not hiding an ip here) I tried going intonsswitch.conf, found the line hosts: files mdns4_minimal [NOTFOUND=return] dnsand changed it to:hosts:files dns mdns4_minimal [NOTFOUND=return]No joy, I still have to do an ifdown eth0 and an ifup eth0 to get dns to work..
When I activate eth0, the system says that the eth0 seems not exist. However, I can surf in the internet.
View 1 Replies View RelatedI am trying to get networking up on an old PII which I have successfully installed with FC4. There is a link and activity on the onboard interface because I see the indicator lights. The controller is a 3Com PCI 3c905 Boomerang 100baseTx @ 0xdc80.The only message returned by dmesg about eth0 is "Dropping NETIF_F_SG since no checksum feature."The driver module, 3c59x, is loaded as well as the mii module that depends on it.There is something about "unknown parameter`irq'" in the dmesg text regarding the driver.I noticed that eth0 is sharing an IRQ with the UHCI Host Controller.That should not be a problem, but it should not be necessary. And I could do away with USB if this is a conflict and that is the easiest way to solve it.When I drop to console at runlevel 3, and call dhclient, which is installed, I get a message telling me there is no reply to the dhcp request.I don't think the problem is on the router/switch side.
View 5 Replies View RelatedI have two network interfaces on my computer but only one of them is connected to an Ethernet cable. Until now on every Fedora release, the activated primary interface has been named as eth0 and everything has always worked well without any problem. Recently I switched to Fedora Core 12 and surprisingly I observed that for the first time, my primary interface has been considered by the system to be eth1 instead of eth0. I tried to replace the content of ifcfg-eth0 by ifcfg-eth1, yet system gave me an error that there was MAC address mismatching. I conserved their MAC addresses in their files and just replaced other connection parameters ( such as IP ADDR, NETWORK, NETMASK, etc.) but it did't work. When I do "server network restart", the command blocks.
As I try to install oracle on this system, regarding the fact that oracle requires static network configuration on the primary network interface, I don't know how to proceed in order to set eth0 as my primary interface (or rather set the current eth1 to eth0 because it is actually eth1 that refers to my activated primary network card).Just one more time, I would like to remark, that with previous versions of the Fedora Core, on the same computer (with the very same two network cards) I never had problem and I had installed oracle on the system with success, having the statically configured eth0 correctly detected by the system.
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 have a couple of interfaces in a Fedora 14 box:
eth0: internet provided by an adsl router
eth1: LAN
I set up system-config-firewall to masquerade all outgoing traffic in eth0, as I did in other Fedora 13 boxes, but it seems it doesn't work. It sets to 1 /proc/sys/net/ipv4/ip_forward and also set the appropriate rules in iptables. But all traffic is blocked from the LAN to the Internet. "ping www.google.com" works in the Fedora box, but doesn't work in the LAN computers using the F14 IP as gateway. I have another F13 computer elsewhere configured this way and it works fine. But this one has Fedora 14.
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".
I've got a vmware install of Fedora 12 running as a server. This install has the /etc/sysconfig/network-scripts/ifcfg-eth0 file configured with the proper info and the service has been restarted. When I run ifconfig I only get the loopback interface, when I run ifconfig -a I can get the eth0, but without the pre-configured ip address. When I enter ifconfig eth0 up I can activate the interface, but without the afore mentioned ip address. I need to be able to yum ssh, install it, and run it with rsa keys. Can do none of this without an interface obviously.
View 3 Replies View Relatedmy eth0 suddenly stopped working on FC10. i have been using it the whole time, and now it refuses to even ping the gateway. dhclient is not receiving a dhcp offer and when i put in the information manually, it is not even able to ping the gateway. netstat -rn shows that the destination of the router is going nowhere.
i do not think it is the hardware/software, but rather maybe the provider? i am from central europe but just moved up to great britain and working at a friends place. i can connect the mac powerbook without a problem (it will get an ip with dhcp), but not the linux machine.it is a normal ethernet modem connection here. can it be, that it checks MAC addresses or even the computer names? the powerbook also has a really weired IP address: 77.102.xxxxx
i am not using network manager, but command line tools and have nm uninstalled. does anyone have a clue, what this could be about? i am not a newbie, but this is really puzzling me.....
I have a troubling networking situation that is compounded by the system being remote without any out-of-band mgmt in place nor a serial connection - but am relying on a coworker entering commands into the terminal for me, or doing stuff in the GUI I have an FC12 i386 install running, that was up and stable for 6 days. Primarily this was only being used for a deployment of nTop. Up through Monday evening, I was connecting to the system (in NY) via VNC (here in SF), and was successfully watching nTop do its thing.
Tuesday morning, I go to connect to SSH and I can't get in. The NAT translation is still in place on the firewall, but there is no connection to the NIC/eth0 from the router. This is what I've had my coworker run:
[code]...
I was going to try and have her run the /sbin/mii-tool eth0 tomorrow a.m. just to verify that the interface isn't physically bad? But this is a brand new desktop, and I can't for the life of me understand why this interface went down. I also have the internal IP on a DHCP reservation, which is the same IP listed in IPADDR in the ifcfg-eth0 file - could this be a problem? should I remove the DHCP reservation? I did this so I could SSH to a public IP which I have NAT'd back to the internal 10.0.x.x address I had my coworker take a look at the GUI, and the eth0 properties are "inactive" and the "Activate|Deactivate" buttons are greyed out.I suppose I can have my coworker grab the /var/log/messages and copy to a USB drive, then email me that from another workstation.
