SNAT Problem Floating IP

Bug #1877978 reported by Christopher Wellie
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


we have problem.

I have two MTRS from From ONE SRC IP to ONE Floating IP i have on second mtr packet loss

I have the Same Problem from VM to by 2 MTRs dann have my local neutron gw Packtetloss

Revision history for this message
Bence Romsics (bence-romsics) wrote :


Thank you for your bug report.

You shared little information to enable us reproduce your problem. I can only ask a few questions that hopefully leads you closer to finding the cause.

1) What makes you think this is a bug of neutron? And not a problem in your network setup, guest operating system, etc?
2) Do you have network connectivity between two vms on the same neutron network?
3) Can you ping the gateway IP of your neutron subnet from a vm?
4) If you attach two subnets to a neutron router and start one vm on each, can you ping between the two vms?
5) Does traceroute work if you run it directly on your network node?
6) In what architecture did you deploy openstack and especially neutron? What drivers and configuration do you use? What version of openstack do you use? What networks, routers, subnets etc did you create in neutron?
7) What exactly is the command that fails and where do you run it?
8) If you identified a component likely to be the cause, do you have logs of it (preferably at debug level)?


Changed in neutron:
status: New → Incomplete
Revision history for this message
Bence Romsics (bence-romsics) wrote :

One more question. I am not familiar with the output format of the traceroute variant (MTR) you use. Do you have a connectivity problem or do you have a problem with hop 2 and/or 3 not sending you ICMP Time Exceeded packets?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.