Unless you have some of the popular AV/AM software packages running, that will actively prevent such things.
Don't ask how I know, but we have LAN equipped kit at work, where sadly due to the AV/AM security software that we have no visibility into, it intercepts and blocks many LAN protocols and such, that it doesn't know about. We have to get IP addresses white listed for them to work, and even then there are issues. It's easier to use an old PC that has been stripped of all such nonsense, we just make sure it's never used on the office LAN itself these days. That, and if there is a LAN port, you usually need a way to control it's settings (IP address, Mask, default gateway etc) else you need to use RARP to find it's IP address from it's MAC address. As per the popular (and very good) Lantronix product line. But finding an AV/AM package that will not scream blue murder when it sees RARP being used is another stumbling block. Then, there are the potential security issues. How many LAN equipped bits of kit, have had their IP stack fully vetted and tested to behave correctly under all situations, plus the products own firmware needs to be written with security in mind. There's enough chaos already from consumer IoT things, from light bulbs to TV/PVR boxes, we don't want similar nonsense in the shack, nor want Elecraft to become yet another IoT bot target. (Google "mirai botnet" for an example.) RS232 works, & is difficult to remotely hijack for malicious purposes. USB connectivity works too (often emulating legacy com ports etc) and is easy to implement. There is nothing "Wrong" with LAN ports for control and I/O etc, but in this day and age, it has to be done perfectly, or not at all. And doing that is not trivial! Plus, any "PC software" will need to be cross platform too. NOT just Windoze. (A Java app perhaps?) Or, fully disclose and publish the protocol used by the "device" so the rest of us can use it. Plus, will users who don't even understand simple serial port settings even get their heads around LAN address settings and such, plus some people will then want WiFi because they don't like wired LAN systems. Where do you stop? Oh, and EMC issues. QRO RF and LAN systems often don't co-exist well, also LAN cables can, and often do leak QRM, so you'll be needing STP cables, not exactly low cost. Again, I know this from first hand experience, at work and play! Why not use Optical fibre links, and simple RS232 like commands/responses. RF proof, no radiated EMI, no ground loop issues, low cost, and 99% of all the needed code probably already exists. Ready made cables and I/O ports exist (Toslink among others, good enough for the golden ears brigade, so...) Just my take on it. 73. Dave G0WBX. On 17/06/17 15:34, [email protected] wrote: > Subject: Re: [Elecraft] Seeking input on KPA1500 station > configurations > > > My 2 cents. > > Drop the RS232 line totally and have only an IP / Lan connection. This > will solve so many connectivity issues. With a PC client software, it will > just find the amplifier. > > This is what other Amp vendors are now doing and it is litterly plug and > play. > > The next K-radio should also be LAN aware. > > Mike va3mw ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
