Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
Hi all, There are several points about VLAN Configuration which are not addressed in the Manuals, Online helps,... It was stated that one can use any "standard" router to do the interVlan routing. Is this true, or does the router have to have "special Features" for the frame tagging,... If the above is true who sends the packet to the router, the client or the VLAN switch. If it is the client is there any special driver,.. needed? If it is the switch how do i configure this? questions over questions regards Robert NEtwork Services X-posted in COMMON_BROUTERS [Posted by WWW Notes gateway]
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3692.1 | PHHSS1::DFAUST | Bad Things, man... | Wed Jul 10 1996 07:37 | 13 | |
The way the VLAN stuff was explained to me, the VLAN switch (DECswitch 900EF, PEswitch 900TX) strips off the VLAN tagging before the packets get delivered to the appropriate VLAN. re: routing between VLANs I'm almost positive you do this the way you would route between any other two LANs, because from a networking point of view, they ARE two separate LANs. Dennis Faust | |||||
3692.2 | NETRIX::"[email protected]" | NS Austria | Wed Jul 10 1996 08:43 | 11 | |
Dennis, This would mean that i have to use different IP-Subnets for each VLAN, so that the router works "as usual". BUT, in this case i CANNOT drag and drop ports(clients) between VLANS since the IP-address of the clients is invalid after the movement. any comments Robert [Posted by WWW Notes gateway] |