OS: LEDE on Raspberry Pi3
Tested version: node-iotronic-lightning-rod - 2.1.0-3
This is probably not a bug in Lightning Rod itself, but a deployment limitation it might be worth knowing about.
When Lightning Rod tries to connect on a network where a firewall with transparent proxy is enabled (ipfire in this case), connection fails with what looks like a crash on the client side (TCP RST).
HTTP/1.1 200 OK
Date: Wed, 16 May 2018 16:15:39 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 11302
X-Cache: MISS from ipfire.fweb
X-Cache-Lookup: HIT from ipfire.fweb:8080
Connection: keep-alive
Unfortunately that's not under my control. The only thing I know is the culprit was the "Transparent on green" flag on ipfire. It might be a bug on the proxy software itself.
OS: LEDE on Raspberry Pi3 Tested version: node-iotronic-lightning-rod - 2.1.0-3
This is probably not a bug in Lightning Rod itself, but a deployment limitation it might be worth knowing about. When Lightning Rod tries to connect on a network where a firewall with transparent proxy is enabled (
ipfirein this case), connection fails with what looks like a crash on the client side (TCP RST).See the following traces captured with tcpdump:
HTTP/1.1 200 OK Date: Wed, 16 May 2018 16:15:39 GMT Content-Type: text/html; charset=UTF-8 Content-Length: 11302 X-Cache: MISS from ipfire.fweb X-Cache-Lookup: HIT from ipfire.fweb:8080 Connection: keep-alive
<!doctype html>
Thanks for your feedback.
Could you please share the settings of the transparent proxy, in order for us to be able to reproduce the issue?
Unfortunately that's not under my control. The only thing I know is the culprit was the "Transparent on green" flag on ipfire. It might be a bug on the proxy software itself.