LanManFS/98
Herbert zur Nedden (9470) 36 posts |
Hi, 1. Multi-IP 2. IP only 3. Special characters Summary Wish |
Rick Murray (539) 13747 posts |
Oh, interesting.
That would be good, especially if looking to support IPv6 which has multiple addresses in addition to IPv4 (sometimes it’s a wonder this stuff actually works, isn’t it?)
I wouldn’t hold your breath waiting for coherent UTF-8 support.
There is now an IPv6 stack. |
Paul Sprangers (346) 516 posts |
A long standing wish, that even attracted me to the bounty scheme (at the donation side). The target amount has been reached many years ago… |
Paolo Fabio Zaino (28) 1821 posts |
What is the IP of your WINS Server? And which system is acting as the official WINS Server in your network? Your NAS or your Windows 11 PC? I have here OmniClient on RPCEmu (and every RISC OS system) connecting fine to my Pi-NAS, passing over 2 different subnets and also using VLANs (I don’t allow any Windows System to use SMBv1 on my network or even sharing resources over SMB 3, they are both vulnerable and being actively exploited by both remote and local malware, so my Windows systems have only SMB Client enabled and only SMB v3). The way to solve name resolution issues (given NetBIOS is blocked on W11, unless you really lower protection) is to use an internal DNS server and use it to resolve WINS names over Linux/BSD. For the multiple IPs on the same system, you’ll need to use port forwarding, because your software switch, not only needs to have the socket ports opened, but it also needs to know “where” to route the traffic in input on the external IP to the internal. The configure your RISC OS as I show at the end of this article here: If your W11 is a laptop, I would advice against allowing RISC OS to use it as an SMB server, you’ll carry that extremely insecure configuration around even going to a caffe or any other public network. If it’s a desktop, oh well, still very dangerous, but at least it shouldn’t be used in public networks.
That will take a bit of work on multiple pieces of the OS: LanManFS and LanMan98, the Filer and the File System… As mentioned by Rick, I wouldn’t hold your breath waiting for it to happen soon. All in all , I think using your NAS is probably the best solution. Keep in mind that MS is going to increase W11 security even more (especially with the new regulations UK telecommunication and network connecting device, EU CRA and the US forthcoming regulations too, so I don’t see using W11 and/or W10 as a reliable way to keep everything working on the long run) HTH |
Steve Pampling (1551) 8125 posts |
Probably had a default gateway defined on both – not good. Of course, if you set the system to disable wireless when wired is active, that problem goes away. Usually a BIOS setting in laptops.
Ah the joys of netbios settings, with a decent DHCP you can set the default 0×08 to be a more useful (in enterprise setups with a WINS server) 0×02, to reduce the broadcasts spammed uselessly round the network segment
|
David J. Ruck (33) 1585 posts |
None of the RISC OS foreign or remote filing systems cope with either reserved character translations or top bit set characters in a consistent or reversible way. The only thing I can recommend that will allow files to be transferred between any type of filing system is to stick to alphanumerics, underscore, dash and pling, which obviously wont work very well for anyone not exclusively using English. |
Herbert zur Nedden (9470) 36 posts |
Here are some responses (I don’t know how to to replies quoting): UTF-8 support: IPv6: WINS: Subnets: Security: Infrastructure: |
David J. Ruck (33) 1585 posts |
Like with most other things on RISC OS the clients date from the 1990s, and have stubbornly remained there regardless of minor tinkering. |