I personally don’t know how to do that, but I found this:
MJPEG streaming on Opera 9.30 (Wii) — proxy approach
MJPEG streaming is not reliably supported by the Wii Internet Channel (Opera 9.30). A practical workaround is to run a small transcoding proxy that converts the MJPEG feed into a format the browser can handle, such as a repeatedly served single JPEG with cache-busting, or a simple multipart response if the browser accepts it.
Why MJPEG fails on the Wii browser
- Opera 9.30 lacks consistent support for multipart/x-mixed-replace and modern HTML5 video APIs.
- JavaScript and HTML support are limited compared with modern browsers, so advanced streaming techniques and APIs are not available.
- Bandwidth and CPU constraints on the Wii make high-resolution, high-frame-rate streams impractical.
Recommended workaround
- Proxy/transcoder: Run a server that reads the MJPEG source, extracts frames, and exposes a Wii-friendly endpoint.
- Serve single JPEGs: Save or generate the latest frame as a static JPEG and let the browser fetch it repeatedly with a cache-busting query parameter.
- Minimal HTML: Provide a very simple HTML page that displays the image and uses a basic timer to reload the image at a low frame rate.
- Fallback: If multipart streaming works for your setup, the proxy can forward the original multipart/x-mixed-replace stream; otherwise use the single-JPEG polling method.
Tools and hosting suggestions
- Use lightweight software on a local machine or Raspberry Pi to minimize latency and avoid NAT/firewall complications.
- Options include small dedicated relays or simple scripts that read an MJPEG URL and write the latest JPEG to disk or memory.
- Keep resolution and JPEG quality low (for example, 320×240 and reduced quality) to reduce stalls and improve responsiveness on the Wii.
Practical tuning and reliability tips
- Frame rate: Target 1–5 FPS for smooth, usable results on the Wii.
- Cache-busting: Append a timestamp or random query string to the image URL to force reloads and avoid stale cached images.
- HTTP headers: Disable conditional responses (304) where possible so the browser always fetches the new image.
- Network: Host the proxy on the same LAN as the Wii to reduce latency and avoid bandwidth limits.