Re: [Shorewall-users] IRC, Shorewall and DCC

[Zipleen <zi...@ne...>]

Zipleen wrote:

> Jan Johansson wrote:
>
>> I know this isnt a shorewall question per se. But i have not found a 
>> better resource for "generally net sawy" persons anywhere
>>
>> With my old firewall (RH6.1, 2.2.19) PMFirewall, tIRCproxy) it was 
>> all so easy, and DCC worked in both directions.
>> But on my new box (Debian 3.0, 2.4.18, Shorewall) i cant make it work 
>> for outgoing DCC.  What should i do to keep stuff happy?
>>
>> I have set my girls mIRC up to use ports 1024-5000 for DCC, i have 
>> configured ez-bounce 1.0 to use 1024-5000for DCC, and i haver the 
>> following in my rules
>>
>> #
>> #IRC
>> ACCEPT          loc     $FW     tcp     6667,6668,1024:5000     
>> ACCEPT          $FW     loc     tcp     6667,6668,1024:5000     
>> ACCEPT          $FW     net     tcp     6667,6668,1024:5000
>>
>> didnt work, so i added
>> ACCEPT         net     $FW     tcp     1024:5000
>> ACCEPT         net     loc     tcp     1024:5000
>>
>> still No go.
>> What is "the way to go"?  Proxy/No proxy? Any special rules? Any 
>> pointers? Help! :)
>> _______________________________________________
>> Shorewall-users mailing list
>> Sho...@sh...
>> http://www.shorewall.net/mailman/listinfo/shorewall-users
>>  
>>
> i had the same problem with mIRC. outgoing DCC connections refused to 
> work. But I solved it right away. I tryed mIRC with everything but no 
> luck and then I tried X-Chat (www.xchat.org). Don´t know why, but 
> x-chat works for dcc just fine, and mIRC doesn´t. So now I use X-chat 
> for windows instead of mIRC... You could give it a try ;)
> btw: i didn´t put any rules or whatesoever... the irc conntrack 
> modules does it all.
> And I think this also happens with the connection sharing stuff witch 
> comes in winXP I guess.
>
> Regards,
> Luis
>
>
>
well, i finally got mIRC to work. don´t know if some of you are 
interested in this or not, but anyway :
go to mirc options, and then to CONNECT | Local Info.
I changed the lookup method to normal and cleread the ips in the two 
boxes above and checked the other two.
Then, go to CONNECT | OPTIONS, click ADVANCED and then check Bind All 
sockets to this IP address: and the fill out the INTERNAL ip of your 
machine (mine is 192.168.0.2).
That should do the trick.

Regards,
Luis