If you're going to use an ISO standard interior gateway routing protocol, such as ISIS, would it not make sense to use the companion exterior gateway protocol ESES and/or the companion hybrid ESIS? BGP is a cool protocol, but it doesn't always play nice. Using something designed specifically to work with ISIS would seem to be more logical.
Since IPv4 is not an ISO standard protocol, why would one worry about using an exterior gateway protocol that is ISO standard, particularly when you have no one else to talk to using said ISO standard protocol?
There's no EGP support. Not catastrophic, as not many people use it as a percentage of the population, but some do. If they do, they cannot work with Cisco products, because Cisco doesn't support it. The same applies to GGP.
I suppose EGP and GGP support would be useful if you invented a time machine and wanted to connect a router of today to the Internet of 1980...
For multicasting, I can't see any support for IGMPv3,
Router(config-if)# ip igmp version 3
Enables IGMPv3 on this interface. The default version of IGMP is set to Version 2.
QoS bugs me a lot. They have weighted fair queueing (forwards and backwards), RED, ECN and CBWFQ (though they seem to still be working on that last one). I've found no reference to CBQ, HFQ, HFSC, BLUE, RSVP or JoBS. Although CBQ is a wretch to configure, if it's done right, it blows the socks off WFQ. If you're doing intranet or extranet videoconferencing, you almost have to use RSVP to maintain the quality.
Then you certainly haven't looked very hard. I'm not a qos expert, since I'm in the service provider sector and not enterprise, but just a couple seconds at cisco.com turned up support for cbq and rsvp.
I would like to see router developers be a little more FOSS-friendly. Hey, I'm not asking Cisco to Open Source IOS - that would never happen - but IOS supports only a small handful of routing protocols and is woefully lacking on QoS support.
What are the routing protocols that Cisco doesn't support you'd be interested in? I only work with IP at layer 3, so I don't do routing protocols for IPX, Appletalk, Vines, DecNet, etc. But for IP Cisco supports:
OSPF RIP v1 and v2 IGRP EIGRP IS-IS IBGP, EBGP, MBGP MPLS TDP and LDP PNNI...and others that I surely can't think of.
Are you maybe confusing "routing protocol" with "routed protocol"?
Whilst Cisco hardware is very likely highly tuned to the protocols they do use, software is software and a module system would be trivial to develop. (This would not be true if Cisco routers were "real" hardware routers, but almost nobody codes in hardware unless they absolutely have to.)
Trivial to develop? Maybe you should ask Cisco's IOS developers about that. Current IOS (not IOS-X or whatever the new thingie is called) is a monolithic operating system. It doesn't use modules. To support modules they would have to, not so trivially, rewrite their operating system.
--Stafford
Re:Routers/Linksys
on
Router Wars
·
· Score: 2, Informative
Linksys, A Division of Cisco Systems, Inc.
Cisco had pretty much given up on the cheap CPE (Customer Premises Equipment) market, then bought Linksys a year or so ago so they could keep a foot in it.
Mt. Hood poses a much larger danger to the Portland area. It's bigger than St. Helens, closer to Portland, and has a number of ski resorts and other people-attracting landmarks.
Portland also has a volcano, presumably extinct, within the densely populated city limits - Mt. Tabor.
I took the Franklin-Covey time management class a couple of years ago, and have been a convert ever since. There is an electronic version of it for Palm and Winders, but I really prefer the low-tech paper system.
It is a complete system, and I highly recommend the class in order to get the most use out of it.
The "Franklin" in Franklin-Covey is from Ben Franklin, who carried around a little black book for his notes, appointments, and, in particular, goals and values planning.
My favorite Zelazny work is the lesser known "A Night in the Lonesome October".
It takes place in and around London in the late 1800s, and is narrated by Snuff, a huge sheepdog.
Snuff's master is Jack, who has a way with knives.
There is also the Count, who sleeps by day, the mad monk Rastov, the Great Detective and his assistant, a witch, a vicar, a druid, and a couple others. All will take part in the Game...
This work I think best shows Zelazny's excellent and warped sense of humor.
I moved from San Diego to Portland a few years ago and have loved it. Granted, many of you would absolutely hate the weather, but I find it almost perfect. Business is not quite as torrid here as in Seattle, but there don't seem to be quite as many of the evil-SUV-landwhale-driving-cell-phone-yacking shallow yuppies here either. Lots of really good pretty cheap restaurants, probably more micro-breweries per capita than anywhere else, and while I'd like to see more startups we do have a lot of long time tech companies - Intel, Sun, Tektronix, Mentor Graphics, Epson, and a bunch of chip manufacturing.
I don't know that slashdot has actually crashed - I do know that routing from where I am to slashdot has been spotty, and most lately it's been a problem in pbi.net land, which appears to belong to PacBell.
Whois.arin.net lists the coordinator of the netblock where my traces have been dying as ip-admin@pbi.net. Email to that address bounces on a mail loop. Bleah.
Slashdot Mirror
If you're going to use an ISO standard interior gateway routing protocol, such as ISIS, would it not make sense to use the companion exterior gateway protocol ESES and/or the companion hybrid ESIS? BGP is a cool protocol, but it doesn't always play nice. Using something designed specifically to work with ISIS would seem to be more logical.
Since IPv4 is not an ISO standard protocol, why would one worry about using an exterior gateway protocol that is ISO standard, particularly when you have no one else to talk to using said ISO standard protocol?
There's no EGP support. Not catastrophic, as not many people use it as a percentage of the population, but some do. If they do, they cannot work with Cisco products, because Cisco doesn't support it. The same applies to GGP.
I suppose EGP and GGP support would be useful if you invented a time machine and wanted to connect a router of today to the Internet of 1980...
For multicasting, I can't see any support for IGMPv3,
Router(config-if)# ip igmp version 3
Enables IGMPv3 on this interface. The default version of IGMP is set to Version 2.
QoS bugs me a lot. They have weighted fair queueing (forwards and backwards), RED, ECN and CBWFQ (though they seem to still be working on that last one). I've found no reference to CBQ, HFQ, HFSC, BLUE, RSVP or JoBS. Although CBQ is a wretch to configure, if it's done right, it blows the socks off WFQ. If you're doing intranet or extranet videoconferencing, you almost have to use RSVP to maintain the quality.
Then you certainly haven't looked very hard. I'm not a qos expert, since I'm in the service provider sector and not enterprise, but just a couple seconds at cisco.com turned up support for cbq and rsvp.
--Stafford
I would like to see router developers be a little more FOSS-friendly. Hey, I'm not asking Cisco to Open Source IOS - that would never happen - but IOS supports only a small handful of routing protocols and is woefully lacking on QoS support.
What are the routing protocols that Cisco doesn't support you'd be interested in? I only work with IP at layer 3, so I don't do routing protocols for IPX, Appletalk, Vines, DecNet, etc. But for IP Cisco supports:
OSPF
RIP v1 and v2
IGRP
EIGRP
IS-IS
IBGP, EBGP, MBGP
MPLS TDP and LDP
PNNI
Are you maybe confusing "routing protocol" with "routed protocol"?
Whilst Cisco hardware is very likely highly tuned to the protocols they do use, software is software and a module system would be trivial to develop. (This would not be true if Cisco routers were "real" hardware routers, but almost nobody codes in hardware unless they absolutely have to.)
Trivial to develop? Maybe you should ask Cisco's IOS developers about that. Current IOS (not IOS-X or whatever the new thingie is called) is a monolithic operating system. It doesn't use modules. To support modules they would have to, not so trivially, rewrite their operating system.
--Stafford
Linksys, A Division of Cisco Systems, Inc.
Cisco had pretty much given up on the cheap CPE (Customer Premises Equipment) market, then bought Linksys a year or so ago so they could keep a foot in it.
--Stafford
Mt. Hood poses a much larger danger to the Portland area. It's bigger than St. Helens, closer to Portland, and has a number of ski resorts and other people-attracting landmarks. Portland also has a volcano, presumably extinct, within the densely populated city limits - Mt. Tabor.
Richard Chamberlain, before he came out of the closet, trying to be Indiana Jones.
Sharon Stone, before she showed off her naughty bits in Basic Instinct.
Not the worst ever, but the worst through which I've ever sat.
--Stafford
I took the Franklin-Covey time management class a couple of years ago, and have been a convert ever since. There is an electronic version of it for Palm and Winders, but I really prefer the low-tech paper system.
It is a complete system, and I highly recommend the class in order to get the most use out of it.
The "Franklin" in Franklin-Covey is from Ben Franklin, who carried around a little black book for his notes, appointments, and, in particular, goals and values planning.
two-AH-lah-tin
It's a river in Oregon.
My favorite Zelazny work is the lesser known "A Night in the Lonesome October".
It takes place in and around London in the late 1800s, and is narrated by Snuff, a huge sheepdog.
Snuff's master is Jack, who has a way with knives.
There is also the Count, who sleeps by day, the mad monk Rastov, the Great Detective and his assistant, a witch, a vicar, a druid, and a couple others. All will take part in the Game...
This work I think best shows Zelazny's excellent and warped sense of humor.
--Stafford
I moved from San Diego to Portland a few years ago and have loved it. Granted, many of you would absolutely hate the weather, but I find it almost perfect.
Business is not quite as torrid here as in Seattle, but there don't seem to be quite as many of the evil-SUV-landwhale-driving-cell-phone-yacking shallow yuppies here either.
Lots of really good pretty cheap restaurants, probably more micro-breweries per capita than anywhere else, and while I'd like to see more startups we do have a lot of long time tech companies - Intel, Sun, Tektronix, Mentor Graphics, Epson, and a bunch of chip manufacturing.
I don't know that slashdot has actually crashed - I do know that routing from where I am to slashdot has been spotty, and most lately it's been a problem in pbi.net land, which appears to belong to PacBell.
Whois.arin.net lists the coordinator of the netblock where my traces have been dying as ip-admin@pbi.net. Email to that address bounces on a mail loop. Bleah.
--Stafford