similar to: Using torrent in tcrules

I am having a problem that I really just don''t get.... I have this in my rules file: DNAT net loc:192.168.1.2 tcp 21 21 Everything worked fine earlier today.. Now it is dropping packets destined for Port 21 /var/log/messages: Dec 14 00:36:39 pcp08479598pcs kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC=00:0b:6a:3f:e6:72:00:01:5c:22:92:42:08:00 SRC=24.210.36.92 DST=68.57.216.61

>> Hello, >> >> I am using Debian Sarge, with Shorewall 2.2.3, >> >> for access control I am using hosts.allow : >> >> ALL: 144.131.xxx.xxx >> >> and hosts.deny: >> >> ALL: ALL >> >> I have a virtual machine that is being port forwarded to with Shorewall : >> >> DNAT net loc:10.0.0.100 tcp 3389

Sorry for asking this, as I believe it to be a kernel-related rather than Shorewall-related problem. But some of you guys seem to have a lot of experience with these kind of things. I''m setting up a NAT''ing router with two ISP lines. At first sight, everything works as expected, however when the local machines try to keep a TCP-connection open for a long time, it disconnects

Hello, all. I''ve been trying to get shorewall to get LISa working on my Gentoo box. It works as long as I have shorewall turned off, but whenever I turn it on, it seems to block all LISa activity. I have TCP port 7741 opened (as per lisa-home.sourceforge.net), and nmap says it''s open. Ethereal indicates that LISa is communicating via TCP port 7741, from 127.0.0.1 to

Hi i have a small problems on one of my interface : i can''t get traffic out and don''t know why. Ither user say me that i can use Shorewall for create the counter and after get the information for mrtg. Anyone know what is the process into shorewall 2.0.X ? i don''t want monitor by specified port, but all ports Thanks for your help

I have two (interconnected) questions: First of all, I''m trying to use IPP2P to classify my P2P traffic and give it a lower network priority. I''ve already successfully built IPP2P into iptables and the kernel. I read http://www.shorewall.net/IPP2P.html, but it''s confusing me. Using the documentation for normal tcrules in 3.0

Have read the comments about Shorewall not being a personal firewall, etc., and am not necessarily advocating such use, but, trying to get into the poster''s head, and doing some creative thinking, thought that possibly some form of EGID rule might help out if there is a reasonable reason behind the question. It is not hard for me to see how something like this could be useful.

Hi there, I''ve read Routing on One Interface, and Shorewall and Aliased Interfaces docs but I''m a little confused, and all my test attempts have mostly failed. Here is my setup: CentOS 4.2 ShoreWall 3.0.2 My server has a subnet 192.168.50.0/29 routed to it via 192.168.1.2. Currently 192.168.1.2 is setup on eth0. With no ShoreWall involved routing seems to work if I just setup

When searching in google I could verify that many examples of used rules in shorewall do not exist to block port scanners external. Example: nmap. Somebody has some rule or example ? thanks.

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

All, I have a problem with H323 the call disconnects when answered. The debug shows -- Executing Dial("SIP/sj1-4ff7", "H323/0797617729") in new stack -- Called 0797617729 -- H323/0797617729 is ringing -- H323/0797617729 answered SIP/sj1-4ff7 == Spawn extension (default, 0797617729, 1) exited non-zero on 'SIP/sj1-4ff7' -- Executing

Hi, I have this message in my syslog: HTB: quantum of class 10001 is big. Consider r2q change. I don''t know why it''s there. I think all my setup is right. I am shaping traffic from my web server. It lives at three IP addresses, first is fast (and most important - aaa.bbb.ccc.1), second slower (aaa.bbb.ccc.2), third slowest (aaa.bbb.ccc.3). Total bandwidth is 2700kBps. Other

look for clamav-devel-* or clamav-dev-* packages of your distribution. Paul Matthews (paul.matthews@cathedral.qld.edu.au) schrieb: > > I have installed the following when it comes to clamAV > > clamav-db-0.87-1.1.fc3.rf.i386.rpm > clamav-0.87-1.1.fc3.rf.i386.rpm > clamd-0.87-1.1.fc3.rf.i386.rpm > > am I missing something if so could you please direct me to the website?

I try use setup traffic shaping with Shorewall-4.0.2 and have fault. When i start Shorewall with tc-files configured i get follow messages: ... RTNETLINK answers: No such file or directory We have an error talking to the kernel ERROR: Command "tc filter add dev eth2 parent ffff: protocol ip prio 50 u32 match ip src 0.0.0.0/0 police rate 500kbit burst 10k drop flowid :1" Failed

Hi ! I found an excellent article about QoS and traffic shaping for VoIP (Asterisk IAX protocol), which is designed to improve sound quality even over very busy lines. http://www.howtoforge.com/voip_qos_traffic_shaping_iproute2_asterisk Should I just cut and paste all that to shorewall''s tcrules (replacing 4569 with 5060)? Additionally, author of this article uses IAX protocol,

In helping a user on IRC today, I was dismayed to find that a bug that was supposedly fixed in Shorewall 3.4.4 was not fixed. Furthermore, I found that the bug is present as far back as 3.2.6 (I didn''t look back further since 3.2.6 was the release where the user (re-) discovered the bug. If HIGH_ROUTE_MARKS=No, then PREROUTING and OUTPUT marking rules are behaving as if TC_EXPERT=Yes was

In helping a user on IRC today, I was dismayed to find that a bug that was supposedly fixed in Shorewall 3.4.4 was not fixed. Furthermore, I found that the bug is present as far back as 3.2.6 (I didn''t look back further since 3.2.6 was the release where the user (re-) discovered the bug. If HIGH_ROUTE_MARKS=No, then PREROUTING and OUTPUT marking rules are behaving as if TC_EXPERT=Yes was

Hi! I have reprise try to resolve this problem, suspended from 17 dec 2005 I have try to apply the suggest of Jerry (see above). The problem still exist. See attach shorewall config, dump and tcpdump when I check to exit whit SSH from firewall... In the masq file is reported the last my attempt in order to resolve my problem, however I have test also the example reported in MultiISP.html, but

Hello, My hoster updated its kernel packages... It contained some old problems that should have been fixed. My servers have now a wonderful 2.6.21.5 kernel + grsec running. Both are running Debian 4.0 (stable release). mx:/etc/shorewall# iptables --version iptables v1.3.6 mx:/etc/shorewall# uname -a Linux mx.network-hosting.com 2.6.21.5-grsec-xxxx-grs-ipv4-32 #1 SMP Fri Jul 27 17:18:23 CEST

Mike Lander wrote: > I am building a shorewall box that the last post has the SSH error and > wanted > some feedback from the list if possible. At first I thought the two ISP''s > I > building this > for had two T-1''s with FQ ip''s as it. I have the box built for this ready > to > go. > Now I find out that one of the T-1''s is