Date: Wed, 27 May 2020 21:22:32 -0400 From: "Donald Mickunas" <dmickunas1954@fastmail.com> To: "Cristian Cardoso" <cristian.cardoso11@gmail.com>, "Doug Hardie" <bc979@lafn.org> Cc: "FreeBSD PF List" <freebsd-pf@freebsd.org> Subject: Re: pkg slow down a lot with simple firewall. Message-ID: <0845d793-2c53-4433-b7a4-a6ca185575c6@www.fastmail.com> In-Reply-To: <CAKeEC-JrvWFWcLqg1D6EuE-3Bvscxox8fw_e=C76KeG=NpdH5A@mail.gmail.com> References: <804eeda4-03ed-4ec8-8755-3130e06382d8@www.fastmail.com> <CAKeEC-L1PTNU4Wr09rspFf7xkn1zE_%2BhghM7k6j9%2BbaZ3ObT-g@mail.gmail.com> <8347b16b-5b9b-4e62-88fc-a3f19dc138a8@www.fastmail.com> <0E48F161-081E-43F8-B00D-9888A48D7AA2@mail.sermon-archive.info> <51ae9da1-ccbb-4a1c-b1e3-155bce912cc5@www.fastmail.com> <E1A56113-CB15-40EF-A398-2DCE4EF900AF@mail.sermon-archive.info> <CAKeEC-JrvWFWcLqg1D6EuE-3Bvscxox8fw_e=C76KeG=NpdH5A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just a note. I have the manpage for pkg.conf printed and in a binder. = Thanks again. On Wed, May 27, 2020, at 20:36, Cristian Cardoso wrote: > I reinforce Doug's recommendation and if you want to log the things > that are possibly blocked, insert it in pf.conf >=20 > block in log all >=20 > About what Doug talked about starting the connection in IPv4 and > switching to IPv6, it is only the DNS request in IPv4 that is managing= > to answer the domain update.freebsd.org in IPv6, with that the pkg > requests come out via IPv6 >=20 > One thing that helped me a lot in the beginning was this URL: > https://www.freebsd.org/cgi/man.cgi?query=3Dpf.conf&sektion=3D5&n=3D1 >=20 > Em qua., 27 de mai. de 2020 =C3=A0s 19:18, Doug Hardie <bc979@lafn.org= > escreveu: > > > > > On 27 May 2020, at 14:38, Donald Mickunas <dmickunas1954@fastmail.= com> wrote: > > > > > > Thanks, Doug. > > > > > > Here are the results after running pkg update once. > > > > > > $ sudo tcpdump -n -e -ttt -r /var/log/pflog > > > Password: > > > reading from file /var/log/pflog, link-type PFLOG (OpenBSD pflog f= ile) > > > 00:00:00.000000 rule 7/0(match): pass out on em0: 192.168.1.4.2533= 4 > 192.168.1.1.53: 18844+[|domain] > > > 00:00:00.049750 rule 7/0(match): pass out on em0: 192.168.1.4.4885= 5 > 192.168.1.1.53: 59873+[|domain] > > > 00:00:00.049459 rule 9/0(match): pass out on em0: 192.168.1.4.123 = > 209.94.190.139.123: NTPv4, Client, length 48 > > > 00:00:00.887723 rule 9/0(match): pass out on em0: 192.168.1.4.123 = > 64.6.144.6.123: NTPv4, Client, length 48 > > > 00:00:29.345987 rule 7/0(match): pass out on em0: 192.168.1.4.5171= 8 > 192.168.1.1.53: 49030+[|domain] > > > 00:00:00.442261 rule 7/0(match): pass out on em0: 192.168.1.4.1222= 8 > 192.168.1.1.53: 15101+[|domain] > > > 00:00:00.105498 rule 7/0(match): pass out on em0: 192.168.1.4.3165= 2 > 192.168.1.1.53: 56618+[|domain] > > > 00:00:00.136933 rule 3/0(match): pass out on em0: 2600:6c5c:6000:3= 2a0:1a03:73ff:fe3a:d596.60802 > 2610:1c1:1:606c::50:1.80: [|tcp] > > > 00:00:34.523685 rule 9/0(match): pass out on em0: 192.168.1.4.123 = > 74.6.168.73.123: NTPv4, Client, length 48 > > > 00:00:00.526029 rule 3/0(match): pass out on em0: 192.168.1.4.1291= 3 > 96.47.72.71.80: Flags [S], seq 1540288966, win 65535, options [mss 1= 460,nop,wscale 6,sackOK,TS[|tcp]> > > > 00:00:00.075191 rule 7/0(match): pass out on em0: 192.168.1.4.1140= 3 > 192.168.1.1.53: 30468+[|domain] > > > 00:00:00.000800 rule 7/0(match): pass out on em0: 192.168.1.4.2714= 5 > 192.168.1.1.53: 3978+[|domain] > > > 00:00:00.000739 rule 3/0(match): pass out on em0: 2600:6c5c:6000:3= 2a0:1a03:73ff:fe3a:d596.64864 > 2610:1c1:1:606c::50:1.80: [|tcp] > > > 00:00:18.977520 rule 3/0(match): pass out on em0: 192.168.1.4.5849= 7 > 96.47.72.71.80: Flags [S], seq 2776579475, win 65535, options [mss 1= 460,nop,wscale 6,sackOK,TS[|tcp]> > > > 00:00:00.082616 rule 7/0(match): pass out on em0: 192.168.1.4.1524= 8 > 192.168.1.1.53: 2366+[|domain] > > > 00:00:00.000531 rule 7/0(match): pass out on em0: 192.168.1.4.6547= 5 > 192.168.1.1.53: 41713+[|domain] > > > 00:00:00.000772 rule 3/0(match): pass out on em0: 2600:6c5c:6000:3= 2a0:1a03:73ff:fe3a:d596.55684 > 2610:1c1:1:606c::50:1.80: [|tcp] > > > 00:00:18.883826 rule 3/0(match): pass out on em0: 192.168.1.4.2503= 9 > 96.47.72.71.80: Flags [S], seq 222404333, win 65535, options [mss 14= 60,nop,wscale 6,sackOK,TS[|tcp]> > > > $ > > > > > > I have no idea how to interpret this. Any help would be appreciat= ed. > > > > That is quite unexpected. The connection starts out with IPv4 and t= hen switches to IPv6. It also only shows the output packets so delays c= aused at the server end cannot be distinguished. I would recommend usin= g tcpdump to see the entire transaction. > > > > In one window, start tcpdump with: > > tcpdump -ixxx -ttt -s0 -X port 80 > > > > Here you need to replace xxx above with your interface name. You ca= n find it in the output of ifconfig. It will be the interface that has = your IP address in it. For example, mine is: > > > > bge0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> m= etric 0 mtu 1500 > > options=3Dc019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_H= WCSUM,TSO4,VLAN_HWTSO,LINKSTATE> > > ether 38:c9:86:07:3b:5b > > inet 10.0.1.250 netmask 0xffffff00 broadcast 10.0.1.255 > > inet6 fe80::3ac9:86ff:fe07:3b5b%bge0 prefixlen 64 scopeid 0x= 1 > > inet6 fee1::250 prefixlen 64 > > media: Ethernet autoselect (100baseTX <full-duplex>) > > status: active > > nd6 options=3D23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> > > > > and the interface name is bge0. > > > > Then in the second window start the pkg update command. Note, tcpdu= mp will produce a lot of output. The output will have a time stamp (hou= rs:minutes:seconds.microseconds). It will be a delta time from the prev= ious packet. Look for one where the seconds are greater than zero. Tha= t is where the delays are occurring. > > > > -- Doug >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0845d793-2c53-4433-b7a4-a6ca185575c6>