ping www.jolt.co.uk Pinging www.jolt.co.uk [84.234.17.86] with 32 bytes of data: Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Ping statistics for 84.234.17.86: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum

ping jolt.co.uk" target=_blank>www.jolt.co.uk Pinging www.jolt.co.uk [84.234.17.86] with 32 bytes of data: Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Reply from 84.234.17.86: bytes=32 time=13ms TTL=123 Ping statistics for 84.234.17.86: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum

take place within a few hours, rather than having to wait the number of days for a switch to normally take place. Ping times are good too: alan-macbook:~ alan$ ping www.jolt.co.uk PING www.jolt.co.uk (84.234.17.86): 56 data bytes 64 bytes from 84.234.17.86: icmp_seq=0 ttl=119 time=21.572 ms 64 bytes from 84.234.17.86: icmp_seq=1 ttl=119 time=19.626 ms 64 bytes from 84.234.17.86: icmp_seq=2 ttl=119 time=19.717

take place within a few hours, rather than having to wait the number of days for a switch to normally take place. Ping times are good too: alan-macbook:~ alan$ ping www.jolt.co.uk PING www.jolt.co.uk (84.234.17.86): 56 data bytes 64 bytes from 84.234.17.86: icmp_seq=0 ttl=119 time=21.572 ms 64 bytes from 84.234.17.86: icmp_seq=1 ttl=119 time=19.626 ms 64 bytes from 84.234.17.86: icmp_seq=2 ttl=119 time=19.717

take place within a few hours, rather than having to wait the number of days for a switch to normally take place. Ping times are good too: alan-macbook:~ alan$ ping www.jolt.co.uk PING www.jolt.co.uk (84.234.17.86): 56 data bytes 64 bytes from 84.234.17.86: icmp_seq=0 ttl=119 time=21.572 ms 64 bytes from 84.234.17.86: icmp_seq=1 ttl=119 time=19.626 ms 64 bytes from 84.234.17.86: icmp_seq=2 ttl=119 time=19.717

Unfortunately, ZyXEL is awesome at DSL stuff and 877s are... not. Actually, can you ping www.jolt.co.uk whilst you're at it and paste results? (from behind the 877 and then the 660 would be awesome)

purpose? I am aware of Wireless Box II both providers use and although I do not hold it in high esteem, after some telnet tweaking they work pretty well. Pinging www.jolt.co.uk on Ethernet connection: PING www.jolt.co.uk (84.234.17.86) 56(84) bytes of data. 64 bytes from bruce.ferrago.net (84.234.17.86): icmp_seq=1 ttl=117 time=986 ms 64 bytes from bruce.ferrago.net (84.234.17.86): icmp_seq=2 ttl=117 time=932 ms 64

purpose? I am aware of Wireless Box II both providers use and although I do not hold it in high esteem, after some telnet tweaking they work pretty well. Pinging jolt.co.uk" target=_blank>www.jolt.co.uk on Ethernet connection: PING www.jolt.co.uk (84.234.17.86) 56(84) bytes of data. 64 bytes from bruce.ferrago.net (84.234.17.86): icmp_seq=1 ttl=117 time=986 ms 64 bytes from bruce.ferrago.net (84.234.17.86): icmp_seq=2 ttl=117 time=932 ms 64

purpose? I am aware of Wireless Box II both providers use and although I do not hold it in high esteem, after some telnet tweaking they work pretty well. Pinging www.jolt.co.uk on Ethernet connection: PING www.jolt.co.uk (84.234.17.86) 56(84) bytes of data. 64 bytes from bruce.ferrago.net (84.234.17.86): icmp_seq=1 ttl=117 time=986 ms 64 bytes from bruce.ferrago.net (84.234.17.86): icmp_seq=2 ttl=117 time=932 ms 64

comparison and costs documents. Many people are unhappy with O2/Be box wireless performance, though for my purposes mine was fine. O2, interleaved, Stepping Hill exchange (south of STockport, Manchester):- C:\Users\Bob>ping www.jolt.co.uk Pinging www.jolt.co.uk [84.234.17.86] with 32 bytes of data: Reply from 84.234.17.86: bytes=32 time=22ms TTL=123 Reply from 84.234.17.86: bytes=32 time=23ms TTL=123 Reply from 84.234.17.86: bytes=32 time=22ms TTL=123 Reply from 84.234.17.86: