Date: Thu, 26 Feb 2015 10:26:50 +0200 From: Ercan Deger <ercandeger76@gmail.com> To: Kevin Oberman <rkoberman@gmail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Cant Access Web site Message-ID: <CAKjZa6VyB5GEoaJcPDbTHEbZ9Q3HChOBgEO52akRuDO8or3o5w@mail.gmail.com> In-Reply-To: <CAN6yY1t4Xq7W8%2Bq5uRhKQKLq%2BV94Nyf42rmtE8%2Bu3xevQC9fTA@mail.gmail.com> References: <CAKjZa6Xg5805QdzJD23PBrKSQKNoiLa%2BphXwbd-fXvyMHc80rw@mail.gmail.com> <CAN6yY1t4Xq7W8%2Bq5uRhKQKLq%2BV94Nyf42rmtE8%2Bu3xevQC9fTA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] I added captured packed, when I open this file via wireshark It shows lots of Fragmented IP Protocol (proto=TCP 6, off=0, id=cbxx) when I change the outside interface mtu to 1492 I can access via squid this site but still cant access without squid I think MTU specific problem but cant solve :( >> > The data you provided shows little. It would be nice to see both sides of > the session. > > I really suggest that you capture the whole session. Something like > "tcpdump -p -s0 -w some_file.bpf tcp port 81 and host 85.96.xx.xx" will > save the packet data to "some_file.bpf" and then you can use other tools to > analyze it. I use wireshark. It's free, in ports and works quite well. It > will flag packets which have issues and handle breaking down the prorocols. > Since port 81 is not the "normal" http port, you will need to tell > wireshark that. I have not had to do that in a while, but it was pretty > obvious. > > wireshark can also do the capture directly, but I'll admit that after > years of using tcpdump (two of the authors used to sit down the hall from > me), I have never tried to use wireshark for packet capture. > -- > Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > [-- Attachment #2 --] ò fTW <
