Re: [leafnode-list] How this network should be configured to

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

shaulka@xxxxxxxxxxxx writes:

> I am not sure how the following network should be configured for
> leafnode. Can you advise?
>
>
>                                     [ 192.168.0.6 ]
>                                    /
>                                   /
>     Internet <--->  [ fqdn + 192.168.0.5 + 192.168.0.7 ]
>                                                  \
>                                                   \
>                                                    [ 192.168.0.8 ]
>
>
> As you can imagine, 
>
>     [ fqdn + 192.168.0.5 + 192.168.0.7 ] 
> is the leafnode server and news readers that are running locally on it
> have no problems. However

> Currently, ifconfig gives:
>
> eth0      Link encap:Ethernet  HWaddr 00:00:21:CE:18:CF  
>           inet addr:192.168.0.5  Bcast:192.168.0.5  Mask:255.255.255.255
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>
> eth1      Link encap:Ethernet  HWaddr 00:60:97:32:C3:78  
>           inet addr:192.168.0.7  Bcast:192.168.0.7  Mask:255.255.255.255
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

Linux has not accepted the point-to-point option, and this setup is
inappropriate for ethernet.

Leafnode has not been designed for point-to-point interfaces.

May I suggest that you reconfigure your network?

Put the server into 192.168.0.5/30 and 192.168.0.9/30 subnetworks, and
the first clients into 192.168.0.6/30 and the second client into
192.168.0.10/30. /30 means: netmask 255.255.255.252. You can't go with
less than 4 IPs per subnet because the all-zeroes and the all-ones
(192.168.0.4, 192.168.0.8, 192.168.0.7, 192.168.0.11) are broadcast
addresses.

So all you need to do:
1. change the netmasks on all three computers to 255.255.255.252.
2. change the server's IP from 192.168.0.7 to 192.168.0.9.
3. change the second client's IP from 192.168.0.8 to 192.168.10.
4. fix up your /etc/hosts, NIS hosts.byname, DNS and other places that
   carry IP mapping if any.

> With this setup, leafnode considers the 2 clients to be outside 
> networks and refuses to serve them (unless I will configure it with
> the STRANGERS option).

Correct, that's because leafnode is unaware of point-to-point networks
at the moment. (And if you had PPP dialins, you could just assign the
client an IP from a certain subnet and everything would be fine.)

> And what should I do with the pointopoint directive?

Drop it. It's ignored on ethernet anyhow.

> As an aside, while we are at it, perhaps you can write a few lines
> about the relevance of the CONFIG_BRIDGE configuration option of the
> Linux kernel? I still have to do my initial reading about it but I
> would be glad to read some short comments about it.

For Linux bridges, you'll need the tools from bridge.sourceforge.net,
and if you wanted to let netfilter work on bridged packets, you'll also
need the bridge-netfilter patch from the same site. I've never used a
Linux bridge in production, but I do have Proxy ARP in production use in
a 100 Mb/s LAN to almost transparently daisy-chain a packet filter
before the actual LAN -- almost because you see the box in
traceroute. Works nicely, is simple to set up and needs no patches for
netfilter.

-- 
Matthias Andree

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list