DMZ systems having internal IP, ok or not? Post: 302501982

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Forwarding internal internet packets to internal webserver using iptables

Hi, I need to redirect internal internet requests to a auth client site siting on the gateway. Currently users that are authenticated to access the internet have there mac address listed in the FORWARD chain. All other users need to be redirected to a internal site for authentication. Can...

2. Linux

routing rules for dmz in debian router.

Hi to all. There are eth0(wan) eth1(lan) and eth3(dmz) in my debian router. In dmz is planing dns, ad, dhcp, smtp/pop/imap, https(web-based imap client). I don't configured rules on "iptables" and "route" loads for right relation lan clients with dmz services. Please explain me example...

3. UNIX for Advanced & Expert Users

How do you manage your DMZ server accounts?

I'd just like to know what you use for user account management on your DMZ servers? Do you use the same authentication realm as internally? Do you use a different authentication realm, perhaps only for the DMZ? Do you use local accounts?

4. Solaris

Setting up a DMZ webserver using Zones

I've been looking at various articles about Zones/Containers, from SUN's website, and through numerous Google searches, and although there's a lot of info out there, I've not got a definitive answer for what I'd like to do.....so here we go..... I'm installing a webserver, which is sitting on a...

5. Shell Programming and Scripting

SFTP and DMZ boxes

Hi I would like write a script that will do sftp frm a box that resides inside the FW to a box that resides in DMZ.Any ideas guys.I tried generating rsa keys for a particular user, however just want to know is there any other solution or not. Your help is much appreciated. Thanks CK

6. What is on Your Mind?

From Systems Admin to Systems Eng.

I have been wondering how do Systems Administrators do the jump into Systems Engineering? Is it only a matter of time and experience or could I actually help myself get there? Opinions? Books I could read? Thanks a lot for your help!

7. Shell Programming and Scripting

Create new users in DMZ box using script

I remote to many DMZ boxes every day to run batch file that allows me to create users. I create users in 17 DMZ boxes every day which takes a lot of my time. Is there any script that would do this job from my local computer? Thank you for your help!

8. UNIX and Linux Applications

One DMZ server reverse proxy for 2 websites

Hi All, Hope this is the correct thread to ask this, if not, can an admin please move it to the correct thread. Got a wee problem I hope someone can point me in the right direction. I have Network A with two servers hosting separate webpages (I will call these WP1 & WP2). A DMZ server...

9. UNIX for Beginners Questions & Answers

Sendmail - issue within DMZ for some servers but not all

Hi All, I have a strange issue and I am not sure where the problem lies. I have about six Ubuntu servers on our DMZ two of which were built on 18.04 from scratch the others were upgraded to 18.04 from 16.04. The servers built from scratch can send emails from the server via sendmail fine, so...

LEARN ABOUT DEBIAN

sysdata

sysdata(1)						      General Commands Manual							sysdata(1)

NAME

       sysdata - find basic hardware system data

SYNOPSIS

       sysdata

DESCRIPTION

       After  the  atlc  package is built, a small benchmark is run as part of the testing procedure. This benchmark tries to get some information
       about the hardware. The program sysdata displays the same hardware information that the benchmark will display, but runs in a fraction of a
       second,	whereas  the benchmark can take from 19 s (quad 1.4 GHz Itainium 2 machine) to 14,906 s (for a very old 33.3 MHz Cray Y-MP). There
       are no options or arguments to sysdata

       The information gathered on hardware and software both developed by the same company (i.e. Solaris on Suns, AIX on  IBM	RS/6000,  IRIX	on
       SGI,  ...  etc etc) is generally more informative than the free systems (Linux, NetBSD, OpenBSD, FreeBSD) where it is usually impossible to
       get much hardware information.

EXAMPLES

       Here are some examples of the use of sysdata on a number of systems. The large number of examples is for my own use as much as anything, so
       I can keep track of the development of sysdata and see easily where it needs extending. Examples are presented for:

       1) Sun Ultra 80 running Solaris 9
       2) HP C3000 running HP-UX 11
       3) SGI Octane running IRIX 6.5.16
       4) IBM RS/6000 running AIX 5.2
       5) Dec Alpha 600a Personal Workstation running Tru64 5.1B
       6) Cray Y-MP running UNICOS 9
       7) Sun SPARCstation 20 running NetBSD 1.6
       8) Sun SPARCstation 20 running OpenBSD 3.2
       9) Sun SPARCstation 20 running Debian Linux
       10) Sun SPARCstation 20 running Solaris 2.5
       11) Generic PC with 350 MHz Pentium II running Redhat Linux 7.2

       Here's the output from sysdata on these 11 systems.

       e.g. 1 (Sun Ultra 80 running Solaris 9)
       Hardware provider:    Sun_Microsystems
       Hardware platform:    SUNW,Ultra-80
       Machine: 	     sun4u
       Sysname: 	     SunOS
       Release: 	     5.9
       Version: 	     Generic_112233-06
       Nodename:	     sparrow
       #CPUs supported:      4
       #CPUs online:	     4
       CPU type:	     sparcv9
       FPU type:	     sparcv9
       Speed:		     450 MHz
       RAM:		     4096 Mb
       L1 data cache	     unknown kB
       L1 instruction cache: unknown kB
       L2 cache:	     unknown kB

       Here's an example on a HP 9000 series Visualize C3000 workstation, fitted with one 400 MHz PA-RISC 8500 CPU and 1.5 Gb of RAM

       e.g. 2 (HP 9000 series Visualize C3000)
       Hardware provider:    HP
       Hardware platform:    unknown
       Machine: 	     9000/785
       Sysname: 	     HP-UX
       Release: 	     B.11.00
       Version: 	     A
       Nodename:	     robin
       #CPUs supported:      1
       #CPUs online:	     1
       CPU type:	     532
       FPU type:	     1048577
       Speed:		     400.0 MHz
       RAM:		     1536 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

       Here's another example this time on an SGI Octane R10000 with 2 x 195 MHz processors. Note the CPU and FPU types reported at not the R10000
       and R10010 that are reported by SGI's hinv. sysdata is not meant to replace other more sophisticated ways of obtaining  system  information
       (such as hinv on IRIX), but its data is useful to record for benchmarking purposes.

       e.g. 3 (SGI Octane R1000)
       Hardware provider:    SGI
       Hardware platform:    unknown
       Machine: 	     IP30
       Sysname: 	     IRIX64
       Release: 	     6.5
       Version: 	     04101931
       Nodename:	     owl
       #CPUs supported:      unknown
       #CPUs online:	     2
       CPU type:	     2343
       FPU type:	     2304
       Speed:		     195 MHz
       RAM:		     1024 Mb
       L1 data cache	     32 kB
       L1 instruction cache: 32 kB
       L2 cache:	     1024 kB

       Here's an example using an IBM RS/6000 F50 with 4 x 332 MHz CPUs and 1 GB of RAM.

       e.g. 4 (IBM RS/6000 F50)
       Hardware provider:    IBM
       Hardware platform:    unknown
       Machine: 	     000245984C00
       Sysname: 	     AIX
       Release: 	     2
       Version: 	     5
       Nodename:	     starling
       #CPUs supported:      unknown
       #CPUs online:	     4
       CPU type:	     unknown
       FPU type:	     unknown
       Speed:		     unknown MHz
       RAM:		     1024 Mb
       L1 data cache	     unknown kB
       L1 instruction cache: unknown kB
       L2 cache:	     unknown kB

       And here's an example from a single 599 MHz processor Dec Alpha 600a Personal Workstation running Tru64 5.1B

       e.g. 5 (Dec Alpha 600a Personal Workstation)
       Hardware provider:    unknown
       Hardware platform:    Digital_Personal_WorkStation_600au
       Machine: 	     alpha
       Sysname: 	     OSF1
       Release: 	     V5.1
       Version: 	     2650
       Nodename:	     dobermann.localhost.ntlworld.co
       #CPUs supported:      1
       #CPUs online:	     1
       CPU type:	     EV5.6_(21164A)
       FPU type:	     unknown
       Speed:		     599 MHz
       RAM:		     1024 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

       Here's some data collected on a very old Cray Y-MP, which was introduced in 1991.

       e.g 6 (Cray Y-MP running UNICOS)

       Hardware provider:    Cray
       Hardware platform:    Y-MP
       Machine: 	     CRAY_Y-MP
       Sysname: 	     sn5176
       Release: 	     9.0.2.2
       Version: 	     sin.0
       Nodename:	     sn5176
       #CPUs supported:      unknown
       #CPUs online:	     4
       CPU type:	     unknown
       FPU type:	     unknown
       Speed:		     33.3 MHz
       RAM:		     unknown Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

       That  is all the examples of commercial hardware running the operating systems made by the manufacturers of the hardware. The following are
       free UNIX versions. In these cases the data gathered is never as complete. In particular the amoumt of memory reported if often	less  than
       the  real  amount due to memory taken by the operating system (kernel etc). The number of processors the system can support is never avail-
       able.

       Here's the first such non-commercial UNIX from a single processor Sun SPARCstation 20 running NetBSD 1.6.

       e.g. 7 (Sun SPARCstation 20 running NetBSD 1.6)
       Hardware provider:    unknown
       Hardware platform:    unknown
       Machine: 	     sparc
       Sysname: 	     NetBSD
       Release: 	     1.6
       Version: 	     NetBSD_1.6_(GENERIC)_#0:_Mon_Sep__9_08:2sparc
       Nodename:	     blackbird
       #CPUs supported:      unknown
       #CPUs online:	     1
       CPU type:	     rg:/autobuild/sparc/OBJ/autobuild/src/sys/arch/sparc/compile/GENERIC
       FPU type:	     unknown
       Speed:		     unknown MHz
       RAM:		     255 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

       Here's data from a Sun SPARCstation 20 running OpenBSD 3.2. The machine has 320 Mb of RAM, not 318 Mb as indicated. The number  of  proces-
       sors  the  system  supports  is reported as unknown, but should the system have been running Solaris 9, as in the example 1 (sparrow), then
       this information would have been determined, but it is not available under OpenBSD - or Solaris 2.5 for that matter.

       e.g. 8 (Sun SPARCstation 20 running OpenBSD 3.2)
       Hardware provider:    unknown
       Hardware platform:    unknown
       Machine: 	     sparc
       Sysname: 	     OpenBSD
       Release: 	     3.2
       Version: 	     GENERIC#36
       Nodename:	     crow.crow.localdomain
       #CPUs supported:      unknown
       #CPUs online:	     1
       CPU type:	     unknown
       FPU type:	     unknown
       Speed:		     unknown MHz
       RAM:		     319 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb
       The next machine is a Sun SPARCstation 20 running Debian Linux. The version of Debian is unknown, but clearly sysdata is unable	to  deter-
       mine this.

       e.g. 9 (Sun SPARCstation 20 running Debian Linux)

       Hardware provider:    unknown
       Hardware platform:    unknown
       Machine: 	     sparc
       Sysname: 	     Linux
       Release: 	     2.2.20
       Version: 	     #1_Fri_Nov_16_15:48:02_EST_2001
       Nodename:	     dove
       #CPUs supported:      unknown
       #CPUs online:	     1
       CPU type:	     unknown
       FPU type:	     unknown
       Speed:		     unknown MHz
       RAM:		     281 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

       Here's  data from a Sun SPARCstation 20 running Solaris 2.5 (SunOS 5.5). The machine probably does have 352 Mb of RAM as reported. The num-
       ber of processors the system supports is reported as unknown, but should the system have been running Solaris 9, as in the example 1 (spar-
       row), then this information would have been determined, but it is not available under Solaris 2.5.

       e.g. 10 (Sun SPARCstation 20 Solaris 2.5)
       Hardware provider:    Sun_Microsystems
       Hardware platform:    SUNW,SPARCstation-20
       Machine: 	     sun4m
       Sysname: 	     SunOS
       Release: 	     5.5
       Version: 	     Generic
       Nodename:	     bluetit
       #CPUs supported:      unknown
       #CPUs online:	     2
       CPU type:	     sparc
       FPU type:	     sparc
       Speed:		     125 MHz
       RAM:		     352 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

       Here's a standard PC, fitted with one processor

       e.g. 11 (350 MHz Pentium II PC running Redhat Linux)
       Hardware provider:    unknown
       Hardware platform:    unknown
       Machine: 	     i686
       Sysname: 	     Linux
       Release: 	     2.4.18-5
       Version: 	     #1_Mon_Jun_10_15:31:48_EDT_2002
       Nodename:	     tiger
       #CPUs supported:      unknown
       #CPUs online:	     1
       CPU type:	     unknown
       FPU type:	     unknown
       Speed:		     unknown MHz
       RAM:		     123 Mb
       L1 data cache	     unknown kb
       L1 instruction cache: unknown kb
       L2 cache:	     unknown kb

FILES

       sysdata does not read/write any files.

SEE ALSO

       atlc(1)
       create_bmp_for_circ_in_circ(1)
       create_bmp_for_circ_in_rect(1)
       create_bmp_for_microstrip_coupler(1)
       create_bmp_for_rect_cen_in_rect(1)
       create_bmp_for_rect_cen_in_rect_coupler(1)
       create_bmp_for_rect_in_circ(1)
       create_bmp_for_rect_in_rect(1)
       create_bmp_for_stripline_coupler(1)
       create_bmp_for_symmetrical_stripline(1)
       design_coupler(1)
       find_optimal_dimensions_for_microstrip_coupler(1)
       hinv - SGI's IRIX only.
       readbin(1)

       http://atlc.sourceforge.net		  - Home page
       http://sourceforge.net/projects/atlc	  - Download area
       atlc-X.Y.Z/docs/html-docs/index.html	  - HTML docs
       atlc-X.Y.Z/docs/qex-december-1996/atlc.pdf - theory paper
       atlc-X.Y.Z/examples			  - examples

Dr. David Kirkby					     atlc-4.5.0 28th Sep 2003							sysdata(1)