-
1. It seems that provided log corresponds to wrong config, i.e. with eth2 and eth3 downstream. Could you please post log with correct config?
2. Had you verified that you are able to capture the traffic directly from the router?
3. Does any previous version (e.g. beta2) work well with you config? If so, please post its log.
2009-11-23 18:21:34 UTC in igmpproxy
-
const86 made 1 file-release changes.
2009-10-05 18:28:13 UTC in igmpproxy
-
In Git. Thanks!
2009-09-30 19:27:32 UTC in igmpproxy
-
This certainly can be implemented. We should refresh state when a user
sends signal or when network gets reconfigured (failure on sending packet).
Refreshing means reloading config and discarding all active routes
which conflict with new state.
As usually, patches are welcome :-)
2009-09-17 19:47:14 UTC in igmpproxy
-
Patch committed. Thanks!
2009-09-06 12:34:54 UTC in igmpproxy
-
const86 made 1 file-release changes.
2009-08-16 16:06:01 UTC in igmpproxy
-
Fixed bug in the tokenizer of config parser. It skipped last token in file usually, so my ppp1 was assumed downstream actually. Hence the igmpproxy exited when sending IGMP from outdated address was failed.
The igmpproxy still would exit if any non-disabled interface will be reconfigured. But restart is needed anyway for updating routes.
2009-08-16 14:19:18 UTC in igmpproxy
-
I have several interfaces configured in igmpproxy.conf:
eth0 - downstream
eth1 - upstream
eth2, ppp0, ppp1 - disabled
I've seen several times that igmpproxy crashes during ppp1 restart.
I believe that this happens after ppp1 stopping, because during system boot igmpproxy usually starts before ppp1 and remains working until ppp1 is restarted.
2009-08-15 13:11:42 UTC in igmpproxy
-
Regarding to subnet fix. I agree that current behaviour is incorrect and should be fixed. Thank you for the patch! But I think that it should be reworked later to consult with route table.
Regarding to daemonizing. I had removed that code because it interferes with logging code in weird manner. Just look: if(!Log2Stderr){...}. Moreover, daemoniizing can be performed well by various tools like...
2009-08-15 13:04:45 UTC in igmpproxy
-
I think this patch would go into 0.2 release.
But could you please clarify why should we restrict multicast groups by igmpproxy itself? What a bad happens if downstream joins restricted group (and igmpproxy forwards request therefore)?.
2009-08-15 12:41:21 UTC in igmpproxy
