I'm just wondering what is the equivalent of apt-get upgrade apt upgrade yum update with OpenWRT or LEDE?

EDIT: Fixed by switching internet service provider ¯\\(°_o)/¯ I have this annoying issue where some of the machines on my network will hang when looking up connecting to certain IPv6 addresses, in particular the ones from Google (but I've also seen issues with others when on the IPv6-enabled network). sadbox $ ping -6c1 -W10 fonts.googleapis.com PING fonts.googleapis.com(arn09s11-in-x0a.1e100.net (2a00:1450:400f:807::200a)) 56 data bytes --- fonts.googleapis.com ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms sadbox $ ssh happybox Last login: Wed Apr 25 10:28:48 2018 from 192.168.1.140 happybox $ ping -6c1 -W10 fonts.googleapis.com PING fonts.googleapis.com(arn09s11-in-x0a.1e100.net (2a00:1450:400f:807::200a)) 56 data bytes 64 bytes from arn09s11-in-x0a.1e100.net (2a00:1450:400f:807::200a): icmp_seq=1 ttl=55 time=25.6 ms --- fonts.googleapis.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 25.675/25.675/25.675/0.000 ms Both give the exact same answers for host fonts.googleapis.com and nslookup fonts.googleapis.com, and for the relevant parts of dig output. Some times the hosts will be connected to just fine on sadbox though, and some times I get a response if I wait long enough. It's not just ping that's affected, I noticed it because Firefox was waiting forever for fonts.googleapis.com on some site. The http://test-ipv6.com/ site gives full scores on sadbox, and I can ping and connect to other IPv6 addresses (e.g. sixxs.net) just fine. All my computers are running **Xubuntu 17.10**, and the router is running **LEDE Reboot (17.01.4, r3560-79f57e422d)**. What could the issue be? How do I debug something like this? ----- EDIT: Contents of sadbox:/etc/nsswitch.conf, comment-lines removed: passwd: compat group: compat shadow: compat hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis and comparing to happybox: sadbox $ diff /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname EDIT2: Pinging hangs on the IP too, e.g. ping -6 2a00:1450:400f:807::200a, so this is not DNS, but an IPv6 transport issue (thanks Patrick Mevzek!). I'll get traceroutes once I'm back on the network. ----- # Traceroutes: From the router itself it works fine: sadbox $ ssh ruter traceroute6 fonts.googleapis.com traceroute to fonts.googleapis.com (2a00:1450:400f:807::200a), 30 hops max, 16 byte packets 1 2a02:fe0:c900:1::1 (2a02:fe0:c900:1::1) 4.753 ms 5.894 ms 5.709 ms 2 2a02:fe0::a:47:a:13:4 (2a02:fe0::a:47:a:13:4) 5.944 ms 8.850 ms 14.108 ms 3 ae11-0.poh-pe1.stv.no.ip.tdc.net (2a02:228:41:100::127:0:9) 26.056 ms 15.009 ms 14.018 ms 4 stkm3nqp7.se.ip.tdc.net (2001:6c8:40::20) 22.371 ms 22.220 ms 21.974 ms 5 peer-as15169.stkm3nqp7.se.ip.tdc.net (2001:6c8:81:2000::9) 24.504 ms 25.047 ms 28.025 ms 6 2001:4860:0:1344::1 (2001:4860:0:1344::1) 26.118 ms 23.686 ms 24.075 ms 7 2001:4860:0:1::15cf (2001:4860:0:1::15cf) 22.793 ms 24.702 ms 23.859 ms 8 arn09s11-in-x0a.1e100.net (2a00:1450:400f:807::200a) 25.886 ms 35.837 ms 36.413 ms and the other working computer gives about the same: sadbox $ ssh happybox traceroute6 fonts.googleapis.com traceroute to ���2>V (2a00:1450:400f:807::200a) from 2a02:fe0:c910:5120:8011:3799:6dc0:2b58, 30 hops max, 24 byte packets 1 2a02:fe0:c910:5120::1 (2a02:fe0:c910:5120::1) 1,123 ms 1,247 ms 3,537 ms 2 2a02:fe0:c900:1::1 (2a02:fe0:c900:1::1) 6,958 ms 9,566 ms 6,955 ms 3 2a02:fe0:0:a:47:a:13:4 (2a02:fe0:0:a:47:a:13:4) 9,985 ms 6,303 ms 8,719 ms 4 ae11-0.poh-pe1.stv.no.ip.tdc.net (2a02:228:41:100:0:127:0:9) 6,811 ms 6,304 ms 6,741 ms 5 stkm3nqp7.se.ip.tdc.net (2001:6c8:40::20) 25,882 ms 26,625 ms 27,079 ms 6 peer-as15169.stkm3nqp7.se.ip.tdc.net (2001:6c8:81:2000::9) 27,169 ms 28,319 ms 28,931 ms 7 2001:4860:0:1343::1 (2001:4860:0:1343::1) 46,643 ms 28,799 ms 25,976 ms 8 2001:4860:0:1::b23 (2001:4860:0:1::b23) 29,373 ms 37,344 ms 28,207 ms 9 arn09s11-in-x0a.1e100.net (2a00:1450:400f:807::200a) 27,72 ms 26,274 ms 27,764 ms But from sadbox not so good: sadbox $ traceroute6 fonts.googleapis.com traceroute to ���V (2a00:1450:400f:807::200a) from 2a02:fe0:c910:5120:95b:58:ab20:d31e, 30 hops max, 24 byte packets 1 2a02:fe0:c910:5120::1 (2a02:fe0:c910:5120::1) 4,095 ms 4,632 ms 1,558 ms 2 2a02:fe0:c900:1::1 (2a02:fe0:c900:1::1) 11,822 ms 15,528 ms 10,568 ms 3 2a02:fe0:0:a:47:a:13:2 (2a02:fe0:0:a:47:a:13:2) 8,823 ms 6,119 ms 10,068 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * – it just keeps giving me stars (also, what's with that ���V?). A sudo traceroute -6 -T from sadbox gives the same. The IPv4 traceroute -4 works fine from all machines, including sadbox. Here's mtr from a working machine: sadbox $ ssh happybox mtr --report fonts.googleapis.com Start: Tue May 1 20:41:57 2018 HOST: happybox Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a02:fe0:c910:5120::1 0.0% 10 0.7 1.0 0.7 2.3 0.5 2.|-- 2a02:fe0:c900:1::1 0.0% 10 7.4 9.0 6.2 14.2 2.6 3.|-- 2a02:fe0:0:a:47:a:13:4 0.0% 10 7.4 8.0 5.6 11.9 1.9 4.|-- ae11-0.poh-pe1.stv.no.ip. 0.0% 10 7.8 8.2 6.2 10.9 1.3 5.|-- stkm3nqp7.se.ip.tdc.net 0.0% 10 29.3 26.8 24.8 29.4 1.6 6.|-- peer-as15169.stkm3nqp7.se 0.0% 10 25.9 40.6 24.6 135.7 34.8 7.|-- 2001:4860:0:1344::1 0.0% 10 63.9 35.4 26.1 63.9 13.8 8.|-- 2001:4860:0:1::15cf 0.0% 10 26.1 28.1 24.7 36.4 3.2 9.|-- arn09s11-in-x0a.1e100.net 0.0% 10 26.7 26.8 24.8 31.4 1.9 while poor sadbox still gets no profit: sadbox $ mtr --report fonts.googleapis.com Start: Tue May 1 20:35:59 2018 HOST: sadbox Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a02:fe0:c910:5120::1 0.0% 10 1.9 27.3 0.6 134.6 55.7 2.|-- 2a02:fe0:c900:1::1 0.0% 10 96.6 33.6 6.0 96.6 32.1 3.|-- 2a02:fe0:0:a:47:a:13:2 0.0% 10 7.8 8.0 6.4 14.0 2.1 4.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

Following on the footsteps of [this question](https://unix.stackexchange.com/q/400207/3285) , which I was able to figure out with the [device page](https://lede-project.org/toh/hwdata/netgear/netgear_r7800) for my device. I want to know if it is possible to find out he build information *without* using the web interface? Such as with an administration/cli tool.

Do you know what initramfs-kernel mean? I know

-factory/squashfs-sysupgrade

. How can I do it or what is it? which is better? I just don't understand what the initramfs-kernel mean. I have

1900ACS v2

and

-Link DL-860l B1

, but I only use

-factory

and

-sysupgrade

. What does the

-kernel

mean? When would I use those? I would even fear to install that. So, continuing, like

-17.01.2-ramips-mt7621-dir-860l-b1-initramfs-kernel.bin

, what does this mean? can i use it and if so, what is the difference between

-17.01.2-ramips-mt7621-dir-860l-b1-squashfs-factory.bin

(which I know what it does and how) or

-17.01.2-ramips-mt7621-dir-860l-b1-squashfs-sysupgrade.bin

(which I know what it does and how).

On our home LAN, after rebooting the router, I cannot ssh from laptop A to laptop B *except* via the router. However, after doing a ping from laptop B to laptop A, I can connect normally from A to B. I can reproduce this issue by rebooting the router. Both laptops are connected to the router via WiFi and there are no other APs or routers connected. There are other devices on the LAN and I am not aware of any other ARP issues. Demonstrating the problem after the router was rebooted: scott@laptopa:~$ ip addr show dev wlp58s0 |grep 'inet ' inet 192.168.8.194/24 brd 192.168.8.255 scope global dynamic noprefixroute wlp58s0 scott@laptopa:~$ ssh 192.168.8.131 echo okay ssh: connect to host 192.168.8.131 port 443: No route to host scott@laptopa:~$ ssh 192.168.8.131 echo okay ssh: connect to host 192.168.8.131 port 443: No route to host scott@laptopa:~$ ssh 192.168.8.131 echo okay ssh: connect to host 192.168.8.131 port 443: No route to host scott@laptopa:~$ arp |grep 9c:b6:d0:44:18:09 scott@laptopa:~$ The awkward work-around: scott@laptopa:~$ ssh -o 'ProxyCommand ssh -q -W %h:%p root@192.168.8.1' 192.168.8.131 'ping -c 10 192.168.8.194' PING 192.168.8.194 (192.168.8.194) 56(84) bytes of data. 64 bytes from 192.168.8.194: icmp_seq=1 ttl=64 time=66.3 ms 64 bytes from 192.168.8.194: icmp_seq=2 ttl=64 time=22.9 ms 64 bytes from 192.168.8.194: icmp_seq=3 ttl=64 time=106 ms 64 bytes from 192.168.8.194: icmp_seq=4 ttl=64 time=230 ms 64 bytes from 192.168.8.194: icmp_seq=5 ttl=64 time=252 ms 64 bytes from 192.168.8.194: icmp_seq=6 ttl=64 time=275 ms 64 bytes from 192.168.8.194: icmp_seq=7 ttl=64 time=298 ms 64 bytes from 192.168.8.194: icmp_seq=8 ttl=64 time=321 ms 64 bytes from 192.168.8.194: icmp_seq=9 ttl=64 time=38.3 ms 64 bytes from 192.168.8.194: icmp_seq=10 ttl=64 time=60.3 ms --- 192.168.8.194 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9012ms rtt min/avg/max/mdev = 22.950/167.478/321.937/112.761 ms Demonstrating that it now works properly: scott@laptopa:~$ ssh 192.168.8.131 echo okay okay scott@laptopa:~$ arp |grep 9c:b6:d0:44:18:09 laptopb.lan ether 9c:b6:d0:44:18:09 C wlp58s0 Laptops A and B are both running Ubuntu 18.04, and the router is Lede (OpenWRT) 17.01.4.

I have an OpenWRT/LEDE router with Dnsmasq. I currently have a local domain (something.lan) that is appended to DHCP names, so I can access devices on my network just by connecting to, let's say, computer.something.lan. Neat. Recently, I have finally gotten native IPv6 connection. This means I can now reach all my IPv6 capable devices from the internet. I have a domain name (something.tld) and I want to use it for AAA records to DHCP names. Something like setting lan.something.tld NS record to routers IPv6 address and then letting Dnsmasq act as a nameserver (somehow)? Then I would be able to use computer.lan.something.tld in both my local network and the internet. Is something like this possible? Of course I can just set the AAAA records manually, but I would like it to be automatic.

System: Onion Omega2s LEDE 17.01 I have connected a Huawei ME90E modem to the USB port of the Omega2s. I have successfully connected the ME906E modem to the Raspberry Pi running Debian, but have problems with the LEDE on the Omega2s. I have tried many times, but still not successful in getting the interface up. I must have missed something. Any help is appreciated. Running ***dmesg*** confirms the modem is recognised: > [ 12.556027] usbserial: USB Serial support registered for GSM modem (1-port) > > [ 12.563783] option 1-1:2.2: GSM modem (1-port) converter detected > > [ 12.570351] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 > > [ 12.577378] option 1-1:2.3: GSM modem (1-port) converter detected > > [ 12.583884] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 > > [ 12.590910] option 1-1:2.4: GSM modem (1-port) converter detected > > [ 12.597470] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2 The ports /dev/ttyUSB0, /dev/ttyUSB1 & /dev/ttyUSB2 are created. I run minicom -D /dev/ttyUSB2 115200 to communicate with the modem and I can connect successfully to the system operator's network by running AT^NDISDUP=1,1,"apn" The file /sys/kernel/debug/usb/devices contains T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 3 P: Vendor=12d1 ProdID=1573 Rev= 2.28 S: Manufacturer=HUAWEI Technology S: Product=HUAWEI Mobile S: SerialNumber=0123456712ABCA17 C: #Ifs= 6 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=02 Driver= E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=03 Driver= E: Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver= E: Ad=84(I) Atr=03(Int.) MxPS= 10 Ivl=32ms E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 3 Alt= 0 #EPs= 3 Cls=0b(scard) Sub=00 Prot=00 Driver= E: Ad=85(I) Atr=03(Int.) MxPS= 4 Ivl=32ms E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=07 Driver= E: Ad=88(I) Atr=03(Int.) MxPS= 8 Ivl=32ms E: Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 5 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=05 Driver= E: Ad=89(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms C:* #Ifs= 5 Cfg#= 2 Atr=a0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=06 Prot=00 Driver=(none) E: Ad=82(I) Atr=03(Int.) MxPS= 16 Ivl=32ms I:* If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=00 Driver=(none) I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=03 Driver=option E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=02 Driver=option E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=05 Driver=option E: Ad=85(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms C: #Ifs= 3 Cfg#= 3 Atr=a0 MxPwr=500mA A: FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=0e Prot=00 I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=0e Prot=00 Driver= E: Ad=82(I) Atr=03(Int.) MxPS= 64 Ivl=32ms I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver= I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver= E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=05 Driver= E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms The file /etc/config/network was modified to add config interface 'usb0' option ifname 'usb0' option proto 'dhcp' I tried both ways - rebooting the system and running /etc/init.d/network reload When the system is up or the network is reloaded, I run ***ip addr*** and the usb0 still does not show up 1: lo: mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000 link/ether 40:a3:6b:c0:3a:01 brd ff:ff:ff:ff:ff:ff inet 192.168.0.149/24 brd 192.168.0.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::42a3:6bff:fec0:3a01/64 scope link valid_lft forever preferred_lft forever 3: ra0: mtu 1500 qdisc fq_codel master br-wlan state UNKNOWN qlen 1000 link/ether 40:a3:6b:c0:39:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::42a3:6bff:fec0:39ff/64 scope link valid_lft forever preferred_lft forever 4: br-wlan: mtu 1500 qdisc noqueue state UP qlen 1000 link/ether 40:a3:6b:c0:39:ff brd ff:ff:ff:ff:ff:ff inet 192.168.3.1/24 brd 192.168.3.255 scope global br-wlan valid_lft forever preferred_lft forever inet6 fd1d:48c4:7633::1/60 scope global valid_lft forever preferred_lft forever inet6 fe80::42a3:6bff:fec0:39ff/64 scope link valid_lft forever preferred_lft forever 5: apcli0: mtu 1500 qdisc fq_codel state UNKNOWN qlen 1000 link/ether 40:a3:6b:c0:39:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::42a3:6bff:fec0:3900/64 scope link valid_lft forever preferred_lft forever

uname -a shows, Linux LEDE 4.4.71 #0 SMP Wed Jun 7 19:24:41 2017 armv7l GNU/Linux But I don't see an [armv7 even available on the build targets for 17.01.4](https://downloads.lede-project.org/releases/17.01.4/targets/) . It's the same major and minor build number. Is armv7 the ar71xx build? I'm running a **"Netgear Nighthawk X4S R7800"**. LuCI shows > LEDE Reboot 17.01.2 r3435-65eec8bd5f / LuCI lede-17.01 branch (git-17.152.82987-7f6fc16)

I enabled HTTPS on openwrt by following the [howto](https://wiki.openwrt.org/doc/howto/secure.access) some while ago. Now I get a certificate warning in Firefox because it has expired. How do I delete the old cert?

I have two zones: lan (type: bridge) and wan. I set the firewall to forward from lan to wan. lan zone: INPUT:ACCEPT, OUTPUT:ACCEPT wan zone: INPUT:REJECT, OUTPUT:ACCEPT Would INPUT for wan apply to packets from just the Internet? Or does it include forwarded packets from thelan zone?

[hostapd.conf](https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf) : # hostapd will generate BSSID mask based on the BSSIDs that are # configured. hostapd will verify that dev_addr & MASK == dev_addr. If this is # not the case, the MAC address of the radio must be changed before starting # hostapd (ifconfig wlan0 hw ether ). If a BSSID is configured for # every secondary BSS, this limitation is not applied at hostapd and other # masks may be used if the driver supports them (e.g., swap the locally # administered bit) # # BSSIDs are assigned in order to each BSS, unless an explicit BSSID is # specified using the 'bssid' parameter. # If an explicit BSSID is specified, it must be chosen such that it: # - results in a valid MASK that covers it and the dev_addr # - is not the same as the MAC address of the radio # - is not the same as any other explicitly specified BSSID The last point is violated by hostap generated by LEDE 17.01.2 :(. The multiple interfaces were created using the LUCI web interface. I don't believe this changed since OpenWrt 15.05 either. interface=wlan0 ctrl_interface=/var/run/hostapd disassoc_low_ack=1 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 wpa_passphrase=hunter2 auth_algs=1 wpa=2 wpa_pairwise=CCMP ssid=VOYAGER2091-90-jenkins wpa_key_mgmt=WPA-PSK okc=0 disable_pmksa_caching=1 bssid=74:44:01:86:42:d4 bss=wlan0-1 ctrl_interface=/var/run/hostapd disassoc_low_ack=1 preamble=1 wmm_enabled=1 ignore_broadcast_ssid=0 uapsd_advertisement_enabled=1 wpa_passphrase=hunter2 auth_algs=1 wpa=2 wpa_pairwise=CCMP ssid=VOYAGER2091-alan wpa_key_mgmt=WPA-PSK okc=0 disable_pmksa_caching=1 bssid=76:44:01:86:42:d4 Why does hostapd say it requires distinct BSSIDs? What are the possible results of violating this? In previous versions, I've had problems even creating multiple wifi networks like this. After switching to this LEDE release, it seems able to create the networks OK. However, moving away from the access point to room B, often one network shows up but not the other. (Client is Fedora 26 with an Intel wireless card). But this is within usable range, and if I had already connected to one of the networks, I think it is always able to remain connected when moving to room B. So I'm slightly suspicious about this business with BSSIDs.

I am a home user, running a Linux-based WiFi-router in Germany (DLink 860L with LEDE-OpenWRT-Spinoff), trying to configure it to a proper set of allowed WiFi frequencies. For "DE", the Linux wireless regulation database currently includes the WiFi channels 149-165 in the 5GHz band (frequency 5.725 - 5.875 GHz). In Germany this range may only be used by organizations and it does require official frequency registration at the "BNetzA" (the german FCC). Unfortunately the DLink 860L running LEDE is technically capable of using these frequencies and when configured as "DE", it seems to automatically adds them to the list of allowed channels it will use, when channel selection is set to "auto". My current workaround to avoid trouble is, to use reg set "BE" (meant for Belgium), as this currently matches the correct set of channels for German non-commercial users. I am missing kind of like a "DE-homeuser" regulation data subset that is like "DE", but without channels 149-165. Is this a data flaw in the linux wifi reg-database or am I missing another config option in Linux wireless for configuring allowed WiFi channels? "iw reg get": country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR, AUTO-BW (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW (5470 - 5725 @ 160), (N/A, 27), (0 ms), DFS (5725 - 5875 @ 80), (N/A, 14), (N/A) <------ allowed for usage in Germany. But requires official BNetzA registration, to not get into trouble (57000 - 66000 @ 2160), (N/A, 40), (N/A) country BE: DFS-ETSI <--- although this is for Belgium, it's currently a more correct WiFi frequency option for German home users (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS (57000 - 66000 @ 2160), (N/A, 40), (N/A)

I have two TP-Link Routers running LEDE with MP-TCP kernel version 4.4.70. One of the routers runs as an AP and the other runs as a station. I use the two wireless interfaces 60 GHz and 2.4 GHz to establish either a single TCP flow or two concurrent flows using MP-TCP. I generate traffic using iPerf v2.0.9. When I use the 60 GHz alone (802.11ad), I get 1.85 GHz of throughput. Whereas when I use the 2.4 GHz (802.11n) alone I get 20 Mbps. The strange thing is when I use MP-TCP (i.e. two flows at the same time), I get around 300 Mbps. So why am I getting this strange result? Should not MP-TCP achieves throughout of 1850 Mbps + 20 Mbps. I tried to tune TCP parameters like maximum read/write buffer but with no success. Here is the network configuration: **60 GHz Interface:** IP Address: 11.0.0.0/24 **2.5 GHz Interface:** IP Address: 10.0.0.0/24 **MP-TCP Configuration:** Congestion Control: Cubic MP-TCP Enabled: True MP-TCP Checksum: False MP-TCP Path Manager = Full Mesh MP-TCP scheduler = default MP-TCP syn retries = 3 MP-TCP version = 0