From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter <netfilter@vger.kernel.org>
Subject: Re: 192.168.2.33/24 & 192.168.2.33/29 on the same box
Date: Mon, 7 Apr 2014 07:57:00 -0500 [thread overview]
Message-ID: <20140407125700.GH32069@harrier.slackbuilds.org> (raw)
In-Reply-To: <534292C8.2070301@yahoo.co.uk>
On Mon, Apr 07, 2014 at 12:58:00PM +0100, lejeczek wrote:
> I'm hoping an expert could help me, clarify this one for me, should
> be simple I guess, probably not for a newbie like me
>
> having on one system
>
> physical eth 192.168.2.33/24
> and a
> bridge (only taps no phys) 192.168.2.33/29
When you're going to bridge an interface, you assign it "0.0.0.0/0"
(which is to bring it up.) Then you assign an IP address to the
bridge.
No time to look it up for you right now, but I believe the brctl(8)
manual should cover this.
> I cannot get to anything behind 192.168.2.33/29 from anything
> behind 192.168.2.33/24 (and vice versa)
Broken bridge, I guess.
> each side can get respectively tofurther-out interface of the
> 192.168.2.33 routing + forwarding I have it set up all I believe
>
> is such a configuration even valid? should be, right?
>
> I'm trying to understand subnet concept of, in this case class C
Do yourself a favor: totally forget about "class".
> private net - is 192.168.2.33/29 still a part of 192.168.2.33/24
> or it is a whole separate network.
It is indeed a part. To turn those addresses into valid CIDR
expressions, change the last quads to be the network address:
1. 192.168.2.33/29 becomes 192.168.2.32/29
This includes IP addresses 192.168.2.32 through .39
2. 192.168.2.33/24 becomes 192.168.2.0/24
This includes IP addresses 192.168.2.0 through .255
--
http://rob0.nodns4.us/
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
prev parent reply other threads:[~2014-04-07 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:58 192.168.2.33/24 & 192.168.2.33/29 on the same box lejeczek
2014-04-07 12:57 ` /dev/rob0 [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=20140407125700.GH32069@harrier.slackbuilds.org \
--to=rob0@gmx.co.uk \
--cc=netfilter@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.