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

[shaulka@xxxxxxxxxxxx]

  Hello,

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

    [ 192.168.0.6 ] and [ 192.168.0.8 ]
are only clients. These clients have only news reader, but no news 
server. The point here is that there is no hub, only point to point
crossed Ethernet connections. Now, assuming I have configured iptables
and tcpd correctly, how can I tell leafnode that I have 2 internal 
networks?

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
          RX packets:179422 errors:0 dropped:0 overruns:0 frame:0
          TX packets:121827 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:14644715 (13.9 MiB)  TX bytes:42303962 (40.3 MiB)
          Interrupt:5 Base address:0x280 

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
          RX packets:315050 errors:0 dropped:0 overruns:0 frame:0
          TX packets:242889 errors:0 dropped:0 overruns:0 carrier:0
          collisions:39 txqueuelen:100 
          RX bytes:28429703 (27.1 MiB)  TX bytes:99361047 (94.7 MiB)
          Interrupt:11 Base address:0x6100 

Where the networks were brought up with

    auto eth1
    iface eth1 inet static
    address 192.168.0.5
	netmask 255.255.255.255
	broadcast 192.168.0.5
	pointopoint 192.168.0.6
				
and a similar entry for the other interface.


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).

Was I supposed to drop the pointopoint mark and use something like

    inet addr:192.168.0.4  Bcast:192.168.0.5  Mask:255.255.255.254

so that each internal network is composed of 2 addresses?
Maybe each internal network should have 4 addresses so that there will
be a decent network and broadcast addresses, something like

    inet addr:192.168.0.5  Bcast:192.168.0.7  Mask:255.255.255.253
?
And what should I do with the pointopoint directive?


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.

802.1d Ethernet Bridging
CONFIG_BRIDGE
  If you say Y here, then your Linux box will be able to act as an
  Ethernet bridge, which means that the different Ethernet segments it
  is connected to will appear as one Ethernet to the participants.
  Several such bridges can work together to create even larger
  networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
  As this is a standard, Linux bridges will cooperate properly with
  other third party bridge products.

  In order to use the Ethernet bridge, you'll need the bridge
  configuration tools; see <file:Documentation/networking/bridge.txt>
  for location. Please read the Bridge mini-HOWTO for more
  information.

  Note that if your box acts as a bridge, it probably contains several
  Ethernet devices, but the kernel is not able to recognize more than
  one at boot time without help; for details read the Ethernet-HOWTO,
  available from in <http://www.tldp.org/docs.html#howto>.

  If you want to compile this code as a module ( = code which can be
  inserted in and removed from the running kernel whenever you want),
  say M here and read <file:Documentation/modules.txt>.  The module
  will be called bridge.o.

  If unsure, say N.

-- 

    Shaul Karl, shaulka@xxxxxxxxxx e t

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