![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Dec. 17th, 2005
verdammit piece of crap
Dec. 17th, 2005 07:32 pmThe murkworks.net router has decided to pitch a gigantic hissyfit and not talk to one of its ethercards. We don't know why. We've swapped cards and cables (and portions of the hub and the hub isn't dead) so we don't know what's going on. I hate system administration.
No, we don't have an eta for uptime. Hopefully soon. Maybe our backup card is dead and it's two dead cards at once. (But the driver doesn't think so.)
Did I mention that I hate sysadmin work? God damn I hate it.
No, we don't have an eta for uptime. Hopefully soon. Maybe our backup card is dead and it's two dead cards at once. (But the driver doesn't think so.)
Did I mention that I hate sysadmin work? God damn I hate it.
Okay, so, once I got enough buffers on the 100mb backbone to be able to make any sense out of the 100mb hub's lights to tell what was going on, I found that lodestone was flooding the LAN with some sort of packet spew. This was not enough flood to interfere with traffic between most machines. However, if that traffic was on the net while bringing up door's on-LAN card (eth0; eth1 is the WAN card), the driver would initialise, and appeared to be able to transmit something, but not talk. With lodestone off the LAN, I was able to get door's card up; it then would survive - at least for a bit - the lodestone onslaught.
(I say "at least for a bit," because I had to restart door's LAN card this morning, too. But it came up cleanly and we were online for a few hours before falling down again. door is our router.)
Meanwhile, newmoon's TCP stack fell over as well, but unlike door, the IP layer stayed up; ICMP worked. Restarting the entire network layer brought it back around.
Back at lodestone, shutting down the network did not stop the strange-activity onslaught. That stayed on until power-down, indicating to me that it was a card issue. As lodestone has been up for over a year (I think it said 380 days), I'm initially willing to ascribe this to the bogon flux reaching critical. (Similarly, a simple reboot was not enough to bring lodestone back up; however, a power-cycle brought it up normally.)
Currently, we are back up and seem reasonably normal. However, I've never been happy with the driver situation on door, which exhibits other flaky behaviours as well. (They're self-compiled Netgear FA312 drivers on Debian, with the source grabbed from a redhat compile package.) For example, almost all successful packets also increment the carrier-error flag. I don't even know what a carrier error is in this context. This appears to be a driver bug. Since our uptime on door is on the order of four months - with occasional incidents like this, but a little different each time - it's not exactly a first-tier issue. And this time, the problem was, I think, triggered by another machine. But it still bugs me.
Anyway, I'm not really asking for help. But if somebody has something specific to say about this, yay.
(I say "at least for a bit," because I had to restart door's LAN card this morning, too. But it came up cleanly and we were online for a few hours before falling down again. door is our router.)
Meanwhile, newmoon's TCP stack fell over as well, but unlike door, the IP layer stayed up; ICMP worked. Restarting the entire network layer brought it back around.
Back at lodestone, shutting down the network did not stop the strange-activity onslaught. That stayed on until power-down, indicating to me that it was a card issue. As lodestone has been up for over a year (I think it said 380 days), I'm initially willing to ascribe this to the bogon flux reaching critical. (Similarly, a simple reboot was not enough to bring lodestone back up; however, a power-cycle brought it up normally.)
Currently, we are back up and seem reasonably normal. However, I've never been happy with the driver situation on door, which exhibits other flaky behaviours as well. (They're self-compiled Netgear FA312 drivers on Debian, with the source grabbed from a redhat compile package.) For example, almost all successful packets also increment the carrier-error flag. I don't even know what a carrier error is in this context. This appears to be a driver bug. Since our uptime on door is on the order of four months - with occasional incidents like this, but a little different each time - it's not exactly a first-tier issue. And this time, the problem was, I think, triggered by another machine. But it still bugs me.
Anyway, I'm not really asking for help. But if somebody has something specific to say about this, yay.
So here we are.
Dec. 17th, 2005 11:59 pmCourtesy ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
jwz's livejournal, we have this news story about how Federal agents are monitoring Inter-Library Loan, and investigating you if you request the wrong book. So we have warrentless spying on American citizens, monitoring of suspect book titles, every attempt they can get away with to eliminate posse comitatus for American citizens, and a desperate fight to be able to torture people on executive order.
Is there any power the Republican party won't trust the government with? Any? I really don't think so anymore. Once upon a time, I did. The complete betrayal of every professed principled position of the Republican party once had genuinely depresses me.
Agents' visit chills UMass Dartmouth senior
By AARON NICODEMUS, Standard-Times staff writer
http://www.southcoasttoday.com/daily/12-05/12-17-05/a09lo650.htm
NEW BEDFORD -- A senior at UMass Dartmouth was visited by federal agents two months ago, after he requested a copy of Mao Tse-Tung's tome on Communism called "The Little Red Book."
Two history professors at UMass Dartmouth, Brian Glyn Williams and Robert Pontbriand, said the student told them he requested the book through the UMass Dartmouth library's interlibrary loan program.
The student, who was completing a research paper on Communism for Professor Pontbriand's class on fascism and totalitarianism, filled out a form for the request, leaving his name, address, phone number and Social Security number. He was later visited at his parents' home in New Bedford by two agents of the Department of Homeland Security, the professors said.
The professors said the student was told by the agents that the book is on a "watch list," and that his background, which included significant time abroad, triggered them to investigate the student further.
[More at URL]
jwz's livejournal, we have this news story about how Federal agents are monitoring Inter-Library Loan, and investigating you if you request the wrong book. So we have warrentless spying on American citizens, monitoring of suspect book titles, every attempt they can get away with to eliminate posse comitatus for American citizens, and a desperate fight to be able to torture people on executive order.Is there any power the Republican party won't trust the government with? Any? I really don't think so anymore. Once upon a time, I did. The complete betrayal of every professed principled position of the Republican party once had genuinely depresses me.
Agents' visit chills UMass Dartmouth senior
By AARON NICODEMUS, Standard-Times staff writer
http://www.southcoasttoday.com/daily/12-05/12-17-05/a09lo650.htm
NEW BEDFORD -- A senior at UMass Dartmouth was visited by federal agents two months ago, after he requested a copy of Mao Tse-Tung's tome on Communism called "The Little Red Book."
Two history professors at UMass Dartmouth, Brian Glyn Williams and Robert Pontbriand, said the student told them he requested the book through the UMass Dartmouth library's interlibrary loan program.
The student, who was completing a research paper on Communism for Professor Pontbriand's class on fascism and totalitarianism, filled out a form for the request, leaving his name, address, phone number and Social Security number. He was later visited at his parents' home in New Bedford by two agents of the Department of Homeland Security, the professors said.
The professors said the student was told by the agents that the book is on a "watch list," and that his background, which included significant time abroad, triggered them to investigate the student further.
[More at URL]
