Re: Kernel Routing and the IntraNet

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



AB> Is routing necessary in an IntraNet?

If you have more than one network then yes. For one LAN there is no
reason.

You also want routing when connecting Ethernets with differnet MTU - so
hosts in network with MTU of 9000 can talk with this MTU and the router
fragments the packets and forwards to hosts in a network with MTU 1500.
Etc.

It's usually simpler to set up routing than to do the same with VLAN's,
bridging etc. But routing usually adds some communication latency.

Most (but not all) sensible firewalls are also implemented as routers,
so from practical viewpoint you can deploy a router-like firewall more
easily.

AB> Switch when you can and Route when you must?

Well, you can sell more switches with this :)

-- 
Meelis Roos
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux