Menu
What's new
By:
Filters Better Search

Recent content by digdesdev

  • 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. D

    Is it possible to block IP ranges from specific ports either directly or with Skynet?

    Sorry for the delayed reply. Life gets in the way. :) I'll try this new rule format. I do appreciate everyone's efforts.
  2. D

    Is it possible to block IP ranges from specific ports either directly or with Skynet?

    Thanks for confirming that. It seems that the best way to be sure is to create all the FORWARD rules in the firewall-start script and not use the GUI list.
  3. D

    Is it possible to block IP ranges from specific ports either directly or with Skynet?

    I appreciate all the help and discussion on how the filtering rules work for this newbie. With regard to this line: iptables -D FORWARD -s 75.0.0.0/8 -d 192.168.1.100/32 -j DROP Just to clarify this for me, this will drop any traffic from any IP address in the 75.x.x.x range that is being...
  4. D

    Is it possible to block IP ranges from specific ports either directly or with Skynet?

    Unless I'm misunderstanding the operation of netfilter (which is a good possibility) that is only a LAN to WAN filter and prevents LAN devices from accessing the Internet. What I need is a WAN to LAN filter so remote systems from blocked addressses can't access the VoIP system ports but other...
  5. D

    Is it possible to block IP ranges from specific ports either directly or with Skynet?

    The need is to block ranges from trying to hack the VoIP while allowing office users to access websites with IP addresses within those ranges. I.e., can I blacklist IP addresses or ranges from specific ports while allowing access to others? I haven't been able to find any info or posts that...
  6. D

    Help getting a firewall-start script to run

    It is now working, but I don't know why. Thinking that I had missed a space character, I changed the shebang to include a space between the command "#!" and the path parameter "/bin/sh" and that seemed to fix it. I thought that was the issue but when I carefully checked all the other posts...
  7. D

    Help getting a firewall-start script to run

    Yes. Here it is again (with the IP addresses x'd out. I'm not sure why I'm protecting malicious hacker IPs.):) The -x was added to the shebang to supposedly enable debug logging but nothing is showing up in the system log. If I've done something wrong please let me know...
  8. D

    Help getting a firewall-start script to run

    Here is your command and the result: admin@RT-AC1900P-96A0:/# l /jffs/scripts -rwxr-xr-x 1 admin root 342 Jun 5 15:31 firewall-start* Thanks for your thought.
  9. D

    Help getting a firewall-start script to run

    Will do when I’m back where I can get access. Just so I understand and can learn something, this is checking for spelling errors in the script, not the name? Thanks.
  10. D

    Help getting a firewall-start script to run

    It does not create the file on a router reboot, nor does it echo the logger line to the system log. It does do those things when I run it from the command line. I did a dos2unix per your suggestion but it didn't help. Because it works when run manually from the command line I don't think the...
  11. D

    Help getting a firewall-start script to run

    The previous thread on this subject is old, from 2015, and morphed into a discussion of version numbers and dos2unix without a complete answer on why it wouldn't run so I have started this thread. Background: The need here is to block specific inbound IP addresses per the request of the VoIP...
See more
Top