Hello Ben, this looks strange and is probably not intended. The behaviour should be similar for IP address and network interface name.
Could you please create an issue on our tracker about it? Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Kaufman <[email protected]> Sent: Thursday, January 19, 2023 12:18 AM To: Kamailio (SER) - Users Mailing List <[email protected]> Subject: [SR-Users] Re: Setting socket_workers does not work if using interface name Not using IPv6. I've created a contianer to easily identify this. After starting the rpc command core.psx is called and it's output printed. By default eth0 will be used: docker run --rm -it whosgonna/kamsockets To use a specific address (and 0.0.0.0 is the easiest), pass it as an environmental variable: docker run --rm -it -e INTERFACE=0.0.0.0 whosgonna/kamsockets The script, etc. can be found here: https://github.com/whosgonna/kam_sockets Kaufman From: Karsten Horsmann <[email protected]<mailto:[email protected]>> Sent: Friday, January 13, 2023 12:45 PM To: Kamailio (SER) - Users Mailing List <[email protected]<mailto:[email protected]>> Subject: [SR-Users] Re: Setting socket_workers does not work if using interface name Hi Kaufmann, did you run ipv6 and the extra listener are ipv6? Kind regards Karsten Horsmann Kaufman <[email protected]<mailto:[email protected]>> schrieb am Fr., 13. Jan. 2023, 04:09: At a quick glance it looks like using socket_workers when the listen parameter uses the interface name does not work. For example: children = 4 socket_workers=2 listen=udp:10.10.10.10:5060<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2F10.10.10.10%3A5060%2F&data=05%7C01%7Cbkaufman%40bcmone.com%7C0d2a7522366647c29eb908daf597c453%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638092329436846029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e1msmpVcoTvDt5ptypJdKPCBI54%2BxH79g7mlFfip%2Bek%3D&reserved=0> Gives two listeners on udp:10.10.10.10:5060<https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2F10.10.10.10%3A5060%2F&data=05%7C01%7Cbkaufman%40bcmone.com%7C0d2a7522366647c29eb908daf597c453%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638092329436846029%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e1msmpVcoTvDt5ptypJdKPCBI54%2BxH79g7mlFfip%2Bek%3D&reserved=0> children = 4 socket_workers=2 listen=udp:eth0:5060 Gives four listeners on the socket. Note this is just a quick cursory observation. Is it by design or a design limitation? Kaufman __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected]<mailto:[email protected]> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
