© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Thanks for the investigation and detailed follow-up.
> 22:17:03.045019 IP 192.168.101.17 > 10.100.69.132: ICMP echo request, id 9430, seq 1, length 64
> 22:17:03.045067 IP 192.168.101.1 > 10.100.69.132: ICMP echo request, id 9430, seq 1, length 64
This is the part that looks off to me. The host NAT'd the source IP from 192.168.101.17 to 192.168.101.1, which doesn't make sense given that the traffic should have been able to route directly without passing through the gateway. I suspect MaaS created iptables NAT rules that are causing this to happen, but I'm not sure.
If you have a minute to share output of `sudo iptables-save` from the host, it would be a big help.
> So it was missing routes on virtualization host. Why they are missing it is a question. Juju is run via non privileged user, so juju cannot update host level routing. So should it be done somehow via MaaS? Or simply install instructions updated with some manual post deployment tasks.
Indeed. We'll need to investigate if this is something that can be fixed in Juju or MaaS, but we may just need to doc it.