Re: Single domain two IP subnets

I wasn't trying to hide behind anything, herb. I just can't abide when
someone tries to make me out to be some kind of loser who doesn't know my
business. I'll go head to head with you any day in a real-life
set-it-up-and-make-it-work situation. I've never claimed to be the sharpest
pencil in the box, and I've learned a lot from your posts in the past. But I
DO know networking from the root and fundamental levels up. I'm not a
hardware engineer, so I can't tell you how the circuitry inside the routers,
NICs and switches do their magic. But as far as designing, installing, and
configuring a network, I know my stuff ! I'm sure you have a better handle
on many things than I do, but not on this subject. Yes, I did make some cut
and paste errors in the post. They are corrected on the links. Come th rhink
of it, that's something I really COULD use some help with - writing (typing
too).

Cheers,
....kurt


"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:uZgbUWU2GHA.1292@xxxxxxxxxxxxxxxxxxxxxxx
"Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx> wrote in message
news:12gmh6bj81rdv34@xxxxxxxxxxxxxxxxxxxxx
First, let's all agree to use the standard, which is now 802.1q. Old
Cisco ISL VLANS are history. Newer Cisco switches don't even support ISL
anymore. Some cheapo switches also support local "port-based" VLANs, but
those do not use tagging, nor are they trunkable to other switches. The
following explains "port-centric" 802.1q VLANs, by far the most widely
used application. Also let's pre-define "traffic", "communication", etc
as TCP/IP on an ethernet network.

No, none of that complication is necessary IF you had really
understood the basics, not made several mistakes, overcomplicated
it, tried to brag about how experienced you are, and then tried to
hide behind obfuscation.

I am never impressed when someone tries to justify their technical
inadequacy by giving their resume:

"True, but I must say that I don't fall into that category. As the
senior
engineer/primary designer of a metro ring infrastructure, I live and
breathe
VLANs and routers every day of my life."

You are wasting my time at this point and you have already confused
the issue for those trying to learn and understand networking correctly.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]




.

Relevant Pages

  • Re: Single domain two IP subnets
    ... ISL VLANS are history. ... Newer Cisco switches don't even support ISL ...
    (microsoft.public.win2000.dns)
  • RE: Firewall and VLAN security design
    ... Because of the way that switches deal with broadcasts, ... The SAFE methodology calls for defence in depth and Private VLANS are one of ... Firewall and VLAN security design ... > This is a FAQ, and the usual answer is that no, VLAN separation is ...
    (Security-Basics)
  • Re: Single domain two IP subnets
    ... hardware or any of the complexities of "network hardward ... I never criticize anyone's typing as long as the words can ... Cisco ISL VLANS are history. ... Newer Cisco switches don't even support ISL ...
    (microsoft.public.win2000.dns)
  • Re: [fw-wiz] Vlans as effective security measures?
    ... The Cisco bug DB has plenty of entries for switches with "bleeding ... VLANs are a cheap/convenient way of defining subnets and moving ports ... >And cars crash and cars burn and people are dying in cars all the ...
    (Firewall-Wizards)
  • Re: vlan tags and ISA2004, what´s the story?
    ... >Well the switches are Layer2 Devices and VLANs are Layer3, ... the Switch port that the ISA plugs into with the Internal Interface ... The Router can be a hardware Router device,...it ...
    (microsoft.public.isa.configuration)