> 1. Go to the bookstore and buy a good intro to TCP/IP book. > O'Reilly has a very good one..
Definitely read up more. You will have many unsolvable problems until you understand subnets, netmask etc better than now. You are certainly jumping in the deep end. > 2. Next - pick one of these 3 solutions to your problem: > > 1. ...2.. > 3. Setup your Linux machine as a bridge. > http://www.linux.org/docs/ldp/howto/BRIDGE-STP-HOWTO/ I would not like to use a bridge. From my understanding of it, it creates a single subnet from two physically separate networks. Remembering that this is over a modem (what is the upstream speed at each end?) then all broadcast traffic is going to travel the modem, as well as the traffic that really needs to go across it. Where would a DHCP server go? Can you have two on the one subnet? If not then you would have to make sure you have a permanent link. The only reason I can think of to use a bridge is if you HAD to support other non-routable protocols, like IPX. I think separate subnets are the better option in the long term. Assuming you are running DHCP then it is not much problem to change. If you aren't, then now will be the perfect time to start. And the Windows machine browsing will, I think, need WINS servers if you don't already have them. (I presume you mean that win boxes on one site want to share files/printers with win boxes on the other site). Samba would presumably be OK as WINS servers, or are you running Win2k servers? What about authentication of users on Win boxes? The solutions will depend on what you do now. And if network B is browsing the internet via network A, then I would definitely recommend running a squid proxy server on network B (in addition to any you might have on network A). This depends, of course, on how many machines you have connected on network B. Cameron. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
