IGMP Proxy - Can't apply config
-
Hi
2.4.0-BETA (amd64)
built on Wed Mar 01 14:03:16 CST 2017: igmpproxy -dvvvv /tmp/igmpproxy.conf Unable to open configfile from /tmp/igmpproxy.confThe file doesn't exist and the User interface always says "The IGMP entry list has been changed. The changes must be applied for them to take effect.". Applying nothing happens and save in general IGMP proxy nothing happens but can add and save each entry.
Edite: Of course is nothing in tmp this was changed to /var/etc/igmpproxy.conf (a51dd381)
Anyone have this? if no what can i do?. Tryied remove and install, same (). Delete each entry, same.
Remove process:```
[1/2] Deinstalling pfSense-2.4.0.b.20170228.2253...
[1/2] Deleting files for pfSense-2.4.0.b.20170228.2253: 100%
[2/2] Deinstalling igmpproxy-0.1_5,1...
[2/2] Deleting files for igmpproxy-0.1_5,1: 40%
igmpproxy-0.1_5,1: missing file /usr/local/man/man5/igmpproxy.conf.5.gz
[2/2] Deleting files for igmpproxy-0.1_5,1: 60%
igmpproxy-0.1_5,1: missing file /usr/local/man/man8/igmpproxy.8.gz
Edite: Of course is nothing in tmp this was changed to /var/etc/igmpproxy.conf[2/2] Deleting files for igmpproxy-0.1_5,1: 100%Top:48514 root 1 20 0 8220K 2168K select 1 0:00 0.00% /usr/local/sbin/igmpproxy -v /var/etc/igmpproxy.conf
/var/etc/igmpproxy.conf##------------------------------------------------------
Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint em0_vlan15 upstream ratelimit 0 threshold 1
altnet 10.173.0.0/16
altnet 224.0.0.0/8
altnet 232.0.0.0/8phyint em1 downstream ratelimit 0 threshold 1
altnet 192.168.1.0/24phyint em0_vlan100 disabled
phyint em1_vlan1100 disabled
phyint em0_vlan101 disabled
phyint em1_vlan110 disabled**Edited:** seems is only the Gui that doesn't know about the config changes, the changes are in config file. I need to learn more about this igmp stuff and pfSense. Thanks -
Hi,
I can confirm this. Am on the latest 2.4 version.
Besides that my igmpproxy works fine.Regards,
gliddie -
Thanks
I'm noob in this stuff. I have a new triple service: data, voip and iptv to configure for a company and the thing missing is the IPTV (less important than the other two but will be needed in the guests apartment side) to take Thomson router out for once.
Now i probably have to restart pfSense the message it appears in the end when igmpproxy -dvvvv /var/etc/igmpproxy.conf is "MC-Router API already in use; Errno(48): Address already in use". But yes should be working.
Maybe if someone see the user.ini from the Thomson Technicolor TG784n v3 can help me?. But is not for this topic. Maybe in the General forum.
-
This should fix the apply button once pulled: https://github.com/pfsense/pfsense/pull/3606/files
-
Restarting pfSense same thing. igmpproxy -dvvvv /var/etc/igmpproxy.conf give in the end "MC-Router API already in use; Errno(48): Address already in use"
Searching for config file at '/var/etc/igmpproxy.conf' Config: Quick leave mode enabled. Config: Got a phyint token. Config: IF: Config for interface em1. Config: IF: Got downstream token. Config: IF: Got ratelimit token '0'. Config: IF: Got threshold token '1'. Config: IF: Got altnet token 192.168.xx.0/24. Config: IF: Altnet: Parsed altnet to 192.168.xx/24. IF name : em1 Next ptr : 0 Ratelimit : 0 Threshold : 1 State : 2 Allowednet ptr : e26000 Config: Got a phyint token. Config: IF: Config for interface em0_vlan101. Config: IF: Got upstream token. Config: IF: Got ratelimit token '0'. Config: IF: Got threshold token '2'. Config: IF: Got altnet token 224.0.0.0/8. Config: IF: Altnet: Parsed altnet to 224/8. Config: IF: Got altnet token 232.0.0.0/8. Config: IF: Altnet: Parsed altnet to 232/8. IF name : em0_vlan101 Next ptr : 0 Ratelimit : 0 Threshold : 2 State : 1 Allowednet ptr : e26020 Config: Got a phyint token. Config: IF: Config for interface em0_vlan100. Config: IF: Got disabled token. IF name : em0_vlan100 Next ptr : 0 Ratelimit : 0 Threshold : 1 State : 0 Allowednet ptr : 0 Config: Got a phyint token. Config: IF: Config for interface em1_vlan1100. Config: IF: Got disabled token. IF name : em1_vlan1100 Next ptr : 0 Ratelimit : 0 Threshold : 1 State : 0 Allowednet ptr : 0 Config: Got a phyint token. Config: IF: Config for interface em0_vlan105. Config: IF: Got disabled token. IF name : em0_vlan105 Next ptr : 0 Ratelimit : 0 Threshold : 1 State : 0 Allowednet ptr : 0 Config: Got a phyint token. Config: IF: Config for interface em1_vlan110. Config: IF: Got disabled token. IF name : em1_vlan110 Next ptr : 0 Ratelimit : 0 Threshold : 1 State : 0 Allowednet ptr : 0 buildIfVc: Starting... buildIfVc: Interface is not AF_INET, skipping ale0 (family 18) buildIfVc: Interface is not AF_INET, skipping em0 (family 18) buildIfVc: Interface is not AF_INET, skipping em0 (family 28) buildIfVc: Interface is not AF_INET, skipping em1 (family 18) buildIfVc: Interface is not AF_INET, skipping em1 (family 28) buildIfVc: Interface em1 Addr: 192.168.xx.x, Flags: 0xffff8b43, Network: 192.168.xx/24 buildIfVc: Interface is not AF_INET, skipping lo0 (family 18) buildIfVc: Interface is not AF_INET, skipping lo0 (family 28) buildIfVc: Interface is not AF_INET, skipping lo0 (family 28) buildIfVc: Interface lo0 Addr: 127.0.0.1, Flags: 0xffff8049, Network: 127/8 buildIfVc: Interface is not AF_INET, skipping enc0 (family 18) buildIfVc: Interface is not AF_INET, skipping pflog0 (family 18) buildIfVc: Interface is not AF_INET, skipping pfsync0 (family 18) buildIfVc: Interface is not AF_INET, skipping em1_vlan110 (family 18) buildIfVc: Interface is not AF_INET, skipping em1_vlan110 (family 28) buildIfVc: Interface em1_vlan110 Addr: 172.16.xx.x, Flags: 0xffff8843, Network: 172.16.xx/24 buildIfVc: Interface is not AF_INET, skipping em1_vlan1100 (family 18) buildIfVc: Interface is not AF_INET, skipping em1_vlan1100 (family 28) buildIfVc: Interface em1_vlan1100 Addr: 192.168.xx.xx, Flags: 0xffff8943, Network: 192.168.xx/24 buildIfVc: Interface is not AF_INET, skipping em0_vlan100 (family 18) buildIfVc: Interface is not AF_INET, skipping em0_vlan100 (family 28) buildIfVc: Interface em0_vlan100 Addr: 188.37.xxx.xxx, Flags: 0xffff8943, Network: 188.37.xxx/18 buildIfVc: Interface is not AF_INET, skipping em0_vlan101 (family 18) buildIfVc: Interface is not AF_INET, skipping em0_vlan101 (family 28) buildIfVc: Interface em0_vlan101 Addr: 10.177.xxx.xxx, Flags: 0xffff8a43, Network: 10.177.xxx/18 buildIfVc: Interface is not AF_INET, skipping gif0 (family 18) buildIfVc: Interface is not AF_INET, skipping gif0 (family 28) buildIfVc: Interface is not AF_INET, skipping gif0 (family 28) buildIfVc: Interface is not AF_INET, skipping em0_vlan105 (family 18) buildIfVc: Interface is not AF_INET, skipping em0_vlan105 (family 28) buildIfVc: Interface em0_vlan105 Addr: 10.53.xxx.xxx, Flags: 0xffff8843, Network: 10.53.xxx/17 Found config for em1 Found config for em1_vlan110 Found config for em1_vlan1100 Found config for em0_vlan100 Found config for em0_vlan101 Found config for em0_vlan105 MC-Router API already in use; Errno(48): Address already in use/var/etc/igmpproxy.conf
##------------------------------------------------------ ## Enable Quickleave mode (Sends Leave instantly) ##------------------------------------------------------ quickleave phyint em1 downstream ratelimit 0 threshold 1 altnet 192.168.11.0/24 phyint em0_vlan101 upstream ratelimit 0 threshold 2 altnet 224.0.0.0/8 altnet 232.0.0.0/8 phyint em0_vlan100 disabled phyint em1_vlan1100 disabled phyint em0_vlan105 disabled phyint em1_vlan110 disabledNetworks
em0_vlan100 -> Internet Data
em0_vlan101 -> Voip
em0_IPTV -> IPTVem1 -> Lan
em1_vlan110 -> Lan GuestsHave changed some IP numbers with xxxx
Something wrong here?
-
igmpproxy -dvvvv /var/etc/igmpproxy.conf ```In the end shows _"MC-Router API already in use; Errno(48): Address already in use_" This error happens because i try to run second time (dumb). My idea is troubleshoot igmpproxy. generally i'm a little better than this on Unix stuff, for some reason i thought this command was to troubleshoot the process already running. So i have to stop it in **Status** > **Services** and then run the command in shell **_igmpproxy -dvvvv /var/etc/igmpproxy.conf_** > This should fix the apply button once pulled: https://github.com/pfsense/pfsense/pull/3606/files I don't know taking off the apply button is a good idea. For the changes take place we need to manually restart the service, the apply button should do that and the save button only save to the config. Thanks for the help. -
I'm not taking off the apply button. I'm making that actually do something (write new config and restart service).
As for the save button on the main page (besides the 'add' button), there is nothing there that really needs saving. Like changing the order of the rows after dragging them to a different position. (Which isn't implemented there.) And it doesn't seem to do anything anyhow.?
-
I'm not taking off the apply button. I'm making that actually do something (write new config and restart service).
Thanks
As for the save button on the main page (besides the 'add' button), there is nothing there that really needs saving. Like changing the order of the rows after dragging them to a different position. (Which isn't implemented there.) And it doesn't seem to do anything anyhow.?
The save button to me was very confuse because the config is saved when saving each entry, right?, so yeah confusing. Don't have opinion on that.
-
I'm not taking off the apply button. I'm making that actually do something (write new config and restart service).
As for the save button on the main page (besides the 'add' button), there is nothing there that really needs saving. Like changing the order of the rows after dragging them to a different position. (Which isn't implemented there.) And it doesn't seem to do anything anyhow.?
Yeh, that's the correct thing to do. With the current code, the "Save" button actually does an "Apply" action, and the "Apply" button does nothing. After fixing that (which PR https://github.com/pfsense/pfsense/pull/3606 does), then the "Save" button has no other use, so deleting it is good.
It works in the same workflow as Firewall Aliases, Firewall Rules etc - changes are saved in the config when pressing "Save" in the edit screen. The user is then shown the "summary" screen listing all the entries and presses "Apply" to implement the changes on the running system.
