cellio: (avatar)
2005-12-03 05:54 pm
Entry tags:

call to brain trust: DSL in Pittsburgh

Rumor has it that the DSL provider we've been happily using for several years may be going poof. I found a list of providers serving the area, but it's just a list, no reviews. I'd be interested in hearing from local people using providers other than Telerama (current) and Verizon (previous, rejected for sucky quality on pretty much every front).

Our needs are fairly simple, but we do require always-on service (no PPPoE stuff with its manual activation and whatnot) and we much prefer a fixed IP address so we can support incoming service. Reliability (with good support when that fails) is more important than cost, though obviously we'd like to keep costs reasonable. All other factors being equal, I prefer to patronize local companies over national providers. We do not have wiring in place to support cable, so we're not looking to change technologies at this time.

And if anyone has information that would counter the remors about Telerama, please let me know. We've had nothing but quality service from them and we'd hate to be part of a stampede based on bad information. However, we also don't want to be stranded, and this doesn't sound good right now.
cellio: (avatar-face)
2004-11-26 03:44 pm
Entry tags:

modem weirdness

The fine folks at Telerama lent us a modem with which to test. (We've been having random short-term network lossage.) The test modem, however, is unhappy in new and novel ways.

With the test modem, pings and SSH connections get through just fine, but web browsing isn't happening. (I saw one page get to "transferring..." before failing, but most sites timed out at "resolving host". Reminder: other uses of name service were fine.) I cleared the cache and restarted the browser, which didn't make a difference. Dani reported the same behavior with a different browser on a different machine. Restoring the original modem made the problem go away.

So that was oddity #1. Oddity #2 presented itself when I picked up the phone to call tech support about oddity #1 -- and found a very noisy line. After switching to my cell phone, I talked to someone who suggested that the noise is due to a lack of filtering on the phone line and he has no clue why the selective network service would be happening. But the old modem doesn't produce noise on the line, and all I did was swap the cables to the new modem and turn it on. I definitely didn't change any configuration on our phone lines.

Could it be that some modems have this filtering built-in and others don't? That seems weird to me, as the person I talked to seemed to be saying that the filtering has to be done to all jacks, and I certainly got the noise on a different jack than the one supporting the modem (which is consistent with that). I know that BellAtlantic came in and did something to our phone line before installing DSL 5+ years ago, but it was a change at the box and not at the jacks.

Both modems are Westell, though of different vintages.

I am now officially perplexed.
cellio: (avatar)
2004-11-17 06:54 pm

good customer support

We get our DSL service through Telerama. Allow me to sing their praises.

We've been seeing apparently-random short network outages just often enough to be annoying, and this is new behavior. The problem could be the DSL service, the modem, or a physical problem on the line, but how do you tell which?

So I wrote to Telerama's support folks to ask if they had any thoughs on this. In particular, had they received similar reports from anyone else? They had not, so they guessed that it probably wasn't them.

They then said "here, let me file a trouble ticket with Verizon on your behalf" and, when the results of that came back today, "sounds like your modem; would you like to borrow one from us to test with?".

I really didn't want to have to go out and buy a modem on the possibility that that was the source. Now we don't have to. Yay Telerama for helping us out with something that's not really their problem!
cellio: (embla)
2004-11-11 11:00 pm

Thursday bits (protest, DSL, feline antics)

Tonight while driving through Squirrel Hill I noticed a large crowd walking up the sidewalk. As I parked the group reached me and I saw that they were protesting the war ("no blood for oil" being the pervasive chant). I walked with them for a block or so, raising the average age a bit, before veering off for groceries. It occurred to me only later that its placement on Veterans' Day was probably not an accident.

Our usually-reliable DSL service has been having random short outages for the last several weeks. (Usually 10-15 minutes, a few times a week.) I'm not sure how to test whether it's the DSL service itself or our 5-year-old modem, though, short of acquiring a test modem. So I sent mail to our provider asking if they had other reports and/or debugging hints. (I noticed in passing that their service hours now end at 8PM. I've had productive conversations with them at midnight in the past. Oh well. 8PM is reasonable; I'd just gotten used to hacker hours.)

Ok, Embla is capable of making normal meowing sounds, as opposed to that quiet chirpy thing she usually does. It just has to be Important. Like, say, being trapped between the window and the screen on a cold evening. For calibration purposes, the time a contractor sealed her into a wall she was silent for a long time, even though I was in the room calling her.

(What was she doing there tonight? Well, our sink was plugged up, so we had initiated chemical warfare, but the chemicals gave off mustard gas or something, and we had to open the windows to help with dispersion. I didn't notice the cat on the windowsill when I pushed the window closed later. Fortunately, she was quick to alert me.)

cellio: (embla)
2002-12-29 10:35 pm

family visit

Today we went to my parents' house to do the holiday get-together. (The rest of the family is my sister and her two kids.) Things went reasonably well, though both of my parents were more distracted than usual (my father by a football game, and my mother by a string of small things). So we didn't spend all that much time talking, which was unfortunate. I can sort of roll with stuff like that because I've known these people a long time, but I could tell that Dani was feeling somewhat on the outside and I didn't know how to fix that.

My parents gave us a George Foreman grill. Woo hoo! I wondered if they were fishing for possible reactions at Thanksgiving when they showed us theirs, but it turns out they bought this for us back in August, before we ever saw theirs. I'm looking forward to using it. It looks like a good size for two people.

They also gave me the first season of Babylon 5 on DVD (I suspected they would, so I held off buying it). They gave Dani an anime movie (on DVD) that I have failed to retain the name of. We got my mother a season of X-Files, my father Band of Brothers (but it's been delayed, so we had to give him a promissory), and my sister the Back to the Future trilogy and the first season of Buffy. It was the year of DVDs in our family. :-) (We all acquired players within the last year, so this was forseeable.)

(There were other gifts, but it's not my intention to catalog everything here. I am pleased that almost all of the gifts we brought were well-received.)

Dinner featured a lamb roast (I really like lamb), which my mother hasn't been making much lately. My sister doesn't like lamb, so they threw some chicken into the GF grill for her. It's about as fast as nuking, I guess, but a lot more tasty. My spice cake went over well. My sister seems to have had a Martha Stewart moment; she fabricated a train out of candy, crackers (small ones for wheels), and assorted other stuff. It was novel. Apparently she got the idea out of that Pilsbury cooking magazine that we both subscribe to; I haven't yet read the recent "holiday desserts" issue.

My father is currently wrestling with DSL from Verizon (sound familiar?), apparently the only carrier serving their town. (I just sent email to Telerama to check on that, as he hadn't heard of them.) He had some problems getting it set up, and spent a while on the phone with a guy with a script, and eventually he got a connection. Then he rebooted the machine, and ever since he has been getting an error (number only, no text -- I thought Macs were supposed to be better than that), and no network connection. And whatever is happening is also hosing his modem, so he can't dial out. I hope he's able to get some help from Verizon tomorrow. Dani and I tried to debug it but didn't get very far. Oh, and one oddity: they have to put some sort of special "filter" hardware on every phone in their house because DSL messes up the phone line. I knew that Verizon required something like that back in 1999, but I was told that they'd eventually fixed that. I wonder if, when they enter new service areas, they start by recycling all the hardware they've stopped using elsewhere. :-) (My parents' town only got DSL recently.)

My niece has become rather sullen and rude, particularly in the last year or so, and I don't know why. I hope that going away to college next year fixes it, rather than making it worse.

cellio: (mandelbrot)
2002-07-09 09:16 pm
Entry tags:

networking weirdness

Ever since the power surge (and resulting replacement of Linksys box and one other hub), we have been noticing sporadic weirdness on our network. We use DHCP to hand out IP addresses (doesn't everybody?). The Linksys box is configured (by default, if I recall correctly) to start handing out addresses at 192.168.1.100. The Linksys itself is 192.168.1.1. As best I recall, these are the same settings we used successfully on its predecessor for close to three years.

So now, every now and then, it will hand out the address 192.168.1.2. And that unlucky machine will be able to see the LAN but not the internet. Rebooting usually does not fix it, but creative sequences of reboots of all machines and power-cycling of the modem and Linksys usually do the trick.

We cannot find any common factor when this happens. Sometimes it just does.

Tonight, when I found myself the unwilling owner of 192.168.1.2, I decided to try an experiment: I gave myself a fixed IP address without changing anything at the Linksys end. I guessed that I should use 192.168.1.1 for the gateway and name service, rather than the "real" ones; after all, the Linksys box is supposed to resolve the interface issues between the local machines and the network, right?

This worked perfectly. In fact, in a rare Windows moment, I didn't even have to reboot!

I assume that as the other machines encounter the wayward 192.168.1.2 we'll make this adjustment on them, too, until nobody's using DHCP any more. Then we'll forget about this until some unlucky house guest wants to plug his laptop into the network. :-)

I feel like this is an ugly hack. I have not solved the real problem. But at this point I think I'm going to stop looking for it.

Because there is a strict quota on hardware happiness, I found that the 4-port hub we had lying around is really only a 2-port hub. (One is "uplink", which seems to be magic and does not work with anything I tried to plug into it, and one is just dead.) So I can't get rid of the cables strung across the floor just yet.
cellio: (avatar)
2002-06-02 01:58 pm
Entry tags:

DSL

Ah, what a joy. I have cast out the demons of stupidity (that would be Verizon) in favor of Telerama. The installation was nearly painless, the pain involved was a problem at our end (not theirs), and the tech-support people (who answer 24 hours a day, by the way) were cheerful, helpful, and not clueless bozos like the guys over at Verizon. (I almost wrote "Luddites", but they obviously don't reject technology wholesale. It provides them an income, after all.)

Read more... )

cellio: (avatar)
2002-04-04 11:04 pm

network

You've just got to love support conversations that include phrases like "how long did you say this has been working for you?" and "who told you that?".

Whee. )
cellio: (avatar)
2002-04-04 06:24 pm
Entry tags:

(no subject)

Well, maybe tonight I'll be able to figure out what's wrong with the damned network connection. Off I go... (It's got to be between the modem and the outside world, and thus Verizon's problem. But the modem itself is the only part I can't either swap or drop out of the loop, so it could be an actual hardware failure. I'll admit, though, that I am trusting in Westel not to light the "ready" light if there's no signal coming in.)
cellio: (avatar)
2002-04-03 05:45 pm
Entry tags:

network connection

Last night our home network connection was dead, but I didn't have a lot of time to investigate it. (I tried all the simple stuff.) This morning it was still dead. I just tried pinging us from work and it appears it's still dead. Grumble. This means I have to start taking things apart... (Yes, I have a firewall and thus won't answer pings. But I should get a rejection notice, not silence, if the connection is there.)

The modem activity light flickers occasionally, but I don't know if that really means anything. The chain is: modem to linksys box to router box(es) to desktop machines. None of the machines that are presently network-aware can see the internet, though I can see the file server. (Dani can't, but his machine is flaky that way so that's inconclusive.) Presumably this means the problem is at or beyond the modem, but I know from past experience that Verizon won't talk to me if I admit to the real wiring. They want the modem to be plugged into a single machine and they'll want me to mess around with my TCP/IP settings even though the problem is not there. Bah. I've got to improve my mental model of all things Windows so I can fake my half of that conversation. :-)

Well, homeward to see if there are any quick fixes before heading out to D&D.
cellio: (Default)
2001-12-03 11:46 am
Entry tags:

DSL

We have a Stupid DSL Setup in our house, but I'm not sure what to do about it. (This thought is brought to mind by friends who were @home customers.)

Once upon a time, I worked for a company that had a policy of paying for a second phone line to support a modem (back in the days before DSL was available). They would pay for installation once.

When Dani and I moved into our house, DSL was available so we decided we wanted that. The company was in the process of figuring out its policies for paying for DSL. They told me to use the modem policy -- get a new phone line, bill the DSL to that, and put the phone line in the company's name.

But, I said, DSL doesn't compete with voice on the line; you don't *need* a second phone line. We can just add DSL to our existing line and you can pay (or reimburse) the DSL part of the bill.

No deal, they said. They would only pay for DSL if it came on a separate bill to them in the company's name. No reimbursement, no layering on an existing phone line.

Well, we said, this is profoundly stupid, but if they want to waste their money... we realized that at some point we would no longer be employed by that company and then we'd have a stupid situation on our hand, but what could we do?

So we got the phone line, and put DSL on it, and the company was happy, and the phone company was undoubtedly laughing all the way to the bank.

A couple weeks after our installation was complete, the company changed the policy to "we'll just give you $40/month if you have DSL and you deal with it". I was peeved, but moving the service would have cost a couple hundred dollars out of our pockets, so we left it alone.

When I got laid off, Dani and I talked about fixing this. But there are two things that have prevented us from doing anything thus far:

1. The current service works. For Verizon, this is no small feat. Moving the existing service would risk disruption for several weeks.

2. The current service is a permanent connection. New accounts are now PPPoE, which is we're told is a royal pain in the ass. And we'd have to reconfigure our network, and every time we look cross-eyed at the network something goes wrong. Why invite it? So if we set up a *second* account (and later kill the existing one, once it works), we'll be stuck with PPPoE because it will be a new account.

We don't actually know that moving the service would preserve our PPPoE-free existence; they might still screw that up. I'm pretty confident that I could not get a reliable answer from their customer-service people before committing, either.

So we are paying $18/month for an unnecessary phone line to preserve a correctly-functioning connection to the Internet. Is that lame, or what?