On Wed, 20 Oct 2021 at 10:22, Chris Green cl@isbd.net wrote:
Doesn't the pi 'know' about the 192.168.8.0/24 anyway? Try a 'route' on the pi and see what it tells you.
I'm not sure how a route on the Pi would help here?
I can add a route on my laptop to send traffic for 192.168.8.0/24 to 192.168.1.200 (the Pi). If I enable forwarding on the Pi that should let me send requests from my laptop to the USB dongle's web server.
But the replies to these requests would need the USB dongle to have a route telling it how to reach 192.168.1.100, ie it would also need a route adding (but this time for 192.168.1.0/24). Which as far as I know the dongle can't do, but if it could I'd need to be able to reach it over the network to set it up and thus be in a chicken/egg scenario.
I did however manage to set up a web proxy (apt get privoxy, and edit /etc/privoxy/config to set listen-address to :8118 as the default only listens on localhost). Changing my laptop to use the proxy gave me access to the web pages (albeit sending all my web traffic through the Pi until I turned the proxy off). So a messy solution but one which worked.
(I also tried browsh which uses a headless Firefox to render the pages, captures the output, and presents it in text form over SSH. Very clever, but painfully slow to the point that I had to give up with it.)
Mark