Le lundi 09 juillet 2007 à 13:17 +0100, Andrew Suffield a écrit : > On Mon, Jul 09, 2007 at 01:32:08PM +0200, bruma wrote: > > > Because as the log message you quote says, the destination port is > > > 4665, which you have not allowed. > > > > In last two weeks I switched from firewall builder to shorewall. As I > > remember opening two ports > > tcp 4662 > > udp 4666 > > on firewall builder was enough to allow edonkey traffic. > > edonkey has always used one tcp port, and one udp port three places > higher. 4662 and 4666 will never have worked. I'm not so sure of that, because these ports are also configured on client side. But this should be default config.
* in my /etc/shorewall/params i use: # Gnutella 2 ports: GNUTELLA2_TCP=6346 GNUTELLA2_UDP=6347,4637 # Edonkey ports: EDONKEY_TCP=4662 EDONKEY_UDP=4662,4666 # Active P2P protocols: P2P_TCP=$GNUTELLA2_TCP,$EDONKEY_TCP P2P_UDP=$GNUTELLA2_UDP,$EDONKEY_UDP and i allow from wan side these P2P_TCP/UDP traffic. But: my fw IS my p2p client. If it is not, you should consider port forwarding to your p2p client. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Shorewall-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
