MMDVM Hotspot not Internet Connection

Help setting up WiFi
DH5SDL
Posts: 13
Joined: Mon Feb 10, 2020 8:50 pm

Re: MMDVM Hotspot not Internet Connection

Post by DH5SDL »

The Passwort (psk) only letters
Raspberry via Lan connected to the Router also no connection to the internet


ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
ap_scan=1
fast_reauth=1
country=DE

network={
ssid="ALFA-AP-KT"
psk="abcdefg"
id_str="0"
priority=100
DH5SDL
Posts: 13
Joined: Mon Feb 10, 2020 8:50 pm

Re: MMDVM Hotspot not Internet Connection

Post by DH5SDL »

Thanks for reply.

i used the Pi-star wifi builder and copy the "wpa_supplicant.conf" to the SD Card.
That works but no internet only with the Caravan Router.
The Home Router works fine.
First i make it for the Home Network and after that works i make it also for the Caravan.
Home OK
Caravan No
AF6VN
Posts: 821
Joined: Fri Jul 20, 2018 1:15 am

Re: MMDVM Hotspot not Internet Connection

Post by AF6VN »

DH5SDL wrote: Thu Apr 02, 2020 4:37 pm The Passwort (psk) only letters
Raspberry via Lan connected to the Router
Well, if you are using a cable between the R-Pi and the router, the WiFi should not be active at all... And the PING test should have been using eth0 rather than wlan0.
network={
#ssid="WLAN-KT"
ssid=574c414e2d4b54
#psk="................."
psk=..............
id_str="0"
priority=100
And do the SSID and PSK entries exactly match the settings of the router? I would comment that the SSID looks like a very generic or factory value (that is, it doesn't look like something that might be unique to one router -- maybe it is, just that I can't see it :? ) (Yes, mine is a factory SSID, but it obviously looks to have been generated by some automatic algorithm and hence is unique).

I'm now trying wild guesses of things to look at for debugging...

Code: Select all

pi-star@pi-star-3b(ro):~$ sudo grep -i "wlan0" /var/log/syslog
Apr  2 13:27:20 pi-star-3b systemd[1]: Found device /sys/subsystem/net/devices/wlan0.
Apr  2 13:27:20 pi-star-3b systemd[1]: Started ifup for wlan0.
Apr  2 13:27:21 pi-star-3b wpa_supplicant[390]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: wlan0: connected to Access Point `'
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: wlan0: waiting for carrier
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: wlan0: carrier acquired
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: wlan0: IAID eb:4b:0b:d5
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: wlan0: adding address fe80::6c4b:16ec:dd77:c5a7
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: wlan0: carrier lost
Apr  2 13:27:21 pi-star-3b wpa_supplicant[390]: wlan0: Trying to associate with SSID 'ATTHWEwm7i'
Apr  2 13:27:22 pi-star-3b sh[264]: wlan0=wlan0
Apr  2 13:27:22 pi-star-3b wpa_supplicant[390]: wlan0: Associated with 64:55:b1:a7:3b:a0
Apr  2 13:27:22 pi-star-3b wpa_supplicant[390]: wlan0: CTRL-EVENT-CONNECTED - Connection to 64:55:b1:a7:3b:a0 completed [id=0 id_str=0]
Apr  2 13:27:22 pi-star-3b dhcpcd[310]: wlan0: carrier acquired
Apr  2 13:27:22 pi-star-3b wpa_supplicant[390]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Apr  2 13:27:22 pi-star-3b dhcpcd[310]: wlan0: connected to Access Point `ATTHWEwm7i'
Apr  2 13:27:22 pi-star-3b dhcpcd[310]: wlan0: IAID eb:4b:0b:d5
Apr  2 13:27:22 pi-star-3b dhcpcd[310]: wlan0: soliciting a DHCP lease
Apr  2 13:27:23 pi-star-3b dhcpcd[310]: wlan0: soliciting an IPv6 router
Apr  2 13:27:23 pi-star-3b dhcpcd[310]: wlan0: offered 192.168.1.79 from 192.168.1.254
Apr  2 13:27:23 pi-star-3b dhcpcd[310]: wlan0: probing address 192.168.1.79/24
Apr  2 13:27:28 pi-star-3b dhcpcd[310]: wlan0: leased 192.168.1.79 for 86400 seconds
Apr  2 13:27:28 pi-star-3b avahi-daemon[304]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.79.
Apr  2 13:27:28 pi-star-3b dhcpcd[310]: wlan0: adding route to 192.168.1.0/24
Apr  2 13:27:28 pi-star-3b dhcpcd[310]: wlan0: adding default route via 192.168.1.254
Apr  2 13:27:28 pi-star-3b avahi-daemon[304]: New relevant interface wlan0.IPv4 for mDNS.
Apr  2 13:27:28 pi-star-3b avahi-daemon[304]: Registering new address record for 192.168.1.79 on wlan0.IPv4.
Apr  2 13:27:29 pi-star-3b ntpd[799]: Listen normally on 3 wlan0 192.168.1.79:123
pi-star@pi-star-3b(ro):~$

pi-star@pi-star-3b(ro):~$ sudo grep -i "eth0" /var/log/syslog
Apr  2 13:27:20 pi-star-3b kernel: [    1.920875] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:1e:5e:80
Apr  2 13:27:21 pi-star-3b dhcpcd[310]: eth0: waiting for carrier
Apr  2 13:27:21 pi-star-3b kernel: [    6.612305] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr  2 13:27:23 pi-star-3b kernel: [    8.094278] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr  2 13:27:29 pi-star-3b minissdpd-systemd-wrapper[787]: Error parsing address/mask (or interface name) : eth0
Apr  2 13:27:29 pi-star-3b minissdpd-systemd-wrapper[787]: can't parse "eth0" as a valid address or interface name
{my unit does not have a cable connection for eth0}

ADDENDUM:

If you are trying to configure for two separate routers (since you mention HOME and CARAVAN), you SHOULD HAVE TWO separate network entries in wpa_supplicant.conf, with different priorities (and id-str?) to control which one is tried first.

The home router should have a different SSID (and PSK) from the mobile router.

If you are using a cable between the R-Pi and the router, then none of the wpa_supplicant stuff applies, since you are not using a WiFi connection on the R-Pi. Problems connecting to the rest of the world when using a cable between the client and the router implies the problem is the router link to the WAN. Either the router is blocking connections, or whatever the router is connected to is blocking connections!
Last edited by AF6VN on Thu Apr 02, 2020 6:20 pm, edited 1 time in total.

--
AF6VN
Dennis L Bieber
M1DNS
Pi-Star Team
Posts: 1388
Joined: Thu Apr 05, 2018 5:30 am

Re: MMDVM Hotspot not Internet Connection

Post by M1DNS »

Check the Wi-Fi connection encryption type. Needs WPA. I've had real headaches trying to get a connection with an older device, where it was using WEP.

Sent from my SM-G935F using Tapatalk

Andrew M1DNS.
Pi-star Admin Team.
DH5SDL
Posts: 13
Joined: Mon Feb 10, 2020 8:50 pm

Re: MMDVM Hotspot not Internet Connection

Post by DH5SDL »

OK i will test tomorrow,but why don't work the Lan Connection? Raspberry to the Router?
At the Moment i have WPA2-PSK
I have one SD Card for the Homenet and one for testing in the Caravan.
AF6VN
Posts: 821
Joined: Fri Jul 20, 2018 1:15 am

Re: MMDVM Hotspot not Internet Connection

Post by AF6VN »

DH5SDL wrote: Thu Apr 02, 2020 7:01 pm I have one SD Card for the Homenet and one for testing in the Caravan.
That actually does NOT HELP!

It means that ANYTHING could be different between the two SD cards which could affect networking.

--
AF6VN
Dennis L Bieber
DH5SDL
Posts: 13
Joined: Mon Feb 10, 2020 8:50 pm

Re: MMDVM Hotspot not Internet Connection

Post by DH5SDL »

Yes i'm sure.
The connection is right.
AF6VN
Posts: 821
Joined: Fri Jul 20, 2018 1:15 am

Re: MMDVM Hotspot not Internet Connection

Post by AF6VN »

Right now there are too many variables in play:

2 SD Cards (which may have different physical behavior)
2 Pi-Star software loads (which may or may not be identical)
2 Connection methods (WiFi at "Home", Ethernet cable at "Caravan")
2 Routers ("Home" and "Caravan")
2 Internet connections ("Home" router is direct, I presume; "Caravan" router is a WiFi extender connecting to some OTHER Router over WiFi)

That's a total of 32 combinations.

To minimize points of failure...

Take the unit to "Home" (use that SD card), but connect it to the "Home" router using an ethernet cable, and power it up.

Open a SSH session to it and enter:

Code: Select all

ifconfig eth0
Record the IP # assigned to that connection, it might be needed later

Code: Select all

sudo ifconfig wlan0 down
sudo ifconfig wlan0_ap down
If you lose the SSH session doing those, it means you were connected over WiFi. Open a new session using the IP # from the first step and continue from where the session was lost.

After doing the above -- the ONLY network connection should be the ethernet cable.

Code: Select all

sudo ping 8.8.8.8
Verify that ping finds the Google nameserver.

Open the Pi-Star dashboard and verify that the status boxes for whichever digital modes (D-STAR, DMR, one of the others?) you are using are green.
Test the connection using your radio.

IF (and only if) the above configuration (ethernet cable, no WiFi, home router) is working can you then go on to the next phase.

Shutdown the Pi-Star unit, and take it (including ethernet cable and working SD card) back to "Caravan". Repeat the above sequence (connect to router via ethernet, power up, SSH, ifconfig eth0, ifconfig wlan0* down).

The Pi-Star should now be in an identical state as it was at "Home". The only difference is likely the IP # that was issued.

If ping fails, or the dashboard does NOT show green for your digital modes, then the fault is NOT in the Pi-Star unit itself -- it is either your "Caravan" router/WiFi extender OR whatever WiFi router the extender is connecting to. The most likely fault point will be that the end WiFi router is blocking the ports needed http://wiki.pistar.uk/Ports_to_forward_ ... NP_network

Only when you get the cable connection to work in both locations can you worry about configuring WiFi connections for both routers (I'd probably make "Caravan" the priority with "Home" the fallback when it can't find "Caravan").

--
AF6VN
Dennis L Bieber
DH5SDL
Posts: 13
Joined: Mon Feb 10, 2020 8:50 pm

Re: MMDVM Hotspot not Internet Connection

Post by DH5SDL »

Now i test the hotspot with one Config,so i put the working Home to the caravan.
Here the result

Thats the Config Home with ethernet cable (it works)

ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:e0:4d:3a:a6:89
inet addr:192.168.2.26 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3309 errors:0 dropped:449 overruns:0 frame:0
TX packets:1721 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2030744 (1.9 MiB) TX bytes:608984 (594.7 KiB)

sudo ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=16.3 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=16.3 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=16.8 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=16.6 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=16.2 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=57 time=16.4 ms
^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6007ms
rtt min/avg/max/mdev = 16.254/16.551/17.007/0.264 ms


Thats the config in the caravan with ethernet cable

ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:e0:4d:3a:a6:89
inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3309 errors:0 dropped:3 overruns:0 frame:0
TX packets:1721 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:215251 (210.2KiB) TX bytes:678222 (662.3 KiB)

sudo ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=18.5 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=21.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=18.9 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=56 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=18.7 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=19.2 ms
^C
--- 8.8.8.8 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9009ms
rtt min/avg/max/mdev = 18.519/19.234/21.651/0.907 ms


The Dashboard shows green ....the same green like Home connected via ethernet cable
All looks good but no link via Dashboard or Transceiver
Attachments
Pi-star.png
Pi-star.png (106.59 KiB) Viewed 4154 times
DH5SDL
Posts: 13
Joined: Mon Feb 10, 2020 8:50 pm

Re: MMDVM Hotspot not Internet Connection

Post by DH5SDL »

I only have one hotspot that works perfectly at home via LAN and WiFi.
Nothing works only in the caravan.
Wifi and Lan ... neither is possible.
I have access to the dashboard but somehow the internet connection is missing
Post Reply