Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Networking Operating Systems BSD Entertainment Games

FreeBSD Based Gaming Router 240

Zaphoid writes "Lan Game Reviews has posted an article on how to use an old computer and FreeBSD distro m0n0wall to create a gaming router. Gaming routers allow users to use their full bandwidth for downloads and other high bandwidth apps, and low latency applications at the same time. By keeping packet queues on the router side, rather than the modem side. Users are able to achive great pings in online games, while fully using their download bandwidth. This is a great alternitive to expensive gaming routers on the market today."
This discussion has been archived. No new comments can be posted.

FreeBSD Based Gaming Router

Comments Filter:
  • Re:Double standard (Score:5, Informative)

    by KnightMB ( 823876 ) on Sunday July 31, 2005 @10:11PM (#13210852)
    Gaming routers are under $100, so unless you already have an old PC, it's cheaper just to get the gaming router and not have to worry about building your own. Plus, what about wireless access? That seems to come with every gaming router today, so even the hardware cost kind of outweigh this approach. I'll stick with my D-Link DGL-4300 router, it's small, uses less power, no noise, has wireless access, and a ton of other features that I'll never use.
  • m0n0wall (Score:5, Informative)

    by tymbow ( 725036 ) on Sunday July 31, 2005 @10:35PM (#13210964)
    Guys (and the few but very welcome gals), before we all start flaming about how hard it is to set up OpenBSD/FreeBSD and a firewall for a newbie, please take a look at the m0n0wall site. m0n0wall is completely self contained and is very easy to set up. It is completely web interface driven and is managed in much the same way as a consumer broadband router is. m0n0wall is, in my humble opinion having used it for a number of years and loveing it, and excellent firewall product and is very capable. If you have not seen it, grab a copy and have a look. Cheers, Tim.
  • Comment removed (Score:3, Informative)

    by account_deleted ( 4530225 ) on Sunday July 31, 2005 @10:47PM (#13211019)
    Comment removed based on user account deletion
  • Re:pf.conf ruleset (Score:2, Informative)

    by Anonymous Coward on Sunday July 31, 2005 @10:56PM (#13211050)
    http://www.benzedrine.cx/ackpri.html [benzedrine.cx]

    That should do it. I've been using ack prioritization since a couple months after the artitcle was released. I've noticed recently that I still get good pings when torrenting and playing RTCW:ET.

    Have fun.

    Beware TPB
  • Re:pf.conf ruleset (Score:1, Informative)

    by Anonymous Coward on Sunday July 31, 2005 @11:02PM (#13211075)
    pf can do this very very well.
    i dont know example links, but let me give you some pointers.

    think about the type of traffic thats bad for gaming and the type thats good.

    make a queue for ack packets and traffic to known ports for your games, and give it higher priority, and then make a queue for ftp/bit torrent/http,etc and give it low priority.

    if you google you can find info on ports that games like wow/counterstrike/doom/quake/etc use and play with it a bit.

    also, make a queue for your gaming machine and give that top priority if that applies to you.

    good luck hope this helps.
  • by raistphrk ( 203742 ) on Sunday July 31, 2005 @11:05PM (#13211087)
    While I'm all about the FreeBSD solution here (m0n0wall is a great package), the idea of using a hub instead of a switch is just asinine. In a gaming environment, where bandwidth is critical and having delays in play can make the difference between a frag and getting fragged, having seperate collision domains is a must. A gaming network should use switches to ensure that collisions won't affect gameplay.
  • by Kiaser Wilhelm II ( 902309 ) <slashpanada@gmail.com> on Sunday July 31, 2005 @11:34PM (#13211203) Journal
    i doubt it. really expensive routers have custom ASICs that are designed specifically for ROUTING. the latency of your PC box router vs a real Cisco or Juniper router will be noticed when you put it into production in a major backbone.

    there is a reason why these companies put R&D effort into making custom hardware for routers.. just becuase you can do the same functions in software doesn't mean its just as good.
  • Firmware? 66Mhz? (Score:3, Informative)

    by cbreaker ( 561297 ) on Sunday July 31, 2005 @11:40PM (#13211221) Journal
    You do realize that firmware is just software on embedded devices? It's usually stored in some sort of non-volatile memory. This doesn't make it any faster then software stuck on a hard or floppy disk.

    And That Old Pentium's 66Mhz backplane is so much more then enough to push around a cablemodem's maximum throughput.

    If you actually read the article, you'd see that this is a distribution of one of the BSD's that is trimmed down and web-interfacified making it extremely easy to install and configure. Install two network cards, load up the CD, and you're pretty much good to go. I don't think installing some network cards is a big deal for a lot of gamers that build their own machines.
  • For this project, I recommend no less than a 486DX2 133Mhz processor with 64 megs of ram

    Because there sure is a lot wrong with asking for a 486 DX2 133MHz. Ain't no such thing exist.

    First, saying that the chip is a DX2 implies that the motherboard opperated at a 66MHz bus speed, which no 486 had the blessing to experience (66MHz bus speeds didn't happen until the Pentium line). The 2 in DX2 implied that the CPU operated at a frequency twice that of the bus speed (DX2 66MHz = 33MHz bus speed). There were certainly DX4s though, where the CPU frequency was 3x that of the bus speed (why it wasn't the DX3, I don't know). DX4 75MHz (25 MHz bus) and 100MHz (33MHz bus).

    Second, the only chip manufacturer ever to release a 133MHz 486 processor was AMD (a true DX4, 33MHz x 4), and by that time, but the Pentium left all 486s in their dust. There was no market for it, and it was laid out to pasture. I doubt anybody still has one running. Well, perhaps except for these guys [totl.net].

  • by YCrCb ( 707622 ) on Sunday July 31, 2005 @11:49PM (#13211249)
    T-3 at work. Shared among 3 sites. No special queue or anything else. 37Mb/s for 28 minutes.
    Router is FreeBSD 4.11, PIII 450 with 2 3COM 3C905B's Around 1100 lines in ipf rule set. Not very well optimized, I have 1 group. I have NAT enabled, but this is not using NAT.

    Does this help for some numbers?
  • The Real Issue.. (Score:2, Informative)

    by jmilezy ( 904134 ) on Sunday July 31, 2005 @11:51PM (#13211253)
    The real issue with these kinds of routers is the fact that the cable/dsl modems themselves are not interactive once their data queue becomes filled. Sure, traffic shapers are execellent and I've read http://lartc.org/howto/ [lartc.org] which has great information for linux. Cable/DSL connections are asymetrical, and when you send data from your pc to the actual cable modem, you send it at 10/100megbit (whatever speed the nic in your pc and cable modem agree on) Your ISP will limit you to 512kBit upload for example. The modem cannot send data to your ISP as fast as you can send it to your modem thus the data queue fills very fast and your modem has trouble keeping up. These shapers can simply slow down the rate at which your PC sends data to the modem and thus stopping the filling of the data queue in the modem which will allow it to be more interactive. That is the biggest problem you'll have with cable/dsl connections for a few users. Sure, more detailed protocol based shaping can and should be used to reserve bandwidth on a larger scale.
  • Re:Double standard (Score:2, Informative)

    by Anonymous Coward on Monday August 01, 2005 @12:09AM (#13211305)
    >lol what? a simple home router doesn't need that horsepower or memory.

    Evidently they do or there wouldnt be much of a market for higher preformance gaming routers with 200mhz processors and 32MB of ram ....

    >we're talking about very meager amounts of data, very little CPU usage, and very little buffering.

    You're deluding yourself, pushing the amount of packets you can over a decent broadband connection preforming address translation, and any kind of moderatly sophisticated firewalling or queueing is pretty intensive, the load can be minimized by using ASICs (and in the future linksys being now a subsidary of CISCO we may see this) but were talking a commodity embeded processor, and not very fast ones at that (the gaming routers are of course better but still no match for a full blown microprocessor)

    >what do you think your $100 pentium II machine is? its mass produced too.
    Sure its mass produced that was a poor selection of words on my part, its not an *emebeded* microprocessor though, with lower clock speeds, less cache, granted they are optimized for lower power consumption and heat there is no such thing as a free lunch.

    >considering that linksys routers run Linux, there isn't anything you can't do with one of those that you could do with your stupid electricity hog, in terms of routing.

    You can install a harddrive ? or do you like burning out flash drives/cards quickly ? I speciffically mentioned caching ... lots of writes. And TFA is about FreeBSD, linux in my experiance has subpar firewalling and queuing features see: http://www.openbsd.org/faq/pf/index.html [openbsd.org]

    I use what was at some point a HP pavillion with a
    second generation celeron, running @ 500mhz with 256mb of ram saved from the trash (free) and a couple of intel 10/100 nics.($0.99 on ebay, shipping was $8) It has a 100 watt power supply, the chip has no fan on the heat sink the tiny power supply fan keeps it very cool, it has a harddrive a 4500rpm plain old ide harddrive. I would be willing to wager that it draws only slightly more power than one of those linksys gamming routers, and is at least twice as fast to boot. We have 5 very heavy computer users sharing a standard cable link, not once has anyone complained about slowness, even with 3 of them playing MMORPGs and two of those same idiots also using various P2P apps.
  • by adrianmonk ( 890071 ) on Monday August 01, 2005 @12:56AM (#13211453)
    I have a hard time believing that using a PC to do routing will be faster than using custom hardware.

    Who on earth said anything about it being faster? My guess is that the performance difference between dedicated hardware and PC is quite negligible. All the article said was that you can do quality-of-service queueing with regular PC hardware pretty easily, and that if you already have a spare PC, that's cheaper than buying dedicated hardware for the purpose. As far as I know, the article didn't claim that a PC was any better at the job than dedicated hardware; it just claimed that routing with quality-of-service is better than routing with it.

    Getting back to the subject of performance for a moment, the low bandwidth involved in most home network connections (even if they are called "broadband") is so small that just about any computer that can run current software can handle it. Remember, computers are built to move hundreds of megabytes around in a second, and we are only talking about fractions of a megabyte.

    That leaves only the issue of latency. But, on regular 10 megabit ethernet, a full-size 1536 byte frame can transmit in not much longer than 1 ms. Lots of fancy routing hardware is built so it can figure out how to retransmit a packet before the entire packet has been received, so a router could in theory add less than 1 ms of latency on 10 megabit ethernet. But even if your PC receives the whole packet and then waits a whole extra millisecond before starting to retransmit it, you've still only added 2 ms of latency, which is really not that much. At least, on my cable modem, if I ping the local university, my latency averages about 125 ms. How big of a deal is it if I had 2 ms to that?

    For what it's worth, I just did two ping tests to test how much latency going through a PC does add. I first pinged the local university from my firewall machine, which is a 600 MHz Athlon running Solaris 8. The lowest ping time recorded was 9 ms. Then, I pinged the same machine from a Mac that sits inside the firewall, so that the Solaris 8 machine is routing the ICMP packets it was (in the previous test) originating. The result? The lowest ping time recorded for the Mac going through the Solaris machine was 9.178 ms. It's hard to say since the Solaris machine doesn't measure in fractions of a millisecond, but the point is that ping times were not increased dramatically. In fact, it appears to be less than one millisecond difference.

  • Comment removed (Score:3, Informative)

    by account_deleted ( 4530225 ) on Monday August 01, 2005 @12:58AM (#13211462)
    Comment removed based on user account deletion
  • Re:wtf? (Score:3, Informative)

    by ArbitraryConstant ( 763964 ) on Monday August 01, 2005 @02:00AM (#13211713) Homepage
    "you still have the TCP/IP traffic to deal with so that packets get TO the game."

    Stateful firewalls know all they need to know about TCP/IP to handle packets on a per-connection level. The game is running on another system, so the firewall need only needs to get a packet out onto the appropriate interface. I know PF can do this at the firewall level (see the fastroute keyword). Even if it does have to use the network stack (IPFW or IPF might not be able to route independantly, I'm not sure) FreeBSD can route packets very quickly[1].

    "If you RTFA this "game router" is really only adding traffic shaping/prioritization, which is something a middle of the road router can do anyway in FIRMWARE which will be lots faster than that software."

    Firmware is software that gets loaded onto a general purpose processor. Usually ARM or MIPS for broadband routers, IIRC. It doesn't matter whether it comes from an EEPROM, a flash memory chip, or a hard drive. Once it's in memory it's pretty much the same. The traffic shaping available with this will be a lot more configurable, and they wrapped the OS up into an easy-to-use distribution. It's not unusual for gamers to have unused computers sitting around, given their upgrade cycle, so it would be cheaper to use this if you have the hardware.

    "Also you have to use good NICs (more $$$) on the old PC, which if it is an ISA bus PC good luck finding them, and if you find then you still got a 66MHz backplane in that old Pentium."

    How many spare NICs do you have? Be honest. Until they started putting them on the motherboard most computers had one and whenever the computer died the NIC was always left over.

    Pretty much any NIC will do for the purposes of broadband routing. The 66 mhz bus on a Pentium is also more than you need. A 486 can handle it. I've used a 486 with ISA NICs as a firewall on a cable modem with 5 megabits downstream bandwidth.

    "There are lots of complexities here, it's not something your average gamer is going to build."

    An easy to use package that runs on PCs a gamer already has? All they need to do is add a NIC or two? When they spend half their time putting in new video cards and RAID arrays on their other PC? When it'll save them enough money to get more game hardware? Sounds pretty plausible to me.

    1 - http://people.freebsd.org/~andre/FreeBSD-5.3-Netwo rking.pdf [freebsd.org] - FreeBSD 5.3 can route 1m packets per second on a 2.8 ghz Xeon, while it's doubtful it would have to do about 1/10000 that for a cable modem on a computer about 1/50 as fast.
  • Try openwrt (Score:4, Informative)

    by speck ( 29023 ) on Monday August 01, 2005 @05:26AM (#13212350)
    http://www.openwrt.org/ [openwrt.org]

    It's the most open of the alternativesd, last I looked. Not necessarily great for the lazy, though, since it will want some hand-configuring.

I've noticed several design suggestions in your code.

Working...