Date: Fri, 30 Dec 2011 22:12:21 -0600 From: Jeffrey McFadden <junkrigsailor@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: very small network Message-ID: <CAFpTYWOxtddrOof1MM-LAS2LdYWbNsMj4yoneiOUdPkAiKPH5A@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Mike, Chad, Damien, thank you all. I'm good to go now. Chad, just because you asked, I'm running behind a Verizon MiFi 5 port 3G router. Out in rural US we don't have cable or dsl, and the latency issues of satellite make it undesirable to me, so the cellular route (not the broadest of broadband but tolerable) is my best choice.. Everything on that side is under control - like I said, all these machines can access the internet. When they were Windows boxes they were networked. I used to do Windows networking for a living, but Windows boxes die too often, with no notice and no hope or restoration, and anyway I find this OS, and this community, to be more enjoyable. I've had considerable experience over the years with standalone Linux boxen, and once built a Windows network with a Debian 1.4 (I think) server running Samba, just never had occasion to hook several *nix's together. I do, so far, prefer FreeBSD to any of the Linux's I've run. I bought into FreeBSD with a DVD of PC-BSD. It's great, but the PC-BSD user manual is not up to the level of the FreeBSD manual. In the latter I have found, as you all suggested, all the necessary information. I haven't set the network up yet but I expect to be able to run both server and client NFS on each machine to enable networking both ways. They are all laptops of one sort or another (Asus eee, Toshiba Satellite, late model Sony Vaio) and it sort of depends on where I sit which machine needs to be client and which server, if that makes any sense. Anyway, once again, thanks to all. Jeff ><> ><> ><> ><> ><> ><> ><> <>< <>< <>< <>< <>< <>< <>< On Thu, Dec 29, 2011 at 9:43 PM, <freebsd-questions-request@freebsd.org>wro= te: > Send freebsd-questions mailing list submissions to > freebsd-questions@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > or, via email, send a message with subject or body 'help' to > freebsd-questions-request@freebsd.org > > You can reach the person managing the list at > freebsd-questions-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-questions digest..." > > > Today's Topics: > > 1. Re: Static IP on a Bridge (Brian Seklecki (Mobile)) > 2. Re: Need to know the compatibility (Daniel Feenberg) > 3. Re: Need to know the compatibility (Daniel Feenberg) > 4. Re: Need to know the compatibility (Mark Blackman) > 5. Same version on binary packages and updated ports > (Walter Alejandro Iglesias) > 6. Re: OT: Root access policy (mikel king) > 7. Re: OT: Root access policy (Carl Johnson) > 8. Re: Static IP on a Bridge (james@colannino.org) > 9. Re: Static IP on a Bridge (james@colannino.org) > 10. Re: Intel EMGD driver on FreeBSD? (Luke Dean) > 11. Re: OT: Root access policy (C. P. Ghost) > 12. Re: Same version on binary packages and updated ports > (Jerry McAllister) > 13. RE: Static IP on a Bridge (Devin Teske) > 14. Re: Same version on binary packages and updated ports (Polytropon) > 15. Re: OT: Root access policy (Polytropon) > 16. RE: OT: Root access policy (Devin Teske) > 17. Re: Same version on binary packages and updated ports > (Chuck Swiger) > 18. Re: Same version on binary packages and updated ports > (Walter Alejandro Iglesias) > 19. Re: Same version on binary packages and updated ports > (Adam Vande More) > 20. Re: Same version on binary packages and updated ports > (Walter Alejandro Iglesias) > 21. Re: ZFS upgrade path (James Edwards) > 22. Host Dynamic DNS configuration for 8.2-RELEASE (akshay sreeramoju) > 23. Re: Host Dynamic DNS configuration for 8.2-RELEASE > (Matthew Seaman) > 24. very small "workgroup" network (Jeffrey McFadden) > 25. Re: Host Dynamic DNS configuration for 8.2-RELEASE > (akshay sreeramoju) > 26. Re: very small "workgroup" network (Mike Jeays) > 27. Re: very small "workgroup" network (Damien Fleuriot) > 28. Re: Host Dynamic DNS configuration for 8.2-RELEASE (Da Rock) > 29. Re: mutual forwarders in ISC BIND (Da Rock) > 30. Re: very small "workgroup" network (Chad Perrin) > 31. FreeBSD Kernel Internals Documentation (David Jackson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Dec 2011 10:07:46 -0500 (EST) > From: "Brian Seklecki (Mobile)" <root@probikesllc.com> > Subject: Re: Static IP on a Bridge > To: Matthew Seaman <m.seaman@infracaninophile.co.uk> > Cc: freebsd-questions@freebsd.org > Message-ID: > <alpine.LRH.2.00.1112291006510.10486@ecs00.cozzaenterprises.com> > Content-Type: TEXT/PLAIN; charset=3DUS-ASCII; format=3Dflowed > > > > Also, what MAC address does the DHCPREQUEST packet appear to be sourced > from (from the view of your DHCP server, or on the wire somewhere > between the two (SPAN PORT)) ~BAS > > This sounds familar. > > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Dec 2011 10:45:14 -0500 (EST) > From: Daniel Feenberg <feenberg@nber.org> > Subject: Re: Need to know the compatibility > To: Vijayamurugan.Kalyanasundaram@emc.com > Cc: freebsdquestions@FreeBSD.org, questions@FreeBSD.org, > freebsd-questions@FreeBSD.org > Message-ID: <alpine.LFD.2.00.1112291041370.14903@sas1.nber.org> > Content-Type: TEXT/PLAIN; charset=3DUS-ASCII; format=3Dflowed > > > > On Mon, 19 Dec 2011, Vijayamurugan.Kalyanasundaram@emc.com wrote: > > > Hi Team, > > > > Kindly let me know on the compatibility of " Intel X520 Dual Port 10 > > Gigabit Ethernet PCIe Adaptor Card " with Free BSD 8.2 OS. > > > > I didn't see any answer to this - but we are interested in ANY 10 > GB ethernet card for FreeBSD or Ubuntu. Does anyone have that working? > > Daniel Feenberg > NBER > > > ------------------------------ > > Message: 3 > Date: Thu, 29 Dec 2011 10:45:14 -0500 (EST) > From: Daniel Feenberg <feenberg@nber.org> > Subject: Re: Need to know the compatibility > To: Vijayamurugan.Kalyanasundaram@emc.com > Cc: freebsdquestions@FreeBSD.org, questions@FreeBSD.org, > freebsd-questions@FreeBSD.org > Message-ID: <alpine.LFD.2.00.1112291041370.14903@sas1.nber.org> > Content-Type: TEXT/PLAIN; charset=3DUS-ASCII; format=3Dflowed > > > > On Mon, 19 Dec 2011, Vijayamurugan.Kalyanasundaram@emc.com wrote: > > > Hi Team, > > > > Kindly let me know on the compatibility of " Intel X520 Dual Port 10 > > Gigabit Ethernet PCIe Adaptor Card " with Free BSD 8.2 OS. > > > > I didn't see any answer to this - but we are interested in ANY 10 > GB ethernet card for FreeBSD or Ubuntu. Does anyone have that working? > > Daniel Feenberg > NBER > > > ------------------------------ > > Message: 4 > Date: Thu, 29 Dec 2011 15:59:50 +0000 > From: Mark Blackman <mark@exonetric.com> > Subject: Re: Need to know the compatibility > To: Daniel Feenberg <feenberg@nber.org> > Cc: Vijayamurugan.Kalyanasundaram@emc.com, > freebsd-questions@FreeBSD.org > Message-ID: <37877907-8E4F-4394-88D7-0CC4B8F09BBC@exonetric.com> > Content-Type: text/plain; charset=3Dus-ascii > > > On 29 Dec 2011, at 15:45, Daniel Feenberg wrote: > > > > > > > On Mon, 19 Dec 2011, Vijayamurugan.Kalyanasundaram@emc.com wrote: > > > >> Hi Team, > >> > >> Kindly let me know on the compatibility of " Intel X520 Dual Port 10 > Gigabit Ethernet PCIe Adaptor Card " with Free BSD 8.2 OS. > >> > > > > I didn't see any answer to this - but we are interested in ANY 10 > > GB ethernet card for FreeBSD or Ubuntu. Does anyone have that working? > > > > Daniel Feenberg > > NBER > > The two drivers below sound promising? > > > http://www.freebsd.org/cgi/man.cgi?query=3Dixgb&apropos=3D0&sektion=3D0&m= anpath=3DFreeBSD+8.2-RELEASE&arch=3Ddefault&format=3Dhtml > > > http://www.freebsd.org/cgi/man.cgi?query=3Dixgbe&apropos=3D0&sektion=3D0&= manpath=3DFreeBSD+8.2-RELEASE&arch=3Ddefault&format=3Dhtml > > > > > ------------------------------ > > Message: 5 > Date: Thu, 29 Dec 2011 17:16:11 +0100 > From: Walter Alejandro Iglesias <roquesor@gmail.com> > Subject: Same version on binary packages and updated ports > To: freebsd-questions@freebsd.org > Message-ID: <20111229161611.GA81214@chancha.local> > Content-Type: text/plain; charset=3Dus-ascii > > Hello, > > I am giving my firsts steps with FreeBSD. > I've searched a lot in google, mailing list, forums, freebsd > handbook and I am still not clear about the following. > > In a RELEASE fresh install, after updating the ports using i.e. > portsnap, the packages downloaded with pkp_add -r are older > versions respect their port counterparts, leading to > dependencies issues. So, once the ports tree is updated: > > 1) Am I forced to compile all? > > 2) Should I use STABLE to get the same versions with pkg_add > than compiling up to date ports? Are STABLE packages compiled > from this ports? > > 3) In case my assumption above is correct; taking in care that > in a production system it is advisable (handbook) to stay with > RELEASE, should I avoid updating the ports tree in i.e. a server > machine? What to do with broken ports in this case? > > Resuming, is there a default way to install-update the software > keeping ports and binary packages in one piece? What is > advisable in general terms for a desktop and what for a server? > > It will be enough for me if someone just point me to documentation. > > Big thanks > > > Walter > > > > > ------------------------------ > > Message: 6 > Date: Thu, 29 Dec 2011 11:34:39 -0500 > From: mikel king <mikel.king@olivent.com> > Subject: Re: OT: Root access policy > To: Irk Ed <irked7189@gmail.com> > Cc: freebsd-questions@freebsd.org > Message-ID: <1AD045F1-BBE7-492C-9F19-FB54F2741D5B@olivent.com> > Content-Type: text/plain; charset=3Dus-ascii > > > On Dec 29, 2011, at 4:01 AM, Irk Ed wrote: > > > For the first time, a customer is asking me for root access to said > > customer's servers. > > > > Obviously, I must comply. At the same time, I cannot continue be > > accountable for those servers. > > > > Is this that simple and clear cut? > > > > Assuming that I'll be asked to continue administering said servers, I > guess > > I should at least enable accounting... > > > > I'd appreciate comments/experience/advice from the wise... > > Call me paranoid but is your contract near term end? > > In my experience this is usually a precursor to a end of year cost cuttin= g > service provider change. Specifically someone in sales's second cousin's > nephew who saw a linux server once and thinks he's an expert. > > I recommend that you complete a backup of everything prior to granting > them sudo access. Possibly even run am md5sum against all important confi= g > files and save that in your back up as well. > > Then give them well written explanation of why sudo is superior or at > least safer to direct root access. > > Regards, > Mikel King > BSD News Network > http://bsdnews.net > skype: mikel.king > http://twitter.com/mikelking > > > > > > ------------------------------ > > Message: 7 > Date: Thu, 29 Dec 2011 09:15:45 -0800 > From: Carl Johnson <carlj@peak.org> > Subject: Re: OT: Root access policy > To: freebsd-questions@freebsd.org > Message-ID: <87y5tvcn9a.fsf@oak.localnet> > Content-Type: text/plain; charset=3Dus-ascii > > Damien Fleuriot <ml@my.gd> writes: > > > On 12/29/11 10:58 AM, Polytropon wrote: > >> On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: > >>> For the first time, a customer is asking me for root access to said > >>> customer's servers. > >> > <snip> > >>> Assuming that I'll be asked to continue administering said servers, I > guess > >>> I should at least enable accounting... > >> > >> You could have better success using sudo. Make sure > >> the customer is allowed to "sudo <command>". The > >> sudo program will log _all_ things the customer > >> does, so you can be sure you can review actions. > >> Furthermore you don't need to give him the _real_ > >> root password. He won't be able to "su root" or > >> to login as root, _real_ root. But he can use > >> the "sudo" prefix to issue commands "with root > >> privileges". > >> > > > > "sudo su -" or "sudo sh" and the customer gets a native root shell whic= h > > does *not* log commands ! > > The sudoers manpage mention the noexec option which is designed to help > with the first problem. They also show an example using !SHELLS which > can help with the second. > > -- > Carl Johnson carlj@peak.org > > > > ------------------------------ > > Message: 8 > Date: Thu, 29 Dec 2011 11:21:11 -0600 > From: james@colannino.org > Subject: Re: Static IP on a Bridge > To: freebsd-questions@freebsd.org > Message-ID: <20111229112111.1079640ol70p51u0@gator1823.hostgator.com> > Content-Type: text/plain; charset=3DISO-8859-1; DelSp=3D"Yes"; > format=3D"flowed" > > Quoting Matthew Seaman <m.seaman@infracaninophile.co.uk>: > > > What's the error message you see when you fail to ping out? > > ping: cannot resolve google.com: Host name lookup failure > > > What does the routing table (netstat -r) look like before and after DHC= P? > > Before DHCP: > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expir= e > localhost link#11 UH 0 0 lo0 > > Internet6: > Destination Gateway Flags Netif Expire > :: localhost UGRS lo0 > localhost localhost UH lo0 > ::ffff:0.0.0.0 localhost UGRS lo0 > fe80:: localhost UGRS lo0 > fe80::%re0 link#5 U re0 > fe80::6ef0:49ff:fe link#5 UHS lo0 > fe80::%lo0 link#11 U lo0 > fe80::1%lo0 link#11 UHS lo0 > fe80::%tap0 link#13 U tap0 > fe80::2bd:8aff:fe3 link#13 UHS lo0 > fe80::%tap1 link#14 U tap1 > fe80::2bd:8dff:fe3 link#14 UHS lo0 > ff01::%re0 fe80::6ef0:49ff:fe U re0 > ff01::%lo0 localhost U lo0 > ff01::%tap0 fe80::2bd:8aff:fe3 U tap0 > ff01::%tap1 fe80::2bd:8dff:fe3 U tap1 > ff02:: localhost UGRS lo0 > ff02::%re0 fe80::6ef0:49ff:fe U re0 > ff02::%lo0 localhost U lo0 > ff02::%tap0 fe80::2bd:8aff:fe3 U tap0 > ff02::%tap1 fe80::2bd:8dff:fe3 U tap1 > > After DHCP: > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expir= e > default 192.168.1.1 UGS 0 0 bridge > localhost link#11 UH 0 0 lo0 > 192.168.1.0 link#12 U 0 1 bridge > 192.168.1.103 link#12 UHS 0 0 lo0 > > Internet6: > Destination Gateway Flags Netif Expire > :: localhost UGRS lo0 > localhost localhost UH lo0 > ::ffff:0.0.0.0 localhost UGRS lo0 > fe80:: localhost UGRS lo0 > fe80::%re0 link#5 U re0 > fe80::6ef0:49ff:fe link#5 UHS lo0 > fe80::%lo0 link#11 U lo0 > fe80::1%lo0 link#11 UHS lo0 > fe80::%tap0 link#13 U tap0 > fe80::2bd:8aff:fe3 link#13 UHS lo0 > fe80::%tap1 link#14 U tap1 > fe80::2bd:8dff:fe3 link#14 UHS lo0 > ff01::%re0 fe80::6ef0:49ff:fe U re0 > ff01::%lo0 localhost U lo0 > ff01::%tap0 fe80::2bd:8aff:fe3 U tap0 > ff01::%tap1 fe80::2bd:8dff:fe3 U tap1 > ff02:: localhost UGRS lo0 > ff02::%re0 fe80::6ef0:49ff:fe U re0 > ff02::%lo0 localhost U lo0 > ff02::%tap0 fe80::2bd:8aff:fe3 U tap0 > ff02::%tap1 fe80::2bd:8dff:fe3 U tap1 > > > What does your arp table look like (arp -a) before and after DHCP? > > Before DHCP: > > (nothing was printed to the screen) > > After DHCP: > > ? (192.168.1.1) at 4c:e6:76:50:86:f6 on bridge0 expires in 1190 > seconds [bridge] > ? (192.168.1.103) at 02:62:11:f0:35:00 on bridge0 permanent [bridge] > > I can see that something is definitely not right. Not sure how to fix > /etc/rc.conf so that it will be setup correctly, though. Thank you > for the help! > > James > > > > > ------------------------------ > > Message: 9 > Date: Thu, 29 Dec 2011 11:22:45 -0600 > From: james@colannino.org > Subject: Re: Static IP on a Bridge > To: freebsd-questions@freebsd.org > Message-ID: <20111229112245.18363n0ssrqycc2s@gator1823.hostgator.com> > Content-Type: text/plain; charset=3DISO-8859-1; DelSp=3D"Yes"; > format=3D"flowed" > > Quoting "Brian Seklecki (Mobile)" <root@probikesllc.com>: > > > Also, what MAC address does the DHCPREQUEST packet appear to be sourc= ed > > from (from the view of your DHCP server, or on the wire somewhere > > between the two (SPAN PORT)) ~BAS > > How do I do that? :) > > James > > > > ------------------------------ > > Message: 10 > Date: Thu, 29 Dec 2011 09:23:07 -0800 (PST) > From: Luke Dean <LukeD@pobox.com> > Subject: Re: Intel EMGD driver on FreeBSD? > To: Mark Felder <feld@feld.me> > Cc: questions@freebsd.org > Message-ID: > <alpine.BSF.2.00.1112290854410.16587@tower.lukas.is-a-geek.org> > Content-Type: TEXT/PLAIN; charset=3DUS-ASCII; format=3Dflowed > > > > On Tue, 27 Dec 2011, Mark Felder wrote: > > > Are you sure that the problem isn't just that the current releases of > FreeBSD > > don't have GEM/KMS support which the newer Intel drivers require? I'm > running > > a test build on my Google CR48 and have OpenGL acceleration without any > major > > hiccups except not being able to get back to a console after starting X= . > > > > > > Test here: > > > > > http://lists.freebsd.org/pipermail/freebsd-current/2011-November/029219.h= tml > > > > > > I converted the image into full install on my hard drive. > > > > > > More details here: http://wiki.freebsd.org/Intel_GPU > > Thank you for the reply. > > I've been unable to lay hands on a USB drive big enough to hold that > entire image, so I can't easily test with it. > > >From what I'm finding on the web, your Google CR48 is probably an Intel > GMA 3150, which looks like it's covered by the normal open source Intel > driver even though it's not explicitly listed on the manpage. > http://intellinuxgraphics.org/documentation.html > > I think my GMA 500 is a different situation. I'm pessimistic. > > > ------------------------------ > > Message: 11 > Date: Thu, 29 Dec 2011 18:25:55 +0100 > From: "C. P. Ghost" <cpghost@cordula.ws> > Subject: Re: OT: Root access policy > To: Irk Ed <irked7189@gmail.com> > Cc: freebsd-questions@freebsd.org > Message-ID: > <CADGWnjUi3jSGp3kNwnsJq+18++2A89uU2bRiKbYdTwQ59Gyjrw@mail.gmail.co= m > > > Content-Type: text/plain; charset=3DISO-8859-1 > > On Thu, Dec 29, 2011 at 10:01 AM, Irk Ed <irked7189@gmail.com> wrote: > > For the first time, a customer is asking me for root access to said > > customer's servers. > > Are we talking about jail(8)- or server-level root access? > > -cpghost. > > -- > Cordula's Web. http://www.cordula.ws/ > > > ------------------------------ > > Message: 12 > Date: Thu, 29 Dec 2011 12:34:11 -0500 > From: Jerry McAllister <jerrymc@msu.edu> > Subject: Re: Same version on binary packages and updated ports > To: Walter Alejandro Iglesias <roquesor@gmail.com> > Cc: freebsd-questions@freebsd.org > Message-ID: <20111229173411.GC24443@gizmo.acns.msu.edu> > Content-Type: text/plain; charset=3Dus-ascii > > On Thu, Dec 29, 2011 at 05:16:11PM +0100, Walter Alejandro Iglesias wrote= : > > Hi, > > I am not expert on all this, but can give a couple of impressions. > > > Hello, > > > > I am giving my firsts steps with FreeBSD. > > Welcome to FreeBSD. It is a good system. > > > I've searched a lot in google, mailing list, forums, freebsd > > handbook and I am still not clear about the following. > > > > In a RELEASE fresh install, after updating the ports using i.e. > > portsnap, the packages downloaded with pkp_add -r are older > > versions respect their port counterparts, leading to > > dependencies issues. So, once the ports tree is updated: > > > > 1) Am I forced to compile all? > > Anything that has changed and anything that depends on those things. > That can mean a lot of recompiling. > > > > > 2) Should I use STABLE to get the same versions with pkg_add > > than compiling up to date ports? Are STABLE packages compiled > > from this ports? > > Check this page: > > http://www.freebsd.org/ports/ > > It's more accurate than what I started to wrie. > > The ports tree and the OS release generally sync up when a RELEASE > comes out, but that soon begins to diverge as ports are changed. > Ports are worked on independently by port maintainers. > > ////jerry > > > > > 3) In case my assumption above is correct; taking in care that > > in a production system it is advisable (handbook) to stay with > > RELEASE, should I avoid updating the ports tree in i.e. a server > > machine? What to do with broken ports in this case? > > > > Resuming, is there a default way to install-update the software > > keeping ports and binary packages in one piece? What is > > advisable in general terms for a desktop and what for a server? > > > > It will be enough for me if someone just point me to documentation. > > > > Big thanks > > > > > > Walter > > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > > ------------------------------ > > Message: 13 > Date: Thu, 29 Dec 2011 09:48:32 -0800 > From: Devin Teske <devin.teske@fisglobal.com> > Subject: RE: Static IP on a Bridge > To: <james@colannino.org>, <freebsd-questions@freebsd.org> > Message-ID: <037401ccc652$15417110$3fc45330$@fisglobal.com> > Content-Type: text/plain; charset=3D"us-ascii" > > > -----Original Message----- > > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- > > questions@freebsd.org] On Behalf Of james@colannino.org > > Sent: Thursday, December 29, 2011 9:21 AM > > To: freebsd-questions@freebsd.org > > Subject: Re: Static IP on a Bridge > > > > Quoting Matthew Seaman <m.seaman@infracaninophile.co.uk>: > > > > > What's the error message you see when you fail to ping out? > > > > ping: cannot resolve google.com: Host name lookup failure > > > > > What does the routing table (netstat -r) look like before and after > DHCP? > > > > Before DHCP: > > > > Routing tables > > > > Internet: > > Destination Gateway Flags Refs Use Netif > Expire > > localhost link#11 UH 0 0 lo0 > > > > Internet6: > > Destination Gateway Flags Netif Expire > > :: localhost UGRS lo0 > > localhost localhost UH lo0 > > ::ffff:0.0.0.0 localhost UGRS lo0 > > fe80:: localhost UGRS lo0 > > fe80::%re0 link#5 U re0 > > fe80::6ef0:49ff:fe link#5 UHS lo0 > > fe80::%lo0 link#11 U lo0 > > fe80::1%lo0 link#11 UHS lo0 > > fe80::%tap0 link#13 U tap0 > > fe80::2bd:8aff:fe3 link#13 UHS lo0 > > fe80::%tap1 link#14 U tap1 > > fe80::2bd:8dff:fe3 link#14 UHS lo0 > > ff01::%re0 fe80::6ef0:49ff:fe U re0 > > ff01::%lo0 localhost U lo0 > > ff01::%tap0 fe80::2bd:8aff:fe3 U tap0 > > ff01::%tap1 fe80::2bd:8dff:fe3 U tap1 > > ff02:: localhost UGRS lo0 > > ff02::%re0 fe80::6ef0:49ff:fe U re0 > > ff02::%lo0 localhost U lo0 > > ff02::%tap0 fe80::2bd:8aff:fe3 U tap0 > > ff02::%tap1 fe80::2bd:8dff:fe3 U tap1 > > > > After DHCP: > > > > Routing tables > > > > Internet: > > Destination Gateway Flags Refs Use Netif > Expire > > default 192.168.1.1 UGS 0 0 bridge > > localhost link#11 UH 0 0 lo0 > > 192.168.1.0 link#12 U 0 1 bridge > > 192.168.1.103 link#12 UHS 0 0 lo0 > > > > Internet6: > > Destination Gateway Flags Netif Expire > > :: localhost UGRS lo0 > > localhost localhost UH lo0 > > ::ffff:0.0.0.0 localhost UGRS lo0 > > fe80:: localhost UGRS lo0 > > fe80::%re0 link#5 U re0 > > fe80::6ef0:49ff:fe link#5 UHS lo0 > > fe80::%lo0 link#11 U lo0 > > fe80::1%lo0 link#11 UHS lo0 > > fe80::%tap0 link#13 U tap0 > > fe80::2bd:8aff:fe3 link#13 UHS lo0 > > fe80::%tap1 link#14 U tap1 > > fe80::2bd:8dff:fe3 link#14 UHS lo0 > > ff01::%re0 fe80::6ef0:49ff:fe U re0 > > ff01::%lo0 localhost U lo0 > > ff01::%tap0 fe80::2bd:8aff:fe3 U tap0 > > ff01::%tap1 fe80::2bd:8dff:fe3 U tap1 > > ff02:: localhost UGRS lo0 > > ff02::%re0 fe80::6ef0:49ff:fe U re0 > > ff02::%lo0 localhost U lo0 > > ff02::%tap0 fe80::2bd:8aff:fe3 U tap0 > > ff02::%tap1 fe80::2bd:8dff:fe3 U tap1 > > > > > What does your arp table look like (arp -a) before and after DHCP? > > > > Before DHCP: > > > > (nothing was printed to the screen) > > > > After DHCP: > > > > ? (192.168.1.1) at 4c:e6:76:50:86:f6 on bridge0 expires in 1190 seconds > [bridge] ? > > (192.168.1.103) at 02:62:11:f0:35:00 on bridge0 permanent [bridge] > > > > I can see that something is definitely not right. Not sure how to fix > /etc/rc.conf > > so that it will be setup correctly, though. Thank you for the help! > > Add the following line (exactly as it appears) to /etc/rc.conf: > > defaultrouter=3D"192.168.1.1" > > -- > Devin > > _____________ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete t= he > message and all copies; (ii) do not disclose, distribute or use the messa= ge > in any manner; and (iii) notify the sender immediately. In addition, plea= se > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > > > ------------------------------ > > Message: 14 > Date: Thu, 29 Dec 2011 18:55:32 +0100 > From: Polytropon <freebsd@edvax.de> > Subject: Re: Same version on binary packages and updated ports > To: Walter Alejandro Iglesias <roquesor@gmail.com> > Cc: freebsd-questions@freebsd.org > Message-ID: <20111229185532.7aeaeaf6.freebsd@edvax.de> > Content-Type: text/plain; charset=3DUS-ASCII > > On Thu, 29 Dec 2011 17:16:11 +0100, Walter Alejandro Iglesias wrote: > > Hello, > > > > I am giving my firsts steps with FreeBSD. > > I've searched a lot in google, mailing list, forums, freebsd > > handbook and I am still not clear about the following. > > > > In a RELEASE fresh install, after updating the ports using i.e. > > portsnap, the packages downloaded with pkp_add -r are older > > versions respect their port counterparts, leading to > > dependencies issues. So, once the ports tree is updated: > > > > 1) Am I forced to compile all? > > No, you aren't forced to anything. :-) > > In case you intend to bring your _installed_ programs > up to date (where "date" is indicated by the ports > tree), use a tool like portmaster or portupgrade to > upgrade all that need upgrading. > > > > > 2) Should I use STABLE to get the same versions with pkg_add > > than compiling up to date ports? > > RELEASE and STABLE are related to the OS, not to the > 3rd party applications found in the ports tree. If > to use RELEASE (with -p<number> security patches) > or following STABLE depends on your requirements. > OS and installed applications are independent (mostly). > > > > > Are STABLE packages compiled > > from this ports? > > Yes. From time to time, a "snapshot" of the (continuously > evolving) ports tree is used to build the binary > packages. _Which_ set of packages will be requested > by running "pkg_add -r <name>" depends on $PACKAGEROOT. > > For example, if it is set to > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest > it will use the latest packages (which are slightly > behind actual ports in most cases). > > But if > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-release > is used, the packages of RELEASE will be used, such as > you can find them on the installation media > > > > > 3) In case my assumption above is correct; taking in care that > > in a production system it is advisable (handbook) to stay with > > RELEASE, should I avoid updating the ports tree in i.e. a server > > machine? > > That depends on the usage profile of that system. > You should keep track of _any_ security issues you > might have with the ports you use (e. g. web servers, > PHP, MySQL and other "potentially dangerous" stuff). > You can use freebsd-update to follow RELEASE-p<number> > to get the security updates for the RELEASE you are > running. > > If you don't update the ports tree, it will stay at > the date of RELEASE, delivering ports from exactly > that date. It's often the better choice to update > the ports tree and upgrade ports that need this > (as I said before, primarily for security reasons, > as you did mention a production system, where > "bleeding edge" is often _not_ desired). > > > > > What to do with broken ports in this case? > > The RELEASE tree typically doesn't contain broken > ports. If an updated ports tree does, update it > again soon and try again. :-) > > In contrast to portsnap, you can use the "classic > approach" of using csup to update your ports tree. > For smaller deltas, this is acceptable, and it will > deliver you the "freshest" ports tree available. > > > > > Resuming, is there a default way to install-update the software > > keeping ports and binary packages in one piece? > > I don't think so. The desired method depends on your > actual usage requirements. I'd suggest to have a look > at a port management tool such as portmaster or > portupgrade, as both can handle both building from > source and using precompiled binary packages, and > keep track of dependencies and automated upgrades. > > > > > What is > > advisable in general terms for a desktop and what for a server? > > Also depends on your usage model. For example, my > home system is a kind of "install once, then keep > using" installation. I'm running 8.2-STABLE and > ports from an updated tree. For a server, this > approach might not fit - maybe you want to keep > all things binary there, or from source only. > > > > > It will be enough for me if someone just point me to documentation. > > The FreeBSD Handbook. :-) > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > > > ------------------------------ > > Message: 15 > Date: Thu, 29 Dec 2011 18:58:09 +0100 > From: Polytropon <freebsd@edvax.de> > Subject: Re: OT: Root access policy > To: Carl Johnson <carlj@peak.org> > Cc: freebsd-questions@freebsd.org > Message-ID: <20111229185809.0b28e71f.freebsd@edvax.de> > Content-Type: text/plain; charset=3DUS-ASCII > > On Thu, 29 Dec 2011 09:15:45 -0800, Carl Johnson wrote: > > Damien Fleuriot <ml@my.gd> writes: > > > > > On 12/29/11 10:58 AM, Polytropon wrote: > > >> On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: > > >>> For the first time, a customer is asking me for root access to said > > >>> customer's servers. > > >> > > <snip> > > >>> Assuming that I'll be asked to continue administering said servers, > I guess > > >>> I should at least enable accounting... > > >> > > >> You could have better success using sudo. Make sure > > >> the customer is allowed to "sudo <command>". The > > >> sudo program will log _all_ things the customer > > >> does, so you can be sure you can review actions. > > >> Furthermore you don't need to give him the _real_ > > >> root password. He won't be able to "su root" or > > >> to login as root, _real_ root. But he can use > > >> the "sudo" prefix to issue commands "with root > > >> privileges". > > >> > > > > > > "sudo su -" or "sudo sh" and the customer gets a native root shell > which > > > does *not* log commands ! > > > > The sudoers manpage mention the noexec option which is designed to help > > with the first problem. They also show an example using !SHELLS which > > can help with the second. > > It's also worth mentioning "super" again - as an > alternative to "sudo". But after all, if restricted > in any way, both of them are _not_ requivalent to > "full root access" (equals: root + root's password) > which the customer initially demanded. > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > > > ------------------------------ > > Message: 16 > Date: Thu, 29 Dec 2011 10:05:58 -0800 > From: Devin Teske <devin.teske@fisglobal.com> > Subject: RE: OT: Root access policy > To: "'Polytropon'" <freebsd@edvax.de>, "'Carl Johnson'" > <carlj@peak.org> > Cc: freebsd-questions@freebsd.org > Message-ID: <037601ccc654$84d8b950$8e8a2bf0$@fisglobal.com> > Content-Type: text/plain; charset=3D"us-ascii" > > > > > -----Original Message----- > > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- > > questions@freebsd.org] On Behalf Of Polytropon > > Sent: Thursday, December 29, 2011 9:58 AM > > To: Carl Johnson > > Cc: freebsd-questions@freebsd.org > > Subject: Re: OT: Root access policy > > > > On Thu, 29 Dec 2011 09:15:45 -0800, Carl Johnson wrote: > > > Damien Fleuriot <ml@my.gd> writes: > > > > > > > On 12/29/11 10:58 AM, Polytropon wrote: > > > >> On Thu, 29 Dec 2011 04:01:42 -0500, Irk Ed wrote: > > > >>> For the first time, a customer is asking me for root access to > > > >>> said customer's servers. > > > >> > > > <snip> > > > >>> Assuming that I'll be asked to continue administering said > > > >>> servers, I guess I should at least enable accounting... > > > >> > > > >> You could have better success using sudo. Make sure the customer i= s > > > >> allowed to "sudo <command>". The sudo program will log _all_ thing= s > > > >> the customer does, so you can be sure you can review actions. > > > >> Furthermore you don't need to give him the _real_ root password. H= e > > > >> won't be able to "su root" or to login as root, _real_ root. But h= e > > > >> can use the "sudo" prefix to issue commands "with root privileges"= . > > > >> > > > > > > > > "sudo su -" or "sudo sh" and the customer gets a native root shell > > > > which does *not* log commands ! > > > > > > The sudoers manpage mention the noexec option which is designed to > > > help with the first problem. They also show an example using !SHELLS > > > which can help with the second. > > > > It's also worth mentioning "super" again - as an alternative to "sudo". > But > after all, > > if restricted in any way, both of them are _not_ requivalent to "full > root > access" > > (equals: root + root's password) which the customer initially demanded. > > > > I highly recommend reading audit(4) and then audit(8) (in that order). > > This will catch more security instances than simply relying on sudo(8) > logging > -- which won't catch any commands once the user has "become root" (ala > "sudo su > -" for example). > > Once upon a time (RELENG_4), we used a kernel module named "lrexec" which > logged > all system calls to exec(3) family of functions, but it was too verbose. > audit(4) replaces our need for lrexec. > -- > Devin > > > > > > > > -- > > Polytropon > > Magdeburg, Germany > > Happy FreeBSD user since 4.0 > > Andra moi ennepe, Mousa, ... > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > _____________ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete t= he > message and all copies; (ii) do not disclose, distribute or use the messa= ge > in any manner; and (iii) notify the sender immediately. In addition, plea= se > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > > > ------------------------------ > > Message: 17 > Date: Thu, 29 Dec 2011 12:14:08 -0500 > From: Chuck Swiger <cswiger@mac.com> > Subject: Re: Same version on binary packages and updated ports > To: Walter Alejandro Iglesias <roquesor@gmail.com> > Cc: freebsd-questions@freebsd.org > Message-ID: <51AF4F0E-AD5A-4D0A-BC33-4C452B2D1650@mac.com> > Content-Type: text/plain; CHARSET=3DUS-ASCII > > On Dec 29, 2011, at 11:16 AM, Walter Alejandro Iglesias wrote: > > I am giving my firsts steps with FreeBSD. > > Greetings and welcome... > > > In a RELEASE fresh install, after updating the ports using i.e. > > portsnap, the packages downloaded with pkp_add -r are older > > versions respect their port counterparts, leading to > > dependencies issues. So, once the ports tree is updated: > > There are tools like portmaster & portupgrade which help manage > the issue of changing dependencies. > > > 1) Am I forced to compile all? > > Mostly, no. There are a few ports which cannot be made available > as packages, typically due to licensing issues. > > > 2) Should I use STABLE to get the same versions with pkg_add > > than compiling up to date ports? Are STABLE packages compiled > > from this ports? > > -STABLE refers to the FreeBSD OS. There is no such thing as > -STABLE for ports/packages. > > > 3) In case my assumption above is correct; taking in care that > > in a production system it is advisable (handbook) to stay with > > RELEASE, should I avoid updating the ports tree in i.e. a server > > machine? > > The ports tree and the OS aren't directly related. People ought to > be fine running a -RELEASE version of FreeBSD with the latest ports > tree (or packages compiled from the ports tree). > > > What to do with broken ports in this case? > > Fix them? Revert to a working backup? > > > Resuming, is there a default way to install-update the software > > keeping ports and binary packages in one piece? > > portupgrade and portmaster (mentioned earlier) do this. > > They can be told to use precompiled packages in preference to building > locally, and you can even set up a local package repository if you > want to build your own packages with specific options that you prefer. > > > What is advisable in general terms for a desktop and what for a server? > > Well, a casual desktop user tends to upgrade whenever they feel motivated > to, > whereas a server ought to be managed. Part of managing a server is > deciding > when and how often to update it, based on workload, fault-tolerance, > security, > and other concerns. > > You might start by using portaudit, and upgrading ports whenever a securi= ty > issue is noticed with a port that you have installed. > > > It will be enough for me if someone just point me to documentation. > > It's not clear whether you'd read the Handbook? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html > > Regards, > -- > -Chuck > > > > > ------------------------------ > > Message: 18 > Date: Thu, 29 Dec 2011 19:53:25 +0100 > From: Walter Alejandro Iglesias <roquesor@gmail.com> > Subject: Re: Same version on binary packages and updated ports > To: freebsd-questions@freebsd.org > Message-ID: <20111229185325.GA56404@chancha.local> > Content-Type: text/plain; charset=3Dus-ascii > > I really appreciate that you all, Jerry, Polytropon and Chuck, > took your time to answer me. But I think some of you understood > paragraphs like individual-separated statements, that's why you > did not fully understand my question (my horrible English helps > too :-)). > > Let's see if I can explain myself. > > I know that FreeBSD base system and 3rd party are "managed" > separately. For RELEASE I meant the ports included in a fresh > RELEASE install. The scenario is: what to do after a fresh > RELEASE install. Once you updated the ports with 'portsnap fech > extract update' you have newer versions at the port tree. Then > you can upgrade the already installed software using > portupgrade... But compiling! > > Because, to download *binary* packages, both tools, portupgrade > and pkg_add, will download RELEASE, STABLE or CURRENT versions > of software depending on what you put in PACKAGESITE variable. > > So, unless I am missing some portupgrade option-feature, once > the port tree is updated I must compile all from source. The > opposite leads to dependencies issues. > > Walter > > > ------------------------------ > > Message: 19 > Date: Thu, 29 Dec 2011 13:03:01 -0600 > From: Adam Vande More <amvandemore@gmail.com> > Subject: Re: Same version on binary packages and updated ports > To: Walter Alejandro Iglesias <roquesor@gmail.com> > Cc: freebsd-questions@freebsd.org > Message-ID: > <CA+tpaK2Knseb0-_6YjWMGO=3DJm4uR7Y6R-5RTHEKPhuaV6QKVGg@mail.gmail.= com > > > Content-Type: text/plain; charset=3DISO-8859-1 > > On Thu, Dec 29, 2011 at 12:53 PM, Walter Alejandro Iglesias < > roquesor@gmail.com> wrote: > > > So, unless I am missing some portupgrade option-feature, once > > the port tree is updated I must compile all from source. The > > opposite leads to dependencies issues. > > > > portmaster -P > > Yes, this will likely result in a significant amount of compiling dependi= ng > time from RELEASE and your chosen packages and whatever PACKAGESITE is se= t > to eg stable. That is the price you pay for updated software on FreeBSD. > > Also be sure to read /usr/ports/UPDATING > > There are man pages and a handbook page which explain all this in detail. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.htm= l > > -- > Adam Vande More > > > ------------------------------ > > Message: 20 > Date: Thu, 29 Dec 2011 20:28:42 +0100 > From: Walter Alejandro Iglesias <roquesor@gmail.com> > Subject: Re: Same version on binary packages and updated ports > To: freebsd-questions@freebsd.org > Message-ID: <20111229192842.GA71854@chancha.local> > Content-Type: text/plain; charset=3Dus-ascii > > On Thu, Dec 29, 2011 at 01:03:01PM -0600, Adam Vande More wrote: > > That is the price you pay for updated software on FreeBSD. > > > > OK, Adam. That's almost as expected. > > > -- > > Adam Vande More > > > Thanks to all. > > > Walter > > > > > > ------------------------------ > > Message: 21 > Date: Thu, 29 Dec 2011 15:10:46 -0500 > From: "James Edwards" <jedwards@bsdftw.org> > Subject: Re: ZFS upgrade path > To: freebsd-questions@freebsd.org > Message-ID: > <bec004e421a3598cf5bd7fc217e1e62c.squirrel@webmail.bsdftw.org> > Content-Type: text/plain;charset=3Diso-8859-1 > > On Wed, December 28, 2011 12:18, James Edwards wrote: > > > There are four disks, all in a single storage pool - tank. > > > > Here is the naming convention I planned on following after 9.0 is > > released: > > > > tank/9.0 > > tank/9.0/usr > > tank/9.0/var > > tank/9.0/tmp > > and so on > > > > This way, in theory at least, when 9.1 (or 10.0) is released, I can > simply > > create tank/9.1 and the associated data sets, make my changes to /etc a= nd > > /boot, change the zfs bootfs, reboot, and finally upgrade the ZFS pools= . > > > > Is this feasible to do, or are there any caveats/gotchas I'm overlookin= g? > > > > It took some time to do, but I was able to demonstrate within VirtualBox > that this can be done. > > I found it important when creating tank/8.2/usr and tank/8.2/var to > specify 'canmount=3Doff', this way the datasets below it inherit the corr= ect > mountpoints. > > After installing 8.2, I created tank/9.0-RC3, associated datasets and the= n > installed 9.0-RC3 to it. From there, I had to create a loader.conf and > rc.conf, copy the zpool.cache to the dataset, change the bootfs ('zpool > set bootfs=3Dtank/9.0 tank'), change the zfs mountpoints and reboot. Aft= er > I rebooted, I was able to upgrade the zpool to v28. > > While this was done from a minimal clean install, it *should* work from a > system that is using the user-land (as long as the daemons are stopped). > > > > ------------------------------ > > Message: 22 > Date: Thu, 29 Dec 2011 12:11:29 -0800 > From: akshay sreeramoju <akshay.sreeramoju@gmail.com> > Subject: Host Dynamic DNS configuration for 8.2-RELEASE > To: freebsd-questions@freebsd.org > Message-ID: > <CAPiX5QHxQJUOcLc1SH8s3xUXr5yBMnGz=3DaQUTLi7Dw9QhX-GJQ@mail.gmail.= com > > > Content-Type: text/plain; charset=3DISO-8859-1 > > Hi, > > What is the required configuration in a FreeBSD 8.2 release host for it t= o > publish its name in a dynamic dns supported network? > > > LINUX: For a Linux host with name x.y.z.com I had to do the following: > =3D=3D=3D=3D=3D > # echo "DHCP_HOSTNAME=3Dx;" >> /etc/sysconfig/network-scripts/ifcfg-eth0 > # echo "PEERDNS=3Dno" >> /etc/sysconfig/network-scripts/ifcfg-eth0 > # echo "SEARCH=3D\" y.z.com" >> /etc/sysconfig/network > # echo "HOSTNAME=3Dx.y.z.com" >> /etc/sysconfig/network > # reboot > > > SEARCH: Couldnt find for host configuration > =3D=3D=3D=3D=3D=3D=3D > My Google search gave some links describing Linux host configuration but > none for freebsd host configuration. Some described FreeBSD server > configuration though ( > > http://www.google.com/search?hl=3Den&client=3Dfirefox-a&hs=3Dl2M&rls=3Dor= g.mozilla%3Aen-US%3Aofficial&q=3Dconfiguring+dynamic+dns+freebsd+dhcp+clien= t&oq=3Dconfiguring+dynamic+dns+freebsd+dhcp+client&aq=3Df&aqi=3D&aql=3D&gs_= sm=3De&gs_upl=3D13114l14889l0l15039l12l12l0l11l0l0l166l166l0.1l1l0 > , > http://alex.kruijff.org/FreeBSD/Dynamic_DNS.html). > > > TIA, > Akshay > > > ------------------------------ > > Message: 23 > Date: Thu, 29 Dec 2011 21:14:21 +0000 > From: Matthew Seaman <m.seaman@infracaninophile.co.uk> > Subject: Re: Host Dynamic DNS configuration for 8.2-RELEASE > To: freebsd-questions@freebsd.org > Message-ID: <4EFCD82D.5050504@infracaninophile.co.uk> > Content-Type: text/plain; charset=3D"iso-8859-1" > > On 29/12/2011 20:11, akshay sreeramoju wrote: > > What is the required configuration in a FreeBSD 8.2 release host for it > to > > publish its name in a dynamic dns supported network? > > Something like this in /etc/dhclient.conf: > > interface "em0" { > send host-name "foo.example.com"; > } > > See dhclient.conf(5), particularly the EXAMPLES section at the end. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard > Flat 3 > PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate > JID: matthew@infracaninophile.co.uk Kent, CT11 9PW > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 267 bytes > Desc: OpenPGP digital signature > Url : > http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20111229= /6f23987f/signature-0001.pgp > > ------------------------------ > > Message: 24 > Date: Thu, 29 Dec 2011 15:06:17 -0600 > From: Jeffrey McFadden <junkrigsailor@gmail.com> > Subject: very small "workgroup" network > To: freebsd-questions@freebsd.org > Message-ID: > <CAFpTYWNXA3A=3Dbx+EHdD4frgkGkb7ThoMBFoV8pENWX+1a8ph7g@mail.gmail.= com > > > Content-Type: text/plain; charset=3DISO-8859-1 > > I feel really inferior to the community here, but I have to ask because I > simply don't know: > > What do I need to do to create a small (3 PC-BSD) home network? I could = do > this in no time in Windows, but I don't know how to find, configure, and > enable the files necessary to make these machines talk to each other and > allow browsing to shared resources. h The connectivity is in place (each > can access the internet.) > > I've Googled considerably and not found instructions. Just a pointer to > instructions on the web somewhere would be fine. > > Blushing and grateful, > > Jeff > > ><> ><> ><> ><> ><> ><> ><> > <>< <>< <>< <>< <>< <>< <>< > > > ------------------------------ > > Message: 25 > Date: Thu, 29 Dec 2011 14:06:24 -0800 > From: akshay sreeramoju <akshay.sreeramoju@gmail.com> > Subject: Re: Host Dynamic DNS configuration for 8.2-RELEASE > To: Matthew Seaman <m.seaman@infracaninophile.co.uk> > Cc: freebsd-questions@freebsd.org > Message-ID: > <CAPiX5QH80CuxdagTNiEJTZWm8Y19POLVOctMrffSTjRDF4Ya1Q@mail.gmail.co= m > > > Content-Type: text/plain; charset=3DISO-8859-1 > > Thanks Matthew. It works. > > Akshay > > On Thu, Dec 29, 2011 at 1:14 PM, Matthew Seaman < > m.seaman@infracaninophile.co.uk> wrote: > > > On 29/12/2011 20:11, akshay sreeramoju wrote: > > > What is the required configuration in a FreeBSD 8.2 release host for = it > > to > > > publish its name in a dynamic dns supported network? > > > > Something like this in /etc/dhclient.conf: > > > > interface "em0" { > > send host-name "foo.example.com"; > > } > > > > See dhclient.conf(5), particularly the EXAMPLES section at the end. > > > > Cheers, > > > > Matthew > > > > > > > ------------------------------ > > Message: 26 > Date: Thu, 29 Dec 2011 17:27:28 -0500 > From: Mike Jeays <mike.jeays@rogers.com> > Subject: Re: very small "workgroup" network > To: freebsd-questions@freebsd.org > Message-ID: <20111229172728.7fca8281@europa> > Content-Type: text/plain; charset=3DUS-ASCII > > On Thu, 29 Dec 2011 15:06:17 -0600 > Jeffrey McFadden <junkrigsailor@gmail.com> wrote: > > > I feel really inferior to the community here, but I have to ask because= I > > simply don't know: > > > > What do I need to do to create a small (3 PC-BSD) home network? I coul= d > do > > this in no time in Windows, but I don't know how to find, configure, an= d > > enable the files necessary to make these machines talk to each other a= nd > > allow browsing to shared resources. h The connectivity is in place (ea= ch > > can access the internet.) > > > > I've Googled considerably and not found instructions. Just a pointer t= o > > instructions on the web somewhere would be fine. > > > > Blushing and grateful, > > > > Jeff > > > > ><> ><> ><> ><> ><> ><> ><> > > <>< <>< <>< <>< <>< <>< <>< > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > > Look up NFS in the FreeBSD handbook : > http://www.freebsd.org/doc/handbook/network-nfs.html and subsequent > pages. It is as easy as Windows once you find out how, and performance is > excellent. > > > > ------------------------------ > > Message: 27 > Date: Thu, 29 Dec 2011 23:50:56 +0100 > From: Damien Fleuriot <ml@my.gd> > Subject: Re: very small "workgroup" network > To: Jeffrey McFadden <junkrigsailor@gmail.com> > Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> > Message-ID: <769D6625-AEAD-4D4F-B7D2-F407963688E0@my.gd> > Content-Type: text/plain; charset=3Dus-ascii > > > On 29 Dec 2011, at 22:06, Jeffrey McFadden <junkrigsailor@gmail.com> > wrote: > > > I feel really inferior to the community here, but I have to ask because= I > > simply don't know: > > > > What do I need to do to create a small (3 PC-BSD) home network? I coul= d > do > > this in no time in Windows, but I don't know how to find, configure, an= d > > enable the files necessary to make these machines talk to each other a= nd > > allow browsing to shared resources. h The connectivity is in place (ea= ch > > can access the internet.) > > > > I've Googled considerably and not found instructions. Just a pointer t= o > > instructions on the web somewhere would be fine. > > > > Blushing and grateful, > > > > Jeff > > > > First of all there's no need for feeling "inferior", we all started > somewhere. > > Second, Mike already pointed out NFS. > > You may also want to look up SaMBa (CIFS windows-like sharing), and sshfs > (filesystem sharing over ssh). > > ------------------------------ > > Message: 28 > Date: Fri, 30 Dec 2011 09:49:37 +1000 > From: Da Rock <freebsd-questions@herveybayaustralia.com.au> > Subject: Re: Host Dynamic DNS configuration for 8.2-RELEASE > To: freebsd-questions@freebsd.org > Message-ID: <4EFCFC91.5060002@herveybayaustralia.com.au> > Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed > > On 12/30/11 08:06, akshay sreeramoju wrote: > > Thanks Matthew. It works. > > > > Akshay > > > > On Thu, Dec 29, 2011 at 1:14 PM, Matthew Seaman< > > m.seaman@infracaninophile.co.uk> wrote: > > > >> On 29/12/2011 20:11, akshay sreeramoju wrote: > >>> What is the required configuration in a FreeBSD 8.2 release host for = it > >> to > >>> publish its name in a dynamic dns supported network? > >> Something like this in /etc/dhclient.conf: > >> > >> interface "em0" { > >> send host-name "foo.example.com"; > >> } > >> > >> See dhclient.conf(5), particularly the EXAMPLES section at the end. > >> > >> Cheers, > >> > >> Matthew > >> > >> > > > FWIW, I never have to set anything to get it to do this. I use ISC DHCP > and BIND9 for DDNS and all my config is done on the dhcp _server_ > config, not the clients. The clients are simply installed and go... :) > > > ------------------------------ > > Message: 29 > Date: Fri, 30 Dec 2011 09:59:00 +1000 > From: Da Rock <freebsd-questions@herveybayaustralia.com.au> > Subject: Re: mutual forwarders in ISC BIND > To: freebsd-questions@freebsd.org > Message-ID: <4EFCFEC4.6070507@herveybayaustralia.com.au> > Content-Type: text/plain; charset=3DUTF-8; format=3Dflowed > > On 12/29/11 12:45, Kevin Wilcox wrote: > > On Dec 28, 2011 9:26 PM, "Victor Sudakov"<vas@mpeks.tomsk.su> wrote: > > > >> And the reason for the whole thread. One of the customers told me that > >> 8.8.8.8 is faster than our own DNS servers which are located on the > >> same 100 MBit/s LAN with them. I was shocked but it seems true, at > >> least for the answers which are not yet cached. > > That actually makes perfect sense. That's one of the Google DNS IP > > addresses and they see a LOT of traffic, they're probably going to have > the > > majority of the domains your clients want to look up (assuming your > clients > > are like mine and most of their lookups are general web traffic) alread= y > in > > cache - your servers will need to go through the whole lookup process. > > > > Still, after a day or two of use, I would think your servers would have > the > > bulk of what they needed in their caches. You may want to enable loggin= g > to > > see which domains are being looked up (if it won't break any applicable > > laws or policies) and do some spot-checks to see why they may not be in > > your cache. > > > A rather amusing observation would be that they're not in the cache > because the clients are using 8.8.8.8 ... > > > ------------------------------ > > Message: 30 > Date: Thu, 29 Dec 2011 17:35:55 -0700 > From: Chad Perrin <perrin@apotheon.com> > Subject: Re: very small "workgroup" network > To: freebsd-questions@freebsd.org > Message-ID: <20111230003555.GA17278@hemlock.hydra> > Content-Type: text/plain; charset=3Dus-ascii > > On Thu, Dec 29, 2011 at 03:06:17PM -0600, Jeffrey McFadden wrote: > > I feel really inferior to the community here, but I have to ask because= I > > simply don't know: > > > > What do I need to do to create a small (3 PC-BSD) home network? I coul= d > do > > this in no time in Windows, but I don't know how to find, configure, an= d > > enable the files necessary to make these machines talk to each other a= nd > > allow browsing to shared resources. h The connectivity is in place (ea= ch > > can access the internet.) > > > > I've Googled considerably and not found instructions. Just a pointer t= o > > instructions on the web somewhere would be fine. > > It is a little difficult to figure out exactly where to start with some > guidance for how to proceed, because I do not know your circumstances. > > What kind of network hardware do you have, and how much network do you > currently have set up? Do you have only a cable or DSL "modem"? Do you > have a combination router/"modem"? Do you have a router separately from > whatever connection you are using to get to the Internet (or do you even > care about Internet connectivity for this network)? > > Even without a router, you can use a switch and some configuration in the > /etc/hosts files of each system you want on the network, if you do not > need a connection to an external WAN (e.g. the Internet). If you do need > that external connection to the Internet, you'll probably want something > (like a router) that can provide NAT (network address translation), > though there are other ways to achieve such connectivity as well (i.e. > IPv6 configuration), depending on your ISP. > > For network resource browsing, I think sshfs (as mentioned by someone > else already) is probably one of the better options available to you, as > long as you do not need to account for any MS Windows machines being > included in the network browsing capabilities. If you do need to account > for MS Windows, you'll probably want to look into using Samba for NetBIOS > and CIFS -- the protocol basis for MS Windows "workgroup" networking. > > If I had to guess what you have going on, based on what you have said so > far, I would guess you probably have some kind of DSL or cable > router/"modem" device or a DSL or cable "modem" with a separate router > plugged into it, and only PC-BSD machines on the network. In that > situation, I would suggest searching for sshfs resources to set up > network browsing, and using explicit hostname resolution configurations > in the /etc/hosts files of your PC-BSD systems. This should add up to a > reasonably robust, secure, and simple setup once you read up a little bit > on the tools you will use. > > I hope that helps. > > ## NOTES > > I wrote this article a long time ago: > > Use The SSH Filesystem For Secure Network Filesystem Access > http://blogs.techrepublic.com.com/security/?p=3D2589 > > It might be useful if you decide to go the sshfs route. You should be > forewarned, however, that . . . > > 1. I have not looked at that article in a couple years, and can only > guess I was not a complete idiot back when I wrote it. > > 2. TechRepublic has screwed around with its CSS so badly in the > intervening years that some of the formatting is quite badly hosed up in > that article. For instance, the code tags used for formatting code > samples used to do code formatting *only*, allowing them to be used > effectively for both separate code blocks and inline code samples; since > then, in their infinite wisdom, the (relatively new) corporate masters at > CBSi have decreed that code tags will also (via CSS) insert newlines > before and after code samples within code tags. Please remember to take > this into account when reading the article, so that it will make more > sense as presented on that page. For all I know, the way TR's > stylesheets handle code formatting might all change again tomorrow, and > make things even worse. > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > > > ------------------------------ > > Message: 31 > Date: Thu, 29 Dec 2011 22:43:16 -0500 > From: David Jackson <djackson452@gmail.com> > Subject: FreeBSD Kernel Internals Documentation > To: freebsd-questions@freebsd.org > Message-ID: > <CAGy-+i-NN_SOYrrE6WgHyCBa5VzFexwT_C9UYhO3GyjvfsxpAA@mail.gmail.co= m > > > Content-Type: text/plain; charset=3DISO-8859-1 > > I have had an interest in studying the FreeBSD kernel and getting to know > its internals better. After all, in Open source projects, they say, > community contributions are important. > > However, My finding is that due to poor documentation, the FreeBSD kernel > is nearly impenetrable to an outsider. I have been able to find no > comprehensive documentation of kernel internals. I have found it nearly > impossible, due to lack of comprehensive documentation, much of any of th= e > kernel internals. What I see is an internal cliche of developers who are > aware of its myraid of undocumented esoteric secrets, and very little to > actually help anyone else to understand it. > > Any good, well designed software projects will have comprehensive > documentation of the source code, this includes code comments, informatio= n > on what every piece of code does, how the entire system fits together, an= d > descriptions of every variable and function. Any well run project would > insist that code contributors upload full and comprehensive documentation > of how their source code is written, how it works, etc. > > Documentation is vital and good practice because it saves time, it preven= ts > people new to the project having to waste immense amounts of time trying = to > figure out a vast and cryptic puzzle. Without good documentation software > can be nearly useless, unmaintainable and difficult for an outsider to > learn, to the point where it may actually take less time to just throw it > out and start from scratch. > > These are reasons that FreeBSD needs better documentation, documentation = of > how the entire system fits together, what lines of code do, the purpose o= f > variables and functions, etc, in descriptive English. This is key to > developing maintainable software. > > I saw where someone automatically generated "documentation" with Doxygen. > This is nearly useless, because all it shows is a huge list of functions > and variables but does not include any text on what they do. At best, > Doxygen can only provide a template for documentation that can be filled = in > with descriptive English information on what everything does. > > One idea might be to have an official wiki that contains the template > generated by Doxygen which can then be filled in. When changes to the > source code is made, it is good practice for the commiter of such changes > to document their code as it is submitted. > > This allows others who come along who need to maintain the code to more > easily understand what the code does. > > Another idea which would also improve the useability of FreeBSD would be = to > have a wiki which would be updated by kernel contributors whenever they a= dd > support for a certain piece of hardware. This would make finding hardware > compatability information easier from one central, up to date and current > source of information. > > These documentaiton ideas, for commiters to document their code when they > upload it, and document their hardware support additions, are just good > software practices that should be highly recommended and encouraged > > > ------------------------------ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > End of freebsd-questions Digest, Vol 395, Issue 6 > ************************************************* >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFpTYWOxtddrOof1MM-LAS2LdYWbNsMj4yoneiOUdPkAiKPH5A>