On Sat, Mar 04, 2006 at 07:37:48AM -0600, Harry Putnam wrote:
> Joachim Schipper <[EMAIL PROTECTED]> writes:
>
> > Well, I am not sure exactly what you are trying to do, but getting 1.1
> > to talk to 1.2 might be somewhat interesting. Nothing too bad, but not
> > exactly simple either.
>
> I've gone clear around the bend ... over complicating.
>
> So backing off to the recommended setup. 192,.168.0/24 255.255.255.0
> for anything wired to the NETGEAR and 192.168.1/24 255.255.255.0
> for the two nics that connect obsd 2nd nic to gentoo 2nd nic.
>
> And no change at NETGEAR. whos address is 192.168.0.20 255.255.255.0
> I hope thats what you were saying.
>
> It doesn't really change the diagram,
What you say is correct, but you should also assign a different IP
address to at least one of the machines in the 192.168.1.0/24 range - or
do you mean that the 192.168.1.0/24 network is actually connected
together? Looking at your diagram, that sort of makes sense.
If not, you should assign 192.168.2.0/24 to one of the machines m1, m4.
> > It's usually better to divide into subnets. /24 is the standard, and
> > plenty big enough for any home LAN. This makes routing tables less
> > complicated
>
> God yes.... I was getting way over my head there.
>
> > . . . . (for instance, the NetGear would need a /32 route entry for
> > both 1.1 and 1.2, as would 0.4 and 0.19; this would be more elegantly
> > solved by reserving 192.168.1.0/24 for the whole net behind 0.4 and
> > 192.168.2.0/24 for the whole net behind 0.19; 192.168.0.0/24 is then the
> > network that is directly attached to the NetGear).
>
> Ok, I see where thats going ... I think. Let me just make sure I
> understand that but in this case we're not going there.
> By /32 I guess you mean a netmask of 255.255.255.255?
Yes, it's CIDR notation. It denotes the amount of bits in the netmask:
255 is eight bits, so /16 is 255.255.0.0, /24 is 255.255.255.0, and /32
is 255.255.255.255 (i.e., a subnet of one host).
This also makes dividing a class C subnet a lot easier: 192.168.0.0/24
can be subdivided into 192.168.0.0/25 and 192.168.0.128/25, for
instance.
However, all this is likely to cause more errors than just sticking to
/24 subnets, of which there are usually plenty in private address space.
> > Of course, all this presumes that the NetGear allows proper manipulation
> > of routing tables, which should be the case but may not be.
>
> It appears to.
>
> But now backed off to the more simplified setup.
> Same diagram and even same addresses but different mask. Everybody
> has 255.255.255.0 including the (NETGEAR) router right?
>
> (All have prefix 192.168)
>
> INTERNET
> | (Dynamic IP)
> |
> NETGEAR (consumer grade router FVS-318)
> reader | 0.20 fwobsd
> --------------------------------------------------
> | 0.4 | 0.3 | 0.5 | 0.19
> | | | |
> [ m1 ] [ m2 ] [ m3 ] [ m4 ]
> | 1.2 | 1.1
> |________________________________________________|
> rdmz fwdmz
>
>
> Things just fall into place with this setup. Just one little glitch
> and this is what caused me to go on the earlier binge and that was the
> setup of bind.
I'm not sure if you have already done this, but you'll want to tell the
NetGear and m2, m3 how to route traffic to 192.168.1.0/24.
> But before getting to that, what happens in this scheme with the
> domain name `local.lan' the numeric domain is now 2 domains right?
> 192.168.0 and 192.168.1. So can `local.lan' still cover both?
> That point has confused me for a while...
I haven't messed with BIND, but I suppose that BIND lets domains cover
whatever you want them to cover. In your case, 192.168.0.0/16 (or the
whole private subnet).
Or, if you want to get tricky, 192.168.0.0/23.
> Now about setup of bind (not on the obsd) ... I had no examples in DNS
> and Bind (4th ed) except like what I posted earlier with 192.168/16
> addressing
<snip: BIND>
I'm afraid I'll have to let someone else floor these questions... ;-)
Joachim
