So, what's changed between Fedora11 and Fedora14, other than setting up the above files (or using system-config-network) what do I need to do???

Maybe selinux is blocking? Maybe the driver is changed?

On Thu, 2011-03-31 at 09:32 -0600, reg@dwf.com wrote:

So, what's changed between Fedora11 and Fedora14, other than setting up the above files (or using system-config-network) what do I need to do???

Have you configured Networkmanager?

poc

On Thu, 2011-03-31 at 09:32 -0600, reg@dwf.com wrote:

I sent this several days ago, and it didnt make it to the list, Im trying again.

---

I am just now bringing up Fedora14 (Ive been running Fedora11).

Something has changed, since the way I have always done things to bring up networking just doen't work.

I can setup /etc/sysconfig/network /etc/sysconfig/network-scripts/ifcfg-eth0

either by hand or using the system-config-network script, and everything LOOKS ok, but I can not ping this machine from the outside, nor can I ping from it to another machine on the same network.

The hardware is fine, since I have Knoppix running on the machine at the moment (to verify that the machine and its cables were ok) and its networking came up just fine.

So, what's changed between Fedora11 and Fedora14, other than setting up the above files (or using system-config-network) what do I need to do???

Thanks in advance.

                                    Reg.Clemens

reg@dwf.com

Your request did come through a day or so and you were asked whether you were running networkmanager at the same time as network. What is your answer?

On Thu, 2011-03-31 at 09:32 -0600, reg@dwf.com wrote:

...

So, what's changed between Fedora11 and Fedora14, other than setting up the above files (or using system-config-network) what do I need to do???

Have you configured Networkmanager?

Actually, my first attempt or two was with NetworkManager enabled. But, since ive never had any luck with it, I turned it off (in /etc/rc.d/rc3.d) and have been doing things by hand like I always have done.

system-config-firewall? You might have the firewall enabled (I think it's on by default) which may be dropping all ICMP packets. --

That was one of the first things I noticed. I turned it off in /etc/rc.d/init.d iptables and ip6tables and rebooted. No luck.

Can ou get out to the internet?

No.

Do you know that the network is NOT working or do you just assume that it's not working since you cant ping the machine?

Nope, tcpdump on another machine does not show anything coming from the machine.

On Thu, Mar 31, 2011 at 6:49 PM, reg@dwf.com wrote:

...

On Thu, 2011-03-31 at 09:32 -0600, reg@dwf.com wrote:

...

So, what's changed between Fedora11 and Fedora14, other than setting up the above files (or using system-config-network) what do I need to do???

Have you configured Networkmanager?

Actually, my first attempt or two was with NetworkManager enabled. But, since ive never had any luck with it, I turned it off (in /etc/rc.d/rc3.d) and have been doing things by hand like I always have done.

I used to hate NetworkMangler also, but I has vastly improved in F14.

Try: (as root) 1) chkconfig NetworkManager on 2) service NetworkManager start 3) right-click NetworkManager icon and select "Edit Connections..." 4) select the "Wired" tab 5) highlight the desired network device (e.g. System eth0) 6) click the "Edit" button 7) ensure "Connect automatically" (checkbox) is enabled 8) set up the device characteristics in the various other tabs 9) "Save" and "Close" out of the Edit Connections dialogues 10) Click the NetworkManager icon and (if necessary) select the device to activate

The device should come up and be active.

If you absolutely don't want to use NetworkManager, ensure that the plain old "network" service is active.

1) chkconfig network on 2) service network start

Hope this helps.

On 03/31/2011 04:34 PM, reg@dwf.com wrote:

...

<reg<at> dwf.com> writes:

...

...

Show us full/unedited outputs: $ yum list installed "*network*" $ chkconfig --list |grep -i network $ /etc/init.d/network status

$ cat /etc/sysconfig/network $ ls /etc/sysconfig/network-scripts/*eth* $ cat /etc/sysconfig/network-scripts/ifcfg-eth0

$ ifconfig -a $ route -n

$ grep -i host /etc/nsswitch.conf $ cat /etc/host.conf $ cat /etc/hosts

$ dig www.yahoo.com $ dig 87.248.122.122

OK, this is going to be interesting, since I cant get the output from the F14 machine to the machine Im posting from over the network. Hopefully, I can write it to a USB stick and transfer it, here we go:

yum list installed "*network*"

Loaded plugins: langpacks, presto, refresh-packagekit Adding en_US to language list Installed Packages NetworkManager.x86_64 1:0.8.1-9.git20100831.fc14 @anaconda-InstallationRepo-201010211827.x86_64 NetworkManager-glib.x86_64 1:0.8.1-9.git20100831.fc14 @anaconda-InstallationRepo-201010211827.x86_64 NetworkManager-gnome.x86_64 1:0.8.1-9.git20100831.fc14 @anaconda-InstallationRepo-201010211827.x86_64 NetworkManager-openconnect.x86_64 0.8.1-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64 NetworkManager-openvpn.x86_64 1:0.8.1-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64 NetworkManager-pptp.x86_64 1:0.8.1-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64 NetworkManager-vpnc.x86_64 1:0.8.1-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64 system-config-network.noarch 1.6.1-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64 system-config-network-tui.noarch 1.6.1-1.fc14 @anaconda-InstallationRepo-201010211827.x86_64

chkconfig --list | grep -i network

NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off network 0:off 1:off 2:on 3:on 4:on 5:on 6:off

/etc/init.d/network status

Configured devices: lo eth0 Currently active devices: lo eth0

cat /etc/sysconfig/network

NETWORKING=yes HOSTNAME=mythtv-fe NTPSERVERARGS=iburst NETWORKING_IPV6=no

cat /etc/sysconfig/network-scripts/ifcfg-eth0

NETWORKING=yes HOSTNAME=mythtv-fe NTPSERVERARGS=iburst NETWORKING_IPV6=no [root@mythtv-fe reg]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 HWADDR=00:19:D1:75:E3:3E IPADDR=192.168.64.99 PREFIX=24 GATEWAY=192.168.64.10 DNS1=192.168.64.10

Really? Your DNS server is also your default gateway? That's not common.

DOMAIN=dwf.com NETMASK=255.255.255.0 USERCTL=no

ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:19:D1:75:E3:3E inet addr:192.168.64.99 Bcast:192.168.64.255 Mask:255.255.255.0 inet6 addr: fe80::219:d1ff:fe75:e33e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41 errors:0 dropped:0 overruns:0 frame:0 TX packets:233 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3978 (3.8 KiB) TX bytes:13541 (13.2 KiB) Interrupt:20 Memory:52200000-52220000

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:131 errors:0 dropped:0 overruns:0 frame:0 TX packets:131 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12612 (12.3 KiB) TX bytes:12612 (12.3 KiB)

route -n

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.64.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0 0.0.0.0 192.168.64.10 0.0.0.0 UG 0 0 0 eth0

grep -i host /etc/nsswitch.conf

#hosts: db files nisplus nis dns hosts: files dns

cat /etc/host.conf

multi on order hosts,bind

cat /etc/hosts

127.0.0.1 localhost.localdomain localhost localhost4 ::1 localhost6.localdomain6 localhost6 192.168.64.99 mythtv-fe.dwf.com mythtv-fe

dig www.yahoo.com

;<<>> DiG 9.7.2-P2-RedHat-9.7.2-2.P2.fc14<<>> www.yahoo.com ;; global options: +cmd ;; connection timed out; no servers could be reached

dig 87.248.122.122

;<<>> DiG 9.7.2-P2-RedHat-9.7.2-2.P2.fc14<<>> 87.248.122.122 ;; global options: +cmd ;; connection timed out; no servers could be reached

---

Thats about it. Hope it shows you something.

Can you ping your gateway?

# ping 192.168.64.10

If that works, then your machine's network is running. Try pinging an external IP address, such as:

# ping 2.17.144.112

(2.17.144.112 is www.redhat.com). If that works, then your networking is functional. Next, verify your gateway is actually running a DNS server, as your dig output simply indicates that you can't reach the DNS server you specified. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, C2 Hosting ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - I'm afraid my karma just ran over your dogma - ----------------------------------------------------------------------

Seems networking should just 'come up' on a new install. Let the user decide how to tighten up his security, Fedora seems to be taking the opposite approach.

Your setup looks fine. You said this was a new install? You shouldn't have to do anything other than install the OS. It's supposed to set up basic networking for you, without restricting you from things like browsing and updates. No restrictions in outward access to the lan and the internet, in other words.

Ruling out anything wrong with Fedora 14 other than a few bugs, I think you have to focus on your nic and your modifications to config files like ifcfg-eth0. What all has been modified?

The driver Fedora 14 is loading, or failing to load, can be a problem. Your ifcfg scripts have options that I've never seen before. However, you seem to understand how the scripts work, so maybe you need those options.

What network card is it? What's the output of:

grep -i eth /var/log/dmesg

The card shows up in lspci?

Well, you can not ping the gateway, and so you can not reach the DNS server there. The gateway is protected by its own firewall, so you have to verify its status and rules there: # iptables -n -L -v

Now back to your machine in question.

I have to ask you to give us an actual response to any entries we request (it may make a difference to see it, instead of your narrative like "no, it does not work"). So, please give us full/unedited output of: $ ping 192.168.64.10 $ cat /etc/resolv.conf # iptables -n -L -v

OK, lets not, the firewall has a complicated Firewall on it, and you would never be able to read thru all of it. Rather lets ping another machine on this subnet, my 'main' machine, deneb at 192.168.64.17 .

ping 192.168.64.17

[root@mythtv-fe VPN]# ping 192.168.64.17 PING 192.168.64.17 (192.168.64.17) 56(84) bytes of data. (several second pause)

From 192.168.64.99 icmp_seq=2 Destination Host Unreachable From 192.168.64.99 icmp_seq=3 Destination Host Unreachable From 192.168.64.99 icmp_seq=4 Destination Host Unreachable

and the

cat /etc/resolv.conf

[root@mythtv-fe VPN]# cat /etc/resolv.conf nameserver 192.168.64.10 search dwf.com

and the list of the Firewall

iptables -n -L -v

[root@deneb ntpd]# /sbin/iptables -n -L -v FATAL: Module ip_tables not found. iptables v1.4.3.1: can't initialize iptables table `filter': iptables who? (do you need to insmod? Perhaps iptables or your kernel needs to be upgraded.

so, no firewall, no iptables, no output of interest.

I guess I just dont understand how others (it would appear) have networking when they bring Fedora14 up, and I dont. I can reinstall a 3rd (or is it 4th time) but all I have done after the install is to try setting up networking, using either system-config-network, or by hand editing network and ifcfg-eth0 and nada, nothing. And yes, by this time Ive turned off NetworkManager, and the Firewall and selinux.

Mumph.

Its got to be something real simple, but Im not seeing it.

On Thursday, March 31, 2011 10:37:46 pm reg@dwf.com wrote:

Seems networking should just 'come up' on a new install. Let the user decide how to tighten up his security, Fedora seems to be taking the opposite approach.

Well, if this were a Fedora-wide issue you'd see lots and lots of threads on the subject, so it's likely localized to your situation.

There are a number of things you can still look for. It seems to me that you have layer 2 connectivity issues, since you can't see anything on your LAN, and nothing else on your LAN seems to be seeing this box.

Do you have Wireshark installed? If you do, start it up, point it at eth0, start a capture, and see if you see any broadcast traffic. Go to that other machine, .17, and attempt to ping this box; you should see incoming broadcasts (for ARP) in Wireshark on this machine, .99. Or use tcpdump on this machine like you did previously on another machine:

Nope, tcpdump on another machine does not show anything coming from the machine.

If you don't see anything coming in, you may have a port negotiation mismatch with that particular Intel NIC (00:19:D1:75:E3:3E being your MAC address as listed by ifconfig; that's an Intel OUI) and your switch with the kernel driver in the Linux kernel included in Fedora. To see what it's set up for, and which driver is in use, use: ethtool eth0 ethtool -i eth0 ethtool -P eth0 in sequence; the first one will give you some general info, and the second one will tell you what driver is loaded and the bus ID of the NIC, and the third gives you the BIA (burned-in address), just to triple-check that the NIC has the HWADDR it's configured for.

Then check your switch (if it's a managed switch) to see what it's negotiating to. Or perhaps you have port security enabled on the switch, or some other networking feature that's contributing to the seeming partitioning of you NIC.

As I've already deleted the initial portions of the thread in my fedora folder, I don't recall if you said this NIC worked with another OS, but even then I have seen issues with certain Intel NICs connected to certain switches in Windows before, where the NIC wouldn't always auto-negotiate properly; but it would under Linux, so the reverse possiblity is always there. And it may be a malfunctioning NIC, as the Mythbusters say, failure is always an option.

As to earlier versions of Fedora working and this one not, it's a different kernel, possibly different drivers, and udev I'm sure has changed.

So I'm thinking, giving you've tried disabling all the security features built-in, that you have a problem at a deeper level, and it's not one that's there by design.

Lots and lots of people are experiencing networking properly operating after F14 install, myself included. With multiple machines, and multiple types/brands of ethernet adapters; we just need to find the layer 2 issue you're having that looks almost like either a PHY misconfig/incompatibility or a layer 1 partitioning due to auto-negotiation issues....