I’m glad to see you checked out the Clarkconnect Forums. Ah, yes, I should have researched further before responding.
After reading the eggdrop-conntrack source I see what you mean, it is not ready for what you had in mind. Damn, I got sucked in!
The eggdrop-conntrack patch still needs some work, maybe someone would volunteer to help ???? ( my coding sucks)
But I have a few questions as to your solution.
You said you
Quote:
1.
in CLARKCONNECT firewall configuration FORWARD ident on port 113 (to e.g.192.168.1.25)
This would send the ident requests from the IRC server ( for those that still use it ) to your IRC client ( 192.168.1.25 )
Quote:
2.
in eggdrop.conf (if editable for you) uncomment and set: set reserved portrange 2010:2020
This would open these ports on the client machine for eggdrop, when it is open?
Quote:
3.
in your IRC client set in options/DCC/options dcc ports to first: 2010 last: 2020
This tells the IRC client to listen to these ports?
Quote:
4.
in CLARKCONNECT firewall configuration FORWARD portrange 2010:2020 (to e.g.192.168.1.25)
This forwards ALL these port transactions to the client machine ( 192.168.1.25 )
Quote:
5.
hmmm.. i bound all sockets in IRC client in
Connect/options/Advanced to the IP where it got forwarded(e.g.192.168.1.25)
[doing so you may not need to edit the eggs conf, but i’m not sure about that.]
You bound the ports in the IRC client to the IP address which was running it ??
So in effect you NATed port 113 ( ident ) and ports 2010 through 2020 to the IRC client machine on your LAN which has been set up to listen to and reserved ports 2010 through 2020 when the IRC program eggdrop is open.
OK, you said it works for you, good for you. ( have I heard that before from an admin?)
Since this site is security related I have a few questions:
1. What if you have a LAN with 1000 machines and more then one person wishes to run IRC with eggdrop ??
2. What happens if someone sends malformed or “crafted” packets to those ports?
3. How does the client machine respond to the ident requests?
4. What happens if the client machine ( 192.168.1.25 ) is running and IRC is not ?
5. What happens if IRC crashes on the client machine ??
Those ports are now open to the NET, and thus your entire LAN through the client machine. How are you protecting them??
I believe these questions need to be answered before your solution can be considered viable.