VOGONS


Reply 40 of 43, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Your best bet would be to make sure your router is compatible with open source router firmware and then request the feature to be added to those.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 42 of 43, by mateusz.viste

User metadata
Rank Member
Rank
Member
carlostex wrote on 2022-03-05, 13:03:

Any chance EtherDFS can work in the future mapping USB (samba- or ftp-exposed) drives on a router?

If you want samba, use MSCLIENT... EtherDFS is a different protocol and requires its implementation to be on server-side.

Cyberdyne wrote on 2022-03-05, 16:31:

Why no EtherSVR port to Windows? How hard would it be?

Why: because I am not interested in Windows.
How hard it would be: No idea. Feel free to do it and tell.

carlostex wrote on 2022-03-06, 21:57:

(...) i was merely suggesting that because there would be no need for an extra machine since routers already have a USB disk.

You can do it the other way around: use your own Linux router instead of some commercial SOHO blobs, and then you have the power to install whatever you want on it. At home my router is a light Linux running on a PC-Engine APU4 board. Works flawlessly. EtherDFS included.

http://mateusz.viste.fr | gopher://gopher.viste.fr

Reply 43 of 43, by keenerb

User metadata
Rank Oldbie
Rank
Oldbie

Bit of a necropost but I have encountered an oddity with etherdfs:

I have two drives available for mapping on the host, /mnt/msdos and /mnt/backup:

etherdfs eth0 /mlnt/msdos /mnt/backup

On the client, I have C: and D: physical drives, D: being a CDROM

CDROM listing without etherdfs loaded reports:

GEOS20 <DIR>
ETHERDFS.EXE
ETHFLOP.COM
MTCPCFG.CFG

Then I type etherdfs :: c-e

It reports installed etc. etc. E: -> [C:] on <mac address>

Now when I check my CD drive the directory listing is

GEOS20 <DIR>
. <DIR>
.. <DIR>
4GB_DR <DIR>

Three of the original folders have been replaced with folders from the /mnt/backup host folder, which I didn't even specify as a mount point.

If I specify a later drive letter, like F: instead of E:, the D: drive is unaffected, which is what I'll be doing from now on unless this "bug" (if it is one) gets looked at.