Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: netfilter@lists.netfilter.org
Subject: Re: irc dcc incoming transfers truncated after a while
Date: Tue, 5 Apr 2005 17:59:50 -0400	[thread overview]
Message-ID: <200504051759.50574.Alistair@nerdnet.ca> (raw)
In-Reply-To: <1112267638.21083.14.camel@localhost.localdomain>

On March 31, 2005 06:13 am, Andrea Ratto wrote:
> Hello List!
> I am running a SuSE based router and NAT gateway. It uses the
> SuSEFirewall iptables based script, which saved me a lot of tweaking.
> Everything works great except irc dcc file transfers. I am not talking
> about uploads from internal network (those works because I use forwarded
> ports) but about downloads. After a minute or so the firewall blocks
> some packages killing the transfer.
	
	Are you absolutely certain that your firewall is doing the blocking? -- LOG 
the packets please and let us see.... 

	When you loaded the ip_conntrack_irc module did you set the server ports you 
would be connecting to?  --> modinfo ip_conntrack_irc for the details, you 
need to have the IRC server ports you are connecting to in there.

> Of course i have modprobed ip_nat_irc and ip_conntrack_irc that SuSE
> didn't load by default, but the problem remains. So I was wondering if
> there is something I still need to do (some iptables command to make use
> of the modules?). I haven't found any doc so I am asking the list.
> Thank very much. Bye


	P.S. I've had problems with users on RR getting dcc transfers started, but 
the  connection dies .. I'm not sure where the problem lies -- but its 
something I've seen.
	
	Alistair


      reply	other threads:[~2005-04-05 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31 11:13 irc dcc incoming transfers truncated after a while Andrea Ratto
2005-04-05 21:59 ` Alistair Tonner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200504051759.50574.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox