I would guess you did cjange yje syslinux.cfg yo look for files on
the DOC not the fd0u1680(floppy). I hope this helps.
Larry Platzek [EMAIL PROTECTED]
On Sun, 26 May 2002, John Mullan wrote:
> Date: Sun, 26 May 2002 21:28:20 -0400
> From: John Mullan <[EMAIL PROTECTED]>
> To: [EMAIL PROTECT
I'm still wondering how to tunnel my http traffic thought ssh to my
internal web server. I use Putty to connect to a RH box behind LEAF from
outside giving me a comand line interface. Is the tunneling done by
somehow directing traffic through PuTTY ?
Cam
(sorry if this got sent twice)
On Fr
Support Requests item #561116, was opened at 2002-05-27 08:43
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=213751&aid=561116&group_id=13751
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (
Support Requests item #561116, was opened at 2002-05-27 08:43
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=213751&aid=561116&group_id=13751
Category: None
Group: None
>Status: Closed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
>Assigned to: Mike Noyes (mh
Hi Brad:
I have tried configuring ntpclient and the package to from size 9979 to
1575. I did try this on another box with more ram with same kind of
results. I need to change the RCDLINKS change 20's to 25's and
TIME to myntpserver address. The rcdlinks need to change because
the ppp is not up bef
On Mon, 27 May 2002 10:05:54 PDT Larry Platzek wrote:
> Hi Brad:
> I have tried configuring ntpclient and the package to from size 9979 to
> 1575.
It looks like the ntpclnt defaults to a partial backup:
[brad@brad-nb ntpclnt]$ cat var/lib/lrpkg/ntpclnt.bktype
Part
which only backs up the
My Bering 2.4.18 firewall is installed on a 486 with HD booting.
I use SSH (PuTTY) to access the firewall from internally, and all works well. I
set up a rule in SHOREWALL to allow this:
ACCESS loc fw tcp 22
Now I want to use SSH to access from the internet. I enter:
ACCESS
Le Lundi 27 Mai 2002 19:35, [EMAIL PROTECTED] a écrit :
> My Bering 2.4.18 firewall is installed on a 486 with HD booting.
>
> I use SSH (PuTTY) to access the firewall from internally, and all works
> well. I set up a rule in SHOREWALL to allow this:
>
> ACCESS loc fw tcp 22
>
> N
My ISP sometimes has short network outages (2-3 minutes). After such an
outage, I have to manually restart networking to get my router back online.
Is there a simple and reliable way to test the status of a connection? a
script that can runs constantly, supervised by daemontools, and restarts
net
At 10:16 PM 5/27/02 +0200, Kiril wrote:
>My ISP sometimes has short network outages (2-3 minutes). After such an
>outage, I have to manually restart networking to get my router back online.
>
>Is there a simple and reliable way to test the status of a connection? a
>script that can runs constantly
I'm not sure I know how to tell you any more than I already have. Set up SSH
Tunneling -- it is a session property. I don't know if putty has it -- can
somebody else on the board please tell us if putty has port forwarding?
Otherwise, Cam, download the trial copy of secureCRT to work with.
Hey all,
I'm trying to make x509 certificates on a RH7.3 system using the
instructions in the Bering User's Guide.
Everything looks good till i enter...
"openssl pkcs12 -export -inkey clientKey.pem -in clientCert.pem -certfile
demoCA/cacert.pem -out clientCert.p12"
What i get back after enter
Quoting Michael and Cam:
cam> I'm still wondering how to tunnel my http traffic thought ssh to
cam> my internal web server. I use Putty to connect to a RH box behind
cam> LEAF from outside giving me a comand line interface. Is the
cam> tunneling done by somehow directing traffic through PuTTY
I think that may be the ticket. I have wondered in the past what those
other utlities on PuTTY download page were for. Thanks for the info. I
will give it a try tomorrow.
Cam
On Mon, 27 May 2002, Brad Fritz wrote:
>
> Quoting Michael and Cam:
>
> cam> I'm still wondering how to tunnel my ht
14 matches
Mail list logo
