Rosemary McGillicuddy wrote: > >> At this point, I would consider setting up dnsmasq on the modem machine, >> and letting it provide dhcp service for the network. It has the >> advantage of providing DNS for the local network, as well as forwarding >> requsets from the second machine to your ISP's name servers as set by >> your modem connection. It gets the names for the local network from >> /etc/hosts on the machine it is running on, as well as from the dhcp >> leases it gives out. It also acts as a chaching name server for the >> local network. It was written for setups like yours. >> >> Once you have this all working, you will need to configure your firewall >> to allow trafic over the local ethernet, and restrict it over the modem >> connection. You also need to set up Internet connection sharing. MCC has >> a section to do this, or it can be set up manualy, but that is for >> another message... >> >> Mikkel > > > Mikkel > > I've got the ssh going between the two machines. Was in IRC and it was > suggested I don't need dnsmasq or dhcp but could simply make first box a > gateway and add ipkungfu to it. I was doing some reading on dnsmasq and > dhcp, and while still befuddled, happy to try with that - what is your > opinion on the pros and cons? I suppose I could do the gateway thing > first, and then the other later? learn both and see what happens? > Thanks > > Rosemary > > Registered Linux User # 386597 http://counter.li.org > "A friend may well be a masterpiece of nature". Emerson > Rosemary, You can configure everything as static routes. The only thing that gets to be a problem when you do that is that you have to set the name server address on the second machine to something. The machine that dials up your ISP gets this set when ever the connection comes up. You could copy the contents of /etc/resolv.conf on the first machine to the second machine after connecting to your ISP, and it should work fine - untill your ISP changes the name server IP addresses, or you change ISPs. I don't know how often that would be a problem. ISPs don't usualy change name server addresses that often. But if your second box develops trouble in the future, where it can connect by IP address, but not by name, to sites on the Internet, then the ISP changed things...
But you can do things in steps - skip using dhcp and dnsmasq for now, and get things up using static IPs. Then implement dnsmasq, and get it working as a name server. After that, edit /etc/resolv.conf to have 192.168.1.1 instead of your ISP's name servers. You can also enable the dhcp functions if you want - just set the range it uses at 192.168.1.100 to 192.168.1.200. That way, the static IP addresses of both boxes will not conflict with the dhcp server, but you can plug a laptop into the network, and it will be able get its information by dhcp. Or you may want to get dial on demand working on the first box before playing with dnsmasq. The nice thing is, you don't have to get everything working at once. The nice thing about implimenting dnsmasq is that it works well with dial on demand, and tends to reduce the number of false dialups. (Not something to worry about if you plan to always bring up the modem link yourself.) It can also speed things up slightly when you have two machines sharing the Internet connection. this is because it "remembers" the IP address for host names it looks up for you. So if you need that name again before it expires, it doesn't have to get it over the modem connection. As part of the record, there is information on how long the information is good for. So you don't usualy end up with outdated information... Mikkel -- Registered Linux User #16148 (http://counter.li.org/)
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
