Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. T

    Allow Packets With Custom iptables Rules

    You are most likely right. I have no experience with this brand. :)
  2. T

    Allow Packets With Custom iptables Rules

    Ah, my bad. I did not know a topic had already been created. I guess I did not try enough search keywords. It's strange that only the RT-AC66U and the RT-N66U experience this issue, while the RT-AC66R and RT-N66W, reportedly, have not. Is it a "66U" series issue?
  3. T

    Allow Packets With Custom iptables Rules

    The destination port for each phone is definitely dynamic. For example, here are a few values: 41397, 46971, 53815, and 53815. Whenever I call the other phones, as long as they've been connected for some time, the calls are connected to the correct phone over cell. I've never received a call...
  4. T

    Allow Packets With Custom iptables Rules

    Thanks for your input. I replaced the port forwarding rules with what you provided and I have the same issue.
  5. T

    Allow Packets With Custom iptables Rules

    After taking quite a bit of time to test the various settings mentioned above, I have concluded that they have no effect on the issue. My family member's phones were still not receiving calls. My phone, however, continued to receive calls correctly because I left the iptables rule in place. I do...
  6. T

    Allow Packets With Custom iptables Rules

    All of those things you mentioned about the script are already true. The script has universal read/write/executable access (-rwxrwxrwx) and I have been using vi to create/edit the script. I do have UPNP enabled already. Another question: how should this script handle multiple phones? Should I...
  7. T

    Allow Packets With Custom iptables Rules

    In the meantime, I have a couple of more general questions: I included a logger message in my script to confirm that it runs on command. How do I ensure that it runs automatically at startup? As far as I could tell, firewall-start is not running automatically. Are these scripts executed before...
  8. T

    Allow Packets With Custom iptables Rules

    I am not getting any other errors. Let's hope this fixes it . . . I now have to wait several minutes and see if this works. I will definitely be back with the results.
  9. T

    Allow Packets With Custom iptables Rules

    Thanks again for your response. After replacing xxx.xxx.xxx.xxx with my phone's IP address, I executed the code that you provided which resulted in the following error message: Like my router, I have no idea what that is intended to be, so I can't move beyond this. :o
  10. T

    Allow Packets With Custom iptables Rules

    The DST value belongs to my ISP (Comcast). The SRC value belongs to Republic Wireless which is my cell phone service provider. Incoming calls from that IP are being rejected by my firewall. This is causing calls to then route over cell which is undesirable in my case. Here is a forum topic...
  11. T

    Allow Packets With Custom iptables Rules

    Those were the first lines of the script, yes. My bad. That is shameful. :o I am trying these custom rules because the packets are being dropped. The FUPNP chain is completely empty.
  12. T

    Allow Packets With Custom iptables Rules

    Thanks for your response. That seems pretty obvious after you mention it. Unfortunately, I am still getting the same results. Does the fact that I have to execute this script manually have any effect? It does not appear to be running automatically after rebooting.
  13. T

    Allow Packets With Custom iptables Rules

    Hello, everyone! I am currently trying to configure my RT-AC66U router (running Merlin's firmware version 376.48_3) to allow incoming VoIP packets through UDP port 5090. I have added the following code to the firewall-start script within /jffs/scripts/: chmod a+rx /jffs/scripts/* #!/bin/sh...
Top