jpalmer is checking out the revolving door lol RandalSchwartz nah, I was updating my irc client, and related configs. at the expense of 24KB of my bandwidth as if it grows on [spanning] trees STP itself will consume far more bandwidth than a few joins ;P phlux: omg your merry christmas banner was awesome NTT: "Failing piece of hardware appears to have failed" well, yeah... that RFO was funny lol AT&T just wasted 30 minutes of my life new router: ICMP works, SSH does not what why? after 30 minutes of restarting and stuff, I try to telnet to my server port 80 and find that instead of rejecting PPPoE auth they put you in a captive portal and leave ICMP working for good measure oh i hate captive portals :) apparently my middle initial is not in my username i hate "free" wifi that expects you to do complicated portal stuff to work they really should ditch usernames honestly having access to the wire is enough for DSL and just do port auth, makes things simpler pppoe is fine, it may work in with their systems beter. better yeah I'm not sure that you can do auth-less PPPoE you can it's common here. but often you need something, anything as a username. maybe it's billing. the part that knows which wire goes to which house just isn't connected it complicates things unncessarily. what happens if you sell your modem to another at&T user who plugs it in and starts using your username? they could've just rejected auth instead of accepting and allowing the basic network test (ping) you erase your username before you sell your modem? I guess that's expecting too much that kind of thing is common, with at least dns working yeah it's expecting too much I guess expecting anything other than plug in open a web browser is too much which is why it took me 30 minutes to find a captive portal basically they can tag you, and know who's account it is some people use usernames for static ip's, and dynamic for the rest. heh but they could do that knowing which wire the connection comes in on? perhaps that equipment doesn't talk to the parts that need to know who is who yeah they should know what dslam port you're provisioned on at exchange they should even know what wire you're connected to on the cable bundles down the street. "should know" AT&T's guys were still claiming our phone troubles were our side when we could hear literal crosstalk i hate crosstalk. it's often that things aren't protected from weather properly. and are getting wet. That's what she said!! but we couldn't talk to them; it was one way. does that still fit? I could see a short putting the wires together, but if it's one way that doesn't make sense? one way is common I don't know much about what goes on on the phone side of things yeah i dunno how it works tbh but i've had the same thing happen to me before. and it's always happened more after it rains. sometimes a couple days after it rains too though often you get no dialtone soon afterwards though anyway, dsl is pretty resilient. even with crosstalk etc your net is probably quite usable. so if you want to get it fixed here at least you have to log it as a phone problem not an internet problem. yeah we never even really saw trouble on the DSL side it can kill your sync rate by like 10% and if it's bad it can cause disconnections sometimes. i used to have a dodgy line that'd disconnect about 3 to 5 times a week. good luck trying to get that fixed :) here they don't want to fix problems unless it happens like 7 times a day yeah they won't listen if it's working "now" and sometimes their definition of working is different from mine it was only unstable when they put a new dslam in closer but i've had that problem before too. net is fine, new dslam closer, sync rate much faster but unstable. one of them was the dslam didn't like ar7 chipset modems... and ar7 chipset is the only one supported by openwrt.