Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cake] looking for some testers this week
Date: Thu, 14 Mar 2019 19:56:00 +0100	[thread overview]
Message-ID: <C96BCBBC-32D2-4AF5-8C46-F90E28E057CB@heistp.net> (raw)
In-Reply-To: <CAA93jw561BQg3MkvfnGncSRVfLboJyBn0QfEWLQDt3W7i5ucwg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]


> On Mar 13, 2019, at 12:20 AM, Dave Taht <dave.taht@gmail.com> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> 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?

[-- Attachment #2: Type: text/html, Size: 8178 bytes --]

      reply	other threads:[~2019-03-14 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12  3:19 Dave Taht
2019-03-12 21:24 ` Pete Heist
2019-03-12 22:08   ` Pete Heist
2019-03-12 23:20   ` Dave Taht
2019-03-14 18:56     ` Pete Heist [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C96BCBBC-32D2-4AF5-8C46-F90E28E057CB@heistp.net \
    --to=pete@heistp.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox