timbuktu & SuSEfirewall2
Hello, I have a SuSEfirewall2 running for a small subnet with masquerading. Everything is fine, but now somebody in intranet would like to access a Timbuktu-based server (it's pc-anywhere like) outside, and it doesn't work... I guess it would probably need another ip_masq module ? Or what do you think? Here are the infos about the ports: Timbuktu uses a well-defined UDP port, 407, for connection handshaking and then switches to other TCP ports for each kind of service: Service TCP Port Control 1417 Observe 1418 Send Files 1419 Exchange Files 1420 Notify Dynamic TCP/IP ports above 1023 Chat Dynamic TCP/IP ports above 1023 Intercom Dynamic TCP/IP ports above 1023 Thx in advance for any hint! Olivier -- _________________________________________________________________ Olivier Mueller - om@8304.ch - PGPkeyID: 0E84D2EA - Switzerland qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
Hi, On 30 Jan 2002 at 1:41, Olivier M. wrote:
I have a SuSEfirewall2 running for a small subnet with masquerading. Everything is fine, but now somebody in intranet would like to access a Timbuktu-based server (it's pc-anywhere like) outside, and it doesn't work... I guess it would probably need another ip_masq module ? Or what do you think?
IIRC timbuktu is a very fragile software to connect Macs to Windows. I can only recommend to update MacOS! The TCP/IP Stacks in older versions are kind of "strange". I expect it to be a pain to route the traffic through a Linux router. mike
On Wed, Jan 30, 2002 at 02:06:37AM +0100, Thomas Michael Wanka wrote:
On 30 Jan 2002 at 1:41, Olivier M. wrote:
I have a SuSEfirewall2 running for a small subnet with masquerading. Everything is fine, but now somebody in intranet would like to access a Timbuktu-based server (it's pc-anywhere like) outside, and it doesn't work... I guess it would probably need another ip_masq module ? Or what do you think?
IIRC timbuktu is a very fragile software to connect Macs to Windows. I can only recommend to update MacOS! The TCP/IP Stacks in older versions are kind of
thx... but it's running under w2k (not my server)
"strange". I expect it to be a pain to route the traffic through a Linux router.
well, but it is possible? I don't care if the traffic will be high, the linux router has nothing else to do... :) Olivier -- _________________________________________________________________ Olivier Mueller - om@8304.ch - PGPkeyID: 0E84D2EA - Switzerland qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
Hi, On 30 Jan 2002 at 2:07, Olivier M. wrote:
well, but it is possible? I don't care if the traffic will be high, the linux router has nothing else to do... :)
according to the information on "http://www.netopia.com/support/howtodocs/router.html" you should need to route ports 407 and 1417 to 1420. HTH mike
On Wed, Jan 30, 2002 at 02:24:00AM +0100, Thomas Michael Wanka wrote:
On 30 Jan 2002 at 2:07, Olivier M. wrote:
well, but it is possible? I don't care if the traffic will be high, the linux router has nothing else to do... :)
according to the information on "http://www.netopia.com/support/howtodocs/router.html" you should need to route ports 407 and 1417 to 1420.
thx, I also know the ports... :) Just don't know how to use this information: how could I set that in the rc.config.d/firewall.rc.config ? Shouldn't the suse firewall let these packets go out and in without problem? The timbuktu server is outside the intranet, somewhere on the internet with a standard IP. Does it mean I would have the same problem with VNC or PC-Anywhere for example? Olivier -- _________________________________________________________________ Olivier Mueller - om@8304.ch - PGPkeyID: 0E84D2EA - Switzerland qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
participants (2)
-
Olivier M. -
Thomas Michael Wanka