top button
Flag Notify
Site Registration

ping -R on Fedora 18 does not work (firewall problem)

0 votes

When I try:

 ping -R

I get:

PING ( 56(124) bytes of data.

but the list of nodes does not appear, and I wait for more than 5 minutes. traceroute gives immediately the list of nodes.

This is fedora 18, iptables stopped (and flushed), firewalld stopped.Could it be somehow due to not flushing firewalld rules ? (I don't know much about firewalld)

posted Jun 17, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

-R ping only. Record route. Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. Note that the IP header is only large enough for nine such routes. Many hosts ignore or discard this option.

answer Jun 17, 2013 by anonymous
Similar Questions
+1 vote

I have two different IP addresses (in a block of /29), one is on port 0 and the other is on port 2 of a Ciso 888. I am doing this so I can have two different certs with two different ip addresses.

I have tried:
1) one machine, two real interfaces, two cables (eth0 and eth2)
2) one machine, one real interface eth0 and one virtual interface eth0:1, one network cable

Using number 2) I can ping the two different ip addresses, no problem. The only problem here is that iptables does not work (I cannot create rules for eth0:1 - and yes I know about the security implications).

I have a problem with number number 1) I can ping the first ip address and I get a return, but I cannot get a return when I ping the second ip address. I can see traffic coming into the second interface but it does not return. Now one of the interfaces needs the "default" route applied (is this correct??), which is eth0.

I assume this is a routing problem? What do I need to do to get this to work?

+1 vote

When I use multi-home function to setup link between 2 fedora 18 hosts, I can not use sctp_sendmsg to send any message and return error "Invalid Parameters" . but the same program runs well in Centos 6.

And the most wired thing is when I run Server side in centos and run Client side in fedora, I have the problem, but everything is fine when I run client side in centos but run server side on fedora.

Does anyone has the same problem?

+1 vote

I have a hosted VM with a provider, which I've set up mainly as a private mail server. It needs to be protected by some sort of firewall, but there are several to choose from, apart from just writing rules for iptables by hand. I don't think I'll be needing an extreme amount of rules.

Writing rules for iptables is not something I've done in many years, so I was wondering about using either ufw, shorewall or ferm. Has anyone got any experience with either of these? I'm looking for something that is easy to set up and maintain. A pointer to a good guide on any of these would also be much appreciated, especially one that centers on protecting a machine that doesn't serve as a firewall for an entire network, it only has the one interface.

Any suggestions?

+2 votes

I am unable to ping my EnB, PGW through ping application.. It says request timed out but thing is I am able to see Request-Reply packets in wireshark captures. Not getting any idea on what is going wrong.

Please suggest some inputs.