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

Change metrics at runtime #18

Open
irl opened this issue Sep 13, 2016 · 7 comments
Open

Change metrics at runtime #18

irl opened this issue Sep 13, 2016 · 7 comments

Comments

@irl
Copy link

irl commented Sep 13, 2016

Is it possible to change metrics for the default route at runtime?

I have an application that I would like to run generating traffic over one interface at a time, so I need to promote and demote the routes to get the traffic generated over the correct one.

I can listen to netfilter messages to make sure the correct thing has happened and that nothing is interrupted, but I'm not sure how to make the correct thing happen to begin with.

Will a SIGHUP cause the yaml file to be reloaded, or is there another way to perform runtime reconfiguration?

@kristrev
Copy link
Owner

This is unfortunately not possible at the moment, but is a very good idea. Not sure when or if I will have time to look at it, unless it fits into one of my use-cases (or the people that pay me :)) Listening to a signal and then reloading the yaml file sounds like a good approach, so if you have to implement it then it would be much appreciated.

However, I have used source-based routing and the routing tables etc. is configured correctly. Thus, if you can modify your application to bind to IP (and potentially interface), then the traffic will be sent over the correct interface. In order to get or monitor all available interfaces, there are many solutions. You can for example listen to RTM_NEWROUTE messages and then filter on if the message describes a default route or not.

@kristrev
Copy link
Owner

I was not aware this was originally a request coming from the MAMI project, which makes the whole funding and priority issue much easier. We are fixing some other stuff related to the rules now, and I will incorporate your feature request in that work.

@sferlin
Copy link

sferlin commented Sep 16, 2016

Is the repo the development code you are having now, or ... not? :)

@kristrev
Copy link
Owner

Yes, this is where the old-school IPv4 routing magic happens.

@irl
Copy link
Author

irl commented Sep 16, 2016

@kristrev Ah cool. I'm looking at modifying PATHspider for source-based routing, but if you get to implementing this feature before I get to that modification then it would be very much appreciated. (:

@kristrev
Copy link
Owner

Let us see who finishes first :) I just got delivered some more urgent tasks, so not sure when I will get to this. Will update this issue as I progress, I have a design ready so it is just a matter of finding a few spare hours.

Though, I think adding proper binding support to Pathspider would be great anyway :)

@sferlin
Copy link

sferlin commented Jan 12, 2017

Do you already have something on this?
( I am afraid i cannot avoid it, so I will have to do it if not available).

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

No branches or pull requests

3 participants