Why is so slow the download speed in OpenBSD?
Hello, I'm using the latest release. Where the dl speed in other OS is approx. 1.4 MB/s in BSD is only approx. 240 KB/s. Why is this? Is about a setting in some config file that limits download/traffic rate? Thanks.
Re: Why is so slow the download speed in OpenBSD?
Hi Zsolt, in order to help us help you try to include more information output from dmesg , what is your network configuration ifconfig route -n show there is no default queuing in OpenBSD that would limit you that badly Thanks On 11 February 2018 at 19:15, Zsolt Kantor wrote: > Hello, > I'm using the latest release. Where the dl speed in other OS is approx. 1.4 > MB/s in BSD is only approx. 240 KB/s. Why is this? Is about a setting in some > config file that limits download/traffic rate? > > Thanks. > -- Kindest regards, Tom Smyth Mobile: +353 87 6193172 The information contained in this E-mail is intended only for the confidential use of the named recipient. If the reader of this message is not the intended recipient or the person responsible for delivering it to the recipient, you are hereby notified that you have received this communication in error and that any review, dissemination or copying of this communication is strictly prohibited. If you have received this in error, please notify the sender immediately by telephone at the number above and erase the message You are requested to carry out your own virus check before opening any attachment.
Re: Why is so slow the download speed in OpenBSD?
On 02/11/18 20:15, Zsolt Kantor wrote: > I'm using the latest release. Where the dl speed in other OS is approx. 1.4 > MB/s in BSD is only approx. 240 KB/s. Why is this? Is about a setting in some > config file that limits download/traffic rate? You're not giving us a lot to work with here. But to answer your question, no, just take a peek at /etc/pf.conf (or run doas pfctl -sr). If you're running with the default config, there is no queueing going on. With no information other than "it's slow" I would have to start guessing. The first thing I'd check is ifconfig output for the interfaces relevant to your traffic. Are they running in a suboptimal mode for some reason? Just to pick a random example, a gigabit interface that for some reason is stuck at 10 or 100 Mbit or even mismatched duplex settings or a wireless interface that for some reason did not get one of the better N modes would fit the symptoms you describe. But so would quite a few other things. You really need to supply more information if you want useful help in troubleshooting. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Why is so slow the download speed in OpenBSD?
Below I provide full information from ifconfig, route and a full dmesg. By the way, I think this is a BUG in the wireless firmware that I'm using (downloaded from the OpenBSD firmware site). I say this because I found this line in the dmesg output: wpi0: fatal firmware error So below are the outputs. ifconfig output: lo0: flags=8049 mtu 32768 index 4 priority 0 llprio 3 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 re0: flags=8802 mtu 1500 lladdr 00:1f:16:03:90:fe index 1 priority 0 llprio 3 media: Ethernet autoselect (none) status: no carrier wpi0: flags=8843 mtu 1500 lladdr 00:1f:3c:8d:aa:a2 index 2 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect (DS1 mode 11g) status: active ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 enc0: flags=0<> index 3 priority 0 llprio 3 groups: enc status: active pflog0: flags=141 mtu 33136 index 5 priority 0 llprio 3 groups: pflog route -n show output: Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default192.168.0.1UGS3 450 -12 wpi0 224/4 127.0.0.1 URS0 12 32768 8 lo0 127/8 127.0.0.1 UGRS 00 32768 8 lo0 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 Internet6: DestinationGatewayFlags Refs Use Mtu Prio Iface ::/96 ::1UGRS 0 0 32768 8 lo0 ::/104 ::1UGRS 0 0 32768 8 lo0 ::1::1UHhl 14 34 32768 1 lo0 ::127.0.0.0/104::1UGRS 0 0 32768 8 lo0 ::224.0.0.0/100::1UGRS 0 0 32768 8 lo0 ::255.0.0.0/104::1UGRS 0 0 32768 8 lo0 :::0.0.0.0/96 ::1UGRS 0 0 32768 8 lo0 2002::/24 ::1UGRS 0 0 32768 8 lo0 2002:7f00::/24 ::1UGRS 0 0 32768 8 lo0 2002:e000::/20 ::1UGRS 0 0 32768 8 lo0 2002:ff00::/24 ::1UGRS 0 0 32768 8 lo0 fe80::/10 ::1UGRS 0 0 32768 8 lo0 fec0::/10 ::1UGRS 0 0 32768 8 lo0 fe80::1%lo0fe80::1%lo0UHl0 0 32768 1 lo0 ff01::/16 ::1UGRS 0 0 32768 8 lo0 ff01::%lo0/32 ::1Um 0 1 32768 4 lo0 ff02::/16 ::1UGRS 0 0 32768 8 lo0 ff02::%lo0/32 ::1Um 0 1 32768 4 lo0 dmesg output: OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb 2 23:02:19 CET 2018 r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2121072640 (2022MB) avail mem = 2049826816 (1954MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x7f6df000 (43 entries) bios0: vendor Phoenix Technologies LTD version "V1.10" date 05/21/2009 bios0: FUJITSU SIEMENS AMILO Li 2735 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET MCFG TCPA TMOR SLIC APIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID0(S3) SLPB(S3) LANC(S4) HDEF(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) EHC1(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz, 1995.61 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
Re: Why is so slow the download speed in OpenBSD?
First of all I must to clarify that I'm newbie in networking and there are some thinks that I don't understand in your message, but, I will do anything you ask to resolve the problem, because I think this is a bug in the wifi firmware that I'm using (please read the reply sent to Tom). I'm running the default config, I have not modified anything related to the network. I will paste here the config file output and the command output. This is in my pf.conf: # $OpenBSD: pf.conf,v 1.54 2014/08/23 05:49:42 deraadt Exp $ # # See pf.conf(5) and /etc/examples/pf.conf set skip on lo block return# block stateless traffic pass# establish keep-state # By default, do not permit remote connections to X11 block return in on ! lo0 proto tcp to port 6000:6010 this is the output of that command: block return all pass all flags S/SA block return in on ! lo0 proto tcp from any to any port 6000:6010
Re: Why is so slow the download speed in OpenBSD?
Hi Zolt when your laptop is on line try fw_update -a command to update firmware... you probably were not online when the firmware update command ran (on first boot after install) See what happens when you run that command .. Thanks Tom Smyth On 11 February 2018 at 23:15, Zsolt Kantor wrote: > Below I provide full information from ifconfig, route and a full dmesg. By > the way, I think this is a BUG in the wireless firmware that I'm using > (downloaded from the OpenBSD firmware site). I say this because I found this > line in the dmesg output: wpi0: fatal firmware error > > So below are the outputs. > > ifconfig output: > > lo0: flags=8049 mtu 32768 > index 4 priority 0 llprio 3 > groups: lo > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet 127.0.0.1 netmask 0xff00 > re0: flags=8802 mtu 1500 > lladdr 00:1f:16:03:90:fe > index 1 priority 0 llprio 3 > media: Ethernet autoselect (none) > status: no carrier > wpi0: flags=8843 mtu 1500 > lladdr 00:1f:3c:8d:aa:a2 > index 2 priority 4 llprio 3 > groups: wlan egress > media: IEEE802.11 autoselect (DS1 mode 11g) > status: active > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > enc0: flags=0<> > index 3 priority 0 llprio 3 > groups: enc > status: active > pflog0: flags=141 mtu 33136 > index 5 priority 0 llprio 3 > groups: pflog > > > > route -n show output: > > Routing tables > > Internet: > DestinationGatewayFlags Refs Use Mtu Prio Iface > default192.168.0.1UGS3 450 -12 wpi0 > 224/4 127.0.0.1 URS0 12 32768 8 lo0 > 127/8 127.0.0.1 UGRS 00 32768 8 lo0 > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 > 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 > > Internet6: > DestinationGatewayFlags > Refs Use Mtu Prio Iface > ::/96 ::1UGRS > 00 32768 8 lo0 > ::/104 ::1UGRS > 00 32768 8 lo0 > ::1::1UHhl > 14 34 32768 1 lo0 > ::127.0.0.0/104::1UGRS > 00 32768 8 lo0 > ::224.0.0.0/100::1UGRS > 00 32768 8 lo0 > ::255.0.0.0/104::1UGRS > 00 32768 8 lo0 > :::0.0.0.0/96 ::1UGRS > 00 32768 8 lo0 > 2002::/24 ::1UGRS > 00 32768 8 lo0 > 2002:7f00::/24 ::1UGRS > 00 32768 8 lo0 > 2002:e000::/20 ::1UGRS > 00 32768 8 lo0 > 2002:ff00::/24 ::1UGRS > 00 32768 8 lo0 > fe80::/10 ::1UGRS > 00 32768 8 lo0 > fec0::/10 ::1UGRS > 00 32768 8 lo0 > fe80::1%lo0fe80::1%lo0UHl > 00 32768 1 lo0 > ff01::/16 ::1UGRS > 00 32768 8 lo0 > ff01::%lo0/32 ::1Um > 01 32768 4 lo0 > ff02::/16 ::1UGRS > 00 32768 8 lo0 > ff02::%lo0/32 ::1Um > 01 32768 4 lo0 > > > > dmesg output: > OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb 2 23:02:19 CET 2018 > r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2121072640 (2022MB) > avail mem = 2049826816 (1954MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x7f6df000 (43 entries) > bios0: vendor Phoenix Technologies LTD version "V1.10" date 05/21/2009 > bios0: FUJITSU SIEMENS AMILO Li 2735 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP HPET MCFG TCPA TMOR SLIC APIC BOOT SSDT SSDT SSDT SSDT > acpi0: wakeup devices LID0(S3) SL
Re: Why is so slow the download speed in OpenBSD?
On 02/11/18 21:41, Tom Smyth wrote: Hi Zolt when your laptop is on line try fw_update -a Best to leave off the `-a' or else you will be downloading all available firmware even that which you do not need. command to update firmware... you probably were not online when the firmware update command ran (on first boot after install) See what happens when you run that command .. Thanks Tom Smyth On 11 February 2018 at 23:15, Zsolt Kantor wrote: Below I provide full information from ifconfig, route and a full dmesg. By the way, I think this is a BUG in the wireless firmware that I'm using (downloaded from the OpenBSD firmware site). I say this because I found this line in the dmesg output: wpi0: fatal firmware error So below are the outputs. ifconfig output: lo0: flags=8049 mtu 32768 index 4 priority 0 llprio 3 groups: lo inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 re0: flags=8802 mtu 1500 lladdr 00:1f:16:03:90:fe index 1 priority 0 llprio 3 media: Ethernet autoselect (none) status: no carrier wpi0: flags=8843 mtu 1500 lladdr 00:1f:3c:8d:aa:a2 index 2 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect (DS1 mode 11g) status: active ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 enc0: flags=0<> index 3 priority 0 llprio 3 groups: enc status: active pflog0: flags=141 mtu 33136 index 5 priority 0 llprio 3 groups: pflog route -n show output: Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default192.168.0.1UGS3 450 -12 wpi0 224/4 127.0.0.1 URS0 12 32768 8 lo0 127/8 127.0.0.1 UGRS 00 32768 8 lo0 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 Internet6: DestinationGatewayFlags Refs Use Mtu Prio Iface ::/96 ::1UGRS 0 0 32768 8 lo0 ::/104 ::1UGRS 0 0 32768 8 lo0 ::1::1UHhl 14 34 32768 1 lo0 ::127.0.0.0/104::1UGRS 0 0 32768 8 lo0 ::224.0.0.0/100::1UGRS 0 0 32768 8 lo0 ::255.0.0.0/104::1UGRS 0 0 32768 8 lo0 :::0.0.0.0/96 ::1UGRS 0 0 32768 8 lo0 2002::/24 ::1UGRS 0 0 32768 8 lo0 2002:7f00::/24 ::1UGRS 0 0 32768 8 lo0 2002:e000::/20 ::1UGRS 0 0 32768 8 lo0 2002:ff00::/24 ::1UGRS 0 0 32768 8 lo0 fe80::/10 ::1UGRS 0 0 32768 8 lo0 fec0::/10 ::1UGRS 0 0 32768 8 lo0 fe80::1%lo0fe80::1%lo0UHl0 0 32768 1 lo0 ff01::/16 ::1UGRS 0 0 32768 8 lo0 ff01::%lo0/32 ::1Um 0 1 32768 4 lo0 ff02::/16 ::1UGRS 0 0 32768 8 lo0 ff02::%lo0/32 ::1Um 0 1 32768 4 lo0 dmesg output: OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb 2 23:02:19 CET 2018 r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2121072640 (2022MB) avail mem = 2049826816 (1954MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0x7f6df000 (43 entries) bios0: vendor Phoenix Technologies LTD version "V1.10" date 05/21/2009 bios0: FUJITSU SIEMENS AMILO Li 2735 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET MCFG TCPA TMOR SLIC APIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID0(S3) SLPB(S3) LANC(S4) HDEF(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX
Re: Why is so slow the download speed in OpenBSD?
I tried that, but as Edgar said it downloaded all the firmware's from the site, even those I'm not needing, eg. radeondrm, but I'm using inteldrm. I want to send a bug report, but (with a big b) the question is who gonna debug the firmware, because as I know those firmware's are non-free code, so maybe it is not even the 'job' of the OpenBSD developers to fix the error. On Monday, February 12, 2018 5:41 AM, Tom Smyth wrote: Hi Zolt when your laptop is on line try fw_update -a command to update firmware... you probably were not online when the firmware update command ran (on first boot after install) See what happens when you run that command .. Thanks Tom Smyth On 11 February 2018 at 23:15, Zsolt Kantor wrote: > Below I provide full information from ifconfig, route and a full dmesg. By > the way, I think this is a BUG in the wireless firmware that I'm using > (downloaded from the OpenBSD firmware site). I say this because I found this > line in the dmesg output: wpi0: fatal firmware error > > So below are the outputs. > > ifconfig output: > > lo0: flags=8049 mtu 32768 > index 4 priority 0 llprio 3 > groups: lo > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet 127.0.0.1 netmask 0xff00 > re0: flags=8802 mtu 1500 > lladdr 00:1f:16:03:90:fe > index 1 priority 0 llprio 3 > media: Ethernet autoselect (none) > status: no carrier > wpi0: flags=8843 mtu 1500 > lladdr 00:1f:3c:8d:aa:a2 > index 2 priority 4 llprio 3 > groups: wlan egress > media: IEEE802.11 autoselect (DS1 mode 11g) > status: active > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > enc0: flags=0<> > index 3 priority 0 llprio 3 > groups: enc > status: active > pflog0: flags=141 mtu 33136 > index 5 priority 0 llprio 3 > groups: pflog > > > > route -n show output: > > Routing tables > > Internet: > DestinationGatewayFlags Refs Use Mtu Prio Iface > default192.168.0.1UGS3 450 -12 wpi0 > 224/4 127.0.0.1 URS0 12 32768 8 lo0 > 127/8 127.0.0.1 UGRS 00 32768 8 lo0 > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 > 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 > > Internet6: > DestinationGatewayFlags > Refs Use Mtu Prio Iface > ::/96 ::1UGRS > 00 32768 8 lo0 > ::/104 ::1UGRS > 00 32768 8 lo0 > ::1::1UHhl > 14 34 32768 1 lo0 > ::127.0.0.0/104::1UGRS > 00 32768 8 lo0 > ::224.0.0.0/100::1UGRS > 00 32768 8 lo0 > ::255.0.0.0/104::1UGRS > 00 32768 8 lo0 > :::0.0.0.0/96 ::1UGRS > 00 32768 8 lo0 > 2002::/24 ::1UGRS > 00 32768 8 lo0 > 2002:7f00::/24 ::1UGRS > 00 32768 8 lo0 > 2002:e000::/20 ::1UGRS > 00 32768 8 lo0 > 2002:ff00::/24 ::1UGRS > 00 32768 8 lo0 > fe80::/10 ::1UGRS > 00 32768 8 lo0 > fec0::/10 ::1UGRS > 00 32768 8 lo0 > fe80::1%lo0fe80::1%lo0UHl > 00 32768 1 lo0 > ff01::/16 ::1UGRS > 00 32768 8 lo0 > ff01::%lo0/32 ::1Um > 01 32768 4 lo0 > ff02::/16 ::1UGRS > 00 32768 8 lo0 > ff02::%lo0/32 ::1Um > 01 32768 4 lo0 > > > > dmesg output: > OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb 2 23:02:19 CET 2018 > r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2121072640 (2022MB) > avail mem =
Re: Why is so slow the download speed in OpenBSD?
Try different channels. See the wireless section of ifconfig(8). On Feb 12, 2018 3:02 AM, Zsolt Kantor wrote: > > I tried that, but as Edgar said it downloaded all the firmware's from the > site, even those I'm not needing, eg. radeondrm, but I'm using inteldrm. > > I want to send a bug report, but (with a big b) the question is who gonna > debug the firmware, because as I know those firmware's are non-free code, so > maybe it is not even the 'job' of the OpenBSD developers to fix the error. > > > On Monday, February 12, 2018 5:41 AM, Tom Smyth > wrote: > > > > Hi Zolt > > when your laptop is on line try > > fw_update -a > command to update firmware... you probably were not online when the > firmware update command ran (on first boot after install) > See what happens when you run that command .. > > Thanks > Tom Smyth > > On 11 February 2018 at 23:15, Zsolt Kantor wrote: > > Below I provide full information from ifconfig, route and a full dmesg. By > > the way, I think this is a BUG in the wireless firmware that I'm using > > (downloaded from the OpenBSD firmware site). I say this because I found > > this line in the dmesg output: wpi0: fatal firmware error > > > > So below are the outputs. > > > > ifconfig output: > > > > lo0: flags=8049 mtu 32768 > > index 4 priority 0 llprio 3 > > groups: lo > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > inet 127.0.0.1 netmask 0xff00 > > re0: flags=8802 mtu 1500 > > lladdr 00:1f:16:03:90:fe > > index 1 priority 0 llprio 3 > > media: Ethernet autoselect (none) > > status: no carrier > > wpi0: flags=8843 mtu 1500 > > lladdr 00:1f:3c:8d:aa:a2 > > index 2 priority 4 llprio 3 > > groups: wlan egress > > media: IEEE802.11 autoselect (DS1 mode 11g) > > status: active > > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey > displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > > enc0: flags=0<> > > index 3 priority 0 llprio 3 > > groups: enc > > status: active > > pflog0: flags=141 mtu 33136 > > index 5 priority 0 llprio 3 > > groups: pflog > > > > > > > > route -n show output: > > > > Routing tables > > > > Internet: > > Destination Gateway Flags Refs Use Mtu Prio > > Iface > > default 192.168.0.1 UGS 3 450 - 12 wpi0 > > 224/4 127.0.0.1 URS 0 12 32768 8 lo0 > > 127/8 127.0.0.1 UGRS 0 0 32768 8 lo0 > > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > > 192.168.0/24 192.168.0.101 UCn 1 0 - 8 wpi0 > > 192.168.0.1 70:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > > 192.168.0.255 192.168.0.101 UHb 0 0 - 1 wpi0 > > > > Internet6: > > Destination Gateway Flags > > Refs Use Mtu Prio Iface > > ::/96 ::1 UGRS > > 0 0 32768 8 lo0 > > ::/104 ::1 UGRS > > 0 0 32768 8 lo0 > > ::1 ::1 UHhl > > 14 34 32768 1 lo0 > > ::127.0.0.0/104 ::1 UGRS > > 0 0 32768 8 lo0 > > ::224.0.0.0/100 ::1 UGRS > > 0 0 32768 8 lo0 > > ::255.0.0.0/104 ::1 UGRS > > 0 0 32768 8 lo0 > > :::0.0.0.0/96 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002::/24 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002:7f00::/24 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002:e000::/20 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002:ff00::/24 ::1 UGRS > > 0 0 32768 8 lo0 > > fe80::/10 ::1 UGRS > > 0 0 32768 8 lo0 > > fec0::/10 ::1 UGRS > > 0 0 32768 8 lo0 > > fe80::1%lo0 fe80::1%lo0 UHl > > 0 0 32768 1 lo0 > > ff01::/16 ::1 UGRS > > 0 0 32768 8 lo0 > > ff01::%lo0/32 ::1 Um > > 0 1 32768 4 lo0 > > ff02::/16 ::1 UGRS > > 0
Re: Why is so slow the download speed in OpenBSD?
I've tried different channels and also different modes, I even replaced the 6.2 firmware with the snapshot (the snapshot version is a little bit bigger in size) hoping that it will work better. To be sure with the configuration I used the same channel and mode with which in other OS (Windows) is working well. So now I'm even more close to the idea that it is a bug in the firmware. If somebody can guaranty that it is not from the firmware than it should be a configuration issue, but as I stated before I have not touched anything related to network configuration, I just made a fresh install and the basic config to set up xfce, that's all. Probably I will fill out a bug report. Thanks for the support, If you have some other ideas please let me know. On Monday, February 12, 2018 2:48 PM, "ed...@pettijohn-web.com" wrote: Try different channels. See the wireless section of ifconfig(8). On Feb 12, 2018 3:02 AM, Zsolt Kantor wrote: > > I tried that, but as Edgar said it downloaded all the firmware's from the > site, even those I'm not needing, eg. radeondrm, but I'm using inteldrm. > > I want to send a bug report, but (with a big b) the question is who gonna > debug the firmware, because as I know those firmware's are non-free code, so > maybe it is not even the 'job' of the OpenBSD developers to fix the error. > > > On Monday, February 12, 2018 5:41 AM, Tom Smyth > wrote: > > > > Hi Zolt > > when your laptop is on line try > > fw_update -a > command to update firmware... you probably were not online when the > firmware update command ran (on first boot after install) > See what happens when you run that command .. > > Thanks > Tom Smyth > > On 11 February 2018 at 23:15, Zsolt Kantor wrote: > > Below I provide full information from ifconfig, route and a full dmesg. By > > the way, I think this is a BUG in the wireless firmware that I'm using > > (downloaded from the OpenBSD firmware site). I say this because I found > > this line in the dmesg output: wpi0: fatal firmware error > > > > So below are the outputs. > > > > ifconfig output: > > > > lo0: flags=8049 mtu 32768 > > index 4 priority 0 llprio 3 > > groups: lo > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > inet 127.0.0.1 netmask 0xff00 > > re0: flags=8802 mtu 1500 > > lladdr 00:1f:16:03:90:fe > > index 1 priority 0 llprio 3 > > media: Ethernet autoselect (none) > > status: no carrier > > wpi0: flags=8843 mtu 1500 > > lladdr 00:1f:3c:8d:aa:a2 > > index 2 priority 4 llprio 3 > > groups: wlan egress > > media: IEEE802.11 autoselect (DS1 mode 11g) > > status: active > > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey > displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > > enc0: flags=0<> > > index 3 priority 0 llprio 3 > > groups: enc > > status: active > > pflog0: flags=141 mtu 33136 > > index 5 priority 0 llprio 3 > > groups: pflog > > > > > > > > route -n show output: > > > > Routing tables > > > > Internet: > > DestinationGatewayFlags Refs Use Mtu Prio > > Iface > > default192.168.0.1UGS3 450 -12 wpi0 > > 224/4 127.0.0.1 URS0 12 32768 8 lo0 > > 127/8 127.0.0.1 UGRS 00 32768 8 lo0 > > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > > 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 > > 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > > 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 > > > > Internet6: > > DestinationGatewayFlags > > Refs Use Mtu Prio Iface > > ::/96 ::1UGRS > > 00 32768 8 lo0 > > ::/104 ::1UGRS > > 00 32768 8 lo0 > > ::1::1UHhl > > 14 34 32768 1 lo0 > > ::127.0.0.0/104::1UGRS > > 00 32768 8 lo0 > > ::224.0.0.0/100::1UGRS > > 00 32768 8 lo0 > > ::255.0.0.0/104::1UGRS > > 00 32768 8 lo0 > > :::0.0.0.0/96 ::1UGRS > > 00 32768 8 lo0 > > 2002::/24 ::1UGRS > > 00 32768 8 lo0 > > 2002:7f00::/24 ::1
Re: Why is so slow the download speed in OpenBSD?
There is a bit of information that I am missing. You mentioned that the throughput on your Amilo, with OpenBSD, is 240KB/s whereas "other OS" (SiC) is able to get a throughput of 1.4MB/s. What application are you using to measure the performance? And this is not meant as an insult, but could it be that whatever you are using on OpenBSD shows the speed in KByte/s, whereas "other OS" shows it in Mbit/s? Second, this might seem unrelated, could you list your fstab? I would like to know whether to applied the 'noatime,softdep' options :-) Regards -J. On Mon, 2018-02-12 at 22:24 +, Zsolt Kantor wrote: > I've tried different channels and also different modes, I even > replaced the 6.2 firmware with the snapshot (the snapshot version is > a little bit bigger in size) hoping that it will work better. To be > sure with the configuration I used the same channel and mode with > which in other OS (Windows) is working well. So now I'm even more > close to the idea that it is a bug in the firmware. If somebody can > guaranty that it is not from the firmware than it should be a > configuration issue, but as I stated before I have not touched > anything related to network configuration, I just made a fresh > install and the basic config to set up xfce, that's all. > Probably I will fill out a bug report. > Thanks for the support, If you have some other ideas please let me > know. > > >
Re: Why is so slow the download speed in OpenBSD?
On 2018-02-12, Zsolt Kantor wrote: > I've tried different channels and also different modes, I even > replaced the 6.2 firmware with the snapshot (the snapshot version is a > little bit bigger in size) hoping that it will work better. It doesn't hurt in this case for wpi, but don't do that: - 6.2 firmware is for use with 6.2. - snapshot firmware is for use with a current snapshot. You can't rely on it working with an earlier release version. Regarding your problem, you need to isolate things more before anyone can give meaningful advice. Does this only affect wireless or also wired? If I understand correctly you see this with downloading and writing to disk, does it also show up with just network traffic? (can you run iperf or similar to a computer on the same network? or at least speedtest-cli?)
Re: Why is so slow the download speed in OpenBSD?
I just made a quick test using the same browser (to not to complicate things with wget) firefox (almost the same versions, the ESR release line). Used the mirror: https://ftp2.eu.openbsd.org/pub/OpenBSD/6.2/amd64/ Started to download the file: install62.fs (360MB) In OpenBSD when the download starts: 11 minutes (remaining), download rate: fluctuating between 450-480 KB/sec, sometimes drops to 320-350 KB/sec, and the remaining time increases to 14 minutes. I wrote here the units (minutes, KB, sec) exactly as appears in the firefox download window. In Windows using the same mirror and the same file, on the other hand the starting download rate is between 1300-1400 KB/sec, and so of course the download time is 2-3 minutes. Just for more info, and to be more precise with the tests I used wget too in OpenBSD. Her is the output of wget after the downloading was started for about 10 seconds: $ wget https://ftp2.eu.openbsd.org/pub/OpenBSD/6.2/amd64/install62.fs --2018-02-14 00:39:01-- https://ftp2.eu.openbsd.org/pub/OpenBSD/6.2/amd64/install62.fs Resolving ftp2.eu.openbsd.org (ftp2.eu.openbsd.org)... 137.208.8.135 Connecting to ftp2.eu.openbsd.org (ftp2.eu.openbsd.org)|137.208.8.135|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 377978880 (360M) Saving to: 'install62.fs' install62.fs 1%[ ] 6.63M 648KB/seta 9m 16s ^C $ It is interesting to observe that with wget the download speed is a little bit higher, but far to be as high as in Windows. So if you have any idea, any new testing method, please tell me, I will try. But after all those tests as I mentioned above, I really think is an issue with the OpenBSD wifi (I'm not a specialist so I can not tell if it is a firmware issue, or default configuration issue, but I think it is.) To be honest my humbling opinion is that it is a firmware issue, Because I saw once in the system message buffer a wpi firmware error (I already mentioned this in an earlier message in the same thread, so you can look around, or if you want I could find it for you and show it). And to answer your question more directly as you can see the programs that I used to test the speed always used KB/s (in case of wget), or KB/sec (in case of firefox). So it is absolutely excluded the term of bits. Thanks, Zsolt > There is a bit of information that I am missing. You mentioned that the > throughput on your Amilo, with OpenBSD, is 240KB/s whereas "other OS" > (SiC) is able to get a throughput of 1.4MB/s. > What application are you using to measure the performance? And this is > not meant as an insult, but could it be that whatever you are using on > OpenBSD shows the speed in KByte/s, whereas "other OS" shows it in > Mbit/s? > Second, this might seem unrelated, could you list your fstab? I would > like to know whether to applied the 'noatime,softdep' options :-) > Regards > -J. On Mon, 2018-02-12 at 22:24 +, Zsolt Kantor wrote: > I've tried different channels and also different modes, I even > replaced the 6.2 firmware with the snapshot (the snapshot version is > a little bit bigger in size) hoping that it will work better. To be > sure with the configuration I used the same channel and mode with > which in other OS (Windows) is working well. So now I'm even more > close to the idea that it is a bug in the firmware. If somebody can > guaranty that it is not from the firmware than it should be a > configuration issue, but as I stated before I have not touched > anything related to network configuration, I just made a fresh > install and the basic config to set up xfce, that's all. > Probably I will fill out a bug report. > Thanks for the support, If you have some other ideas please let me > know. > > >
Re: Why is so slow the download speed in OpenBSD?
On Tue, 13 Feb 2018 10:38:36 + (UTC) Hi, Stuart asked > Does this only affect wireless or also > wired? Did you answer this yet?
Re: Why is so slow the download speed in OpenBSD?
On Tue, Feb 13, 2018 at 11:00:39PM +, Zsolt Kantor wrote: > So if you have any idea, any new testing method, please tell me, I will try. The information we'd need to fix anyting is still not there because what you are measuring is the result of an interaction between many layers: application, sockets, TCP, IP, wifi, physical medium (radio). In order to fix anything we'll need to determine which layer is causing the problem, and why. I can make a guess, based on my knowledge of how the wifi layer behaves: The transmit rate used by wpi(4) is selected dynamically by the wifi layer. The higher the selected transmit rate is the faster your TCP stream will be because your TCP ACKs will flow faster. In the current implementation, the wifi layer selects a transmit rate based on the number of frame transmission retries reported by wpi(4) firmware. Frame transmission retries at a given transmit rate will happen if either: 1) You are too far away from the AP. A lower rate has more chance of getting through so lowering the rate is a good idea. or: 2) You are close to the AP but there is lots of unrelated wifi traffic on the same channel using up air time. Attempts to transmit a frame are often blocked by other legitimate frames on the air, so we need more than one attempt and all our attempts get counted as retries, and now we end up using a lower transmit rate. Using a lower rate in this situation means we use up more air time and make the problem even worse, not just for us but for everyone on this channel. The access point density in many residential buildings today means that case 2 is very likely and case 1 is very unlikely, especially on a 2GHz channel. Adapting the transmit rate based on retries doesn't achieve the desired result in this situation, so your download speed sucks. You can test my theory by disabling the automatic rate selection algorithm and tell wpi(4) to send all frames at a transmit rate of your choice. To do so, associate to the AP, and now fix the transmit rate as shown below. Repeat your test each time after changing the transmit rate. ifconfig wpi0 media OFDM6 mode 11g # repeat test ifconfig wpi0 media OFDM9 mode 11g # repeat test ifconfig wpi0 media OFDM12 mode 11g # repeat test ifconfig wpi0 media OFDM18 mode 11g # repeat test ifconfig wpi0 media OFDM24 mode 11g # repeat test ifconfig wpi0 media OFDM36 mode 11g # repeat test ifconfig wpi0 media OFDM48 mode 11g # repeat test ifconfig wpi0 media OFDM54 mode 11g # repeat test If you find that one of these commands makes it work as fast as it does on Windows, we can conclude that the problem is with OpenBSD's rate selection algorithm. This algorithm is very old and dates from a time when wifi networks were much less densly deployed. Windows is probably using a different algorithm to make decisions about which transmit rate to use (for reference, it probably uses a similar algorithm as was implemented in Intel's Linux iwlegacy driver, in file 3945-rs.c of that driver's source code).
Re: Why is so slow the download speed in OpenBSD?
You told me a very interesting thing, and I need to admit that I did not thought about this (although in the past I wrote some ping program using sockets, so I have a basic knowledge about networking in general). I will try that, but right now I need to resolve other things (not related to OpenBSD), I also thought to do some wireshark tests in Win and BSD and check the traffic, the packets, and the times between the packets sent and received. I also want to test the wired connection in OpenBSD. I'm only using wifi, I have no wires to connect to the router, so I need to buy one and test. I also need to study a little bit more how transmissions are working in OpenBSD, the layers, etc. I will be back when I have some concrete result. Thanks for the advices, Zsolt On Wednesday, February 14, 2018 1:09 PM, Stefan Sperling wrote: On Tue, Feb 13, 2018 at 11:00:39PM +, Zsolt Kantor wrote: > So if you have any idea, any new testing method, please tell me, I will try. The information we'd need to fix anyting is still not there because what you are measuring is the result of an interaction between many layers: application, sockets, TCP, IP, wifi, physical medium (radio). In order to fix anything we'll need to determine which layer is causing the problem, and why. I can make a guess, based on my knowledge of how the wifi layer behaves: The transmit rate used by wpi(4) is selected dynamically by the wifi layer. The higher the selected transmit rate is the faster your TCP stream will be because your TCP ACKs will flow faster. In the current implementation, the wifi layer selects a transmit rate based on the number of frame transmission retries reported by wpi(4) firmware. Frame transmission retries at a given transmit rate will happen if either: 1) You are too far away from the AP. A lower rate has more chance of getting through so lowering the rate is a good idea. or: 2) You are close to the AP but there is lots of unrelated wifi traffic on the same channel using up air time. Attempts to transmit a frame are often blocked by other legitimate frames on the air, so we need more than one attempt and all our attempts get counted as retries, and now we end up using a lower transmit rate. Using a lower rate in this situation means we use up more air time and make the problem even worse, not just for us but for everyone on this channel. The access point density in many residential buildings today means that case 2 is very likely and case 1 is very unlikely, especially on a 2GHz channel. Adapting the transmit rate based on retries doesn't achieve the desired result in this situation, so your download speed sucks. You can test my theory by disabling the automatic rate selection algorithm and tell wpi(4) to send all frames at a transmit rate of your choice. To do so, associate to the AP, and now fix the transmit rate as shown below. Repeat your test each time after changing the transmit rate. ifconfig wpi0 media OFDM6 mode 11g # repeat test ifconfig wpi0 media OFDM9 mode 11g # repeat test ifconfig wpi0 media OFDM12 mode 11g # repeat test ifconfig wpi0 media OFDM18 mode 11g # repeat test ifconfig wpi0 media OFDM24 mode 11g # repeat test ifconfig wpi0 media OFDM36 mode 11g # repeat test ifconfig wpi0 media OFDM48 mode 11g # repeat test ifconfig wpi0 media OFDM54 mode 11g # repeat test If you find that one of these commands makes it work as fast as it does on Windows, we can conclude that the problem is with OpenBSD's rate selection algorithm. This algorithm is very old and dates from a time when wifi networks were much less densly deployed. Windows is probably using a different algorithm to make decisions about which transmit rate to use (for reference, it probably uses a similar algorithm as was implemented in Intel's Linux iwlegacy driver, in file 3945-rs.c of that driver's source code).
Re: Why is so slow the download speed in OpenBSD?
Now, I just switched to OpenBSD, and executed the commands as you wrote down. AND IT WORKS! You have more in depth network knowledge than me, so I just will write down what I did, and I have also some questions related to that media option of the ifconfig (which I, to be honest don't really understand). So, I used the same mirror (https://ftp2.eu.openbsd.org/pub/OpenBSD/6.2/amd64/) for testing and used only wget for downloads. With wget the download speed is a bit higher compared to firefox or chromium, I think because wget is more 'light', command line tool, more optimized (probably the code is more clear), firefox and chromium opens slower maybe also bloat in code, so the download rate is also less. Now back to the point. I logged in to Xfce, I opened a terminal with two tabs, one for normal user, to execute the downloads, with the following command: 'wget https://ftp2.eu.openbsd.org/pub/OpenBSD/6.2/amd64/install62.fs', and one for root user to use ifconfig to make those settings. After every ifconfig change, I switched to the normal user tab and started the download process (sometimes, when I saw some unusual fluctuation I interrupted the download process and started again, waited a while to see what happens, than if the download process was not stable I waited a little to be just sure, after that started the process again and so on, to have a more precise report). Here are the test results: OFDM6: max: 1.30MB/s, min: 700KB/s (this config. is not stable, sometimes drops from 1.20MB/s to 700KB and back) OFDM9: average: 1.45MB/s (more stable, do not drops above 1.30MB) OFDM12: quite stable as with OFDM9, sometimes reaches a max. of 1.70MB/s OFDM18: stable, average: 1.50MB (I saw also 1.80MB/s for fractions of seconds) OFDM24: At the first try was not stable, fluctuated between 900KB/s and 1.70Mb/s, at the second try it was stable, avg: 1.55MB/s (for fractions of seconds 1.80MB/s), at the third, fourth . . . tries was stable, avg: 1.60MB OFDM36: quiet stable, avg: 1.55MB/s OFDM48: not so stable, 700KB/s, 800KB/s, rarely reaches 1000KB/s (but immediately drops) OFDM54: not stable at all, between 700KB and 900KB (sometimes reaches 1.1MB/s, rarely drops down to 300KB/s), the avg. rate is 700-750KB. These for the tests. Now, I have a few questions. In the ifconfig manual at the media option states that if it is used with no arguments displays all available media. In my case it looks like this: supported media: media autoselect media autoselect mediaopt monitor media autoselect mode 11a media autoselect mode 11a mediaopt monitor media autoselect mode 11b media autoselect mode 11b mediaopt monitor media autoselect mode 11g media autoselect mode 11g mediaopt monitor But what you proposed to me to try is OFDM6, 9, 12 . . . In the supported media list I don't find those types, why? The second question is: now theoretically the problem is solved, to be honest I have no clue about media types, radio frequencies and such things, but based on my tests it's need to be corrected something in OpenBSD related to this issue? Or it is more like a user side configuration? If somebody would ask me I think the optimal media type should ne automatically selected by the system (driver, firmware . . . I don't know who's in charge for this), and not by the user (after the system is installed). That's all, thanks again. For me the problem is solved. You need to decide if this is a malfunction or not. Thanks again. On Wednesday, February 14, 2018 9:36 PM, Zsolt Kantor wrote: You told me a very interesting thing, and I need to admit that I did not thought about this (although in the past I wrote some ping program using sockets, so I have a basic knowledge about networking in general). I will try that, but right now I need to resolve other things (not related to OpenBSD), I also thought to do some wireshark tests in Win and BSD and check the traffic, the packets, and the times between the packets sent and received. I also want to test the wired connection in OpenBSD. I'm only using wifi, I have no wires to connect to the router, so I need to buy one and test. I also need to study a little bit more how transmissions are working in OpenBSD, the layers, etc. I will be back when I have some concrete result. Thanks for the advices, Zsolt On Wednesday, February 14, 2018 1:09 PM, Stefan Sperling wrote: On Tue, Feb 13, 2018 at 11:00:39PM +, Zsolt Kantor wrote: > So if you have any idea, any new testing method, please tell me, I will try. The information we'd need to fix anyting is still not there because what you are measuring is the result of an interaction between many layers: application, sockets, TCP, IP, wifi, physical medium (radio). In order to fix anything we'll need to determine which layer is causing the problem, and why. I can make a guess, based on my knowledge of how the wifi layer behaves: The transmit rate used by wpi(4) is selected dynamically by the wifi
Re: Why is so slow the download speed in OpenBSD?
Nice! >From Stefan's mail: >"In the current implementation, the wifi layer selects a transmit rate based >on the number of frame transmission retries reported by wpi(4) firmware." That's the "automatically selected optimal media type", comme ci comme ca defined w/r/t the strictness of your definition. >"If you find that one of these commands makes it work as fast as it does on >Windows, we can conclude that the problem is with OpenBSD's rate selection >algorithm. This algorithm is very old and dates from a time when wifi networks >were much less densly deployed." It looks like OpenBSD is like driving a beautiful old car. Malfunction doesn't make sense to say even though existing properties of the OS and existing properties of the world aren't making it easy. On Wed, Feb 14, 2018 at 1:47 PM, Zsolt Kantor wrote: > > > Now, I just switched to OpenBSD, and executed the commands as you wrote > down. AND IT WORKS! > You have more in depth network knowledge than me, so I just will write > down what I did, and I have also some questions related to that media > option of the ifconfig (which I, to be honest don't really understand). > So, I used the same mirror (https://ftp2.eu.openbsd.org/ > pub/OpenBSD/6.2/amd64/) for testing and used only wget for downloads. > With wget the download speed is a bit higher compared to firefox or > chromium, I think because wget is more 'light', command line tool, more > optimized (probably the code is more clear), firefox and chromium opens > slower maybe also bloat in code, so the download rate is also less. > Now back to the point. I logged in to Xfce, I opened a terminal with two > tabs, one for normal user, to execute the downloads, with the following > command: 'wget https://ftp2.eu.openbsd.org/pub/OpenBSD/6.2/amd64/ > install62.fs', and one for root user to use ifconfig to make those > settings. After every ifconfig change, I switched to the normal user tab > and started the download process (sometimes, when I saw some unusual > fluctuation I interrupted the download process and started again, waited a > while to see what happens, than if the download process was not stable I > waited a little to be just sure, after that started the process again and > so on, to have a more precise report). > Here are the test results: > OFDM6: max: 1.30MB/s, min: 700KB/s (this config. is not stable, sometimes > drops from 1.20MB/s to 700KB and back) > OFDM9: average: 1.45MB/s (more stable, do not drops above 1.30MB) > OFDM12: quite stable as with OFDM9, sometimes reaches a max. of 1.70MB/s > OFDM18: stable, average: 1.50MB (I saw also 1.80MB/s for fractions of > seconds) > OFDM24: At the first try was not stable, fluctuated between 900KB/s and > 1.70Mb/s, at the second try it was stable, avg: 1.55MB/s (for fractions of > seconds 1.80MB/s), at the third, fourth . . . tries was stable, avg: 1.60MB > OFDM36: quiet stable, avg: 1.55MB/s > OFDM48: not so stable, 700KB/s, 800KB/s, rarely reaches 1000KB/s (but > immediately drops) > OFDM54: not stable at all, between 700KB and 900KB (sometimes reaches > 1.1MB/s, rarely drops down to 300KB/s), the avg. rate is 700-750KB. > > These for the tests. Now, I have a few questions. In the ifconfig manual > at the media option states that if it is used with no arguments displays > all available media. In my case it looks like this: > > supported media: > media autoselect > media autoselect mediaopt monitor > media autoselect mode 11a > media autoselect mode 11a mediaopt monitor > media autoselect mode 11b > media autoselect mode 11b mediaopt monitor > media autoselect mode 11g > media autoselect mode 11g mediaopt monitor > > But what you proposed to me to try is OFDM6, 9, 12 . . . In the supported > media list I don't find those types, why? > > The second question is: now theoretically the problem is solved, to be > honest I have no clue about media types, radio frequencies and such things, > but based on my tests it's need to be corrected something in OpenBSD > related to this issue? Or it is more like a user side configuration? If > somebody would ask me I think the optimal media type should ne > automatically selected by the system (driver, firmware . . . I don't know > who's in charge for this), and not by the user (after the system is > installed). > That's all, thanks again. For me the problem is solved. You need to decide > if this is a malfunction or not. > > Thanks again. > > > > > On Wednesday, February 14, 2018 9:36 PM, Zsolt Kantor < > zsoltkan...@yahoo.co.uk> wrote: > > > > You told me a very interesting thing, and I need to admit that I did not > thought about this (although in the past I wrote some ping program using > sockets, so I have a basic knowledge about networking in general). I will > try that, but right now I need to resolve other things (not related to > OpenBSD), I also thought to do some wireshark tests in Win and BSD and > check the traffic, the packets, and the times between the packets sent and > received. I also want
Re: Why is so slow the download speed in OpenBSD?
Ok, in this case, what I understood is that the "optimal rate algorithm" needs to be updated, rewritten, corrected . . . etc. I was also a programmer once, and I know that this can't happen from one day to another, so as a workaround I propose the following: mention about these "issue" in the afterboot manual (afterboot - things to check after the first complete boot) . For more about afterboot type man afterboot. On Thursday, February 15, 2018 1:46 AM, Charlie Eddy wrote: Nice! >From Stefan's mail: >"In the current implementation, the wifi layer selects a transmit rate >based>on the number of frame transmission retries reported by wpi(4) firmware." That's the "automatically selected optimal media type", comme ci comme ca defined w/r/t the strictness of your definition. >"If you find that one of these commands makes it work as fast as it does on >Windows, we can conclude that the problem is with OpenBSD's rate selection >algorithm. This algorithm is very old and dates from a time when wifi networks >were much less densly deployed." It looks like OpenBSD is like driving a beautiful old car. Malfunction doesn't make sense to say even though existing properties of the OS and existing properties of the world aren't making it easy. On Wed, Feb 14, 2018 at 1:47 PM, Zsolt Kantor wrote: > >Now, I just switched to OpenBSD, and executed the commands as you wrote down. >AND IT WORKS! >You have more in depth network knowledge than me, so I just will write down >what I did, and I have also some questions related to that media option of the >ifconfig (which I, to be honest don't really understand). >So, I used the same mirror (https://ftp2.eu.openbsd.org/ >pub/OpenBSD/6.2/amd64/) for testing and used only wget for downloads. With >wget the download speed is a bit higher compared to firefox or chromium, I >think because wget is more 'light', command line tool, more optimized >(probably the code is more clear), firefox and chromium opens slower maybe >also bloat in code, so the download rate is also less. >Now back to the point. I logged in to Xfce, I opened a terminal with two tabs, >one for normal user, to execute the downloads, with the following command: >'wget https://ftp2.eu.openbsd.org/ pub/OpenBSD/6.2/amd64/ install62.fs', and >one for root user to use ifconfig to make those settings. After every ifconfig >change, I switched to the normal user tab and started the download process >(sometimes, when I saw some unusual fluctuation I interrupted the download >process and started again, waited a while to see what happens, than if the >download process was not stable I waited a little to be just sure, after that >started the process again and so on, to have a more precise report). >Here are the test results: >OFDM6: max: 1.30MB/s, min: 700KB/s (this config. is not stable, sometimes >drops from 1.20MB/s to 700KB and back) >OFDM9: average: 1.45MB/s (more stable, do not drops above 1.30MB) >OFDM12: quite stable as with OFDM9, sometimes reaches a max. of 1.70MB/s >OFDM18: stable, average: 1.50MB (I saw also 1.80MB/s for fractions of seconds) >OFDM24: At the first try was not stable, fluctuated between 900KB/s and >1.70Mb/s, at the second try it was stable, avg: 1.55MB/s (for fractions of >seconds 1.80MB/s), at the third, fourth . . . tries was stable, avg: 1.60MB >OFDM36: quiet stable, avg: 1.55MB/s >OFDM48: not so stable, 700KB/s, 800KB/s, rarely reaches 1000KB/s (but >immediately drops) >OFDM54: not stable at all, between 700KB and 900KB (sometimes reaches 1.1MB/s, >rarely drops down to 300KB/s), the avg. rate is 700-750KB. > >These for the tests. Now, I have a few questions. In the ifconfig manual at >the media option states that if it is used with no arguments displays all >available media. In my case it looks like this: > >supported media: >media autoselect >media autoselect mediaopt monitor >media autoselect mode 11a >media autoselect mode 11a mediaopt monitor >media autoselect mode 11b >media autoselect mode 11b mediaopt monitor >media autoselect mode 11g >media autoselect mode 11g mediaopt monitor > >But what you proposed to me to try is OFDM6, 9, 12 . . . In the supported >media list I don't find those types, why? > >The second question is: now theoretically the problem is solved, to be honest >I have no clue about media types, radio frequencies and such things, but based >on my tests it's need to be corrected something in OpenBSD related to this >issue? Or it is more like a user side configuration? If somebody would ask me >I think the optimal media type should ne automatically selected by the system >(driver, firmware . . . I don't know who's in charge for this), and not by the >user (after the system is installed). >That's all, thanks again. For me the problem is solved. You need to decide if >this is a malfunction or not. > >Thanks again. > > > > > >On Wednesday, February 14, 2018 9:36 PM, Zsolt Kantor > wrote: > > > >You told me a very interesting thi