Good core connection, but can't ping

Sixfab Connect Sixfab CORE
1

Hi All

Here are results of inputs … wondering why I can’t ping 192.168.225.29

I feel like I’m so close, but am doing something stupid for final connection :slight_smile: I am new to this and volunteering my time to get it running. If it works, I think many astronomical clubs will be interested in what we are doing.

I have no problems pinging 192.168.225.29 packets to and from using the pi … the problem is remote computers getting to the modem and then having access to the pi 5.

I was even able to SSH via the pi 5 … simply can’t outside of the pi5.

Here is info you requested, I also included a quick ssh connect:

mas-fits-allsky@mas-fits-allsky:~ $ ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255

inet6 fe80::5d2:928e:83e4:cb8a prefixlen 64 scopeid 0x20

inet6 fda9:6cae:b84d:1abf:b6e5:f4ef:9f41:1fc prefixlen 64 scopeid 0x0

ether d8:3a:dd:f4:fe:20 txqueuelen 1000 (Ethernet)

RX packets 4036 bytes 1193846 (1.1 MiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 2345 bytes 6550419 (6.2 MiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

device interrupt 112

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet 127.0.0.1 netmask 255.0.0.0

inet6 ::1 prefixlen 128 scopeid 0x10

loop txqueuelen 1000 (Local Loopback)

RX packets 124 bytes 10047 (9.8 KiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 124 bytes 10047 (9.8 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

ether d8:3a:dd:f4:fe:21 txqueuelen 1000 (Ethernet)

RX packets 0 bytes 0 (0.0 B)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 0 bytes 0 (0.0 B)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wwan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 192.168.225.29 netmask 255.255.255.0 broadcast 192.168.225.255

inet6 fe80::574:a5a8:db71:b9b7 prefixlen 64 scopeid 0x20

ether 2a:bf:4d:64:4d:93 txqueuelen 1000 (Ethernet)

RX packets 35 bytes 2104 (2.0 KiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 68 bytes 6770 (6.6 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

mas-fits-allsky@mas-fits-allsky:~ $ ping -I wwan0 8.8.8.8 -c 10

PING 8.8.8.8 (8.8.8.8) from 192.168.225.29 wwan0: 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=189 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=72.6 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=73.1 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=70.2 ms

64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=68.8 ms

64 bytes from 8.8.8.8: icmp_seq=6 ttl=56 time=76.9 ms

64 bytes from 8.8.8.8: icmp_seq=7 ttl=56 time=90.3 ms

64 bytes from 8.8.8.8: icmp_seq=8 ttl=56 time=77.7 ms

64 bytes from 8.8.8.8: icmp_seq=9 ttl=56 time=82.2 ms

64 bytes from 8.8.8.8: icmp_seq=10 ttl=56 time=74.5 ms

— 8.8.8.8 ping statistics —

10 packets transmitted, 10 received, 0% packet loss, time 9013ms

rtt min/avg/max/mdev = 68.821/87.540/189.042/34.354 ms

mas-fits-allsky@mas-fits-allsky:~ $ ping -I wwan0 google.com -c 10

PING google.com (142.250.113.113) from 192.168.225.29 wwan0: 56(84) bytes of data.

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=1 ttl=54 time=218 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=2 ttl=54 time=107 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=3 ttl=54 time=102 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=4 ttl=54 time=125 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=5 ttl=54 time=103 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=6 ttl=54 time=102 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=7 ttl=54 time=103 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=8 ttl=54 time=99.5 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=9 ttl=54 time=98.2 ms

64 bytes from rs-in-f113.1e100.net (142.250.113.113): icmp_seq=10 ttl=54 time=107 ms

— google.com ping statistics —

10 packets transmitted, 10 received, 0% packet loss, time 9012ms

rtt min/avg/max/mdev = 98.201/116.571/218.041/34.548 ms

mas-fits-allsky@mas-fits-allsky:~ $ ssh mas-fits-allsky@192.168.225.29

The authenticity of host ‘192.168.225.29 (192.168.225.29)’ can’t be established.

ED25519 key fingerprint is SHA256:dCs1xfENa2tOrUgiZlA92UthDUg6/20SVknffMKuRlA.

This key is not known by any other names.

Are you sure you want to continue connecting (yes/no/[fingerprint])? yes

Warning: Permanently added ‘192.168.225.29’ (ED25519) to the list of known hosts.

mas-fits-allsky@192.168.225.29’s password:

Linux mas-fits-allsky 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64

The programs included with the Debian GNU/Linux system are free software;

the exact distribution terms for each program are described in the

individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

mas-fits-allsky@mas-fits-allsky:~ $ netstat -tuln | grep ‘:22’

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN

tcp6 0 0 :::22 :::* LISTEN

2

Getting no reply from here or support, I guess it’s time I ask Sales for an RMA. Everything seems to be configured properly and I can ping on local pi machine. The IP address must be bogus or configured improperly at Sixfab end. Or there is a hardware problem.

I’ll give support another day to respond.

It’s crazy to me that I can remote into the Sixfab/core/agent folder, but nowhere else.

Hope someone can help!

sixfab@mas-fits-allsky:/opt/sixfab/core/agent $ ip route
default via 192.168.225.1 dev wwan0 proto dhcp src 192.168.225.29 metric 500
192.168.225.0/24 dev wwan0 proto dhcp scope link src 192.168.225.29 metric 500

sixfab@mas-fits-allsky:/opt/sixfab/core/agent $ route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.225.1 0.0.0.0 UG 500 0 0 wwan0
192.168.225.0 0.0.0.0 255.255.255.0 U 500 0 0 wwan0

sixfab@mas-fits-allsky:/opt/sixfab/core/agent $ ping google.com
PING google.com (142.251.16.100) 56(84) bytes of data.
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=1 ttl=103 time=70.0 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=2 ttl=103 time=78.4 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=3 ttl=103 time=71.1 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=4 ttl=103 time=69.5 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=5 ttl=103 time=67.3 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=6 ttl=103 time=72.7 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=7 ttl=103 time=84.9 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=8 ttl=103 time=60.1 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=9 ttl=103 time=78.9 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=10 ttl=103 time=71.6 ms
64 bytes from bl-in-f100.1e100.net (142.251.16.100): icmp_seq=11 ttl=103 time=76.2 ms
^C
— google.com ping statistics —
11 packets transmitted, 11 received, 0% packet loss, time 10014ms
rtt min/avg/max/mdev = 60.131/72.796/84.885/6.321 ms

3

and goodbye and good riddance to sixfab. I’ll go with people who help.

4

Hi,

According to the information provided, it seems that your Raspberry Pi can access the Internet and successfully ping external hosts. However, you cannot ping the Raspberry Pi from outside your local network.

5

Yes I agree with that. Some on this forum say your product is not designed to be used for remote connections to pi, and if that is the case, that is fine. I just need to move on.

6

Your core connection has ability to access the modem, I don’t know if you use ip address or what. But pi cannot be accessed with ip showing up with wwan0.

7

It actually accesses your device, not the modem. Remote terminal is already doing this job. If you want to access your Raspberry Pi, you need to configure port forwarding, firewall settings, dynamic DNS, tunnelling, etc. yourself.

8

Do you have tutorial on that? What port is sixfab using? and how do I port it to public port?

9

Unfortunately, there is no tutorial I can share with you.

10

What port are you using that I need to forward?

11

if you’re not going to answer, please give me an RMA, I like to work with people who help me out and don’t tell me to figure it out myself.

12

I don’t quite understand your question.

13

product does not work as I was told, I would either like support to get it to work, or I would like a return authorization so I can start working with another vendor.

I didn’t understand this from you

“If you want to access your Raspberry Pi, you need to configure port forwarding, firewall settings, dynamic DNS, tunnelling, etc. yourself.”

It seems it works in folder:
sixfab@mas-fits-allsky:/opt/sixfab/core/agent $

How do I use the dynamic IP to access?

This is what happens with ifconfig:

Yet when I ping 92.168.225.29, I have no access. What do I have to configure to get that to work, assuming you can get it to work.

sixfab@mas-fits-allsky:/opt/sixfab/core/agent $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.3 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fda9:6cae:b84d:1abf:b6e5:f4ef:9f41:1fc prefixlen 64 scopeid 0x0
inet6 fe80::5d2:928e:83e4:cb8a prefixlen 64 scopeid 0x20
ether d8:3a:dd:f4:fe:20 txqueuelen 1000 (Ethernet)
RX packets 399 bytes 227254 (221.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 330 bytes 44746 (43.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 112

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 65 bytes 8409 (8.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 65 bytes 8409 (8.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether d8:3a:dd:f4:fe:21 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wwan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.225.29 netmask 255.255.255.0 broadcast 192.168.225.255
inet6 fe80::380c:e6f4:8e9d:7e62 prefixlen 64 scopeid 0x20
ether f6:11:09:3d:69:38 txqueuelen 1000 (Ethernet)
RX packets 12 bytes 756 (756.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 46 bytes 5040 (4.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

sixfab@mas-fits-allsky:/opt/sixfab/core/agent $

14

So all your logs have a cellular interface as expected and you can ping. What I mean is that you need to do what you want with a third party application or a service / application that you will create yourself. These are not part of a product but your own wishes. You can use the “Remote Terminal” feature provided by CORE as a product.

Sorry for your RMA request, you can send an email to hello@sixfab.com for this.

15

I can’t ping remotely … have to use Core … that makes no sense? How do you run web pages from a browser?

If you explain how your system works, I’ll use it.

I go get an IP from ifconfig, I should be able to use that?

16

Yes or no. Can you access this device with the public IP shown with ifconfig?

If Yes, how do you configure the hat to get the access to the IP?