problems using ipmasqadm

Hawke proudhawk@uswestmail.net
Thu, 24 Aug 2000 20:12:28 -0700


-----BEGIN PGP SIGNED MESSAGE-----

Well,
heres the story..
I have ipchains already acting as the IP_MASQ. no problem.
most of my apps work fine that way from the windows box.
HOWEVER, when I follow the instructions on the dialpad.com help
page for using dialpad through a linux IP_MASQ/firewall, then
icmp packets won't forward properly, dialpad fails to work and
my network communications from this box (192.168.0.2) are no
longer being sent to 24.21.77.91, period.

It takes a reboot of linux to erase the problem and reset to
what I had before (ipchains with IP_MASQ).

now, is there a way I can have the ports on 192.168.0.x
mapped such that they appear to be the same ports
going out on 24.21.77.91 (i.e. port 7175 on eth1 is transmitted
both directions <192.168.0.2.7175 <> 24.21.77.91:7175>).

IP_MASQ tends to translate the ports up toward the lower end of 61000
and this will not sue for dialpad.

any other solutions would be greatly appreciated.

One solution: get a routable IP for the second machine and set up
gated/routed and get a name server on the net to see it (such as
pcA (routabel ip)>eth1>eth1(24.21.77.91)>network)

HELP!

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQEVAwUBOaXkFm3D7Y3zM/L3AQGSogf/ZzmUf0YrDqfKZOlCmmhSv9HEFoqI3Kq2
22oBu+Ufd6RFk3DiU9pFy7bI6daG+CAhtRQJE0OLd0RHKZSwS4ea0uocfXqs2mbe
AMY9rL960o2ALXbxWMpIv/VobOubB+tm2IpsYLptybJ28OeNTTw+sgi1rAFGTX3y
grZ3rwydEl+8bXgpy2B2i7WyJN+zBL1m/HamiJGrSk2QHUTJ9lmyFyMNTCjCt+0v
CiWaCVfmsxCopW6YhmoJ4deLqPQHfonlZ3ZvATzNcIx0XCYwyRcMvWzShO+t8J6l
hx6P3YdCzu/Erxire6fwP9Ntu0RpIdlKJilVNSJwqW3iFomSBIIPcw==
=WRMo
-----END PGP SIGNATURE-----