-
Notifications
You must be signed in to change notification settings - Fork 230
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
vagrant setup not work as expected... #102
Comments
with director2 (xdp) up and director1 (dpdk) down... from router machine they use the correct ip source (192.168.50.2)... but i see gue encapsulation arriving on router...
but from proxy1 they use 195.168.50.1...
from users machine they use 192.168.40.1 on router machine in place of the 192.168.40 interface ip...
but on the proxy1 machine they use 192.168.50.1...
|
i've found... is because libvirt create there vm with default gateway on the ssh part of vagrant, and all network are nat network with dhcp... the first ip of each network can route traffic... |
i've configured as https://github.com/github/glb-director/blob/master/docs/setup/example-setup-vagrant.md.
i've shutdowned director2 that use xdp and use dpdk.
when i use curl from user machine... i go in timeout...
when i use curl from router machine they work but... the ip source that are seen front proxy are 192.168.50.1, in place of 192.168.50.2 why ?
and when try from user machine they use the same ip (192.168.50.1) as ip source in place of 192.168.40.x source ip, and cannot reply to user machine beceause that machine not have the 192.168.50 network...
what are missing ? why glb-director not correctly encapsulate the source ip ?
this ip are not configured any where (no default route any where! but exist on 192.168.50 network because of virtual network as host ip interface)....
The text was updated successfully, but these errors were encountered: