Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #1634
| From | orcus@pwr.wroc.pl |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: buying a router or using router in kernel |
| Date | 2012-08-29 16:55 +0000 |
| Organization | Politechnika Wroclawska |
| Message-ID | <slrnk3sia4.a5j.orcus@orcus.wcss.wroc.pl> (permalink) |
| References | <MPG.2aa33fe2df2234ff989687@nntp.aioe.org> <503e2cbb$0$6904$e4fe514c@news2.news.xs4all.nl> |
On 2012-08-29, Simon Quantrill <simon.quantrill@gmail.com.invalid> wrote: > On 2012-08-25 19:03:16 +0000, david nnaemeka said: > >> Which is better, buying a router and learning a new set of commands or >> using the router in the linux kernel? >> I really don't know what considerations one has to outline for making a >> decision. Can anyone give me some and point to what direction is >> simpler, cost effective and qualitative? >> tnx > > They are both the samething routing in linux kernel and routing on a > router is practially the same thing. It's true only for SOHO routers. In linux box decision how to handle incoming packet is made by kernel code. It depends on data provided by various userspace daemons which set routing table and firewall rules. At the time software(kernel included) eats all its resources(heavy trafic, ddos, etc.) kernel don't have a chance to run "routing code". Often there are problems even in lower layer - linux cannot handle getting packets from interface when there is a lot of inbound packets. There was some enhancements in networking kernel code last years, but its still fully software based. I think it will always be in desktop machines since they have no specialized routing hardware. In enterprise class routers there is a feature called forwarding plane and control plane separation. Decision on packet handling is made by piece of hardware which is autonomous. Control plane is "programming" forwarding plane but if control plane is busy(lot of new routing information) or even dead packets are still following already programmed routes. Same for firewall rules, but only in high-end equipment. -- Regards orcus
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
buying a router or using router in kernel david nnaemeka <odimegwudavid@yahoo.fr> - 2012-08-25 20:03 +0100
Re: buying a router or using router in kernel Dan C <youmustbejoking@lan.invalid> - 2012-08-25 23:27 +0000
Re: buying a router or using router in kernel Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-08-26 06:01 +0000
Re: buying a router or using router in kernel Peter Köhlmann <peter-koehlmann@t-online.de> - 2012-08-26 09:44 +0200
Re: buying a router or using router in kernel Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2012-08-25 19:31 -0500
Re: buying a router or using router in kernel General Schvantzkoph <schvantzkoph@yahoo.com> - 2012-08-27 17:11 +0000
Re: buying a router or using router in kernel Dave <dave@llondel.org> - 2012-08-27 20:08 +0100
Re: buying a router or using router in kernel Whiskers <catwheezel@operamail.com> - 2012-08-27 21:56 +0000
Re: buying a router or using router in kernel Stefan Monnier <monnier@iro.umontreal.ca> - 2012-08-29 10:36 -0400
Re: buying a router or using router in kernel telsar <noone@nowhere.com> - 2012-08-27 16:59 -0500
Re: buying a router or using router in kernel Simon Quantrill <simon.quantrill@gmail.com.invalid> - 2012-08-29 16:52 +0200
Re: buying a router or using router in kernel orcus@pwr.wroc.pl - 2012-08-29 16:55 +0000
Re: buying a router or using router in kernel Simon Quantrill <simon.quantrill@gmail.com.invalid> - 2012-08-29 23:37 +0200
csiph-web