From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Walton Subject: Linux Server and Echolink on Windoze98 client! Date: Mon, 30 Dec 2002 14:31:37 -0800 Sender: linux-hams-owner@vger.kernel.org Message-ID: <3E10C949.9010704@kj6eo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LINUX HAMS MAILING LIST Edson - Thank you for replying to my message on the linux-hams mailing list regarding the problems I am having with getting "Echolink" working on my Windoze98 client on my LAN. I read the articles that you directed me to and added the following commands to my system: FIREWALL FILE (/etc/sysconfig/ipchains): 1) ipchains -A input -s 0/0 -d 0/0 5200 -p tcp -y -j ACCEPT 2) ipchains -A input -p udp -s 0/0 -d 0/0 5198:5199 -j ACCEPT Command #1 above should punch any port 5200 tcp packets through the firewall. Command #2 above should punch any port 5198 and 5199 udp packets through the firewall. Now the udp packets need to be redirected from my internet-ip to the Windoze98 box over on my local LAN: 3) ipmasqadm portfw -f ipmasqadm portfw -a -P udp -L eth0 5198:5199 -R 192.168.1.10 5198:5199 -p 100 Do the above commands work ? No .... it appears that I have overlooked someting. The message that I see when I am monitoring eth0 is: "kj6eo.com udp port 5198 unreachable" It appears that this message is being generated by my server, and being sent to the originator that is trying to connect to the kj6eo.com port 5198. My ADSL modem router does not have the firewall enabled since my entire LAN is behind my Linux firewall. My ISP does source filter but that problem should only pertain to my TNOS system and my 44 packets. Since I can see the requests coming in at ETH0 I can assume that they are "in fact" passing through the router. Echolink uses tcp port 5200 and udp ports 5198 and 5199. Any additional suggestions that you might have would be appreciated! Regards, Bill KJ6EO