-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Parse error in conf file #175
Comments
Well, does all these interfaces exist on the system? I've set up something similar with your config, different interfaec names only, and that works fine as long as the interfaces exist. |
Yes, they do. As I said there is only one difference - existing '-N' flag which causing this log message to appear. |
Hmm, could you show me the complete command line for starting smcrouted? It's a bit fishy that the daemon name is |
Also, could you dump the output of |
By the way, its OpenWrt 21.01
I tried to debug smcroute code and inserted a Lines 468 to 471 in e22f63d
and the value of rc var was -4 . Then I remove mrdisc from smcroute.conf and rc became -5 .TLDR; I found that this code decrements rc :Lines 328 to 329 in e22f63d
because I build smcroute with mrdisc support.
|
Thanks, reproduced now! :-) Just pushed a fix, the |
I'll prepare a new release in a couple of days, and hopefully get it out the door during the weekend. Thank you for reporting and helping debug this! <3 |
Thanks, works now! |
Great :) |
Release available at https://github.com/troglobit/smcroute/releases/tag/2.5.5 |
Hi!
I use pretty simple config:
phyint eth1 enable ttl-threshold 1 mrdisc
phyint net1 enable ttl-threshold 2
phyint net2 enable ttl-threshold 2
phyint net3 enable ttl-threshold 2
phyint net4 enable ttl-threshold 2
mgroup from eth1 group 225.1.2.3 source 192.168.1.42
mroute from eth1 group 225.1.2.3 source 192.168.1.42 to net1
And it works just fine, until I pass
-N
flag to smcroute. In that case it also works fine except there is a message in the log:smcroute[2789]: Parse error in /etc/smcroute.conf
.Both cases observed in 2.5.3 and 2.5.4 versions. Didn't check in previous versions.
The text was updated successfully, but these errors were encountered: