|
| Boy, if that's the case, I would be ecstatic if I can get this
resolved. OK, say the scenario you described is applicable in my case.
How would I best explain this to my ADSL provider (SBC) to convince
them of an actual problem that falls within the scope of their service
guarantees? I'm worried that the conversation will end with "Well, you
can surf the internet, right? Then it's working as it shoud."
>From the central office (192.168.0.1), I tried pinging the opposite
routers for 2-3 minutes w/1427 bytes when the tunnels were working,
wasn't losing anything:
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=216ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=218ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=218ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.1.1: bytes=1427 time=217ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=173ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=171ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=171ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=171ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=171ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=171ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=170ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=171ms TTL=254
Reply from 192.168.2.1: bytes=1427 time=172ms TTL=254
Does this mean my problems don't match with what you had?
|
|