I have a circuit that I am able to ping with pattern of 0's just fine, but when I ping with 1's I get about 95% packetloss. I have seen an issue with optioning problems on a DS1 when there was a B8ZS/AMI mismatch, but in that case I couldn't ping with 0's but could with 1's. The symptoms are the same for the enduser which is trouble with anything that is compressed data, i.e., jpgs, zip files..and the like...text transfer is fine...any help would be appreacitated. The connection comes of a cisco 7206, I have other connections that are fine with both types of pings...
here is what I see
$ ping -p 1 x.x.59.77
PATTERN: 0x01
PING x.x.59.77 (x.x.59.77) from 10.25.254.230 : 56(84) bytes of data.
--- x.x.59.77 ping statistics ---
19 packets transmitted, 0 received, 100% loss, time 18016ms
$ ping -p 0 x.x.59.77
PATTERN: 0x00
PING x.x.59.77 (x.x.59.77) from 10.25.254.230 : 56(84) bytes of data.
64 bytes from x.x.59.77: icmp_seq=1 ttl=60 time=8.24 ms
64 bytes from x.x.59.77: icmp_seq=2 ttl=60 time=8.02 ms
64 bytes from x.x.59.77: icmp_seq=3 ttl=60 time=7.84 ms
64 bytes from x.x.59.77: icmp_seq=4 ttl=60 time=7.94 ms
--- x.x.59.77 ping statistics ---
4 packets transmitted, 4 received, 0% loss, time 3030ms
rtt min/avg/max/mdev = 7.845/8.016/8.245/0.183 ms
also getting wierd ping responses with packet size of 1500
$ ping x.x.59.77 -s 1500
PING x.x.59.77 (x.x.59.77) from 10.25.254.230 : 1500(1528) bytes of data.
1480 bytes from x.x.59.77: icmp_seq=1 ttl=60 (truncated)
1480 bytes from x.x.59.77: icmp_seq=2 ttl=60 (truncated)
1480 bytes from x.x.59.77: icmp_seq=3 ttl=60 (truncated)
1480 bytes from x.x.59.77: icmp_seq=4 ttl=60 (truncated)
1480 bytes from x.x.59.77: icmp_seq=5 ttl=60 (truncated)
1480 bytes from x.x.59.77: icmp_seq=6 ttl=60 (truncated)
--- x.x.59.77 ping statistics ---
6 packets transmitted, 6 received, 0% loss, time 5043ms
rtt min/avg/max/mdev = 70.072/70.180/70.276/0.166 ms
