tomkcook

Thanks, that's really helpful. Unfortunately the device we're targeting has a 4.14 kernel that doesn't support kernel-side filtering, but the custom parser is really useful. Using this, I've written this...

I don't recall the thinking that went into using IPDB here, though it was admittedly probably mostly me that wrote the code. We're working on a fairly constrained embedded platform...

Having spent today thinking about it, I've decided to drop IPDB and roll my own netlink socket code to listen for interface up/down events and parse out the bare minimum...

...and have checked that `google.client_id` is ending up with the right value.

An answer on this would be really good. Is there some way to wrap text, or do we have to do it manually? The ReportLab documentation on the `reportlab.graphics` package...

A complete example: ``` def foo(): matching_routes = [ r for r in routes if r.get("dst") and ip in ipaddress.ip_network(r.get("dst")) ] + [r for r in routes if r.get("dst") ==...

`tcpdump` shows the DHCP reply landing correctly so not clear why the library doesn't see it, even though it rejects its own packet and then listens again.

FWIW I tracked this down. The version of Linux I'm using doesn't deliver UDP broadcasts to a socket bound to `(0.0.0.0, 68)` if the interface doesn't already have an IP...

AFAICT, you should be able to take the mqtt_esp8266 example and substitute the WiFiClientSecure class in place of the WiFiClient class and it should just work. I haven't had a...

Of course it won't verify the server. But it should connect. And if you've got the fingerprint of your MQTT server's certificate, you can use WiFiClientSecure::verify() to verify it.