iptables forwarding question
James Pifer
jep at obrien-pifer.com
Fri Mar 17 21:32:36 UTC 2006
> >
> > No, I sure didn't give much info.
> >
> > I don't have access to server2.
>
> Not a ton of suggestions based on what you sent. Try 'ping'ing server2.
> Your log suggests you may have noticable packet loss. 'ping' will tell you
> if that is your problem.
>
> - Benjamin Franz
>
>
I had a chance to do this right now on a windows machine. I let it ping
40 or 50 times. It had one little hiccup in the middle, but otherwise
seemed ok. The response times are about the same as what I see on my
linux machine that is the router.
Thanks,
James
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=128ms TTL=57
Reply from server2: bytes=32 time=112ms TTL=57
Reply from server2: bytes=32 time=125ms TTL=57
Reply from server2: bytes=32 time=142ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=122ms TTL=57
Reply from server2: bytes=32 time=118ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=114ms TTL=57
Reply from server2: bytes=32 time=118ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=121ms TTL=57
Reply from server2: bytes=32 time=128ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=111ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Request timed out.
Reply from server2: bytes=32 time=418ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=122ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=114ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=120ms TTL=57
Reply from server2: bytes=32 time=112ms TTL=57
Reply from server2: bytes=32 time=112ms TTL=57
Reply from server2: bytes=32 time=120ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=114ms TTL=57
Reply from server2: bytes=32 time=132ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=118ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=123ms TTL=57
Reply from server2: bytes=32 time=120ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=139ms TTL=57
More information about the fedora-list
mailing list