--
You received this message because you are subscribed to the Google Groups "kplex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kplex+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kplex/c9ef256e-0c7d-42c6-8693-2e92e2ca6bcbn%40googlegroups.com.
How can I get it to report its exit reason in syslog?The documentation suggests that a space is needed between the -d switch and the debug level but your example suggests -d5 is correct. I guess I should have looked at the code.
--
You received this message because you are subscribed to a topic in the Google Groups "kplex" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kplex/w9ZnesiPA90/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kplex+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kplex/e174b09c-5bd6-464e-b6a4-f04824da81d3n%40googlegroups.com.
All,
Is it a good idea to begin with to use DHCP on a device which is acting as a server?
I'd answer that question with no. That noted as a newbie to all things relating to RPi's and Raspios, I recently installed kplex on an RPi3B with a dAISy HAT using DHCP to serve AIS messages to OpenCPN running on a Windows desktop and, much to my surprise I got it working relatively quickly following the documentation supplied by the respective vendors or, in the case of kplex, developers to the letter.
To get kplex to start automatically I used:
sudo update-rc.d kplex defaults
To stop kplex without rebooting run:
sudo service kplex stop
To start kplex without rebooting run:
sudo service kplex start
See http://www.stripydog.com/kplex/kplex.html.
Regards, Jk.
--
You received this message because you are subscribed to the Google Groups "kplex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kplex+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kplex/CAKqYLu2OXggqH24%3DE3BJzmbw0Omu7BT4T0z8ggDqZ-ZORaowUA%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "kplex" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kplex/w9ZnesiPA90/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kplex+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kplex/16c6dc97-125e-42f1-953d-9def7bed1a8dn%40googlegroups.com.
Brett, et all,
Although I have quite an extensive background in IT, my experience is rather dated as well as limited when it comes to UNIX derivatives, so as I already noted, I am a newbie to all things relating to RPi's and Raspios. That noted I'd argue the letter "D" in the acronym DHCP most likely didn't end up there by chance. In fact, as many on this list are probably aware DHCP is an acronym for Dynamic Host Configuration Protocol, or in other words when designing the protocol the designers probably had hosts in mind that tend to roam in a (wired) network, i.e. they don't always connect to the same network wall socket or wireless access point.
So in that sense such hosts are, from a network perspective, dynamic in that they are moved around a network by their end users. They may connect to a network at someone's desk in the morning and in a conference room of another site of the same company in the afternoon, in doing so chances are that, from an IP-protocol perspective, such an end user device is going to need to use IP addresses in different subnets of the same company's network throughout the day, week, etc.
To remove the burden of manually assigning a new IP address and manually configuring it in every host every time it moves within a network a couple of clever dudes at some point in time conceived the DHCP protocol (https://tools.ietf.org/html/rfc2131#page-6).
As for your question and not knowing the specifics of what you're trying to achieve, but in general I'd say it's probably best to always first think about what role (client or server) one's end user device, in this case an RPi, is going to have before one starts to download, install and configure software. I.e. if the aim is to use an RPi as a cheap alternative to a PC like end user device it's OK to use DHCP. However, if one intends to use an RPi as a server that is going to serve one or more clients I'd opt for a statically rather than for a dynamically assigned and configured IP-address on the server.
I'm not saying you must, but I think you should (https://tools.ietf.org/html/rfc2119).
Obviously there are many different ways in which one can use an RPi. In addition an end user device like an RPi may be used to act as both server and client. That is to say I believe software like OpenCPN can also be installed on the same Pi that is receiving the AIS messages, so what would one do in such a case?
But in general I would stick with the rule of thumb of sorts that I described above.
Earlier this month someone pointed me to the following (I quote):
If you want to fix your LAN IP you do it by amending /etc/dhcpcd.conf adding the following lines (adjust to suit your environment):
# It is possible to fall back to a static IP if DHCP fails:
# define static profile
profile static eth0
static ip_address=192.168.1.7/24
static routers=192.168.1.254
static domain_name_servers=8.8.8.8 8.8.4.4
# fallback to static profile on eth0
interface eth0
fallback static_eth0
This way DHCP will work if plugged into a client switch port, but static IP will default when no DHCP is available.
Great for testing the box on one’s desktop before going live.
Amend your hostname by editing /etc/hostname and then adding the below to /etc/hosts.
I.e. if you call your machine ‘brett’ fix the /etc/hosts 127.0.1.1 line:
127.0.1.1 brett
(end of quote)
I haven't tested it, but at first glance it seems to make sense, so I hope this helps.
Regards, Jk.
From: kp...@googlegroups.com [mailto:kp...@googlegroups.com] On Behalf Of Brett Marl
Sent: Tuesday, 26 January, 2021 18:48
To: kplex
Subject: Re: Kplex on Raspberry Pi 4, Ubuntu 20.04
In general I’d agree that servers should be static but I’m not sure that is always the case nor should it be assumed. I can see plenty of reasons where DHCP might be acceptable.
In any case - I think the interesting thing here is that a few people have reported issues with auto-starting kplex on a RPi and Keith went out of his way to get systemd working assuming init.d was somehow the problem. I suspect regardless of which boot method you use the underling problem to kplex not launching an interface it uses is setup for DHCP vs static. Maybe this is reported more with Pi users as perhaps they know less about what they are doing (like me ;)) to assume they would need a static ip.
On Tuesday, January 26, 2021 at 5:27:14 AM UTC-8 John W. Kitz wrote:
All,
Is it a good idea to begin with to use DHCP on a device which is acting as a server?
I'd answer that question with no. That noted as a newbie to all things relating to RPi's and Raspios, I recently installed kplex on an RPi3B with a dAISy HAT using DHCP to serve AIS messages to OpenCPN running on a Windows desktop client and, much to my surprise I got it working relatively quickly following the documentation supplied by the respective vendors or, in the case of kplex, developers to the letter.
To view this discussion on the web visit https://groups.google.com/d/msgid/kplex/28a17b76-32a0-49fc-a576-3a100b5677f7n%40googlegroups.com.