Skip to content

Conversation

@sg00dwin
Copy link

No description provided.

@sg00dwin
Copy link
Author

@benjaminapetersen pr

let me know if you have questions

benjaminapetersen pushed a commit that referenced this pull request Mar 16, 2016
Style adjustments to needed to position utility nav links
@benjaminapetersen benjaminapetersen merged commit 35e04c8 into benjaminapetersen:bpeterse/extension-points Mar 16, 2016
@sg00dwin sg00dwin deleted the extension-points branch March 16, 2016 21:55
benjaminapetersen pushed a commit that referenced this pull request Jul 8, 2016
Docker-only containers (eg, "docker run foobar") get attached to lbr0, and
their traffic flows from lbr0 -> vlinuxbr -> vovsbr -> br0.  To ensure that
docker-only containers can access the rest of the world through tun0, we
need to pass their traffic along instead of dropping it in table #3:

 cookie=0x0, duration=12307.238s, table=0, n_packets=292, n_bytes=23330, actions=learn(table=7,hard_timeout=900,priority=200,NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[],load:NXM_NX_TUN_IPV4_SRC[]->NXM_NX_TUN_IPV4_DST[],output:NXM_OF_IN_PORT[]),goto_table:1
 cookie=0x0, duration=12307.227s, table=1, n_packets=165, n_bytes=13199, actions=goto_table:3
 <drop due to no match>

Add a rule allowing traffic from vovsbr to jump from table #3 to table #4,
where it will get directed to the right place (either other pods or tun0).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants