Fedora 16 - Strange Ping effect?

[L3l00]

For some reason Fedora 16 regular gui network setup for a static ip address just didn't seem to work at all!

would do something like Manual - 192.168.0.55 255.255.255 192.168.0.1

I would be able to ping the NIC and Default gateway but nothing out of the network like google.com?

So While searching I came across a couple of alternatives to setting up a static IP (This comp is going to act as my clients main server).

(just letting you know what text editor I was using even though it makes no difference)
So first I did: sudo nano /etc/sysconfig/network-scripts/ifcfg-Wired_connection_1


now in here it was a bit strange, it had a PREFIX, I removed it and changed the Wired_connection_1 to eth0 basically because eth0 looks prettier and that is what I am used to seeing for a wired connection. Also there was a zero after everything, like GATEWAY was GATEWAY0. I removed the zero and it's now

I set BOOTPROTO to static, noticed when I reopend this dock, BOOTPROTO swiched back to none.
I get internet and it looks like the ip is now static

The thing that is kind of scaring me is when I go to ping a website like google.com
I would get a slightly different ip address response almost everytime!

Sometimes ping google.com would give me:
ssl.gstatic.com
mt0.google.com
i4.ytimg.com
clients1.google.com
Sometimes what it should be, google.com
ad.doubleclick.net

everytime I just do a simple : ping google.com

all these addresses if you type the ip will go to the google main page, on rare occasions though the ip will be google but it will say youtube.com?


what is going on!?

[errorxp]

Did you set dns server as well?

[L3l00]

sudo system-config-network-tui>DNS conifig>
Hostname: uServer.(Company Name)
Primary DNS: 192.168.0.1


for the Device Config section:

eth0 (Wired_connection_1) - Ethernet>
name: eth0
Device: Wired_connection_1
Use DHCP [ ]
Static IP: 192.168.0.55
Netmask: 255.255.255.0
Default gateway IP: 192.168.0.1
Primary DNS Server: 192.168.0.1

---------- Post added at 11:40 AM ---------- Previous post was at 11:37 AM ----------

would this affect Samba in anyway? I usually ALWAYS have issues getting Samba to work, first I open SMB ports in firewall then install samba and typical test settings. usually never works right off the bat.

I really want to know if this will affect it, I rebooted and the ip stayed the same for the server which is a good sign. Just the ping showing different other than google.com kind of scary

---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------

OH Another thing
I do ifconfig

and it says em1 instead of eth0?

[errorxp]

Yes, i think they switched from ethX to emX in f16, god knows why
Might be worth checking /etc/hosts & /etc/resolv.conf
Don't know too much about samba as i've had problems with it myself, although I don't see why setting a static ip would affect it in any way.
Another thing, bootproto is supposed to be "none" for a static ip configuration.

[marko]

Originally Posted by errorxp

Yes, i think they switched from ethX to emX in f16, god knows why

https://fedoraproject.org/wiki/Featu...rkDeviceNaming

[L3l00]

Dig the link Marko, so ya I'm okay with it not being eth0
About the bootproto, turns out no matter what fedara will always click it to none! I did a cat on the eth and it appeared none again.

cat /etc/hosts (this doesn't look right)

127.0.0.1 localhost.localdomain localhost

::1 lolcalhost.localdomain localhost.localdomain localhost6 localhost6.localdomain6 localhost

---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------

I was curious about the Static and the Samba because well one, Servers should be Static!

This Server will have a shared folder and every computer in the office will (All XP and Vista, bleh) and it will hold the company files. I have it set up on an Ubuntu Server. The thing is, Fedora has always been my fav and I have no idea why I didn't just build a fedora server in the beginnnig. IDK I'm fixing it now, I just know my way around Fedora more anyways.

[errorxp]

This is what I have:

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

Another idea - try changing your dns server to the google ones (8.8.8.8 or 8.8.4.4) and see what happens.

[Doug G]

As far as I know it's normal to get different servers replying when you ping google.com. They have lots of machines at google.com.

[jims]

You might want to check the DNS status on your router. In particular whether you have enabled DNS relay from your normal DNS servers (addresses that are usually provided by your ISP).

[Doug G]

Also, consider not using your router IP for your DNS server setting. Starting a year or so ago, I had a number of customers whose DNS resolution quit working when using the router DNS proxy, usually on older broadband routers. My guess is that starting around that time lots of DNS servers got upgrades to support DNSSEC and in some cases I think the DNS servers disabled UDP.

Just guessing on all this though, but the users that had problems got the problem resolved by changing the DNS server settings in their workstations (mostly windows) to use the actual ISP DNS IP rather than the router IP.