Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

gateway template should replace bosh declared gateway, not just add. #3

Open
poblin-orange opened this issue Oct 7, 2015 · 2 comments

Comments

@poblin-orange
Copy link

Hello,
im trying to use this bosh release to enable access to an internet gateway from a bosh deployment.
The context :

  • single NIC eth0, bosh networks declares gateway 10.234.228.129
  • add the gateway template to specify default gateway to my internet gateway 10.234.228.130
  • add route template, so that intranet access (10.0.0.0 ..) are routed to the bosh declared gateway
  • the release im using is docker-boshrelease.

After deployment, i see 2 defaults gateways declared. Seems strange ?

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.234.228.130 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 10.234.228.129 0.0.0.0 UG 0 0 0 eth0
10.0.0.0 10.234.228.129 255.255.255.192 UG 0 0 0 eth0
10.234.228.128 0.0.0.0 255.255.255.192 U 0 0 0 eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0

It prevents the internet access. Removing the initial default gateway fixes the issue (see gist below)

https://gist.github.com/poblin-orange/5ac277854a24b4a35966

@frodenas
Copy link
Collaborator

The gateway job only allows to add new gateways, but never deletes the existing ones. I mainly used this job on an IaaS that didn't have a default gateway.

Glad to accept a PR that deletes existing ones.

@voelzmo
Copy link

voelzmo commented Jan 8, 2016

Not sure if this is feasible, though. The agent will write the network settings on a regular basis and therefore re-add the gateway if you delete it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants