On Sun, 2 Sep 2007, C. Jon Larsen wrote:
> Where is the access list that is going to prevent cross talk between the
> subnets ? Otherwise rogueware on one tenants computer will attack the
> other tenants. Simply splitting each tenant onto its own vlan is ncie but
> its a far cry from secure if yo
>> Where is the access list that is going to prevent cross talk between the
>> subnets ? Otherwise rogueware on one tenants computer will attack the
>> other tenants. Simply splitting each tenant onto its own vlan is ncie but
>> its a far cry from secure if you tie the subnets into a router that
Hi,
On Sun, Sep 02, 2007 at 04:51:46PM +0200, Niels Bakker wrote:
> I assume you'll be selling these people Internet access.
If they get 172.16-Addresses, he's not selling Internet access...
SCNR.
gert
--
USENET is *not* the non-clickable part of WWW!
lf Of David L. West
> Sent: Sunday, September 02, 2007 10:48 AM
> To: cisco-nsp@puck.nether.net
> Subject: Re: [c-nsp] Cisco noob -- design guidance request
>
> > No - you just need one Layer 3 device, with an interface in each
> subnet.
> > Neither the 2960G nor the 3
On Sun, 2 Sep 2007, Niels Bakker wrote:
>>> Where is the access list that is going to prevent cross talk between the
>>> subnets ? Otherwise rogueware on one tenants computer will attack the
>>> other tenants. Simply splitting each tenant onto its own vlan is ncie but
>>> its a far cry from secu
> I assume you'll be selling these people Internet access. Their
> neighbours are also part of the Internet. I see no reason why you
> should protect those from each other but not any other host connected to
> the Internet.
> (I, for one, will have my internet transparent please, thankyouverymuc
>> Where is the access list that is going to prevent cross talk between the
>> subnets ? Otherwise rogueware on one tenants computer will attack the
>> other tenants. Simply splitting each tenant onto its own vlan is ncie but
>> its a far cry from secure if you tie the subnets into a router tha
> No - you just need one Layer 3 device, with an interface in each subnet.
> Neither the 2960G nor the 3548XL is a Layer 3 device, so you'll need to
> find
> a router from somewhere, and trunk all the vlans into that to do the
> routing
> between them, and to the outside world.
>
If I understand
> Where is the access list that is going to prevent cross talk between the
> subnets ? Otherwise rogueware on one tenants computer will attack the
> other tenants. Simply splitting each tenant onto its own vlan is ncie but
> its a far cry from secure if you tie the subnets into a router that is
>
On Sun Sep 02, 2007 at 08:16:14AM -0600, David L. West wrote:
> Thanks. I think I screwed up buying the hardware though. I have a 2960G-24TC
> as the core switch in the server room, a 2960-48TT for the first floor, and
> a 3548XL for the 3rd. Only the last is Layer 3.
>
> Reading your message an
Thanks. I think I screwed up buying the hardware though. I have a 2960G-24TC
as the core switch in the server room, a 2960-48TT for the first floor, and
a 3548XL for the 3rd. Only the last is Layer 3.
Reading your message and doing further research I begin to suspect I have to
have Layer 3 swit
On Sun, 2 Sep 2007, Simon Lockhart wrote:
> On Sat Sep 01, 2007 at 10:12:07PM -0600, David L. West wrote:
>> I'm setting up a new LAN in an office building with multiple tenants who
>> will be sharing internet access, DNS/DHCP but have individual VLANS to keep
>> them seperate from the other tena
On Sat Sep 01, 2007 at 10:12:07PM -0600, David L. West wrote:
> I'm setting up a new LAN in an office building with multiple tenants who
> will be sharing internet access, DNS/DHCP but have individual VLANS to keep
> them seperate from the other tenants. I think that the key here is having
> ea
I'm setting up a new LAN in an office building with multiple tenants who
will be sharing internet access, DNS/DHCP but have individual VLANS to keep
them seperate from the other tenants. I think that the key here is having
each VLAN have a "helper address" that serves as a DHCP Relay Agent , wh
14 matches
Mail list logo