Re: transparent IRC proxy: doesnt work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On October 23, 2003 11:03 am, Sylvain BERTRAND wrote:
> My apologiesHi everyone,
>
> I have a router/firewall on a public /24. I installed tircproxy in order to
> have a transparent proxy (to filter DCC send requests). Here are the lines
> related to IRC in my rc.firewall:
>
> ${IPTABLES} -t nat -A PREROUTING -s ${INTERNAL_LAN} -p tcp --dport
> 6660:6669 -j REDIRECT --to-port 7666 ${IPTABLES} -t nat -A PREROUTING -s
> ${INTERNAL_LAN} -p udp --dport 6660:6669 -j REDIRECT --to-port 7666
>
> and here's the command I use to launch the proxy:
>
> tircproxy -s 7666 -b ${MY_IP} -S -K -R -I
>
> There are several strange things:
> - many connexions between my internal lan and external servers on port 6667
> still exist... they shouldnt since I redirected the 6667 trafic? - many
> connexions between my router on ports >1024 and.... my router's port 7666!
> I was expecting local machines to connect on 7666, but not the router
> itself?
>
> IRC seems to be working for clients, but I think it does through direct
> connexions... Can anyone help me about that?
>

	This is what DCC does. Direct client to client connection.  Once the 
	initial communication is done from the clients to the server and back, 
	the actual transfer is direct from client to client

	For the record, why are you using a proxy? -- does this proxy do filtering on 
some other level? --  is this filtering working?

>
> Sylvain

-- 

	Alistair Tonner
	nerdnet.ca
	Senior Systems Analyst - RSS
	
     Any sufficiently advanced technology will have the appearance of magic.
	Lets get magical!


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux