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
FS#320 - relayd feature request #5356
Comments
jow-: Rewriting user configurations based on DHCP events is an absolute no-go, we need to find a better solution here. |
finas: makes sense. relayd was made by nbd, right? |
jow-: Yes, the easiest would be to extend relayd or to extend the init script of relayd to fetch the gateway info from ubus. Then we could install hotplug events to reload relayd on dhcp changes. |
finas: cool. extending the init script seems easier. Thanks for the input. hoping someone will pick this down the road, I had to resort to gargoyle for a specific case where I really needed this functionality and it kills me really. |
finas: Hi guys, Any decision regarding implementing this? |
jow-: Yes, it would be nice. Someone just has to do it :) |
finas: like, someone like nbd ;) |
finas: please? |
@jow- is this still of use? If not please close this |
finas:
I found a couple of bugs with relayd based bridge configuration and I would like to suggest a feature request. Will fill one entry per issue:
On today's trunk
3- in a configuration where the network attached to the wireless radio is configured via DHCP, the listening interface is not set up automatically. DD-WRT and Gargoyle do this automatically ( they overwrite the config/network file with the gateway parameter and reload relayd.
The text was updated successfully, but these errors were encountered: