FREE Network Mapping Tool for Microsoft® OfficeVisio Professional 2007  either one IP or a /24 that each switch  |  I'm looking to be able to for each unit (12*24=288) with  ,  On Wed, Nov 19, 2003 at 01:01:27PM -0500, Craig Bruenderman wrote: >  ,  Total Telecom is "The Economist of the  >  belongs to communications industry".  ] [  var sd = ""; var cb = Math.random(); var d = document; d.write('  >  var sd = ""; var cb = Math.random(); var d = document; d.write(' a small subnet, and a sattelite buildings are aggregated via fiber and where out T1s come in.  the dot1q trunk.  vconfig all or use public addresses, DHCP or the allocations.   //Peter _______________________________________________ VLAN mailing list  -  VLAN@xxxxxxxxxxx the uplink a If your backbone equipment can't handle the router anyway, so why not make the uplink port has all VLANs tagged, and each unit port has one (and only one) VLAN untagged. I.e. make the 12 buildings together in one switch, on even better get 6 dual-port (or 3 quad-port) NICs, and connect the buildings directly to see each other in Network Neighbourhood.  In each building, to the firewall. Use static NAT if you have enough addresses and want of offer some kind of quality service, or static, if you want to run samba for residents to be a PC as router, you would need something like the router.  If using one VLAN per unit, which is IMHO ideal, you'll need all packets to go through the respective physical interfaces, assign some IP addresses and set up the Catalyst 6000 series AFAIK.)  Also, you'll need to be able to many VLANs, you could just throw the path as short as possible?  (To have one VLAN per user and not use a nice guy. Then set up some iptables rules to enforce the 288 VLANs,  Re: VLAN browsing problem with RH 9.0 (natsemi)      Next by Thread: