All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkap@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Not understanding network setup!!
Date: Fri, 02 Jun 2006 06:50:16 +0000	[thread overview]
Message-ID: <e5on24$rfk$1@sea.gmane.org> (raw)

Eliot, Wireless and Server Administrator, Great Lakes Internet wrote:
> -----Original Message-----
> From: lartc-bounces@mailman.ds9a.nl
> [mailto:lartc-bounces@mailman.ds9a.nl] On Behalf Of
> ramsurrunv@mx.uom.ac.mu
> Sent: Thursday, June 01, 2006 2:58 PM
> To: lartc@mailman.ds9a.nl
> Subject: [LARTC] Not understanding network setup!! 
> 
>> Hi to all,
...
> First, 10.0.0.0/31 would be a network address. Second, a 31 bit subnet
> is meaningless. It only offers two addresses, the network address at
> 10.0.0.0 and the broadcast address at 10.0.0.1. That leaves no available
> addresses for host addresses. You probably mean /30 instead of /31. If
> you were using a /30, then you would run:
> 
> ip addr add 10.0.0.1/30 dev eth1
> ip addr add 10.0.0.5/30 dev eth2
> ip addr add 10.0.0.9/30 dev teql0
> 
> The .1, .5, and .9 would be the first available addresses in their
> respective subnets.

You probably mean /28 instead of /30:

ip addr add 10.0.0.9/28 dev teql0

Jarek P.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2006-06-02  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02  6:50 Jarek Poplawski [this message]
2006-06-02 14:20 ` [LARTC] Re: Not understanding network setup!! Jarek Poplawski

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='e5on24$rfk$1@sea.gmane.org' \
    --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.