This is a discussion on eMule and iptables within the Linux Security forums, part of the System Security and Security Related category; I am looking for iptables firewall rules for eMule, which accepts all connections and forwards, but I can find anything ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I am looking for iptables firewall rules for eMule, which accepts all
connections and forwards, but I can find anything useful on the net. There are lots of discussions on usenet about rules but I'd rather have a set of rules which will work right away than trying out all suggestions in the discussion threads. I have a Linux router which runs RH 7.3 with two network cards of which eth0 (with IP 10.0.0.1) is connected to an Alcatel/Thompson ADSL modem (with IP 10.0.0.138). The other network card eth1 (IP 192.168.1.10) is connected to a switching hub and connected to that is a PC which runs eMule (IP 192.168.1.60). Maybe someone has a similar setup and can give me a copy of their rc.firewall or rc.local with all the rules necessary to allow all e-mule connections through. Thank you, Martijn Janssen |
|
|||
|
Martijn wrote:
> I am looking for iptables firewall rules for eMule, which accepts all > connections and forwards, but I can find anything useful on the net. > There are lots of discussions on usenet about rules but I'd rather > have a set of rules which will work right away than trying out all > suggestions in the discussion threads. > > I have a Linux router which runs RH 7.3 with two network cards of > which eth0 (with IP 10.0.0.1) is connected to an Alcatel/Thompson ADSL > modem (with IP 10.0.0.138). The other network card eth1 (IP > 192.168.1.10) is connected to a switching hub and connected to that is > a PC which runs eMule (IP 192.168.1.60). > > Maybe someone has a similar setup and can give me a copy of their > rc.firewall or rc.local with all the rules necessary to allow all > e-mule connections through. > > Thank you, > > Martijn Janssen 1) Find what ports eMule uses. 2) Open those to all incoming connections (if you're using stateful, then it's state "new", or else include -syn to denote SYN packets). 3) P2P sharing of copyrighted materials is against the law and is evil. -- By doing just a little every day, you can gradually let the task completely overwhelm you. |
|
|||
|
NeoSadist wrote:
> Martijn wrote: >> I am looking for iptables firewall rules for eMule, which accepts all >> connections and forwards, but I can find anything useful on the net. >> There are lots of discussions on usenet about rules but I'd rather >> have a set of rules which will work right away than trying out all >> suggestions in the discussion threads. [snip] > 1) Find what ports eMule uses. There's a couple of ways to do this. One would be to turn off the firewall for a few minutes, run eMule and a packet sniffer, and see what ports get used. It'd probably be a good idea to do it twice, so you can see which ports (if any) are dynamically assigned. Ideally, you ought to be able to dig up the docs for eMule and find out from them; unfortunately, ports used aren't always well-documented. > 2) Open those to all incoming connections (if you're using stateful, then > it's state "new", or else include -syn to denote SYN packets). > 3) P2P sharing of copyrighted materials is against the law and is evil. Well, actually, it's neither. -- ZZzz |\ _,,,---,,_ Travis S. Casey <efindel@earthlink.net> /,`.-'`' -. ;-;;,_ No one agrees with me. Not even me. |,4- ) )-,_..;\ ( `'-' '---''(_/--' `-'\_) |
|
|||
|
Travis Casey wrote:
>> 3) P2P sharing of copyrighted materials is against the law and is evil. > > Well, actually, it's neither. As in sharing copyrighted materials P2P without the license to do so. I'm not going to argue this over usenet because it's already been decided. -- Only adults have difficulty with childproof caps. |
|
|||
|
NeoSadist wrote:
> Travis Casey wrote: >>> 3) P2P sharing of copyrighted materials is against the law and is evil. >> >> Well, actually, it's neither. > > As in sharing copyrighted materials P2P without the license to do so. I'm > not going to argue this over usenet because it's already been decided. You didn't say anything about lacking a license. In any case, though, what you need to share copyrighted files is permission; a license is one way to obtain that, but not the only one. Whether it's evil, however, is a moral question, and depends on the moral system in use. -- ZZzz |\ _,,,---,,_ Travis S. Casey <efindel@earthlink.net> /,`.-'`' -. ;-;;,_ No one agrees with me. Not even me. |,4- ) )-,_..;\ ( `'-' '---''(_/--' `-'\_) |
|
|||
|
On Fri, 10 Sep 2004 10:00:30 +0000, Travis Casey wrote:
> You didn't say anything about lacking a license. In any case, though, what > you need to share copyrighted files is permission; a license is one way to > obtain that, but not the only one. Whether it's evil, however, is a moral > question, and depends on the moral system in use. I share Linux ISO's with MLDonkey does that make me evil? -- A bug in the hand is better than one as yet undetected. |
|
|||
|
Geoffrey King wrote:
> On Fri, 10 Sep 2004 10:00:30 +0000, Travis Casey wrote: > >> You didn't say anything about lacking a license. In any case, though, >> what you need to share copyrighted files is permission; a license is one >> way to >> obtain that, but not the only one. Whether it's evil, however, is a >> moral question, and depends on the moral system in use. > > I share Linux ISO's with MLDonkey does that make me evil? No, but it makes you look stupid because we're talking about something else. Even then, BitTorrent works better and faster, and is more trustworthy when coming from the home page of the Linux ISO maker. You must also realize that P2P has a bad history of people sending each other infected files, so don't think ISOs are immune to infection, or loss of data integrity as well. But anyways, we were talking about something totally different. -- Death is nature's way of telling you to slow down |