-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
switch does not respond to routed packets with a ttl of 1 #43
Comments
This only happens with routed pkts with ttl=1 - directly pinging the switch works fine and triggers an imcp echo reply. So the echo reply time too live exceeded does not work. Is this somehow related to? |
A |
got it fixed by enabling forwarding for all interfaces. Is this a bug in OPX? all interfaces got installed with net.ipv4.conf.e101-047-0.forwarding = 0 even net.ipv4.conf.default.forwarding is set |
@disaster123 I've verified in S4200FBL platform with latest packages and I could see the TTL exceeded message is being sent out and traceroute gets completed. Also forwarding is enabled in all the interfaces by default . Please share the steps if you can identify what could make the forwarding to be disabled.
|
Running a traceroute in standard udp mode or in -I icmp mode results in * * * on S4248fbl-ON device for the opx hop.
The packets are correctly arriving at the opx device with a ttl of 1:
but the opx device / kernel does not send any icmp response :-(
ping @mikelazar and @gunasekaran-t
Greets,
Stefan
The text was updated successfully, but these errors were encountered: