RE: tunneling through public IP destroys my network

Hi,

> I'm new to Zebedee, and tunneling for that matter, so while I
> have a problem, I'm not real sure which question to ask.
>
> I set up Zebedee on a separate server, static IP, and then I set
> up a client machine.  On the LAN side of my router, that is when
> the IP address in the client is pointing to the zebedee server I
> am able to connect to my firebird database do my business and
> disconnect at will.  Seems to work good.
>
> However, when I take the client outside the network and try to
> connect to the public address, I get a brief connection to the
> database (just the login screen) (though it seems to take to long
> to make the connection) and then I can't continue any further.
> But here is the kicker.  After I make that connection, it throws
> my whole network on the LAN side into disarray.  None of the
> clients can connect to the Firebird database.

I've never seen anything like this with Zebedee. It does sound more like a
router configuration problem. There isn't some kind of looping in the config
is there? Having said that, there are some problems with the Zebedee config
files, more below ...

> The database server and the Zebedee have a static IP address, but
> all the other clients are getting a dynamic IP address from the router.
>
> The router is a Netopia 3346ent.  What we did on it was set up a
> server list that said any traffic on this public IP address on
> nnnnn port is to be sent to the private IP address of the Zebedee server.
>
> From our ISP, we have 5 static addresses, the first useable is
> a.b.c.194 up to a.b.c.198.  I used the a.b.c.194 as the ip the
> client is trying to tunnel to.  this is the main address, would
> that cause it to mess up my internal network.
>
> I dont know, maybe this should be a netopia question, but I have
> to start somewhere.
>
> here is the client configuration file
>
> verbosity 1	# Basic messages only
>
> detached true	# Detach from terminal
> server false	# It's a client
> compression zlib:9	# Allow maximum zlib compression
> include c:\zebedee\allam.key
>
> #tunnel 3051:a.b.c.197:3050	#public ip  was 194
> tunnel 3051:192.168.1.83:3050  #private ip

It's probably best here to replace that tunnel spec with this:

serverhost a.b.c.194	# public IP address
tunnel 3051:192.168.1.83:3050		# private IP

As you only have a single permitted target in your server config then this
would be OK too:

tunnel 3051:192.188.1.83:3050

Now for the server config ...

> here is the server config file
>
> #
> #  Config file to use on a Server running Firebird & ZeBeDee
> #
>
> verbosity 2	# Slightly more than basic messages
> detached true	# free from console
> server true	# Yes, it's a server!
> ipmode tcp	# Operate only tcp
> logfile         c:\zebedee\zebedee.log
>
> compression zlib:9	# Allow maximum zlib compression
> keylength 256		# Allow keys up to 256 bits
> keylifetime 36000	# Shared keys last 10 hours
> maxbufsize 16383	# Allow maximum possible buffer size
> keygenlevel 2		# Generate maximum strength private keys
> checkidfile 		c:\zebedee\allam.id
>
> redirect 3050:192.168.c.d:3050  #Firebird port
> targethost 192.168.c.d # Set up firebird server as the target

It's generally better not to use the obsolete redirect and targethost
keywords (and the syntax you are using isn't really right for the redirect
spec). Instead I'd do this:

tunnel 192.168.1.83:3050

> I would appreciate any and all help on this

Sorry it has taken so long.

	Regards,
		Neil




-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl