From: Bill Walton <kj6eo@kj6eo.com>
To: LINUX HAMS MAILING LIST <linux-hams@vger.kernel.org>
Subject: Regarding RedHat v7.2 and Echolink!
Date: Sun, 29 Dec 2002 20:42:59 -0800 [thread overview]
Message-ID: <3E0FCED3.2000506@kj6eo.com> (raw)
Gentlemen -
I have a question that I feel might pertain to this list. I am running
my own domain
(kj6eo.com) and my RedHat v7.2 server also serves up an internet
connection to
all the machines on my LAN. "ETH0" is connected directly to my ADSL router
and "ETH1" is connected to my HUB. "ETH1" carries the IP address of 192.168
.1.1 and "IP-forwarding" is enabled:
echo "1" > /proc/sys/net/ipv4/ip_forward
and ip masquerading is set for "ETH1":
ipchains -A forward -s 192.168.1.0/24 -d 0/0 -j MASQ
I am also running the RedHat v7.2 firewall which consists of a dozen or so
ipchains commands located at /etc/sysconfig/ipchains.
MY QUESTION:
I have installed "Echolink" software on my Windoze 98 box on the LAN. My
DHCP server serves up a static IP of 192.168.1.10 to the Windoze box.
Echolink uses udp ports 5198 and 5199 and tcp port 5200. So, I opened up
tcp port 5200 via the "ipchains file"
ipchains -A input -s 0/0 -d 0/0 5200 -p tcp -y -j ACCEPT
The firewall is not configured to do anything to udp ports 5198 or 5199.
Via the
tcpdump command watching everything on eth0 I can see that the return
packets
from the echolink server are getting a "udp port 5198 unreachable error".
Besides accepting tcp 5200 do I have to also masquerade it and or
forward it over
to eth1? Also do the udp ports 5198 and 5199 have to be forwarded or
masqueraded?
Any suggestions that you could offer would be greatly appreciated. I
can make
my firewall "ipchains" file available to you if necessary!
Regards,
Bill KJ6EO
next reply other threads:[~2002-12-30 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 4:42 Bill Walton [this message]
2002-12-30 4:53 ` Regarding RedHat v7.2 and Echolink! Edson Pereira
2002-12-30 22:24 ` terry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E0FCED3.2000506@kj6eo.com \
--to=kj6eo@kj6eo.com \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox