Guest's secondary/virtual IP
laurentfdumont at gmail.com
Tue Oct 26 01:01:28 UTC 2021
Couple of things to try
- At the VM level, ping your own address on eth1 to see if local traffic
- Using your existing port config, capture traffic at the VM level to
see if the packets are reaching the VM.
- Disable port-security on the port level and validate if the traffic is
reaching the VM.
- If you have access to the compute, capture traffic at the
interface/tap/bridge level. Where to capture will depend on if you are
- I do believe that even with allowed-address on the port, you will need
to have the corresponding traffic allowed in your sec-group.
Can you paste the port info with "openstack port show $port_id_here"?
On Mon, Oct 25, 2021 at 10:23 AM lejeczek <peljasz at yahoo.co.uk> wrote:
> Hi guys.
> What I expected turns out not to be enough, must be
> something trivial - what am I missing?
> I set a port with --allowed-address and on the
> instance/guest using the port I did:
> -> $ ip add add 10.0.1.99/24 dev eth1
> yet that IP other guest cannot reach.
> many thanks, L.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss