[Cialug] Network Layout

Korver, Aaron cialug@cialug.org
Tue, 4 Jan 2005 11:32:18 -0600


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4F283.56DF0330
Content-Type: text/plain;
	charset="iso-8859-1"

Or the only....

But in this case
http://www.gnome.org/projects/dia/

> -----Original Message-----
> From: Dave J. Hala Jr. [mailto:dave@58ghz.net]
> Sent: Tuesday, January 04, 2005 11:33 AM
> To: Cialug
> Subject: Re: [Cialug] Network Layout
> 
> 
> 
> Its ok to use microsuck tools, when they are the best choice for the
> job.
> 
> <ducks>
> 
> 
> On Tue, 2005-01-04 at 11:14, Claus wrote:
> > On 1/4/2005 12:26 AM, Don Cady wrote:
> > >>Network Layout (proposal):
> > >>==========================
> > >>Best is to look at a picture of it at:
> > >> http://www.public.iastate.edu/~cniesen/future-network.jpg
> > > 
> > > Neat picture, howdya make it?!
> > 
> > I'd rather not tell. :) (MS Visio, because it was available.)
> > 
> > The question wether the WLAN access point shoud run its own 
> DHCP server 
> > seems to be a mute point as the Linksys WRT54GS doesn't has 
> a bridging 
> > unless I get the Sveasoft firmware for $20 but that seems 
> to be silly if 
> > I'm just going to make it a dumb bridge.  So I'll end up 
> with NAT and 
> > DHCP and pray that double NATing doesn't give me to much problems.
> > 
> >    Claus
> > 
> > PS: All references of WAN im my original post should have been WLAN.
> > _______________________________________________
> > Cialug mailing list
> > Cialug@cialug.org
> > http://cialug.org/mailman/listinfo/cialug
> -- 
> 
> Open Source Information Systems (OSIS)
> Dave J. Hala Jr. <dave@osis.us>
> 641.485.1606
> 
> _______________________________________________
> Cialug mailing list
> Cialug@cialug.org
> http://cialug.org/mailman/listinfo/cialug
> 

------_=_NextPart_001_01C4F283.56DF0330
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Cialug] Network Layout</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Or the only....</FONT>
</P>

<P><FONT SIZE=3D2>But in this case</FONT>
<BR><FONT SIZE=3D2><A HREF=3D"http://www.gnome.org/projects/dia/" =
TARGET=3D"_blank">http://www.gnome.org/projects/dia/</A></FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Dave J. Hala Jr. [<A =
HREF=3D"mailto:dave@58ghz.net">mailto:dave@58ghz.net</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, January 04, 2005 11:33 AM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Cialug</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Cialug] Network Layout</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Its ok to use microsuck tools, when they are =
the best choice for the</FONT>
<BR><FONT SIZE=3D2>&gt; job.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &lt;ducks&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On Tue, 2005-01-04 at 11:14, Claus =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; On 1/4/2005 12:26 AM, Don Cady =
wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&gt;Network Layout (proposal):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
&gt;&gt;=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&gt;Best is to look at a picture of it =
at:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&gt; <A =
HREF=3D"http://www.public.iastate.edu/~cniesen/future-network.jpg" =
TARGET=3D"_blank">http://www.public.iastate.edu/~cniesen/future-network.=
jpg</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; Neat picture, howdya make it?!</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'd rather not tell. :) (MS Visio, because =
it was available.)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The question wether the WLAN access point =
shoud run its own </FONT>
<BR><FONT SIZE=3D2>&gt; DHCP server </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; seems to be a mute point as the Linksys =
WRT54GS doesn't has </FONT>
<BR><FONT SIZE=3D2>&gt; a bridging </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; unless I get the Sveasoft firmware for $20 =
but that seems </FONT>
<BR><FONT SIZE=3D2>&gt; to be silly if </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'm just going to make it a dumb =
bridge.&nbsp; So I'll end up </FONT>
<BR><FONT SIZE=3D2>&gt; with NAT and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; DHCP and pray that double NATing doesn't =
give me to much problems.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; Claus</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; PS: All references of WAN im my original =
post should have been WLAN.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cialug mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cialug@cialug.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://cialug.org/mailman/listinfo/cialug" =
TARGET=3D"_blank">http://cialug.org/mailman/listinfo/cialug</A></FONT>
<BR><FONT SIZE=3D2>&gt; -- </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Open Source Information Systems (OSIS)</FONT>
<BR><FONT SIZE=3D2>&gt; Dave J. Hala Jr. &lt;dave@osis.us&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; 641.485.1606</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Cialug mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; Cialug@cialug.org</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://cialug.org/mailman/listinfo/cialug" =
TARGET=3D"_blank">http://cialug.org/mailman/listinfo/cialug</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C4F283.56DF0330--