Re: Single domain two IP subnets

"Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx> wrote in message
news:12gn1rklotg357@xxxxxxxxxxxxxxxxxxxxx
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.

Does that happen to you a lot?

I certainly wasn't trying to make you out a loser (only you
can do that yourself) but I will correct you if you make technical
errors AND in the process are confusing those trying to learn.

So don't do that anymore.

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.

Then you have no excuse for such elementary errors -- whether
you truly misunderstand or were just unable to explain how things
work. You claimed experience suggests you SHOULD know better.

I am always much tougher on those who are beginners than those
who claim they know what they poorly understand.

I'm not a hardware engineer, so I can't tell you how the circuitry inside
the routers, NICs and switches do their magic.

And that was always PART of my major point: You do not need
to be a "hardware engineer" to understand IP, nor to understand
routing and bridging.

They are simple subjects if presented simply. No one can fully
understand Switching in general and VLANs in particular with
with an understanding of routing and bridging but it amazes me
how many people seem to try.

These are actually very simple subjects and in fact are better
understood simply without reference to specific network
hardware or any of the complexities of "network hardward
engineering".

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.

Then when you figure that out -- stop arguiing.

It's only when people argue BEYOND their mistakesm, rather than
admitting and correcting them, that they begin to sound truly foolish.

Everyone has to learn -- and their is no shame in being
uninformed, but anytime we argue despite the facts we
are not helping nor are we learning.

Come th rhink of it, that's something I really COULD use some help with -
writing (typing too).

I never criticize anyone's typing as long as the words can
be decyphered. Seldom their grammar or English either.

I personally type these notes as stream of consciousness,
much like a conversation except we have to wait days or
hours for a response and thus it is very easy to be misunderstood
and for tones to be misinterpreted.

As to typing (serious suggestion): Any good typing tutor works
wonders. Even today I still use one regularly to counteract the
bad habits I would otherwise fall into more deeply.

Mavis Beacon and Tux Typing Tutor are my current favorites.


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

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: To vlan or not to vlan, thats the question
    ... > divide the network in two, ... Unless you will now or in the near future implement vlans there is no ... routers to route traffic _between_ different vlans as well as switches ... opposed to conventional switching. ...
    (comp.os.linux.networking)
  • Layer 2 design question
    ... I have inherited this network. ... All the switches are ... department VLANS) on the 6509 this would decrease the broadcast domain ... In addition I am seeing STP: ...
    (comp.dcom.sys.cisco)
  • Re: To vlan or not to vlan, thats the question
    ... "They (vlans) will not _inherently_ add to your security and performance ... The real life example network (3000 ... >>switches, and a firewall interconnecting them (managing ... > opposed to conventional switching. ...
    (comp.os.linux.networking)
  • Re: Long ethernet
    ... switches close to each datalogger, and an utp link from switch to the ... and that we should split the network up using ... Assuming that the switches are:- ... These VLANs were then connected ...
    (comp.dcom.lans.ethernet)
  • 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)