Skip to content
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

Set weight of a next-hop-route for multiple pppoe-uplinks? #133

Open
RubenKelevra opened this issue Jun 7, 2016 · 3 comments
Open

Set weight of a next-hop-route for multiple pppoe-uplinks? #133

RubenKelevra opened this issue Jun 7, 2016 · 3 comments
Labels

Comments

@RubenKelevra
Copy link

RubenKelevra commented Jun 7, 2016

How do I set the weight for the next-hop route entry to loadbalance on multiple pppoe-uplinks?

Something like:

ip route add default scope global nexthop via $nexthop_ppp0 dev ppp0 weight 1 \
nexthop via $nexthop_ppp1 dev ppp1 weight 1

@k0ste
Copy link
Contributor

k0ste commented Jun 23, 2016

Try to add to your profile.

IPCustom=(
'route add default scope global nexthop via $your_address dev ppp0 weight 1 nexthop via $your_address dev ppp1 weight 1'
)

@RubenKelevra
Copy link
Author

RubenKelevra commented Jun 23, 2016

@k0ste $your_address can't be my address and my gateway...

I know that it's possible to script everything, I hoped for something profildriven something like this:

Interface=ppp0
Connection=pppoe
User='example@yourprovider.com'
Password='very secret'
ConnectionMode='persist'
DefaultRoute=true
Weight=1

@k0ste
Copy link
Contributor

k0ste commented Jun 23, 2016

Why are you complicating simple things? All that could pass to ip can be set in IPCustom.

I test this, work properly.

Description='VLAN555'
Connection='vlan'
Interface='vlan555'
IP='static'
BindsToInterfaces='eth0'
VLANID='555'
IPCustom=(
'ro add 0.0.0.0/0 scope global nexthop dev Tunnel1 weight 1 nexthop dev Tunnel2 weight 1'
)

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

No branches or pull requests

3 participants