|
|
Hi Tom,
Thanks for helping out thus far, I feel like I've almost got it working
perfectly.
It seems that http no longer works, but it might be other protocols as
well. Http is most important, so it's what i noticed first. I believe
it's an mtu issue.. i am also seeing truncated-ip errors..
15:50:01.320770 truncated-ip - 214 bytes missing! 198.175.96.33.80 >
64.90.164.230.4729: . 1:1461(1460) ack 578 win 16943 (DF)
I believe it's an mtu issue, but i have no idea which mtu setting to
set (there are about 5 different mtu related options) and what to set
it to,
Alex
On Thursday, September 4, 2003, at 01:36 PM, Tom Bin wrote:
Alex,
I am happy to know your vpn is working well now.
It's a really cool vpn solution.
I think you're on to something.. I noticed that when i set an IP on
the tap devices, i started seeing traffic from the other side on one
side of the segment. This however seems to only be happening on one
half of the network. It's strange, I set ip's on both sides,
everything i do on one side i'm now doing on the other to make it
symmetrical. But ping packets from outside i only see on one side and
not the other. Any idea what could be causing this?
I am not sure what happened to the ping packets.
I need to know more detailed information to figure it out.
Ex. the ip of all your interfaces, from which interface did you ping to
where.....
how you bridge your interfaces....
Also is it documented anywhere that ip addresses need to be set on tap
devices? It doesn't seem to follow any logic i was aware of, so it
should probably be stated somewhere (or at least an explaination
written somewhere why this is critical).
Yes, I agree with you.
What we saw is against what we know.
Tom
____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users
|