Hi tia, Some local ISPs have been doing traffic control (some deny it). Anyway you could test by changing the port number.
But it could also be an incompatible MTU settings between the real and the virtual eth causing too much fragmentation. If your connection to the remote office is by DSL, try a 1400 mtu setting (or lower to accomodate the overhead of vpn packets). I believe DSLs are usually at 1492. A setting that you might also mess with is the MSS. I'm not sure about it, but I recall reading somewhere that mtu's should be multiples of mss to get optimum performance. agi On Wednesday 12 November 2008 12:38:34 pm plug bert wrote: > Hello All, > > i've been getting some strange problems from our ISP lately. We were > given a set of ip addresses along with our subscription, and we've used one > to set up a VPN going to our remote office. > > Right now i'm getting 1- 1.2second ping times; based on the traceroute > results, we're getting 100-120ms ping times going to the intermediate > routers, but are getting 1 second ping times to our remote office. > > > The odd thing is that our remote office reports no problems pinging our > immediate gateway, but they're also getting 1 second ping times pinging our > vpn server. > > Any ideas on what the problem might be? My guess is that there could be > some bandwidth/traffic control settings that may be messing up the > connection. > > tia > > > > > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
