Re: Linux vs FreeBSD: wlan-cards
On Mon, 13 Sep 2004 21:01:26 +0200 "Florian Hengstberger" <[EMAIL PROTECTED]> wrote: > Hi! > > I know I posted a similar question two days ago, sorry - I?m > still in trouble with finding a proper wlan-card. > The hardware "database" on the freebsd-site did not help me: > most cards are either not avaiable in Austria or simply to > expensive. > > So my question is: > Has anybody found a cheap wlan-card running under freebsd? > I bet that most experienced users have a wlan card working. > What about the cheap d-link and netgear cards, is the prism-chipset > supported? > > (Sorry, but that?s a very important to me: I think of > changing to FreeBSD from Linux and both OS are now competing! > I want to give both a fair chance in hardware-questions.) Like some one else said, man wi. Also when 5.3 hits stable you will have the ability to make use of ndis stuff drivers for it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Linux vs FreeBSD: wlan-cards
> -Original Message- > From: Florian Hengstberger [mailto:[EMAIL PROTECTED] > Sent: Monday, September 13, 2004 12:01 PM > To: FreeBSD mailinglist > Subject: Linux vs FreeBSD: wlan-cards > > > Hi! > > I know I posted a similar question two days ago, sorry - I?m > still in trouble with finding a proper wlan-card. The > hardware "database" on the freebsd-site did not help me: most > cards are either not avaiable in Austria or simply to expensive. > > So my question is: > Has anybody found a cheap wlan-card running under freebsd? > I bet that most experienced users have a wlan card working. > What about the cheap d-link and netgear cards, is the > prism-chipset supported? > > (Sorry, but that?s a very important to me: I think of > changing to FreeBSD from Linux and both OS are now competing! > I want to give both a fair chance in hardware-questions.) > > Thanks in advance > Florian > man wi will give you a pretty good list of supported cards dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linux vs FreeBSD: wlan-cards
ive been looking for this too im about to order netgear wg511t and wg311t cards from the google searches ive done they look to be supported Arden On Mon, 2004-09-13 at 20:01, Florian Hengstberger wrote: > Hi! > > I know I posted a similar question two days ago, sorry - I?m > still in trouble with finding a proper wlan-card. > The hardware "database" on the freebsd-site did not help me: > most cards are either not avaiable in Austria or simply to expensive. > > So my question is: > Has anybody found a cheap wlan-card running under freebsd? > I bet that most experienced users have a wlan card working. > What about the cheap d-link and netgear cards, is the prism-chipset > supported? > > (Sorry, but that?s a very important to me: I think of > changing to FreeBSD from Linux and both OS are now competing! > I want to give both a fair chance in hardware-questions.) > > Thanks in advance > Florian > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Upgrading (was) Re: Linux vs. FreeBSD
On Thu, 24 Oct 2002, Roger 'Rocky' Vetterberg wrote: > An upgrade consists of the following commands: > 'cvsup -g -L2 stable-supfile && cd /usr/src/ && make buildworld && > make buildkernel KERNCONF=whatever && make installkernel > KERNCONF=whatever && make installworld && reboot' > Theoretically you could just paste those lines into a shellscript, > make a crontab entry and be done Nope. If you're tracking -STABLE, an upgrade isn't guaranteed to be automatable like this - you should check /usr/src/UPDATING. You're also missing any calls to mergemaster to update your configuration files. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ Rereleasing dolphins into the wild since 1998. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Linux vs. FreeBSD
how funny. i'm having the exact same problem at my school. this debate will never cease. :) Charles Pelletier Tech. Coordinator St Luke's School - Original Message - From: "Bsd Neophyte" <[EMAIL PROTECTED]> To: "Derrick Ryalls" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, October 24, 2002 5:56 PM Subject: Re: Linux vs. FreeBSD > > --- Derrick Ryalls <[EMAIL PROTECTED]> wrote: > > I don't want to start a Linux/FreeBSD flamewar, but I do need some info > > > > I have an associate who will be making major changes to their network > > and want my help/advice. He intends to have a something like this: > > > > Web server (Public IP) > > inet - router( Public IP) --- / > >\DMZ (Private IPs) > > > > > > The DMZ will house his mail, misc. servers and workstations. > > > > They might use some CISCO equipment for the router but it would limit > > them to 10mbs, and he would rather have 100mps. > > > > His first thought besides CISCO was Linux, as some of his clients use > > Linux and it is a good idea to use what your clients use. I have almost > > zero experience with Linux, but I am a FreeBSD fan, so naturally, I > > recommended it to him. I tried to give him some of the > > benefits/hinderances to using either, but I am not well enough versed in > > Linux to give good data. > > > > I was hoping someone on this list might have real data/reasons to use > > one or the other. Valid concerns are: security, compatibility, > > stability, flexibility, support, etc. > > > > Some concerns I have with Linux are the variety of distros available for > > Linux, even if clients are using it, which ones are they using, etc. > > Also, I am naturally biased to FreeBSD because I have used it for quite > > a while. > > > i feel i have to be the voice of disent here. personally i feel that a > router is made to route packets, if cost is an issue then go with a > FreeBSD box, but if you can spend a few dollars, get something that was > designed to route packets. > > first of all your concern with the cisco's routers are unfounded. > > your friend can get a 2620 which has 1 100bT port and a 2621 which has > two. Cisco routers are not limited to 10bT connections. even 1700-series > routers allow have 100bT ports. you'll find some decent deals on ebay, > and cisco support is second to none. > > as for your DMZ... i doubt you'd want to expose your private network to > the public. you'd be better off opening the standard ports for whatever > services you need than allowing unresticted access to your internal network. > > __ > Do you Yahoo!? > Y! Web Hosting - Let the expert host your web site > http://webhosting.yahoo.com/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Linux vs. FreeBSD
--- Derrick Ryalls <[EMAIL PROTECTED]> wrote: > I don't want to start a Linux/FreeBSD flamewar, but I do need some info > > I have an associate who will be making major changes to their network > and want my help/advice. He intends to have a something like this: > > Web server (Public IP) > inet - router( Public IP) --- / >\DMZ (Private IPs) > > > The DMZ will house his mail, misc. servers and workstations. > > They might use some CISCO equipment for the router but it would limit > them to 10mbs, and he would rather have 100mps. > > His first thought besides CISCO was Linux, as some of his clients use > Linux and it is a good idea to use what your clients use. I have almost > zero experience with Linux, but I am a FreeBSD fan, so naturally, I > recommended it to him. I tried to give him some of the > benefits/hinderances to using either, but I am not well enough versed in > Linux to give good data. > > I was hoping someone on this list might have real data/reasons to use > one or the other. Valid concerns are: security, compatibility, > stability, flexibility, support, etc. > > Some concerns I have with Linux are the variety of distros available for > Linux, even if clients are using it, which ones are they using, etc. > Also, I am naturally biased to FreeBSD because I have used it for quite > a while. i feel i have to be the voice of disent here. personally i feel that a router is made to route packets, if cost is an issue then go with a FreeBSD box, but if you can spend a few dollars, get something that was designed to route packets. first of all your concern with the cisco's routers are unfounded. your friend can get a 2620 which has 1 100bT port and a 2621 which has two. Cisco routers are not limited to 10bT connections. even 1700-series routers allow have 100bT ports. you'll find some decent deals on ebay, and cisco support is second to none. as for your DMZ... i doubt you'd want to expose your private network to the public. you'd be better off opening the standard ports for whatever services you need than allowing unresticted access to your internal network. __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: Linux vs. FreeBSD
W. D. writes: > At 20:39 10/23/2002, Dan Pelleg, wrote: > >FreeBSD systems are easy to maintain. You can do a source upgrade, > >or a binary upgrade, and the system will go through it and boot > >to the new version without a hitch. On one system I have I've gone from > >FreeBSD 4.1 to 4.7, including every release in between, without ever > >touching the console. When a major version comes out, I typically > >upgrade 10 systems in multiple locations, all within half a day > >without leaving my office. > > Pray tell, how do you do this? > 1. cvsup to update the system sources. 2. look at /usr/src/UPDATING and follow instructions. (do not forget the mergemaster step!). The "drop to single user mode" step can be skipped, at your own risk, which my experience proves to be acceptable when the machine is not too busy. Read all about it in the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html (do not be alarmed by the name - the same method is used for the security patches, as well as going from one release to the next, so it's as stable as anything you get on a CD-ROM; of course you can use this method to track -STABLE, which may occasionally not be, and rebuild your kernel and world nightly; whatever suits your needs). -- Dan Pelleg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Linux vs. FreeBSD
W. D. wrote: At 20:39 10/23/2002, Dan Pelleg, wrote: FreeBSD systems are easy to maintain. You can do a source upgrade, or a binary upgrade, and the system will go through it and boot to the new version without a hitch. On one system I have I've gone from FreeBSD 4.1 to 4.7, including every release in between, without ever touching the console. When a major version comes out, I typically upgrade 10 systems in multiple locations, all within half a day without leaving my office.> Pray tell, how do you do this? Start Here to Find It Fast!© -> http://www.US-Webmasters.com/best-start-page/ I can confirm that this is in fact possible, and not even difficult to accomplish. My home machine has gone from FreeBSD 2.2.8 to 4.7 without reinstall, and I disconnected the monitor and keyboard somewhere around 3.3. An upgrade consists of the following commands: 'cvsup -g -L2 stable-supfile && cd /usr/src/ && make buildworld && make buildkernel KERNCONF=whatever && make installkernel KERNCONF=whatever && make installworld && reboot' Theoretically you could just paste those lines into a shellscript, make a crontab entry and be done, but I do recommend that you add some error checking and maybe some interaction with the user. Of course, this should _not_ be used on production or otherwise heavy loaded machines. Doing install in single user is recomended, but a box with very low loads will probably do it just fine running multi user. Ive used this method for years (allthough not added to cron but started manually when I think it's needed) and it has only failed me once. When going from 4.6 to 4.7 I had to do a reboot between installkernel and installworld, or the system would fail with a lot of weird memory errors. Luckily, I always update my testmachine first, so when the time came to update the "real" machine I was aware of this and avoided the problem. -- R To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Linux vs. FreeBSD
"Derrick Ryalls" <[EMAIL PROTECTED]> writes: > I have an associate who will be making major changes to their network > and want my help/advice. He intends to have a something like this: > > Web server (Public IP) > inet - router( Public IP) --- / >\DMZ (Private IPs) > > > The DMZ will house his mail, misc. servers and workstations. I'm no networking expert, but that doesn't sound like a DMZ to me. Sounds like your "private" network. Except I'm not sure how private it is on the same network as the Web server. I was told to use: /-DMZ (with public services) | inet --- (router+filter) [with three NICs] | \-PrivateZone (with private services) If someone cracks one of your buggy public serviers, they're still "outside" the firewall. The router+filter is easily handled by a 486/66 at 10Mbps; I don't know about 100. Any Unixy OS should do the job OK in all but a few cases, though different people have favorites for different reasons which I'm not able or willing to delve into. All have good, stateful filters available. They probably all have ways of booting the router/filter's software off a floppy or CDROM (picoBSD, for FreeBSD). I suppose familiarity is the most important factor. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: Linux vs. FreeBSD
At 20:39 10/23/2002, Dan Pelleg, wrote: >FreeBSD systems are easy to maintain. You can do a source upgrade, >or a binary upgrade, and the system will go through it and boot >to the new version without a hitch. On one system I have I've gone from >FreeBSD 4.1 to 4.7, including every release in between, without ever >touching the console. When a major version comes out, I typically >upgrade 10 systems in multiple locations, all within half a day >without leaving my office. Pray tell, how do you do this? Start Here to Find It Fast!© -> http://www.US-Webmasters.com/best-start-page/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Linux vs. FreeBSD
From: "Dan Pelleg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, October 23, 2002 8:39 PM Subject: RE: Linux vs. FreeBSD > > As has been said, the clients don't care much what the router is > running as long as it handles the packets correctly. > > I would strongly recommend FreeBSD for this and this is based on my > experience in a mixed FreeBSD/Linux shop. > > FreeBSD has excellent support for intelligent and traditional > packet filtering. ipfw can do all of the following: > - header-based filtering > - stateful filtering > - bandwidth shaping (make sure some server doesn't use more > than N bits/second, or even make sure no one server hogs the > entire bandwidth) - via dummynet > - "limit" rules (cap the number of connections a particular > server can have open at any given time) > > And all of these can be applied to either the internal, external, > or DMZ networks. NAT is also supported. > > I'm sure Linux has similar capabilities. But with FreeBSD you get > them in the base system - no need to go hunt for tarballs or > kernel patches (see below more on stability). > > As far as security is concerned, FreeBSD's record is excellent. When > people say "Linux" they often mean "Red Hat", who seem to have > a major mis-configuration problem and virus/worm attacks with every > single version they put out. I am sure there are Linux distros that > fare better on security but they rarely the advantages that Red > Hat is enjoying (these being support and large user base). > > FreeBSD systems are easy to maintain. You can do a source upgrade, > or a binary upgrade, and the system will go through it and boot > to the new version without a hitch. On one system I have I've gone from > FreeBSD 4.1 to 4.7, including every release in between, without ever > touching the console. When a major version comes out, I typically > upgrade 10 systems in multiple locations, all within half a day > without leaving my office. > > When security advisories come out, they are published quickly, and yet give > accurate description of the problem and its impact, letting you make an > informed decision. They also provide tested workarounds and pointers to > source and binary patches, which make your life as administrator > easy. Again, being on both the FreeBSD and Red Hat security advisory > mailing-lists, I can tell you none of these points are to be taken for > granted for even the biggest and most trusted vendor. > > Linux and its various distros has its merits and is certainly a system of > choice for certain uses. But if your time and sanity are worth anything to > you, you'd better put FreeBSD on this system. > > -- > Dan Pelleg I'd second a great deal of this. When I was first introduced to what lay behind the Internet, everyone was talking about the Penguin, but I've discovered that FreeBSD has a richer background, classic roots, and extremely confident and competent individual users and maintainers who go an extra mile to make it a top-notch server OS. Kudos to all! Kevin Kinsey To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: Linux vs. FreeBSD
As has been said, the clients don't care much what the router is running as long as it handles the packets correctly. I would strongly recommend FreeBSD for this and this is based on my experience in a mixed FreeBSD/Linux shop. FreeBSD has excellent support for intelligent and traditional packet filtering. ipfw can do all of the following: - header-based filtering - stateful filtering - bandwidth shaping (make sure some server doesn't use more than N bits/second, or even make sure no one server hogs the entire bandwidth) - via dummynet - "limit" rules (cap the number of connections a particular server can have open at any given time) And all of these can be applied to either the internal, external, or DMZ networks. NAT is also supported. I'm sure Linux has similar capabilities. But with FreeBSD you get them in the base system - no need to go hunt for tarballs or kernel patches (see below more on stability). As far as security is concerned, FreeBSD's record is excellent. When people say "Linux" they often mean "Red Hat", who seem to have a major mis-configuration problem and virus/worm attacks with every single version they put out. I am sure there are Linux distros that fare better on security but they rarely the advantages that Red Hat is enjoying (these being support and large user base). FreeBSD systems are easy to maintain. You can do a source upgrade, or a binary upgrade, and the system will go through it and boot to the new version without a hitch. On one system I have I've gone from FreeBSD 4.1 to 4.7, including every release in between, without ever touching the console. When a major version comes out, I typically upgrade 10 systems in multiple locations, all within half a day without leaving my office. When security advisories come out, they are published quickly, and yet give accurate description of the problem and its impact, letting you make an informed decision. They also provide tested workarounds and pointers to source and binary patches, which make your life as administrator easy. Again, being on both the FreeBSD and Red Hat security advisory mailing-lists, I can tell you none of these points are to be taken for granted for even the biggest and most trusted vendor. Linux and its various distros has its merits and is certainly a system of choice for certain uses. But if your time and sanity are worth anything to you, you'd better put FreeBSD on this system. -- Dan Pelleg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Linux vs. FreeBSD
Hi Derrick, On Wed, Oct 23, 2002 at 01:17:10PM -0700, Derrick Ryalls wrote: > I don't want to start a Linux/FreeBSD flamewar, but I do need some info > > I have an associate who will be making major changes to their network > and want my help/advice. He intends to have a something like this: > > Web server (Public IP) > inet - router( Public IP) --- / >\DMZ (Private IPs) > > > The DMZ will house his mail, misc. servers and workstations. > > They might use some CISCO equipment for the router but it would limit > them to 10mbs, and he would rather have 100mps. > > His first thought besides CISCO was Linux, as some of his clients use > Linux and it is a good idea to use what your clients use. I have almost > zero experience with Linux, but I am a FreeBSD fan, so naturally, I > recommended it to him. I tried to give him some of the > benefits/hinderances to using either, but I am not well enough versed in > Linux to give good data. > > I was hoping someone on this list might have real data/reasons to use > one or the other. Valid concerns are: security, compatibility, > stability, flexibility, support, etc. > > Some concerns I have with Linux are the variety of distros available for > Linux, even if clients are using it, which ones are they using, etc. > Also, I am naturally biased to FreeBSD because I have used it for quite > a while. Well, first of all, on a router, it doesn't really matter what the clients are using, they should never "see" the router anyway. So really I would just think about what a router does, and wich one (Linux or BSD) would best suit the task. Linux and BSD both have excellent routing capabilities, no doubt. I think the main thing to consider here is the firewall, since as I understand it, that's the point where Linux and BSD begin to differ. I am not too familiar with FreeBSD ipfw capabilities, (Or firewall's in general), but I suggest that what's you take a look at to determin what will be best for the job. Does your client need a statefull firwall? I know Linux can do this with the 2.4 kernel, can FreeBSD? (I would assume so)... Also, another concer for a router is security updates. The BSD's have very good security update proceedurs, (Maybe you should use OpenBSD?), some Linux distro's are *very* good about this as well, especially Debian. Just some things to consider. - Nick Jennings - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
