iptables-persistent and Homer problem ? #629
Replies: 3 comments
-
Hello @sraimondeau You will need to set up explicit rules for any port you want to use and save them as persistent. |
Beta Was this translation helpful? Give feedback.
-
Hello @lmangani , thank you for your reply. This is the content of /etc/iptables/rules.v4 generated during iptables-persistent installation: Generated by xtables-save v1.8.2 on Mon Feb 26 15:39:17 2024*filter Completed on Mon Feb 26 15:39:17 2024I think my problem is not linked to the iptables rules because there are none. |
Beta Was this translation helpful? Give feedback.
-
Thanks to @ewadii (sipcapture/homer-installer#88), problem is resolved with the modification of /lib/systemd/system/heplify-server.service : |
Beta Was this translation helpful? Give feedback.
-
Hello,
I don't know if it is the right place to post an issue I have. anyway I need help so... :-)
I have setup a fresh Homer 7 install on a Debian 10 (test also with Debian 11) using ./homer_installer.sh bash script.
VM is hosted at OVHcloud.
My Oracle SBCs are sending HEP and everything is OK. I can see the SIP exchanges in the web interface.
I see also the increment in the psql table hep_proto_1_call (https://github.com/sipcapture/homer/wiki/Troubleshooting-Homer-7.7)
Now, I want to secure a little bit the installation.
So I install iptables-persistent with apt-get install iptables-persistent .
No rules in it, only the package.
Just after install, the count in hep_proto_1_call is incrementing correctly.
Now I reboot the server,
After the reboot, the count in hep_proto_1 stops incrementing and so the web interface does not get the new SIP communications.
Of course, with a simple reboot without package iptables-persistent, everything is fine.
apt-get remove iptables-persistent does not solve the issue.
Have you got an idea where the problem is ?
Kind regards, Stéphane.
Beta Was this translation helpful? Give feedback.
All reactions