-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "seth" == seth <seth@cql.com> writes:
seth> That's not what I meant. In no sense can the ethernet encoding be viewed as
seth> bits on the wire. There is no simple explanation, but basically the
seth> interpretation of the signal on the wire depends on the history of the signal.
Yes, FastEthernet encodes as sequences of MII symbols in a star pattern,
like modems, of which 16 of them encode 4 bits of data at a
time. GigEthernet, depending upon the media does other various things.
However, on FE, you can send a non-integral number of bytes, by sending an
odd number of nibbles.
In this case, it is 10Mb/s UTP, so there really are 8 bit times worth of
data, with appropriate manchester encoding. As this goes into a ADSL box,
and that box is *certainly* regenerating the signal on the wire (since it has
to shop it up in various ways to spread the bit errors over the FEC, and then
there is ATM encoding on top of that), it seems like some kind of cabling
issue.
For what it's worth, I think it went away! I did change the cable, but that
didn't immediately help. It is next to a cold basement wall, and it has been
- -40, so...
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBPi8k6IqHRg3pndX9AQElOgQAx8QadCmvt7xRksu17V4xN8aiaAYRrgX/
S5mekIHWfCWkZ4B9bbrzFl1Gn5eMCz5kMO3B1viEgfiT4QEEQw7MDInJuCGQvH0P
6GjSU09FXjm1NF9vXit/jeDNEuTCsmUzSUj6bZ43QdV64xCXXmPf4o0VRVyLdnlL
luQK4TvAdnE=
=rhJ7
-----END PGP SIGNATURE-----