> On Mar 13, 2019, at 12:20 AM, Dave Taht wrote: > > only 225/8-231/8 are opened up from the relevant reserved for > multicast space by this patch series. They have always been unassigned > addresses. I did not change the userspace IN_MULTICAST macro, but > nearly nothing in userspace checks that. So, for ar71xx generic om2p, I’m able to set up an AP/router with IP 225.1.2.1: root@uniextap:~# ip addr show br-lan 8: br-lan: mtu 1500 qdisc noqueue state UP qlen 1000 link/ether ac:86:74:10:26:30 brd ff:ff:ff:ff:ff:ff inet 225.1.2.1/24 brd 225.1.2.255 scope global br-lan valid_lft forever preferred_lft forever and pick up a DHCP address in that subnet from an STA: root@uniextsta:~# ip addr show wlan0 5: wlan0: mtu 1500 qdisc noqueue state UP qlen 1000 link/ether ac:86:74:03:0d:f2 brd ff:ff:ff:ff:ff:ff inet 225.1.2.120/24 brd 225.1.2.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::ae86:74ff:fe03:df2/64 scope link valid_lft forever preferred_lft forever and NAT traffic on that subnet to the Internet: root@uniextsta:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=56 time=11.562 ms 64 bytes from 8.8.8.8: seq=1 ttl=56 time=12.722 ms root@uniextap:~# tcpdump -i eth1 icmp tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes 18:50:32.290616 IP uniextap.lan > google-public-dns-a.google.com: ICMP echo request, id 1252, seq 0, length 64 18:50:32.300259 IP google-public-dns-a.google.com > 10.72.0.37: ICMP echo reply, id 1252, seq 0, length 64 18:50:33.291222 IP uniextap.lan > google-public-dns-a.google.com: ICMP echo request, id 1252, seq 1, length 64 18:50:33.302339 IP google-public-dns-a.google.com > 10.72.0.37: ICMP echo reply, id 1252, seq 1, length 64 Tires kicked. Anything else?