##### ### ## ### ######## ### ## ### ###TM ####### ####### ####### ######## ####### ####### ####### ### ### ### ### # ### ### ### ### # ### ## ## ## ## ## ### ## ## ## ## ## ### ### ### ## ### ### ### ### ## ### ## ####### ####### ## ######## ### ####### ## ####### ##### ### ## ######## ### ### ## ### ## ####### ##### Viking I Chipset Configuration File from: http://corz.org/public/docs/comms/router/ready-made/ "default+p2p" config file for Viking I chipset based broadband router, Like the BT Voyager 205. Upload this to your router via FTP, or use the web interface.. http://192.168.1.1/hag/emweb/bkupRestoreConfigNS.htm It will reboot immediately. It may even look like the upload failed. It didn't - your page/ftp session has hung - the unit is rebooting, just kill that. When the router comes back up, the new settings will be applied. The router is now stealthed, with all the tweaks found at the router page.. http://corz.org/network/routers/Voyager/bt.voyager.205_router.how-to.php There is a DHCP pool of addresses from 192.168.1.50 - 192.168.1.99 available for your guests, or whatever. No USB interface is available. Some p2p applications have been pre-configured as follows.. 49200 BitTorrent custom ports (I do not support connexions in the 6881-6999 range!) to Only one port required for Azzy (take your pick) or if you use a lesser client 49209 you can utilise the entire range 4662 eMule standard TCP port 4672 eMule standard UDP port 6257 WinMX standard UDP port 6699 WinMX standard TCP port 6346 standard Gnutella port (Limewire, Shareaza, etc) 41170 generic high port range to both TCP and UDP 41350 for use in Piolet, or whatever you need. Inbound connexion attempts on these ports will be accepted and forwarded to a computer at IP 192.168.1.3, ensure that the machine running the p2p app is at this IP! or else alter the cfg file to suit your needs. If you have any problems with this cfg file, please do let me know! ;o) (or © corz.org 2005