View Single Post
Old 11-01-2024, 08:57 AM   #9
elinkser
Addict
elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.elinkser has survived committing the World's Second Greatest Blunder.
 
Posts: 242
Karma: 146236
Join Date: Oct 2022
Device: Kobo Clara HD
rThe USB networking may be already built into the Linux kernel, as opposed to loadable as a module.
(That might explain the conflicts.)

If it is supported, I think you would get a similar log notice as here, except it would happen at boot in your case, as opposed to when the module is loaded:

# dmesg | grep usb0
usb0: MAC CA:79:8D:D4:F8:14

i.e. the MAC address was assigned to a usb0 interface before any ifconfig command was issued.

Then you can do a ping after the ifconfig.


***

I neglected to mention that vnc is inherently insecure.
http://www.mit.edu/~avp/lqcd/ssh-vnc.html

So even if you try to never connect your Kobo to insecure networks, hosts, USB devices, etc., your host vnc server you are connecting to is still a security vulnerability. I would not use this host for anything critical. I would set a firewall and have the vnc server be read-only.


***

Last edited by elinkser; 11-08-2024 at 02:43 PM. Reason: sp,ping after ifconfig,wording
elinkser is offline   Reply With Quote