Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 24 Aug 2003 18:42:30 +0100
From:      Mario Freitas <sub_0@netcabo.pt>
To:        jarthel@excite.com
Cc:        freebsd-net@freebsd.org
Subject:   Re: DCC send/receive and FBSD 5.1 using IPF/IPNAT
Message-ID:  <1061746950.809.15.camel@suzy.unbreakable.homeunix.org>
In-Reply-To: <20030824163109.77577BF88@xmxpita.excite.com>
References:  <20030824163109.77577BF88@xmxpita.excite.com>

index | next in thread | previous in thread | raw e-mail

On Sun, 2003-08-24 at 17:31, Jayel wrote:
> well I searched google and several messages came up with the suggestion of using tircproxy. I then installed tircproxy from ports and ran the configure my setup to use transparent proxy.
> 
> as a test I ran the script (tircproxy -d9 -s 7666 -MILHR -i 10.10.10.254) as suggested by the online manual. The problem with this is that it keeps on saying "CDIR or UDB is not configure in tircproxy.h". I then modified the tircproxy.h to use UDB but I can't compile it.
> 
> any ideas or maybe suggestions that doesn't involve tircproxy. Thanks
> 
> jayel
> 
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

Well, you don't need tircproxy at all. You can DCC receive with no
problems since you have NAT enabled. What you can do for DCC send is:

1) force your irc clients (such as xchat, irssi, mirc, others) to 
auto-detect (some clients may not support detect option) or choose
yourself your internet address.
2) set a range of DCC ports (some irc clients only support one DCC
port). Note: that range will be your maximum DCC send connections.
3) redirect connections from the external interface on your DCC ports
(those you've chosen on step 2) to the internal address where the client
is running.

Something like (pseudo-rule): protocol tcp from any to <your external
interface address> on port <range of ports> redirect-to <your internal
address> on port <range of ports> 

Hope that works, it works for me :)
-- 
Mário Freitas (sub_0@netcabo.pt)
Núcleo Português de FreeBSD (NPF)



help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1061746950.809.15.camel>