Can't ping my Fedora 4 default gateway

Greetings All,

This is my first posting so please excuse any bad etiquette.

Issue: I'm having a problem pinging my gateway after moving my Fedora 4 box to a different subnet. I was careful to make sure that I entered in the correct addresses and updated the right network files. Mind you the system worked fine in the other subnet and initially worked on the new subnet. However, after I rebooted, network connectivity ceased. I have also removed the the firewall as a potential problem by temporarily disabling it. I would love to know what I may have screwed up or changed that could be causing me this headache.

Question??: Looking at the files/configuration below, can you tell me what could be the source of my problem?

Any sugestions or ideas are greatly appreciated.

My configuration is as follows:

The /etc/sysconfig/network-scripts/ifcfg-eth0 file looks like the following:

DEVICE=eth0
USERCTL=no
ONBOOT=yes
BOOTPROTO=none
BROADCAST=146.138.133.255
NETMASK=255.255.255.0
IPADDR=146.138.133.207

The /etc/sysconfig/network file looks like the following:

NETWORKING=yes
HOSTNAME=localhost.localhostdomain
FORWARD_IPV4=yes
GATEWAYDEV=
GATEWAY=148.138.133.1

arp -a returns nothing

tcpdump -nn for port 53 give me...

16:00:34.201445 IP 146.138.133.2.2852 > 146.138.198.215.53: 1+ A? akapp.whenu.com. (33)
16:00:34.219812 IP 146.138.198.215.53 > 146.138.133.2.2852: 1 4/9/9 CNAME[|domain]
16:00:38.042495 IP 146.138.133.2.25884 > 146.138.198.215.53: 7636+ A? blog.washingtonpost.com. (41)
16:00:38.051782 IP 146.138.198.215.53 > 146.138.133.2.25884: 7636 1/6/6 A[|domain]
16:00:44.202601 IP 146.138.133.2.2853 > 146.138.198.215.53: 1+ A? sports.aol.com. (32)
16:00:44.241888 IP 146.138.198.215.53 > 146.138.133.2.2853: 1 6/10/9 CNAME[|domain]
16:00:44.295667 IP 146.138.133.2.2854 > 146.138.198.215.53: 1+ A? akapp.whenu.com. (33)

# netstat -rn gives me the following without the loopback address ???

Kernel IP routing table
Destination        Gateway       Genmask          Flags MSS Window  irtt   Iface
146.138.133.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      0      0          0    eth0
0.0.0.0             146.138.133.1 0.0.0.0              UG   0      0          0    eth0

# ip route
146.138.133.0/24 dev eth0 proto kernel scope link src 146.138.133.207
169.254.0.0/16 dev eth0 scope link
default via 146.138.133.1 dev eth0

# ifconfig

eth0 Link encap:Ethernet HWaddr 00:0F:1F:85:9E:A1
inet addr:146.138.133.207 Bcast:146.138.133.255 Mask:255.255.255.0
inet6 addr: fe80::20f:1fff:fe85:9ea1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3673 errors:0 dropped:0 overruns:0 frame:0
TX packets:318 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1935348 (1.8 MiB) TX bytes:20629 (20.1 KiB)
Interrupt:169

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:26003 errors:0 dropped:0 overruns:0 frame:0
TX packets:26003 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Ironman88Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gabriel OrozcoSolution ArchitectCommented:
Hello

did you consider to be filtered on the gateway?
It looks like your gateway it's filtering you. what do nmap say?
if you have permission/right to do so, use
nmap -sS -P0 -v -O 146.138.133.1

to see if it's not a problem on your switch/hub, check if you can see all your peers on the subnet:
nmap -sP 146.138.133.0/24

if you get more peers than your own ip, then the problem is on the gateway. If you get response from your gateway with the first scan, then they are filtering you. just check why and (maybe) advise them you moved to the new subnet so they can setup their boxes accordingly

Regards
0
Ironman88Author Commented:
I will check and see if I am being filtered in any shape form or fashion and let you know.

Thanks,
I-Man
0
Ironman88Author Commented:
I found out what the problem was...  It was discovered that the port on the switch was not configured correctly.  I am now able to ping the gateway and other devices on the network.

0
Gabriel OrozcoSolution ArchitectCommented:
good to read that =)
0
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.