Most of our customers require that we assume an address within the private
range they have been using and would not let us dictate them a renumbering
orgy. And of course, you will find that at least two of them use the same
address space.
Also: If two of them want to run an SMTP server, how would you translate
from public address space into private? At your border router using multiple
public IP addresses - but then, why not give them a public IP address on the
wireless interface and have the CPE do NAT on the private address space? No
more problems ... in fact, all your customers could use 192.168.1.0/24 ...
regards,
--
true global communications GmbH
Thomas Giger
In der Au 27, 61440 Oberursel, Germany
fon +49.6171.6381-0, fax +49.6171.6381-19
www.tgnet.de || www.megaspeed-internet.de
> -----Original Message-----
> From: wesley allison [mailto:scgn@pipeline.com]
> Sent: Friday, August 22, 2003 9:31 PM
> To: Karlnet Mailing List
> Subject: [Karlnet] Base station question?????
>
>
> I am setting up a base station to service an area and I was
> wondering if I
> could get some feedback. I am going to setup the base as a
> bridge and setup
> the CPE to route. I am doing this so each CPE has a private IP on the
> wireless side "192.168.1.x" and a different private on the LAN side
> "172.16.x.x" dispensing DHCP for the client. My theory is, I
> am able to
> manage my network and CPE equipment with my private IP and I
> give the client
> there own private IP range so they do not step on anybody's
> toes and they
> are free to network their house or what ever. I was wondering
> if this sounds
> feasible or is their a better way.
>
> wes
>
> ----- Original Message -----
> From: "Thomas Giger TGC" <thomas.giger@tgc.de>
> To: "'Norm Young'" <npyoung@applegatebroadband.net>; "'Karlnet Mailing
> List'" <karlnet@WISPNotes.com>
> Sent: Friday, August 22, 2003 12:41 PM
> Subject: RE: [Karlnet] Ping time differences
>
>
> > > I've been noticing some rather serious jitter between our
> > > client stations and our NOC or AP. When I ping from the
> > > client radio out towards the NOC or AP, I see anything
> > > between 15mS-300mS.
> >
> > That's what I would expect from a polled system. Note that
> the polling
> > frequency has no correlation to your ping interval; the
> activity of other
> > systems influence how frequently this (idle) client is
> being permitted to
> > transmit. So some echo requests wait longer than others
> until they allowed
> > on the air.
> >
> > > The ping time jitter has no correlation
> > > to system load, but responds well if I load the client that
> > > I'm testing from. (Start a download from the NOC towards
> > > the client, and the ping times drop down to 20-30mS )
> >
> > That is because the PINGs can now "ride on the ACK packets" of your
> > download.
> >
> > > Pinging back from the NOC to the client, I see stable 10mS or
> > > less ping times.
> >
> > That is maybe because the base anticipates that if a packet
> goes out to a
> > satellite, there is likely a paket to come back - so it
> will poll this
> > satellite in its next round.
> >
> > > Is it even a problem?
> >
> > 300 ms (your worst figure) seems to be too much unless the
> base has many
> > satellites and there is traffic to others. If the cell is
> idle and there
> are
> > not too many satellites being polled, it may be a sign of
> interference and
> > retransmission.
> >
> > The question really is whether this was less significant in earlier
> versions
> > and if yes, if it is a side-effect from other optimizations
> in the recent
> > releases. I seem to remember there was something on the KN
> website along
> > with the release that talked about increased responsiveness in paket
> > forwarding vs. RTT for lightly loaded satellites.
> >
> > regards,
> > --
> > true global communications GmbH
> > Thomas Giger
> > In der Au 27, 61440 Oberursel, Germany
> > fon +49.6171.6381-0, fax +49.6171.6381-19
> > www.tgnet.de || www.megaspeed-internet.de
> > _______________________________________________
> > Karlnet mailing list
> > Karlnet@WISPNotes.com
> > http://lists.wispnotes.com/mailman/listinfo/karlnet
>
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com
> http://lists.wispnotes.com/mailman/listinfo/karlnet
>
|