-
Notifications
You must be signed in to change notification settings - Fork 45
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
[RFC] [RFT] Move options to config file #60
[RFC] [RFT] Move options to config file #60
Conversation
Have seen this, but won't look into this until thursday, if my weekplan works out. |
Thanks for making that happen, I'll also have to find time in the next few days to review and test this. |
I like the config format and with minor nits got it up and running – but it does not seem to work properly. Config: https://gist.github.com/mweinelt/696d5b33c08944a1f65ccb439b346cf2 It does open a socket and listen on it.
But I don't see queries arriving at the process and thus no replies. The firewall rules are still in place as they were before, so they're not at fault.
Meanwhile queries are incoming:
And the firewall allows that:
Puzzling. |
Misread the documentation, inheritance from the default section should now work correctly
Finally … Yanic seems to be unhappy about an empty node_id.
|
In Kiel the responses generated look perfectly normal to me
{
"software": {
"fastd": {
"enabled": true,
"version": "v18"
},
"batman-adv": {
"version": "2016.4"
},
"firmware": {
"base": "Debian",
"release": "9.11"
}
},
"vpn": true,
"node_id": "deadbeefff00",
"hardware": {
"nproc": 8
},
"network": {
"mac": "de:ad:be:ef:ff:00",
"mesh": {
"bat-ffki": {
"interfaces": {
"tunnel": [
"de:ad:be:ef:ff:00",
"8a:18:67:f9:b8:08",
"6e:f6:4e:2c:e2:6f",
"3e:4b:3c:92:f5:20",
"2a:f4:70:32:f9:f7",
"92:62:15:4d:2f:8d"
]
}
}
},
"addresses": [
"2a07:59c6:ec02::1",
"2a03:2260:1017::1",
"fe80::dcad:beff:feef:ff00",
"fda1:384a:74de:4242::ff00"
]
},
"hostname": "vpn0"
} I'd only expect the node id to be missing it the domain is either
or
|
The DefaultDomainType does not take effect. Works if I set |
However still no domain code. Is that expected?
|
@mweinelt Ah, sorry. I changed the name of the default domain type setting to just The missing domain code is not expected, however I simply forgot to support that feature while converting to the config file based system |
Fixed in d3d587b |
Yep, that makes everything work. Thanks! |
What's the holdup? In Freifunk Rhein-Neckar we started using the config file method yesterday and it seems to work. You could of course discuss about continuing to support single domain setups via command line arguments (if there is any need), but i would tend not to do that. |
Hey @herbetom , |
|
Thanks, I'll be in freifunkh's mumble at seven, if anyone wants to join. |
This branch looks promising. As soon as this branch gets merged, I'd vote for merge. btw, is there an option to override the hostname? |
I don't think so, but with the config file it should be easilier possible to add such an option, since their is to need to add another argc. 😄 |
Merged |
they implemented a long awaited PR, where they'd change the config from arguments to one configfile. Look here for further reference: ffnord/mesh-announce#60
This PR moves the configuration of mesh-announce to a config file. The old commandline based config interface is a hot mess.
Currently this is a breaking change. The old command line options have been removed and replaced by a config file.
@AiyionPrime @mweinelt what are your thoughts on this change? Do you agree with the overall config concept?