K7LKA wrote: ↑Mon Jun 10, 2019 11:33 pm
I'm having major issues trying to open the dashboard via the server.
Why does one have to connect to a server to configure a pi star.
I'll echo the question: "What server?"
Do you mean a router? I'm also presuming you mean via an ethernet cable
I should be able to connect the pi direct to my laptop and configure pi star
Is your laptop running a DHCP daemon? The R-Pi, on boot, is going to send DHCP requests over the Ethernet cable, asking to be issued an IP address from the "network". Issuing IP addresses is normal for routers (and, in truth, if you don't have the laptop connected to a router -- it won't have an IP address either unless you manually configure a fixed address for the NIC).
If you have your laptop connecting to the network via WiFi, and are attempting to connect to the R-Pi using cable, you need to enable "internet connection sharing" so the laptop will pass traffic from the R-Pi through to the WiFi router (so the router can respond to the DHCP request for an IP #). In actual operations, the R-Pi is going to need some sort of connection to a router (cable or WiFi) in order to pass digital voice traffic.
I'm have major issues trying to connect to the server.
After 10 tries I put everything away and call it quits.
I have to pi's a pi 3 and a pi3b+
Is it common to have conection issues to the server.
I think it only took me about an hour when I first configured mine -- and that was, I believe, BEFORE the "Auto AP" mode was implemented.. Would have been faster, but I hadn't realized the WiFi network connection is not made if there is a cable connection.
Granted, I tend to prefer working cable connections (while both of my printers have WiFi features, I direct cabled them to a high-speed switch -- faster data transfer than one gets with WiFi, and doesn't conflict with the router (the switch goes to the router, but traffic between nodes of the switch don't have to hit the router).
My procedure summarizes as:
Connect R-Pi to switch via cable and boot; it gets assigned a LAN IP from the router (check the router status page for client connections if I need to use the IP# itself)
Use browser to connect to R-Pi via hostname (just pi-star, no .local was needed)
Configure Pi-Star services (I also changed the hostname as I was thinking of getting a second unit so I could run both D-Star and DMR without having the hassle of Hang-time or chatty folks locking one mode).
Configure WiFi information (this is what took me some time before -- rebooting with the cable connected did not activate the WiFi connection. I finally disconnected the cable [for some reason] and rebooted -- this time the WiFi connected to the router).
More recent Pi-Star releases have Auto AP -- if the R-Pi, with no cable connection, is unable to connect to a WiFi router/access point, it will ITSELF create an Access Point (one with no internet access, obviously). One then arranges there computer to search for and connect to the Pi-Star setup access point (if one was using WiFi for internet, one has to disconnect from the internet to change to Pi-Star setup). Do configuration -- at the least of the WiFi router information, reboot. The R-Pi should now connect to the router/AP via WiFi (and your computer will not be connected to anything, so you need to reconnect it to the router). Check your router status pages for WiFi clients to ensure the R-Pi shows up...
Code: Select all
IPv4 Address / Name MAC Address Status Allocation Action
192.168.1.68 / EPSONF4EF32 00:26:ab:f4:ef:32 on DHCP Allocation
192.168.1.65 / DIRECTV-HR54-C94828D7 18:16:c9:48:28:d9 on DHCP Allocation
192.168.1.83 / unknown28c68efb9d7b 28:c6:8e:fb:9d:7b off DHCP Allocation
192.168.1.74 / unknown64c6670531d3 64:c6:67:05:31:d3 off DHCP Allocation
192.168.1.70 / Galaxy-S9 8c:45:00:6d:1a:4c on DHCP Allocation
192.168.1.79 / pi-star-3b b8:27:eb:4b:0b:d5 on DHCP Allocation
192.168.1.252 / microdiversity b8:27:eb:ce:b1:eb on DHCP Allocation
192.168.1.66 / ElusiveUnicorn b8:ca:3a:79:0c:36 on DHCP Allocation
192.168.1.84 / HP7C548D c4:65:16:7c:54:8d on DHCP Allocation
{the "unknown" are likely some of my Nook readers. Note that for my router, that table lists both WiFi and cable devices -- DirectTV, both "unknown", Galaxy phone, pi-star-3b, and microdiversity [another R-Pi 3B running a light duty web server] are WiFi; Epson and HP printers, and main computer are wired [and if I boot my laptop, it too is wired]}