On Mon, Sep 12, 2016 at 3:14 PM, Luca 'remix_tj' Lorenzetto <
lorenzetto.luca(a)gmail.com> wrote:
On Mon, Sep 12, 2016 at 2:11 PM, Colin Coe
<colin.coe(a)gmail.com> wrote:
> So is the problem getting traffic between two different VLANs working?
If
> so, have you double checked your routing?
No, the issue is that VM cannot still ping the gateway of it's own network.
Resuming:
VM can ping the host interface assigned to the logical network (eno5)
VM cannot ping gateway
Host can ping gateway and VM
External machine (e.g. gateway) cannot ping VM
External machine can ping the host interface assigned to the logical
network (eno5)
I may be missing something here, and a diagram would have helped.
Assuming this is your setup, see how vlan tagging matters and translates to
the network:
[pc]---<vlan 828, access>[switch]<trunk, tag
828>----<trunk>[eno5]-[eno5.828]<tag stripped>[bridge]---<vtap>-[vNIC
-
regular iface, no vlan]
In this setup, eno5 and eno5.828 should not have any IP defined, that is
not legal. You need the address on the bridge.
And you are not suppose to add it manually, but set it through Engine.
Based on your description, setting an address on eno5, means that your
gw/pc is not residing on a VLAN, or you have no trunk between eno
to it.
Perhaps it will be better to just add here the output of from the host:
ip addr
brctl show
vdsClient -s 0 getVdsCaps
and fix the data flow diagram if it is not correct.
--
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
"Internet è la più grande biblioteca del mondo.
Ma il problema è che i libri sono tutti sparsi sul pavimento"
John Allen Paulos, Matematico (1945-vivente)
Luca 'remix_tj' Lorenzetto,
http://www.remixtj.net , <
lorenzetto.luca(a)gmail.com>