¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. QnetGateway
  2. Topics

QnetGateway Dashboard

 

IP address moved. Here is the dashboard relating to my previous request for help.

Carty KA2Y

QnetGateway Dashboard.pdf
QnetGateway Dashboard.pdf

 

Do you mean the it has moved up the screen?

The order of elements is set in Qnet configure the UPPER case D opption. Case is important here.?
 

¿ªÔÆÌåÓý

no, I meant my ip address hadchanged and that is why I could noy find the dashboard.

Carty


On Feb 6, 2021, at 2:58 PM, John F Davis <wa8yxm@...> wrote:

?

Do you mean the it has moved up the screen?

The order of elements is set in Qnet configure the UPPER case D opption. Case is important here.?
 

That is why I know how to querry the router to find the IP address.
you can also set static address.

"Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis

On Saturday, February 6, 2021, 03:18:22 PM EST, Carty Ellis <carty.ellis@...> wrote:


no, I meant my ip address hadchanged and that is why I could noy find the dashboard.

Carty


On Feb 6, 2021, at 2:58 PM, John F Davis <wa8yxm@...> wrote:

?

Do you mean the it has moved up the screen?

The order of elements is set in Qnet configure the UPPER case D opption. Case is important here.?
 

Whenever I bring up a new computer on my local network, I make sure it has a unique hostname. For the Raspberry Pi, you can do this with the rasp-config program.

If you have a halfway decent home router, you should be able to bring up your QnetGateway dashboard from any system on your local network using the url "<hostname>.local" where <hostname> is the hostname assigned to the system QnetGateway is installed. For example, I assigned "zumspot" to my Pi Zero W with ZUM board.

Then in a browser, I type "zumspot.local". No "http://", no "www.", just "zumspot.local" and the browser will query my home router and figure out how to get to my zumspot.
 

Setting a simple text network ID is always a good idea, but I typically take further steps as well in order to make sure I know where and what everything is.

For ipv4, I have the DHCP server hand out static addresses as opposed to setting static addresses on the individual devices.? Nearly every commercial or hobby device has DHCP enabled by default, making this a very clean method to ensure that everything has a static IP without conflicts.

For ipv6, conflicts are precluded by using SLAAC; but addresses can change.? When I can, I used hardware based addressing.? Each device generates its IP address using the prefix advertised by the router, and completes its address using the MAC of its network card.? With hardware SLAAC, you effectively obtain a static IP--unless your prefix changes (extremely rare in my experience, even if your provider doesn't explicitly provide a static IP).? If the prefix does change, it will be evident on all devices on your network; so determining the address of a specific device is simple.

1 - 6 of 6