VLANs aren't the solution. The device you are using the share the Internet
is. You simply set it to allow certain IP#s and to not allow certain
others. If it cannot do that then you should replace it with something that
can.
To use VLANs you would have to have a Router (a "real" router, not an
Internet NAT device). The router would need to be capable to using ACLs. The
ACLs would be set to block traditional Internet traffic from crossing the
subnets. This is overkill and over complication,...a decent NAT Device that
shares the Internet to the network should be capable of allowing and denying
certain addresses irrelevant to what subnet they are in.
VLANs are "logically" no different than what regular subnets are
"physically" so all the same principles apply.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"richms" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> I have a generic National semiconductors gigabit card, that claims to
> support 802.1q vlan tagging, and a friend has sucessfully used a
> similar card under linux on multiple vlans.
>
> I am wanting to seperate the network here as I have some people living
> in the house who I dont want to provide internet access to, but do wish
> to provide access to the file and printer server. As I dont want to
> pull more cables, vlans seem to be the ideal solution. I have the
> switch side sorted out, but I am at a loss how to set windows xp, and
> 2000 server up to have the card take trunked vlans and present them as
> seperate interfaces that I can number seperatly. Can someone direct me
> to a howto on this issue?
>
Similar Threads
Linear Mode
