Re: Route table growth and hardware limits...talk to the filter
On Mon, Sep 10, 2007 at 10:16:17AM -0500, Stephen Sprunk wrote: Thus spake Jon Lewis [EMAIL PROTECTED] The trouble is, it turns out there are a number of networks where CIDR isn't spoken. They get their IP space from their RIR, break it up into /24s, and announce those /24s (the ones they're using anyway) into BGP as /24s with no covering CIDR. IMHO, such networks are broken and they should be filtered. If people doing this found themselves unable to reach the significant fraction of the Net (or certain key sites), they would add the covering route even if they were hoping people would accept their incompetent/TE /24s. well, your assumptio n about how prefixes are used might be tempered with the thought that some /24s are used for interconnecting ISP's at exchanges... and for that matter it seems a lazy ISP to pass the buck on routability to an org that runs no transit infrastructure. RIR's (Well ARIN anyway) has NEVER assured routability of a delegated prefix. Tracking /filters based on RIR delegation policy seems like a leap to me... --bill Stephen Sprunk God does not play dice. --Albert Einstein
Re: Using Mobile Phone email addys for monitoring
* matthew zeier [EMAIL PROTECTED] [2007-09-06 23:39]: It's more effective to spend the money on SMS messages. Mobile providers are forced to use very aggressive anti spam measures, which can add significant delays in message delivery. Recommendations on software and modems? the UMTS PC-Cards you can get rather cheap these days show up as usb controllers with usb-cereal converters behind. add a little kermit magic and you're done (this is on OpenBSD). unlock at boottime (replace with your PIN): #!/usr/local/bin/kermit + set line /dev/ttyU0 if failure exit 1 set carrier-watch off set input echo on lineout AT+CPIN? input 10 +CPIN: SIM PIN if failure exit 1 input 10 OK if failure exit 1 lineout AT+CPIN= input 20 OK if failure exit 1 lineout AT+CPIN? input 10 +CPIN: SIM PIN2 if failure exit 1 input 10 OK if failure exit 1 exit 0 send an sms: parameters: number message (+49177... is the SMSC, replace by your provider's one) #!/usr/local/bin/kermit + set line /dev/ttyU0 if failure exit 1 set carrier-watch off lineout ATZ input 10 OK if failure exit 1 lineout AT+CSCA=+49177061 input 10 OK if failure exit 1 lineout AT+CMGF=1 input 10 OK if failure exit 1 lineout AT+CMGS=\%1 input 10 lineout \%2 output \26 input 100 ok if failure exit 1 exit 0 of course I have some shell around it for failure handling (retries) etc -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: shameful-cabling gallery of infamy - does anybody know where it went?
Alright, this is all scary familiar and bringing back bad memories. Wooden modem racks, POPs in disued bathrooms, demarcs so stuffed with wire (solder post, wrap, AND 66 blocks) that you can't find your cable, movin' cools exhausting hot air into a hall way just to get the POP down to 90... And the most interesting bit was just what sort of buildings you could manage to find 300 pair to. Why a small hair salon had a need for a 100 pair cable is beyond me. Then of course there's the stories of things like coring a hole through a floor only to come up in the middle of the hallway upstairs by mistake because someone didn't know how to measure, and the myriad beanie bundles splicing 25 pair cables that accidentally got cut made even more obvious by the large quantity of electrical tape holding the thing together... The things we had to go through for dialup. On Mon, Sep 10, 2007 at 12:34:22AM -0400, Vinny Abello wrote: Scott Weeks wrote: --- [EMAIL PROTECTED] wrote: - From: Justin M. Streiner [EMAIL PROTECTED] Note that telcos are not immune to shoddy cabling/installation work. snip http://www.cluebyfour.org/~streiner/mbr-pop-2000-ladder.JPG Do that at the telco in Hawaii and you won't be working here very long. ;-) The installation work and wiring here is something to swoon over. One of the stranger things a field tech of ours encountered wasn't necessarily bad wiring (although it's not great), but the fact that the demarc was located next to the toilet in the bathroom. Naturally, the constant humidity caused bad corrosion problems and other issues with their telco services. :) So as a general rule of thumb, avoid putting your telco and/or network gear next to the crapper or the services the equipment is meant to provide might also stink. http://users.tellurian.com/vabello/bathroom-demarc.jpg -- Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain --- Wayne Bouchard [EMAIL PROTECTED] Network Dude http://www.typo.org/~web/
RE: shameful-cabling gallery of infamy - does anybody know where it went?
Alright, this is all scary familiar and bringing back bad memories. Wooden modem racks, POPs in disued bathrooms, demarcs so stuffed with At one point, we had 200 pair installed into a two family house in rural NJ. The pop was in the basement, which had dirt floors. Or, the local phone company begging us to get lines in different CO's so that we wouldn't overload inter-office trunks and tandems. Or, the custom made racks to hold USR Sportster modems (which had to be removed from their enclosure) Or, Livingston PM3's that cost $17k for two PRIs Or, full BGP between AGIS and iMCI (note the 'i') on a 2501 Or, when you had a mail server (it was monolithic, remember) fail, and you told customers, they'd say, OK, I'll check my mail tomorrow Ah, the good old days.
Good Stuff [was] Re: shameful-cabling gallery of infamy - does anybody know where it went?
[EMAIL PROTECTED] wrote: Scott Weeks wrote: --- [EMAIL PROTECTED] wrote: - Note that telcos are not immune to shoddy cabling/installation work. snip http://www.cluebyfour.org/~streiner/mbr-pop-2000-ladder.JPG Do that at the telco in Hawaii and you won't be working here very long. ;-) The installation work and wiring here is something to swoon over. One of the stranger things a field tech of ours encountered wasn't necessarily bad wiring (although it's not great), but the fact that the demarc was located next to the toilet in the bathroom. Naturally, the constant humidity caused bad corrosion problems and other issues with their telco services. :) So as a general rule of thumb, avoid putting your telco and/or network gear next to the crapper or the services the equipment is meant to provide might also stink. http://users.tellurian.com/vabello/bathroom-demarc.jpg --- It was brought to my attention that some of the folks here may not have ever seen good wiring, so I snapped a few photos of good wiring here and wrote a quickie web page for the photos. I couldn't get pictures of Ethernet wiring, but it's the same. Except the last photo, it's all wax string done very neatly. This is the goal. ;-) http://mauigateway.com/~surfer/wiring.html scott
Re: Good Stuff [was] Re: shameful-cabling gallery of infamy - does anybody know where it went?
On Tue, 11 Sep 2007, Scott Weeks wrote: It was brought to my attention that some of the folks here may not have ever seen good wiring, so I snapped a few photos of good wiring here and wrote a quickie web page for the photos. I couldn't get pictures of Ethernet wiring, but it's the same. Except the last photo, it's all wax string done very neatly. This is the goal. ;-) Nice - they even wrapped the fiber to keep the wax twine from pinching it. Some of the telcos around here do (or did) very clean wiring jobs like this. The ATT Local (TCG from way back in the day) guys who put the OC48 bay and related breakouts for T1s and DS3s did very neat wiring. Some of the local old-school Bell Atlantic/Verizon techs also did very clean work, but most of them took the early retirement packages that were offered 4-5 years ago. jms
Re: Good Stuff [was] Re: shameful-cabling gallery of infamy - does anybody know where it went?
--- [EMAIL PROTECTED] wrote: Some of the local old-school Bell Atlantic/Verizon techs also did very clean work, but most of them took the early retirement packages that were offered 4-5 years ago. - That's what's happening here. A lot of the old-school folks are moving on and the younger folks (I'm in between the two) don't take as much care and don't understand why guys like me grump about some of the new wiring. I got it installed really fast, didn't I? It's hard to watch art be trashed with graffiti. scott
Re: Route table growth and hardware limits...talk to the filter
On Mon, 10 Sep 2007, Stephen Sprunk wrote: Sucks to be them. If they do not have enough PA space to meet the RIR minima, the community has decided they're not worthy of a slot in the DFZ by denying them PI space. Not true, there is an ARIN policy that allows you to get a /24 from one of your providers even if you only need 1 IP address: If the PA /24 is under 199/8 or 204-207/8, then the filters being discussed would allow their advertisement through, because ARIN's minimum allocation for those blocks is /24. In ARIN's 22 other /8s, the filters would not because the minimum is /20 (or /22, for 208/8). As long as enough NSPs don't filter on RIR minimums, there's still a pretty good chance that when a small PA multihomer's IP space provider's connection is down, traffic routed towards that provider will get rerouted to their other provider(s). Breaking PA /24 multihoming would be unfortunate collateral damage. Perhaps someone could use the data from the cidr-report and RIRs to create a precision targeted prefix-list intended just to block unnecessary more specifics rather than across the board on RIR minimums? You could even do two different versions. A loose version that just throws out covered subnets with same as-path and a BOFH version that throws out all apparently gratuitous subnetting smaller than RIR minimums, but not all smaller than RIR minimum routes. I just wonder how huge the list would be and what the CPU and config size damage would be. -- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net| _ http://www.lewis.org/~jlewis/pgp for PGP public key_
Re: Route table growth and hardware limits...talk to the filter
On Tue, Sep 11, 2007, Jon Lewis wrote: You could even do two different versions. A loose version that just throws out covered subnets with same as-path and a BOFH version that throws out all apparently gratuitous subnetting smaller than RIR minimums, but not all smaller than RIR minimum routes. I just wonder how huge the list would be and what the CPU and config size damage would be. If only people were charged for CPU time and RIB hardware space used on other peoples' routers to carry their stuff. (tongue, cheek, etc /) Adrian
Re: shameful-cabling gallery of infamy - does anybody know where it went?
On Tue, Sep 11, 2007, Alex Rubenstein wrote: Or, the local phone company begging us to get lines in different CO's so that we wouldn't overload inter-office trunks and tandems. Or the weekly exchange 'reboots' that happened at ~1am. the MRTG graphs of your dialins would show everyone logging off quickly followed by 100% of CPU use as people autodialed back in.. Or, the custom made racks to hold USR Sportster modems (which had to be removed from their enclosure) .. and the custom toroidal 10A 12V AC PSUs you'd have to build (and get tagged by an electrician!) because 300 odd modems in a small space meant you had 300 odd black wallwarts.. Or, Livingston PM3's that cost $17k for two PRIs .. hahahaha. And the PM3's that had busted-ass TS015 (I think) PRI code which meant they wouldn't properly work in Australia. We had to roll Bay 5399's (with the BLUE LED of doom) or AS5200's. Migrating to Euro ISDN was a smart move. Thanks Telecom. Anyone remember when Cisco would sell the dial solution as AS5200's with Cisco VXR's doing L2F offload? (Our solution: disable PPP multilink on the normal dialin; have a different number + 2 PRIs for the multilink clients.) Or, full BGP between AGIS and iMCI (note the 'i') on a 2501 Or, when you had a mail server (it was monolithic, remember) fail, and you told customers, they'd say, OK, I'll check my mail tomorrow .. how's that different from ISPs today? :) Adrian
Re: Good Stuff [was] Re: shameful-cabling gallery of infamy - does anybody know
It was brought to my attention that some of the folks here may not have ever seen good wiring, so I snapped a few photos of good wiring here and wrote a quickie web page for the photos. I couldn't get pictures of Ethernet wiring, but it's the same. Except the last photo, it's all wax string done very neatly. This is the goal. ;-) http://mauigateway.com/~surfer/wiring.html scott If you find any pictures of NY.NET; Terry Kennedy made the above look sloppy. Many places ban cable ties due to the sharp ends; some allow 'em if tensioned by a pistol-grip installer. Terry required lacing cord. You can guess his heritage. As for horror stories, a certain ISP near here that started out in a video store had piles of Sportsters. The wall warts were lined up and glued dead-bug style to a number of long 1x3's; then #14 copper was run down each side, daisy-chain soldered to each plug blade. There was no attempt to insulate any of upright plugs... I am SURE this is long gone, and the people there will likely deny it was them...as I would if it were me! -- A host is a host from coast to [EMAIL PROTECTED] no one will talk to a host that's close[v].(301) 56-LINUX Unless the host (that isn't close).pob 1433 is busy, hung or dead20915-1433
