Building off of Charles' comment: If you *are* looking to enable subnet-to- subnet browsing of Windows shares, Samba does the trick without much heartache at all. I have an SME/e-smith box on one end of my VPN lab setup, and a remote machine on the other end. The remote-end clients simply have the IP address of the SME box (default configured as a Master) in the WINS server configuration of the Windows IP configuration. The remote clients report themselves to the Master, and it in turn re-advertises their existence to the local subnet. So all Windows clients on a 10.1.2.0/24 network can see all Windows clients thru the tunnel on a 192.168.1.0/24 subnet (and vice versa), thru an intervening 174.16.1.0/24 "simulated internet." Works slick.
If you want a braindead-easy Samba server (and really a complete drop-in Linux replacement for NT server) see the details at www.e-smith.org. It's open source and freely distributed, with commercial support if desired. My primary fileserver runs 2 60 GB disk RAID 1, on a P100 throw-away. Free. And I mean, braindead easy... Dan Quoting Ed Zahurak <[EMAIL PROTECTED]>: > > Is it possible to configure a set of LRP/LEAF routers to forward > broadcast > traffic accross a vpn link between the two subnets? If so, how would I > go > about configuring the boxes to take the traffic? > > Thanks, > Ed Z. > > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
