I did mine with an old cable. I cut it in a half and changed the wires order, and it works xD
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
I did mine with an old cable. I cut it in a half and changed the wires order, and it works xD
those powerline-style adapters usually use upnp and typically just suck. i do IT administration on the side and running a simple packet sniffer on the connection the powerline (or any other oe the sort) continuously shows dropped packets. that's not even considering the NAT in the router seemingly always wanting to block the ports the powerline connection requests through upnp. so yes, while tcp-ip technically does mean two-way communication, the powerline crap doesnt do a good job of it (on any other port except 80, the default internet port). defining ports (turning off upnp) doesnt help neither. the lack of a continuous twisted pair when using a powerline adapter also promotes transmission errors & packet loss. proper cabling ethics also means keeping ethernet cables at least 12 inches away from power lines and never running parallel to them (crossing perpendicular). untwisted & unshielded signalling theoretically can only run a distance of a few feet without errors.
i also do electrical contracting for a construction company that builds new homes. all side-by-side, cat5/cat5e/cat6 have increasing thicknesses - at least in my experience. there are two kinds of ethernet cabling: plenum and non-plenum. plenum cables are 4 solid wire twisted pairs; non-plenum are stranded wire twisted pairs. i've only used plenum cables, which are typically used in commercial buildings and higher-end home networking (newer homes or remodels incorporating wired ethernet in the wall) since it has a longer electrical life and overall just generally sturdier.
Last edited by sel2killa; 03-06-2012 at 07:09 AM.
From my experience from my studies on networking in year one of my Polytechnic education, I always thought that the Powerline adaptors replicate the physical media level of the OSI model (Hence, what has this got to do with uPnP?), and that the problems with packets getting dropped/poor throughput was caused by the powerline adaptors being unable to send and receive data amongst themselves quickly due to electrical interferrence (Which really worsens as the signal strength/connection LED on them turns orange from green).
But yea, I agree with you on the rest of this matter. Powerline adaptors don't give the performance they advertise on the outside. Without proper shielding (And since the electrical cables are not even twisted), interferrence impacts the signal quality between Powerline adaptors and impacts performance and data reliability severely (Might cause dropped packets).
Fair enough. It's just that I've never seen any thick CAT6 cables here in Singapore... yet. It's probably either because the network engineers of many of those buildings I've been to frequently don't use CAT6 cables or the shops here only sell those thin CAT6 cables (And those regular CAT5e cables).
This is what my CAT6 cables look like: http://www.computercableinc.com/ccin...k-BestLink.jpg
Well, thanks for sharing your experience with us. I never knew that thick CAT6 cables do exist as well.

The upnp not working is because the connection drops packets, so whichever port is being requested either never gets assigned by the router's nat. Kind of critical when you have software wanting to use more than just port 80. But yes, powerline still sucks! Lol? And you are correct, the powerline-style adapters all try to replicate the physical layer on top of the existing phy of the actual Ethernet adapter. Not at all efficient....
Last edited by sel2killa; 03-07-2012 at 02:54 AM. Reason: T
| « Previous Thread | Next Thread » |