All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] Traffic control on a single interface
@ 2006-12-05 14:53 Tom Smith
  2006-12-05 15:31 ` Marek Kierdelewicz
  0 siblings, 1 reply; 2+ messages in thread
From: Tom Smith @ 2006-12-05 14:53 UTC (permalink / raw)
  To: lartc

I'm in the process of replacing a Novell server that had a single NIC 
and routed traffic from our local network to either the Internet or to 
the Corporate office. I have this configuration working now but we've 
run in to some bandwidth problems.

The server that I have set up now is Linux. It uses a different IP for 
Samba than for the DNS/DHCP and routing (different VMs in VMware 
Server). What I'd like to do is configure the traffic control to do 
several things:

1) It needs to be able to control traffic leaving our local network and 
going to either Corporate (via point-to-point T-1) or the Internet (via 
fractional T-1).
2) It needs to be able to control traffic coming IN TO our network from 
remote VPN connections.
3) Telnet and SSH traffic should be real time.
4) All other local traffic (that is, traffic not leaving our local 
network) needs to be real time AND at local network speeds.

It there a good way to achieve these goals given that the router only 
has one NIC in it?

Or might there be a better way of doing this?

Thanks, in advance, for your help.

~ Tom
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [LARTC] Traffic control on a single interface
  2006-12-05 14:53 [LARTC] Traffic control on a single interface Tom Smith
@ 2006-12-05 15:31 ` Marek Kierdelewicz
  0 siblings, 0 replies; 2+ messages in thread
From: Marek Kierdelewicz @ 2006-12-05 15:31 UTC (permalink / raw)
  To: lartc

Hi there,

> 
> It there a good way to achieve these goals given that the router
> only has one NIC in it?

Connect the NIC to managed L2 switch. Configure connection as a trunk
carrying some vlans. Configure remaining L2 switch ports as untagged
and assign them do appropriate vlans. Functionally you'll have Linux
router with more NICs (groups of untagged switch ports will be
equivalent to one linux NIC). On linux system you'll have separate
interfaces like eth0.1 eth0.2 and so on. This can significantly ease
task of shaping and routing your traffic the way you want it.

Another option is using IFB/IMQ for shaping traffic, but such setup
won't be too straightforward and bug-prune.

pozdrawiam
--
Marek Kierdelewicz
Kierownik Działu Systemów Sieciowych, KoBa
Network Department Manager, KoBa
tel. (85) 7406466; fax. (85) 7406467
e-mail: admin@koba.pl
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-12-05 15:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-05 14:53 [LARTC] Traffic control on a single interface Tom Smith
2006-12-05 15:31 ` Marek Kierdelewicz

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.