![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
New Year, Better Year?
Well, my sinus infection has died back to a whisper. Megadoses of vitamin C and many of my hoarded allergy meds later.
A friend is going to come up with some money to cover my insurance bill (thanks![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
dubhain) so I don't lose it.
I got a call from one of my agencies today, and I'll have about 5 days work later this month (at $10/hr - not princely, but >> 0). So I will have that in time for the March rent, which means that I can go ahead and have the car work done.
We got our house lan up today, after D got to learn about cat5 and 100baseT ethernet...
It seems that D, when he made ethernet cables, just made plain straight through cables - i.e. green pr, orange pr, blue pr, and brown pr. Now, this is fine for 10baseT ethernet, although not really according to spec. He didn't know this, and when told, said it shouldn't make a difference because the straight ones worked... for 10bT.
So we plug the router/firewall into the cable modem last night, and the switches downstream from that. All devices downstream of the router are 100bT capable. Should just work. It's *not* rocket science.
The one that is connected with the cheap commercial cable by a short run to the router is fine. The one to S's room is not - no steady connect light at the router (all on, then off, lather, rinse, repeat), not able to ping gateway. Fine. Unplug the switch, do a pass through. Still fscked. Troubleshoot, get it through to D that it *is* a cable problem. Great, he'll have to restring through the attic.
I ask about making new cables. He comes off with the straight through thing again. I use his system, which is up, to search for a howto, and show him the correct wiring. Pins 3 and 6 *must* be from the same pair. He doesn't really believe me, but plans to make the changes (today).
I go to bed. He then plugs in the switch in his room, again on a long, homemade cable. *Same problem* at the router, and no connect.
This morning, he gets up, grumbles, and since there's nothing else to try (except restringing cable, which is grief), tries putting new connectors on, wired according to the standard I dug up on the net. Does his room first, it's easier to get at.
Success, of course.
Does S's room, has problem (wired the hard to get at one backwards - connector upside down). I suggested redoing the other end, and putting the connector upside down there, too. D looks dubious, but does it. Finally gets the computer plugged in to the right port (uplink and one straight through are either/or).
Guess what? It works.
The moral(s)?? a) 100bT *is* sensitive to crosstalk if pin 3 & 6 are not the same twisted pair, b) when in doubt, listen to the person who has done it before, c) RTFM, damnit!
The T568A(number may be wrong) spec, for those who care:
1) white-green
2) green
3) *white-orange
4) white-blue
5) blue
6) *orange
7) white-brown
8) brown
The only connectors actually used are 1, 2, 3, and 6. 4 and 5 are telephone, and not used in case of misplug.
Happy New Year!
A friend is going to come up with some money to cover my insurance bill (thanks
dubhain) so I don't lose it.I got a call from one of my agencies today, and I'll have about 5 days work later this month (at $10/hr - not princely, but >> 0). So I will have that in time for the March rent, which means that I can go ahead and have the car work done.
We got our house lan up today, after D got to learn about cat5 and 100baseT ethernet...
It seems that D, when he made ethernet cables, just made plain straight through cables - i.e. green pr, orange pr, blue pr, and brown pr. Now, this is fine for 10baseT ethernet, although not really according to spec. He didn't know this, and when told, said it shouldn't make a difference because the straight ones worked... for 10bT.
So we plug the router/firewall into the cable modem last night, and the switches downstream from that. All devices downstream of the router are 100bT capable. Should just work. It's *not* rocket science.
The one that is connected with the cheap commercial cable by a short run to the router is fine. The one to S's room is not - no steady connect light at the router (all on, then off, lather, rinse, repeat), not able to ping gateway. Fine. Unplug the switch, do a pass through. Still fscked. Troubleshoot, get it through to D that it *is* a cable problem. Great, he'll have to restring through the attic.
I ask about making new cables. He comes off with the straight through thing again. I use his system, which is up, to search for a howto, and show him the correct wiring. Pins 3 and 6 *must* be from the same pair. He doesn't really believe me, but plans to make the changes (today).
I go to bed. He then plugs in the switch in his room, again on a long, homemade cable. *Same problem* at the router, and no connect.
This morning, he gets up, grumbles, and since there's nothing else to try (except restringing cable, which is grief), tries putting new connectors on, wired according to the standard I dug up on the net. Does his room first, it's easier to get at.
Success, of course.
Does S's room, has problem (wired the hard to get at one backwards - connector upside down). I suggested redoing the other end, and putting the connector upside down there, too. D looks dubious, but does it. Finally gets the computer plugged in to the right port (uplink and one straight through are either/or).
Guess what? It works.
The moral(s)?? a) 100bT *is* sensitive to crosstalk if pin 3 & 6 are not the same twisted pair, b) when in doubt, listen to the person who has done it before, c) RTFM, damnit!
The T568A(number may be wrong) spec, for those who care:
1) white-green
2) green
3) *white-orange
4) white-blue
5) blue
6) *orange
7) white-brown
8) brown
The only connectors actually used are 1, 2, 3, and 6. 4 and 5 are telephone, and not used in case of misplug.
Happy New Year!