sjanssen15 commented on PR #10861:
URL: https://github.com/apache/cloudstack/pull/10861#issuecomment-2898806155
> > I have now a VXLAN segment with a virtual router attached to it. I'm
able to ssh into the VR and ping the running instance (from a different host as
well). I'm however unable to reach the public network where the VR is attached
to. I do have the correct VLAN and type configured. On the KVM host itself I'm
able to reach the public gateway via that cloudbridge.
>
> You cannot reach the gateway 10.4.152.1 from the VR, right ?
>
> can you assign a temporary IP (in 10.4.152.1/24 network) to the linux
bridge (brXXXX.1452) on the kvm host, and check if the .1 and .102 are
reachable ?
I tried with `ip addr add 10.4.152.14/24 dev brens1np1-1452` but still won't
work. I'm able to ping the 10.4.152.1 since my cloudbr3 is configured with a
working configuration. I use the following netplan config (I redacted the other
bridges). One perhaps important caveat: I have to rename "ens7f1np1" since they
are too long in order for Linux to create bridges for them, this is known
limitation (15 characters). Could this be the issue perhaps?
```
network:
version: 2
ethernets:
eno5np0: {}
eno6np1: {}
ens0np0:
match:
name: ens7f0np0
set-name: ens0np0
ens1np1:
match:
name: ens7f1np1
set-name: ens1np1
vlans:
< redacted >
ens1np1.1452:
id: 1452
link: "ens1np1"
bridges:
< redacted >
cloudbr3:
addresses:
- "10.4.152.10/24"
routes:
- to: "10.4.152.0/24"
via: "10.4.152.1"
dhcp4: false
dhcp6: false
interfaces: [ ens1np1.1452 ]```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
