Hostname display is garbled and overwrites kernel version

[n3gwg]

Andy, et alia:

The hostname for my Pi-Star node is a fully qualified domain name (36 characters in length), as such when I go to the Dashboard page of Pi-Star it simply splats this right over the Kernel information making the entire thing unreadable.

In cases whereby someone has a hostname that is an FQDN can the Dashboard be amended in some way whereby it is displayed absent trashing other data displayed on the dashboard?

Thanks!

Stuart, N3GWG

[MW0MWZ]

Can I have a screen shot to show me what this looks like for you please.

[n3gwg]

Andy, A screen-shot has been attached hereto. Stuart Quoting: MW0MWZ ***@***.***>

  Can I have a screen shot to show me what this looks like for you please. — Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. You are receiving this because you authored the thread.Message ID: ***@***.***>

Links: ------ [1] #179 (comment) [2] https://github.com/notifications/unsubscribe-auth/ANYWYHBP5B24EASDJIAAY2LYXCOFHAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGAZTMNZSGE

[MW0MWZ]

Sadly I didn't get the pic, but I have made some adjustments based on assumption (you know what they say about that).

[n3gwg]

Andy, I am not sure why it did not get through (I replied via email to github, maybe that is why). Whatever the case, send me an email out of github or tell me how to upload a photo into github and I will send it to you. If you want to send me zoom link I can do a screen share and show it to you too. I suspect most hams do not have such an advanced home lab environment (I am a consultative computer scientist after all) that which instantiates hostname that is inclusive of the FQDN with a LAN subdomain, but I did notice the issue. My father once told me...we all know the problems when you assume, so, go ahead and presume and you should be fine! :) I have also attached it hereto again. 73, Stuart, N3GWG Quoting: MW0MWZ ***@***.***>

  Sadly I didn't get the pic, but I have made some adjustments based on assumption (you know what they say about that). — Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. You are receiving this because you authored the thread.Message ID: ***@***.***>

Links: ------ [1] #179 (comment) [2] https://github.com/notifications/unsubscribe-auth/ANYWYHDVBDKVSQYPUXUWRADYXCQH7AVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA3DQNZRGM

[AndyTaylorTweet]

Update and have a look, I did alraedy make some changes.

…

On 7 Mar 2024, at 18:12, Stuart Blake Tener ***@***.***> wrote: Andy, I am not sure why it did not get through (I replied via email to github, maybe that is why). Whatever the case, send me an email out of github or tell me how to upload a photo into github and I will send it to you. If you want to send me zoom link I can do a screen share and show it to you too. I suspect most hams do not have such an advanced home lab environment (I am a consultative computer scientist after all) that which instantiates hostname that is inclusive of the FQDN with a LAN subdomain, but I did notice the issue. My father once told me...we all know the problems when you assume, so, go ahead and presume and you should be fine! :) I have also attached it hereto again. 73, Stuart, N3GWG Quoting: MW0MWZ ***@***.***> > > > Sadly I didn't get the pic, but I have made some adjustments based > on assumption (you know what they say about that). > > — > Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. > You are receiving this because you authored the thread.Message ID: > ***@***.***> Links: ------ [1] #179 (comment) [2] https://github.com/notifications/unsubscribe-auth/ANYWYHDVBDKVSQYPUXUWRADYXCQH7AVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA3DQNZRGM — Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEPCN3BMU6ZQ7OBZ25KYJYDYXCUYFAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE2DQNBRG4>. You are receiving this because you are subscribed to this thread.

[n3gwg]

Andy, I just absorbed the update and it is an improvement for sure. Most devices on my network obtain their hostname and IP address via DHCP (static DHCP, but DHCP). As such, they all have FQDNs because pfSense also assigns the hostnames via DHCP. I have not looked at how Pi-Star is getting its IP and hostname, but that might be why. I would recommend substituting the architecture for the hostname in the field on the configuration screen and then placing a larger hostname field that could support a 40 character FQDN below and then adding the IP address as well. Thus, if you access Pi-Star's web interface via an FQDN it would also show the IP address it received and perhaps as well some other information like its gateway address, DNS address, and internet facing IP address. Just some ideas! :) By the way, I did notice that there is a field for hostname in the configuration below, how does that impact the hostname of Pi-Star when it might be receiving its hostname with FQDN via DHCP? I did post this in the Pi-Star forum and on the OpenDV Groups.io but perhaps you know the answer: I have a ZUMspot v0.6 hat and I am trying to figure out what "Radio/Modem Type" is the proper one to use and as well what the latest firmware I can load on the ZUMspot v0.6 is. I had version 1.6.1 installed and someone said no that is wrong 1.5.2 is the latest so I reverted back. Thanks again! Be safe and healthy in these challenging times. Stuart Quoting: Andy Taylor ***@***.***>

Update and have a look, I did alraedy make some changes. > On 7 Mar 2024, at 18:12, Stuart Blake Tener ***@***.***> wrote: > > > Andy, > > I am not sure why it did not get through (I replied via email to > github, maybe that is why). Whatever the case, send me an email out of > github or tell me how to upload a photo into github and I will send it > to you. If you want to send me zoom link I can do a screen share and > show it to you too. > > I suspect most hams do not have such an advanced home lab environment > (I am a consultative computer scientist after all) that which > instantiates hostname that is inclusive of the FQDN with a LAN > subdomain, but I did notice the issue. > > My father once told me...we all know the problems when you assume, so, > go ahead and presume and you should be fine! :) > > I have also attached it hereto again. > > 73, > Stuart, N3GWG > > Quoting: MW0MWZ ***@***.***> > > > > > > > Sadly I didn't get the pic, but I have made some adjustments based > > on assumption (you know what they say about that). > > > > — > > Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. > > You are receiving this because you authored the thread.Message ID: > > ***@***.***> > > > > Links: > ------ > [1] > #179 (comment) > [2] > https://github.com/notifications/unsubscribe-auth/ANYWYHDVBDKVSQYPUXUWRADYXCQH7AVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA3DQNZRGM > > — > Reply to this email directly, view it on GitHub > <#179 (comment)>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEPCN3BMU6ZQ7OBZ25KYJYDYXCUYFAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE2DQNBRG4>. > You are receiving this because you are subscribed to this thread. >   — Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. You are receiving this because you authored the thread.Message ID: ***@***.***>

Links: ------ [1] #179 (comment) [2] https://github.com/notifications/unsubscribe-auth/ANYWYHC4S4LIAD4NB6CBIFDYXCWOLAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE3TEOBQGQ

[AndyTaylorTweet]

I also use pfSense, it’s a very sensible choice… I also have fully working / integrated DNS, and my devices have FQDN, and all their settings assigned by DHCP, and my devices only show their hostname and not FQDN, so not sure what you did there. Your device should know it’s FQDN, but the hostname should not be the FQDN…. somthing for you to look at possibly. I have a couple of ZumSpot boards, and mine are all loaded with 1.6.1 firmware, not sure where the idea that 1.5.1 is the latest build comes from. The FW should match the MMDVM Version you run, I now supply firmware with Pi-Star for this reason. Andy

…

On 7 Mar 2024, at 18:43, Stuart Blake Tener ***@***.***> wrote: Andy, I just absorbed the update and it is an improvement for sure. Most devices on my network obtain their hostname and IP address via DHCP (static DHCP, but DHCP). As such, they all have FQDNs because pfSense also assigns the hostnames via DHCP. I have not looked at how Pi-Star is getting its IP and hostname, but that might be why. I would recommend substituting the architecture for the hostname in the field on the configuration screen and then placing a larger hostname field that could support a 40 character FQDN below and then adding the IP address as well. Thus, if you access Pi-Star's web interface via an FQDN it would also show the IP address it received and perhaps as well some other information like its gateway address, DNS address, and internet facing IP address. Just some ideas! :) By the way, I did notice that there is a field for hostname in the configuration below, how does that impact the hostname of Pi-Star when it might be receiving its hostname with FQDN via DHCP? I did post this in the Pi-Star forum and on the OpenDV Groups.io but perhaps you know the answer: I have a ZUMspot v0.6 hat and I am trying to figure out what "Radio/Modem Type" is the proper one to use and as well what the latest firmware I can load on the ZUMspot v0.6 is. I had version 1.6.1 installed and someone said no that is wrong 1.5.2 is the latest so I reverted back. Thanks again! Be safe and healthy in these challenging times. Stuart Quoting: Andy Taylor ***@***.***> > Update and have a look, I did alraedy make some changes. > >> On 7 Mar 2024, at 18:12, Stuart Blake Tener ***@***.***> wrote: >> >> >> Andy, >> >> I am not sure why it did not get through (I replied via email to >> github, maybe that is why). Whatever the case, send me an email out of >> github or tell me how to upload a photo into github and I will send it >> to you. If you want to send me zoom link I can do a screen share and >> show it to you too. >> >> I suspect most hams do not have such an advanced home lab environment >> (I am a consultative computer scientist after all) that which >> instantiates hostname that is inclusive of the FQDN with a LAN >> subdomain, but I did notice the issue. >> >> My father once told me...we all know the problems when you assume, so, >> go ahead and presume and you should be fine! :) >> >> I have also attached it hereto again. >> >> 73, >> Stuart, N3GWG >> >> Quoting: MW0MWZ ***@***.***> >> >> > >> > >> > Sadly I didn't get the pic, but I have made some adjustments based >> > on assumption (you know what they say about that). >> > >> > — >> > Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. >> > You are receiving this because you authored the thread.Message ID: >> > ***@***.***> >> >> >> >> Links: >> ------ >> [1] >> #179 (comment) >> [2] >> https://github.com/notifications/unsubscribe-auth/ANYWYHDVBDKVSQYPUXUWRADYXCQH7AVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA3DQNZRGM >> >> — >> Reply to this email directly, view it on GitHub >> <#179 (comment)>, or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AEPCN3BMU6ZQ7OBZ25KYJYDYXCUYFAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE2DQNBRG4>. >> You are receiving this because you are subscribed to this thread. >> > > > — > Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. > You are receiving this because you authored the thread.Message ID: > ***@***.***> Links: ------ [1] #179 (comment) [2] https://github.com/notifications/unsubscribe-auth/ANYWYHC4S4LIAD4NB6CBIFDYXCWOLAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE3TEOBQGQ — Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEPCN3BWK4HVP5NVG6HEN53YXCYMJAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE4TSNRTGA>. You are receiving this because you commented.

[n3gwg]

Andy, Succeding my query to you about the firmware for the ZUMspot v0.6 someone promptly repied on the OpenDV forum! Never miss a chance to make myself look silly! :) I indeed installed the 1.6.1 firmware using the modem upgrade command: pistar-modemupgrade zum_rpi Here is what I have, perhaps you can advise me as to what (if anything) ought change: ***@***.***(rw):~# cat /etc/hostname pi-star-n3gwg ***@***.***(rw):~# cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters   127.0.1.1 pi-star-n3gwg ***@***.***(rw):~# hostname -f pi-star-n3gwg.lan.tener4assembly.com ***@***.***(rw):~# hostname -s pi-star-n3gwg ***@***.***(rw):~# hostnamectl --transient pi-star-n3gwg.lan.tener4assembly.com ***@***.***(rw):~# hostnamectl --static pi-star-n3gwg ***@***.***(rw):~# hostnamectl --pretty   ***@***.***(rw):~# domainname (none) ***@***.***(rw):~#  Stuart   Quoting: Andy Taylor ***@***.***>

I also use pfSense, it’s a very sensible choice… I also have fully working / integrated DNS, and my devices have FQDN, and all their settings assigned by DHCP, and my devices only show their hostname and not FQDN, so not sure what you did there. Your device should know it’s FQDN, but the hostname should not be the FQDN…. somthing for you to look at possibly. I have a couple of ZumSpot boards, and mine are all loaded with 1.6.1 firmware, not sure where the idea that 1.5.1 is the latest build comes from. The FW should match the MMDVM Version you run, I now supply firmware with Pi-Star for this reason. Andy > On 7 Mar 2024, at 18:43, Stuart Blake Tener ***@***.***> wrote: > > > Andy, > > I just absorbed the update and it is an improvement for sure. > > Most devices on my network obtain their hostname and IP address via > DHCP (static DHCP, but DHCP). As such, they all have FQDNs because > pfSense also assigns the hostnames via DHCP. I have not looked at how > Pi-Star is getting its IP and hostname, but that might be why. > > I would recommend substituting the architecture for the hostname in > the field on the configuration screen and then placing a larger > hostname field that could support a 40 character FQDN below and then > adding the IP address as well. Thus, if you access Pi-Star's web > interface via an FQDN it would also show the IP address it received > and perhaps as well some other information like its gateway address, > DNS address, and internet facing IP address. Just some ideas! :) > > By the way, I did notice that there is a field for hostname in the > configuration below, how does that impact the hostname of Pi-Star when > it might be receiving its hostname with FQDN via DHCP? > > I did post this in the Pi-Star forum and on the OpenDV Groups.io but > perhaps you know the answer: I have a ZUMspot v0.6 hat and I am trying > to figure out what "Radio/Modem Type" is the proper one to use and as > well what the latest firmware I can load on the ZUMspot v0.6 is. I had > version 1.6.1 installed and someone said no that is wrong 1.5.2 is the > latest so I reverted back. > > Thanks again! > > Be safe and healthy in these challenging times. > > Stuart > > > Quoting: Andy Taylor ***@***.***> > > > Update and have a look, I did alraedy make some changes. > > > >> On 7 Mar 2024, at 18:12, Stuart Blake Tener ***@***.***> wrote: > >> > >> > >> Andy, > >> > >> I am not sure why it did not get through (I replied via email to > >> github, maybe that is why). Whatever the case, send me an email out of > >> github or tell me how to upload a photo into github and I will send it > >> to you. If you want to send me zoom link I can do a screen share and > >> show it to you too. > >> > >> I suspect most hams do not have such an advanced home lab environment > >> (I am a consultative computer scientist after all) that which > >> instantiates hostname that is inclusive of the FQDN with a LAN > >> subdomain, but I did notice the issue. > >> > >> My father once told me...we all know the problems when you assume, so, > >> go ahead and presume and you should be fine! :) > >> > >> I have also attached it hereto again. > >> > >> 73, > >> Stuart, N3GWG > >> > >> Quoting: MW0MWZ ***@***.***> > >> > >> > > >> > > >> > Sadly I didn't get the pic, but I have made some adjustments based > >> > on assumption (you know what they say about that). > >> > > >> > — > >> > Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. > >> > You are receiving this because you authored the thread.Message ID: > >> > ***@***.***> > >> > >> > >> > >> Links: > >> ------ > >> [1] > >> > #179 (comment) > >> [2] > >> > https://github.com/notifications/unsubscribe-auth/ANYWYHDVBDKVSQYPUXUWRADYXCQH7AVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGA3DQNZRGM > >> > >> — > >> Reply to this email directly, view it on GitHub > >> > <#179 (comment)>, or > unsubscribe > >> > <https://github.com/notifications/unsubscribe-auth/AEPCN3BMU6ZQ7OBZ25KYJYDYXCUYFAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE2DQNBRG4>. > >> You are receiving this because you are subscribed to this thread. > >> > > > > > > — > > Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. > > You are receiving this because you authored the thread.Message ID: > > ***@***.***> > > > > Links: > ------ > [1] > #179 (comment) > [2] > https://github.com/notifications/unsubscribe-auth/ANYWYHC4S4LIAD4NB6CBIFDYXCWOLAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE3TEOBQGQ > > — > Reply to this email directly, view it on GitHub > <#179 (comment)>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEPCN3BWK4HVP5NVG6HEN53YXCYMJAVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGE4TSNRTGA>. > You are receiving this because you commented. >   — Reply to this email directly, view it on GitHub[1], or unsubscribe[2]. You are receiving this because you authored the thread.Message ID: ***@***.***>

Links: ------ [1] #179 (comment) [2] https://github.com/notifications/unsubscribe-auth/ANYWYHFSUQGM7HHCVD4VQCDYXC2J5AVCNFSM6AAAAABELLUKY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBUGIZDMNJUHA