-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/15/2010 12:18 AM, Rick Sewill wrote: > On 11/14/2010 10:23 PM, Luis Suzuki wrote: >> All below was taken when Gnome NetworkManager was saying that Auto eth0 >> was active and OK. > >> Below some more data:# ping 192.168.1.254 >> PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. >> 64 bytes from 192.168.1.254: icmp_req=1 ttl=64 time=1.15 ms >> 64 bytes from 192.168.1.254: icmp_req=2 ttl=64 time=0.700 ms >> 64 bytes from 192.168.1.254: icmp_req=3 ttl=64 time=0.733 ms >> 64 bytes from 192.168.1.254: icmp_req=4 ttl=64 time=0.715 ms >> 64 bytes from 192.168.1.254: icmp_req=5 ttl=64 time=0.706 ms >> 64 bytes from 192.168.1.254: icmp_req=6 ttl=64 time=0.775 ms >> 64 bytes from 192.168.1.254: icmp_req=7 ttl=64 time=0.801 ms >> 64 bytes from 192.168.1.254: icmp_req=8 ttl=64 time=0.716 ms >> 64 bytes from 192.168.1.254: icmp_req=9 ttl=64 time=0.726 ms >> 64 bytes from 192.168.1.254: icmp_req=10 ttl=64 time=0.708 ms >> 64 bytes from 192.168.1.254: icmp_req=11 ttl=64 time=0.709 ms > > > This means the ethernet hardware is working. You can ping the router. > >> #less /etc/resolv.conf >> # Generated by NetworkManager >> domain lan >> search lan >> nameserver 192.168.1.254 >> /etc/resolv.conf (END) > > > This is good as long as the router will do DNS for you. > >> #ifconfig -a > >> eth0 Link encap:Ethernet HWaddr 00:21:70:BC:71:84 >> inet addr:192.168.1.64 Bcast:192.168.1.255 Mask:255.255.255.0 >> inet6 addr: fe80::221:70ff:febc:7184/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:120 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:153 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:11211 (10.9 KiB) TX bytes:19119 (18.6 KiB) >> Interrupt:43 Base address:0x8000 > > The interface IP address is 192.168.1.64...okay. > >> # ip route >> 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.64 >> metric 1 > >> # netstat -rn >> Kernel IP routing table >> Destination Gateway Genmask Flags MSS Window irtt >> Iface >> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 >> eth0 > > > You have no default route...this is part of the problem. > When doing ip route, you should have something like > default via 192.168.1.254 dev eth0 > When doing netstat -rn, you should have something like > 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 > 0 eth0 > >> # cat /etc/sysconfig/network-scripts/ifcfg-eth0 >> cat: /etc/sysconfig/network-scripts/ifcfg-eth0: No such file or directory > > > Argh. I don't use NetworkManager...if there is no ifcfg-eth0 file, > what does NetworkManager do? People? > > What you need to do is add a default route to 192.168.1.254 for eth0 > > I have no plans to use NetworkManager any time soon so I can only give > you general hints...I wish someone who does use NetworkManager would > take over this discussion. > > Needless to say...I will try. > > When you start the Network Manager client to examine/modify > configurations, you should find the configuration for eth0. > > I'm only guessing, but is it something like Network connections? > Can you select the ethernet network connection and push the edit button? > > When you do that, does a pop-up appear? > Does it have a IPv4 Settings tab? > > Can you select the IPv4 Settings tab. > > What is the Method: "Automatic (DHCP)" > or "Automatic (DHCP) addresses only" > or "Manual" > or what? > > I'm guessing the Method is Manual...but please tell me. > > The following advice is based on the belief the Method is Manual. > > Is there a Routes button? Please press it. > > Does another pop-up appear, something like "Editing IPv4 routes for .... > Can you add a route, > Address Netmask Gateway Metric > 0.0.0.0 0.0.0.0 192.168.1.254 1 > > Can someone who does use NetworkManager correct the above please? > I'm sure I have things wrong since I don't use NetworkManager. > Hopefully, people can get the idea what I want tried. > > Please let me know how far off I am regarding the NetworkManager GUI. > > When you are done, please do either > ip route or netstat -rn > I wish to see if the default route has been added. > If you have a default route...try to ping something on the Internet. > > I manage my interfaces myself...I do networking things for a living. > NetworkManager was not my friend, in the past, when it interfered with > what I needed to do...so I turned it off, and never turned it back on. Shows what I know about NetworkManager...yes, I'm learning, if for your eth0 connection, You have Method: Manual Instead of doing what I suggested by pushing the Routes button and adding the default gateway there... Change the Addresses entry from Address Netmask Gateway 192.168.1.64 255.255.255.0 0.0.0.0 to Address Netmask Gateway 192.168.1.64 255.255.255.0 192.168.1.254 That's probably the NetworkManager way to specify the default gateway manually. I finally bit the bullet and started NetworkManager. I am letting it manage my WAN interface. I still want control over my LAN interface. I still need complete control over my LAB interface...as long as NetworkManager doesn't interfere with LAB configurations I will leave it running...I know about NM_CONTROLLED=no in the ifcfg-ethx scripts. Again, I'd like to know if you do have Method: Manual or what you have. Sorry for the bandwidth. Time I stop rambling now. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkzhiyMACgkQyc8Kn0p/AZRyKACggJno8kxQc4+UIfDZSXydxPnQ om4AoK5YijnyJO5bCRPbz0REFFLjRFA5 =CZhw -----END PGP SIGNATURE----- -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
