Date: Sun, 15 Oct 2000 12:06:21 -0400 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: <jay.krell@cornell.edu> Cc: <questions@FreeBSD.ORG> Subject: Re: FreeBSD 3.x->4.1, my experience, Samba, dhcpd, ppp, nat, dns, named Message-ID: <002e01c036c1$defbdd10$1200a8c0@gsicomp.on.ca> References: <001001c03686$e697a7b0$8001a8c0@jayk3>
next in thread | previous in thread | raw e-mail | index | archive | help
> The configuration I was after, at least: > two machines > dialup ppp to an isp > FreeBSD is the, in Microsoft terms, "internet connection provider" -- the > other machine is running NT and whenever it or the FreeBSD machine needs > internet access, the FreeBSD machine dials its modem; they are networked via > ethernet, of course. The NT machine has no hardcoded network configuration. > It uses "dhcp". > The FreeBSD machine provides dhcp and dns. The FreeBSD machine is also a > Samba server. It's still unclear which among ppp, dhcpd, samba, named is > providing dns, but it works. I think it is named providing dns and ppp just > writes into /etc/resolve.conf. Anyway, most of this I vaguely figured out > enough in the 3.x timeframe.. > > the resolutions were > Samba > -------- > There is conflicting information here. > 1) Samba installs /usr/local/etc/rc.d/samba.sh.sample, with the > implication that you just > cp /usr/local/etc/rc.d/samba.sh.sample /usr/local/etc/rc.d/samba.sh > 2) /etc/inetd.conf has two lines commented out referring to smbd and > nmbd and a comment saying to uncomment them to enable Samba "within inetd". There are two ways to run servers in the UNIX world. They can run standalone (always ready and waiting), or they can run on-demand. The first way is accomplished by running the samba.sh script when the server boots, as it starts smbd and nmbd which then respond to SMB queries. The second way is done by running them from inetd. In the case of Samba, Inetd will listen for connections on ports 137-139, and when requests come in inetd will start smbd/nmbd and pass off the requests to Samba, but will terminate smbd/nmbd once the request has been completed. In the case of Samba, the first method is much better performance-wise, which is why the installation installs the sample startup script and doesn't mention anything about inetd. > Dhcp server > ---------------- > This wasn't easy in the 3.x timeframe. First, at that time there was the > isc-dhcp and wide-dhcp ports. I arbitrarily tried the isc one and got it to > work. On the 4.1 CD, isc is marked broken due to security problems (I think > only the client), so I tried wide. I was unable to configure wide to work. As you mentioned, isc-dhcpd2 is the way to go. > Ok well, the answer is embedded in there. The boilerplate for /etc/rc.local > apparently changed between 3.x and 4.x. Upgrading requires updating it, > adding the "source_rc_confs" line. A better solution might be copy the last > part of rc.local to something like /usr/local/etc/rc.d/dhcpd.sh. I don't > know. This works for me. As for starting it at boot, you don't need an rc.local script for it. (In fact, rc.local has been obsolete for some a long time - it's denoted as obsolete on my 3.1-REL machine.) All you need to do is write a little boot script and stick it in /usr/local/etc/rc.d, just like samba did. This will make dhcpd start upon boot. > Given that FreeBSD includes the isc-dhcp client, why not the server? I think it might have something to do with ISC's policy on distribution. For the longest time dhclient was not included in FreeBSD. Perhaps it's just time until dhcpd is available in the base distribution, although it's not a huge deal to grab it from the ports in the meantime. > This functionality is all _vastly_ easier to get working in Windows 2000 > Pro, taking under an hour vs. days. The biggest problem I had there was > having to "unconfigure" the client, to stop using hardcoded IP addresses, > which you have to do for FreeBSD too. In the pre Win2k timeframe though, I > don't think you could do this with NT4 Workstation, and I've never > configured NT4 Server to do this. I want the FreeBSD machine around too for > other reasons. As for "hours vs days", it's all a matter of background knowledge. The FreeBSD setup you describe is only an "afternoon job" by my standards, but I've been using FreeBSD for ~4 years now. I recently had to do a massive upgrade/reconfigure effort an NT4 network (2 physical locations, 50 clients) after a change in ISP at one location. I never had touched NT4 Server before. It took me three days to get the PDC and BDC all synch'd up and DHCP and WINS working properly. (Had it been a FreeBSD setup with DHCPd and Samba, it would have only taken a few hours.) Regardless, I'm glad to see that you're sharing your results and findings with the FreeBSD community. We're happy to see that you've taken the time to learn and figure things out, instead of being a l4m3r and saying "I can't make it work, FreeBsd sux, Linux r00lz!" -- Matthew Emmerton GSI Computer Services +1 (800) 217 5409 (Canada) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002e01c036c1$defbdd10$1200a8c0>