From: Jarek Poplawski <jarkap@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: Not understanding network setup!!
Date: Fri, 02 Jun 2006 14:20:11 +0000 [thread overview]
Message-ID: <4480491B.2040901@poczta.onet.pl> (raw)
In-Reply-To: <e5on24$rfk$1@sea.gmane.org>
Eliot, Wireless and Server Administrator, Great Lakes Internet wrote:
>> -----Original Message-----
>> From: Jarek Poplawski [mailto:jarkap@poczta.onet.pl]
>> Sent: Friday, June 02, 2006 9:57 AM
>> To: Eliot, Wireless and Server Administrator, Great Lakes Internet
>> Cc: lartc@mailman.ds9a.nl
>> Subject: Re: [LARTC] Re: Not understanding network setup!!
>>
...
>> Maybe we are thinking about something else but I don't think:
>> "If you were using a /30, then" ... ".5, and .9 would be the
>> first available addresses in their respective subnets" is all
>> correct.
>
> 10.0.0.0/30:
>
> 10.0.0.0 - NETWORK ADDRESS
> 10.0.0.1 - HOST
> 10.0.0.2 - HOST
> 10.0.0.3 - BROADCAST ADDRESS
>
> First available address is .1
>
> 10.0.0.4/30:
>
> 10.0.0.4 - NETWORK ADDRESS
> 10.0.0.5 - HOST
> 10.0.0.6 - HOST
> 10.0.0.7 - BROADCAST ADDRESS
>
> First available address is .5
>
> 10.0.0.8/30:
>
> 10.0.0.8 - NETWORK ADDRESS
> 10.0.0.9 - HOST
> 10.0.0.10 - HOST
> 10.0.0.11 - BROADCAST ADDRESS
>
> First available address is .9
>
> Thus:
>
> "The .1, .5, and .9 would be the first available addresses in their
> respective subnets."
>
> Is a true statement.
>
> How are you interpreting this?
OH! Now I understand! I'm sorry for bothering you and many thanks
for this clare explaining.
Jarek P.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-06-02 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 6:50 [LARTC] Re: Not understanding network setup!! Jarek Poplawski
2006-06-02 14:20 ` Jarek Poplawski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4480491B.2040901@poczta.onet.pl \
--to=jarkap@poczta.onet.pl \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.