On 6/5/07, Carlos F Lange wrote:

I did that. I just assigned the usual IP number in Yast (along with subnet mask and gateway), but I still cannot ping the gateway or other machines in the LAN, nor is it seen by them.

Check if you have installed netdiag package. It contains mii-diag utility, which can produce more information about the card. You can use it as well to force it to use only 10 or 100 connection, etc. I had problems with a netwrok card, which could not negotiate correctly 100 mbps speed because of faulty cable, and I could make it run on 10 mbps, until I found out that the problem is with the cable, and I need to replace it. Cheers -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

M Harris wrote:

On Tuesday 05 June 2007 12:53, Sunny wrote:

...

I had problems with a netwrok card, which could not negotiate correctly 100 mbps speed because of faulty cable, and I could make it run on 10 mbps, until I found out that the problem is with the cable, and I need to replace it.

I had the same problem... new cable solved the problem. For 100 always use the cat 6 cables with the gold leads... they're a little more... but they're worth every penny.

Disagree. For 100Mbps, just get Cat. 5. It'll work fine. Spend your pennies on something else. That's not to say the odd cable doesn't need replacing, but that's usually due to damage. I don't think Cat. 6 is immune to that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John E. Perry wrote:

Russell Jones wrote:

...

... Disagree. For 100Mbps, just get Cat. 5. It'll work fine. Spend your pennies on something else.

Same here. I have my home network connected with cat-5E (only a little more costly than cat-5 when I bought it, and it runs 100Mbps just fine -- even over the 40 ft to my son's room.

John Perry

If I remember correctly shielding is a two way thing, basically you are running a potential 40ft radio aerial in the latter case. If you have a lot of cables or have anything which is sensitive to radio emissions close by, Cat 6 starts making sense. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGZ8rDasN0sSnLmgIRAnuYAJ9icYWPE6PNTCgUnUh9It+RtZBr+gCfRalU UD+EGY9vqOn2SHlaopuq1Ag= =AXv8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 07 June 2007, James Knott wrote:

...

If I remember correctly shielding is a two way thing, basically you are running a potential 40ft radio aerial in the latter case. If you have a lot of cables or have anything which is sensitive to radio emissions close by, Cat 6 starts making sense.

????

There are two ways to reduce interference to & from a cable.  Those are shielding and twisted pairs.  UTP cable, including CAT 6 relies on twisted pairs to reduce interference.  Unless the twist rate for CAT 6 is significantly more than CAT 5, there will be little difference between the two for interference purposes.

Exactly so. Also this 40 foot figure bandied about here totally ignores the fact that entire buildings are wired with CAT5 runs much longer than that with no problem. -- _____________________________________ John Andersen

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Knott wrote:

John Andersen wrote:

...

On Thursday 07 June 2007, James Knott wrote:

...

...

If I remember correctly shielding is a two way thing, basically you are running a potential 40ft radio aerial in the latter case. If you have a ^^^^^^^^^ lot of cables or have anything which is sensitive to radio emissions ^^^ close by, Cat 6 starts making sense. ^^^^^^

????

Clarifications

'potential' not actual, I have come across scenarios with old battered bits of wire holding things together, and the more the thing twists, turns and gets squeezed the worse the issue becomes. Of course the odd nail through the wire makes life more interesting... :-) By a lot, I mean bundles of wires not loads of single wires (apparently cabling spaghetti is a good thing and neatly parallel bundles are not). I remember a report in institution I worked for, of a rather expensive bit of research kit which after installation started apparently randomly recalibrating itself. It was only when someone had the bright idea of checking the local train timetable, it was realised recalibration coincided with certain electric diesel services on a train line about 100m from the location of the equipment. Electrical interference can be an issue in all sorts of odd ways. The CAT6 does have a significantly better crosstalk specification. NEXT spec of 44.3db as against 35.3db, as this is a logarithmic measure, in this case I think this means that CAT 6 should be approx. twice as effective as CAT 5 in this area. The spec seems to be aimed at GigaByte ethernet and is rated at 250MHz (I assumed this indicates use of all eight wires for this purpose). CAT 5e is apparently (a not really defined) standard, with some additional specs on the crosstalk department defined. For home use CAT5 would probably be adequate in most cases, though when one starts talking lots of longish cable runs WiFi makes more sense.

Yep, up to 100M or about 330'.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGaTpaasN0sSnLmgIRAh6gAKCGMGI0DkDnPcSqBYX8fJWxXu7rbQCfXQga T3jEoUnpJb3Zar5HFWgWKOQ= =Jj+6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John E. Perry wrote:

James Knott wrote:

...

G T Smith wrote:

...

John E. Perry wrote:

...

Russell Jones wrote:

...

... Disagree. For 100Mbps, just get Cat. 5. It'll work fine. Spend your pennies on something else.

Same here. I have my home network connected with cat-5E (only a little more costly than cat-5 when I bought it, and it runs 100Mbps just fine -- even over the 40 ft to my son's room. John Perry

If I remember correctly shielding is a two way thing, basically you are running a potential 40ft radio aerial in the latter case. If you have a lot of cables or have anything which is sensitive to radio emissions close by, Cat 6 starts making sense.

????

There are two ways to reduce interference to & from a cable. Those are shielding and twisted pairs. UTP cable, including CAT 6 relies on twisted pairs to reduce interference. Unless the twist rate for CAT 6 is significantly more than CAT 5, there will be little difference between the two for interference purposes.

In fact, twisting is superior to shielding in practical installations, unless there's a great deal of near-field interference, when shielding can be really effective. But the purpose of the high-quality cables is to preserve waveform fidelity, which is why the more carefully made cables give better bandwidth.

I didn't know cat-6 cables were available yet. I'll have to give it a look.

This is true, but they won't give you any better performance for 100Mbps. If there's an EMR source bad enough to affect them, you should work around it (move it or the cables, or perhaps shield them better, e.g. with metal ducting) not replace them with Cat. 6, or other more heavily shielded cable, unless there's really no other way. In normal situations, though, you just don't need them. You can put bundles of dozens of shielded Cat. 5 cables in your walls without any problems of crosstalk (doing this redundantly is a good way of being prepared for faults in cables that may develop later). By all means though, buy shielded rather than unshielded Cat. 5 (or Cat. 5e if you want to be pedantic; but you can't easily get anything else, so it's not a very relevant distinction). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org