On Tuesday 02 March 2004 01:18 pm, Karl Schmidt wrote:
I've just moved a fire wall from Dachstein to Bering and have everything
working except one thing.
Before there was a set up where if I would:
ssh -P333 firewall.domain.com
The firewall would pass that on to a private server using port
Try:
DNATnet loc:192.168.1.200:22 tcp 333
On Tue, Mar 02, 2004 at 03:18:38PM -0600, Karl Schmidt wrote:
I've just moved a fire wall from Dachstein to Bering and have everything
working except one thing.
Before there was a set up where if I would:
ssh -P333
Karl
At 15:18 02.03.2004 -0600, Karl Schmidt wrote:
I've just moved a fire wall from Dachstein to Bering and have everything
working except one thing.
Before there was a set up where if I would:
ssh -P333 firewall.domain.com
The firewall would pass that on to a private server using port 22.
17, 2003 3:54 PM
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject:Re: [leaf-user] Moving from Dachstein to Bering
Eddie Wilson wrote:
Thanks Charles. I tried changing the interfaces statement and the result
was as expected. I am not sure how I would assign the extra
Eddie Wilson wrote:
Hi Charles,
I do have the /29 being routed as you expected. I have had them assigned to
the same interface as the p-t-p /30 address for the last 2 years and
running fine.
If there is a better (correct) way of doing this I would be greatfull for
any advice.
Ipsec included
Charles Steinkuehler wrote:
Eddie Wilson wrote:
Hi Charles,
I do have the /29 being routed as you expected. I have had them assigned to
the same interface as the p-t-p /30 address for the last 2 years and
running fine.
If there is a better (correct) way of doing this I would be greatfull for
To: [EMAIL PROTECTED]
Cc: '[EMAIL PROTECTED]'
Subject:Re: [leaf-user] Moving from Dachstein to Bering
Eddie Wilson wrote:
Hi Charles,
I do have the /29 being routed as you expected. I have had them assigned to
the same interface as the p-t-p /30 address for the last 2 years
To: '[EMAIL PROTECTED]'
Subject:[leaf-user] Moving from Dachstein to Bering
While moving from DachsteinCD to Bering rc3 I've run into ipsec0 being
assigned to the last of my public address range instead of the first. Does
anyone know of a way to change this back?
Maybe use an older version
Eddie Wilson wrote:
Thanks Charles. I tried changing the interfaces statement and the result
was as expected. I am not sure how I would assign the extra addresses
differently. I am assigning the p-t-p address in my wanpipe configuration
and adding 2 of the extra 6 I have through Shorewall-NAT,
While moving from DachsteinCD to Bering rc3 I've run into ipsec0 being
assigned to the last of my public address range instead of the first. Does
anyone know of a way to change this back?
Thanks,
Eddie Wilson
Stature Electric, Inc.
---
10 matches
Mail list logo
