Hello Joe,
Thanks for the reply. You are right but I have tried with 0/0_www also. It is not
working.
As you can see from my ipchains ruleset that I'm getting packet at 111.222.333.444
-
5 300 ACCEPT tcp -- 0xFF 0x00 eth0
0.0.0.0/0 111.222.333.444 * - 80
Currently I use Dachsteinv-v1.0.2-1680 as my firewall. It's seem verygood. But now I
want to telnet to it while I'm at DMZ's machine. I found that inetd.conf comment out
for telnetd and /usr/sbin/in.telnetd is missing. How could I set it up?
Thank you so much.
Chutima S.
--- Chutima S. [EMAIL PROTECTED] wrote:
Currently I use Dachsteinv-v1.0.2-1680 as my
firewall. It's seem verygood. But now I want to
telnet to it while I'm at DMZ's machine. I found
that inetd.conf comment out for telnetd and
/usr/sbin/in.telnetd is missing. How could I set it
up?
well you may want to block Ident (113) - though it should already be
blocked. I know some servers require an Ident daemon to be running (like
dalnet). But blocking 6000 - 8000 is a good start. You could also create a
list of hosts that you want to autodeny traffic from (just based on IRC
Also remember that the port something runs on is a matter of convention,
not requirement. If you really want to block things, do a default deny
outbound and then open up services and locations that are approved. At
my work there is no outbound access for any endusers; everything has to
go through
And here is the link on how to install ssh v2
http://www.leaf-project.org/devel/jnilo/openssh.html
--- Chutima S. [EMAIL PROTECTED] wrote:
Currently I use Dachsteinv-v1.0.2-1680 as my
firewall. It's seem verygood. But now I want to
telnet to it while I'm at DMZ's machine. I found
that
If you are running the floppy version, you may either need second floppy to
hold the new ssh package, or you can look for an older version of ssh,
Kong's ssh.lrp, which can fit into your existing floppy.
Anyway, if possible, I think you should go with the CD version of Dachstein.
You will have
Charles Steinkuehler wrote:
from the man page
configuration file (ssh.conf)
UsePrivilegedPort
Specifies whether to use a privileged port for outgoing connec
tions. The argument must be ``yes'' or ``no''. The default is
``no''.
^^
Jack Coates wrote:
Also remember that the port something runs on is a matter of convention,
not requirement. If you really want to block things, do a default deny
outbound and then open up services and locations that are approved. At
my work there is no outbound access for any endusers;
from the man page
configuration file (ssh.conf)
UsePrivilegedPort
Specifies whether to use a privileged port for outgoing connec
tions. The argument must be ``yes'' or ``no''. The default is
``no''.
^^
So if the default is no, Scott,
The problem a friend has is needing a firewall but does not want to change
current setup on his boxes except inserting a firewall between
cable modem a Netgear MR314 cable/DSL Wireless router.
There is a maxium of 8 computers in his network.
I have made Bering Beta-4 ping the internet by name
On Wednesday 06 March 2002 15:32, Jan Linders wrote:
Hi there.
Can someone please tell me if there is a limit on the length of
the record : default linux .(etc) in the syslinux.cfg file.
And if so, what I can do to solve this ?
I'm trying to load several packages which i added after
Jan Linders wrote:
Hi there.
Can someone please tell me if there is a limit on the length of
the record : default linux .(etc) in the syslinux.cfg file.
And if so, what I can do to solve this ?
I'm trying to load several packages which i added after LRP=.
All packages before
Hi,
Maybe I'm missing something here but don't you want to load the 3c90x
module?
Stephen
On Tue, 2002-03-05 at 10:56, Simon Bolduc wrote:
I'm not sure whether the 905c's are supported by this driver - I do know
that 905c's are quite different from 905b's - and did require different
On 6 Mar 2002, Stephen Lee wrote:
Hi,
Maybe I'm missing something here but don't you want to load the 3c90x
module?
That is one option. Newer (than what I don't know exactly) versions of
3c59x are supposed to support the 3C905C NIC, but I haven't used any of
them personally. 3c59x is
Nah - the 59x module supports the 90x series of cards - altho I have had
problems with it and 905c's previously...
S
From: Stephen Lee [EMAIL PROTECTED]
To: Leaf-user [EMAIL PROTECTED]
Subject: Re: [Leaf-user] Problem with 3c59x.o on Dachstein disk
Date: 06 Mar 2002 16:44:49 -0800
Hi,
Maybe
A quick look at the modules for dachstein, oxygen and lrp 2.9.8 don't
have any 3c90x module available. I remember finding one somewhere, but
found that the 3c59x works. Why does 3com have such a confusing
numbering system for their products anyways? 905; 509; 59x?.
Cheers and have a good
I was at my uncle's house this past weekend. He has an
Eigerstein LRP box for his adsl connection. On one
port of the hub he uses, he plugged in a Linksys
wireless access point. He is not using dhcp for his
lan. He assigned a static IP of 192.168.1.x to his
wireless client, just like the
Hello,
Making good progress on my Dachstein migration, but just had a hiccup
with forwarding. The uncommented line (well they all would) from below
gives me an error when starting the network: IP filters: portfw:
Invalid protocol specified.
The INTERN_SERVER section (not indexed) works ok,
On Wed, 6 Mar 2002, Matt Schalit wrote:
Jack Coates wrote:
Also remember that the port something runs on is a matter of convention,
not requirement. If you really want to block things, do a default deny
outbound and then open up services and locations that are approved. At
my work there
Yes it uncommented it. A 1 is there. And I have checked that it from outside my
firewall.
But not working.
Thanks.
Sudhir
guitarlynn wrote:
And yes I have checked it from outside of my network but still not
working. Thanks.
Sudhir,
Have you uncommented ip_masq_portfw in /etc/modules (or
21 matches
Mail list logo
