Can I tunnel thru my Verizon cel phone?

10 posts / 0 new

Tue, 01/29/2019 - 22:21

KG4IKT

Here's the hardware:
Verizon LG G6 supplies a hot spot which is connected to by a TP-Link Nano router which is cabled to the Wan port on a MikroTik hAP ac lite.

My computer is plugged into the Mikrotik, and i'm surfing the web just fine.

I set up a tunnel from my existing tunnel server node and it's similar to other tunnels i'm serving.
On the client i'm using my kg4ikt.ddns.net like other clients that connect to my server.
Doesn't appear to make a connection.

Is this a port 5525 issue?

I looked at the data from the client node and found this;
Tue Jan 29 21:12:30 2019 daemon.info vtund[3494]: Connecting to kg4ikt.ddns.net
Tue Jan 29 21:12:31 2019 daemon.info vtund[3494]: Connection denied by kg4ikt.ddns.net
Is there a connection limit to ddns.net?

Wed, 01/30/2019 - 13:14

AE6XE

looks like a password or

looks like a password or hostname issue. Check the server log side to see if there is a logread entry for failed login. To diagnose network connection issues, on the client side, "telnet <IP of tunnel server> 5525" If it connects and you see a vtun header line, then the network is correctly configured and not the problem.

Joe AE6XE

Wed, 01/30/2019 - 14:29

(Reply to #2) #3

KG4IKT

The "telnet <IP of tunnel

The "telnet <IP of tunnel server> 5525 " does connect.

Below is some of the data file.
How about that "bad address at /var/run/hosts_olsr line 2"? See my notes further below.

Should I be concerned about all the denied connections?
My cel currently has 174.195.129.56

Wed Jan 30 13:03:28 2019 daemon.info vtund[29201]: Denied connection from 64.253.211.118:53979
Wed Jan 30 13:03:29 2019 daemon.info vtund[29202]: Denied connection from 174.195.129.56:11021
Wed Jan 30 13:03:31 2019 daemon.info vtund[29216]: Denied connection from 64.253.211.83:37743
Wed Jan 30 13:03:32 2019 daemon.info vtund[29217]: Denied connection from 64.253.213.33:36295
Wed Jan 30 13:03:33 2019 daemon.info vtund[29222]: Denied connection from 64.253.211.118:39461
Wed Jan 30 13:03:35 2019 daemon.info vtund[29223]: Denied connection from 174.195.129.56:11035
Wed Jan 30 13:03:36 2019 daemon.info vtund[29234]: Denied connection from 64.253.211.83:32771
Wed Jan 30 13:03:37 2019 daemon.info vtund[29269]: Denied connection from 64.253.213.33:40083
Wed Jan 30 13:03:39 2019 daemon.info vtund[29275]: Denied connection from 64.253.211.118:49383
Wed Jan 30 13:03:39 2019 daemon.info dnsmasq[1708]: read /etc/hosts - 9 addresses
Wed Jan 30 13:03:39 2019 daemon.err dnsmasq[1708]: bad address at /var/run/hosts_olsr line 2
Wed Jan 30 13:03:39 2019 daemon.info dnsmasq[1708]: read /var/run/hosts_olsr - 647 addresses
Wed Jan 30 13:03:39 2019 daemon.info dnsmasq-dhcp[1708]: read /etc/ethers - 5 addresses
Wed Jan 30 13:03:40 2019 daemon.info vtund[29281]: Denied connection from 174.195.129.56:11036
Wed Jan 30 13:03:41 2019 daemon.info vtund[29303]: Denied connection from 64.253.211.83:43941
Wed Jan 30 13:03:43 2019 daemon.info vtund[29308]: Denied connection from 64.253.213.33:44777
Wed Jan 30 13:03:44 2019 daemon.info vtund[29309]: Denied connection from 64.253.211.118:59541
Wed Jan 30 13:03:45 2019 daemon.err uhttpd[848]: No such wireless device: eth0.3975
Wed Jan 30 13:03:46 2019 daemon.info vtund[29342]: Denied connection from 174.195.129.56:11019
Wed Jan 30 13:03:47 2019 daemon.info vtund[29360]: Denied connection from 64.253.211.83:36443
Wed Jan 30 13:03:48 2019 daemon.info vtund[29365]: Denied connection from 64.253.213.33:45529
Wed Jan 30 13:03:49 2019 daemon.info vtund[29371]: Denied connection from 64.253.211.118:40442
Wed Jan 30 13:03:51 2019 daemon.info vtund[29402]: Denied connection from 174.195.129.56:11011
Wed Jan 30 13:03:52 2019 daemon.info vtund[29403]: Denied connection from 64.253.211.83:42129
Wed Jan 30 13:03:53 2019 daemon.info vtund[29408]: Denied connection from 64.253.213.33:33183
Wed Jan 30 13:03:54 2019 daemon.info vtund[29409]: Denied connection from 64.253.211.118:50997
Wed Jan 30 13:03:57 2019 daemon.info vtund[29424]: Denied connection from 64.253.211.83:39877
Wed Jan 30 13:03:57 2019 daemon.info vtund[29423]: Denied connection from 174.195.129.56:11023
Wed Jan 30 13:03:58 2019 daemon.info vtund[29425]: Denied connection from 64.253.213.33:39877
Wed Jan 30 13:03:59 2019 daemon.info vtund[29430]: Denied connection from 64.253.211.118:60022
Wed Jan 30 13:04:00 2019 cron.info crond[771]: USER root pid 29431 cmd /usr/local/bin/rssi_monitor
Wed Jan 30 13:04:00 2019 cron.info crond[771]: USER root pid 29432 cmd /usr/local/bin/snrlog
Wed Jan 30 13:04:00 2019 cron.info crond[771]: USER root pid 29433 cmd /usr/local/bin/clean_zombie.sh
Wed Jan 30 13:04:02 2019 daemon.info vtund[29445]: Denied connection from 64.253.211.83:33321
Wed Jan 30 13:04:03 2019 daemon.info vtund[29447]: Denied connection from 174.195.129.56:10016
Wed Jan 30 13:04:04 2019 daemon.info vtund[29452]: Denied connection from 64.253.213.33:37783
Wed Jan 30 13:04:04 2019 daemon.info vtund[29455]: Denied connection from 64.253.211.118:37021
Wed Jan 30 13:04:07 2019 daemon.info vtund[29467]: Denied connection from 64.253.211.83:33941
Wed Jan 30 13:04:08 2019 daemon.info vtund[29468]: Denied connection from 174.195.129.56:10040
Wed Jan 30 13:04:09 2019 daemon.info dnsmasq[1708]: read /etc/hosts - 9 addresses
Wed Jan 30 13:04:09 2019 daemon.err dnsmasq[1708]: bad address at /var/run/hosts_olsr line 2
Wed Jan 30 13:04:09 2019 daemon.info dnsmasq[1708]: read /var/run/hosts_olsr - 647 addresses
Wed Jan 30 13:04:09 2019 daemon.info dnsmasq-dhcp[1708]: read /etc/ethers - 5 addresses
Wed Jan 30 13:04:09 2019 daemon.info vtund[29474]: Denied connection from 64.253.213.33:45405
Wed Jan 30 13:04:10 2019 daemon.info vtund[29475]: Denied connection from 64.253.211.118:35210
Wed Jan 30 13:04:10 2019 daemon.info vtund[29451]: Denied connection from 174.195.129.56:10036
Wed Jan 30 13:04:13 2019 daemon.info vtund[29501]: Denied connection from 64.253.211.83:46565
Wed Jan 30 13:04:14 2019 daemon.info vtund[29503]: Denied connection from 64.253.213.33:38451
Wed Jan 30 13:04:14 2019 daemon.info vtund[29502]: Denied connection from 174.195.129.56:10017
Wed Jan 30 13:04:15 2019 daemon.info vtund[29509]: Denied connection from 64.253.211.118:48287
Wed Jan 30 13:04:15 2019 daemon.err uhttpd[848]: No such wireless device: eth0.3975
Wed Jan 30 13:04:17 2019 daemon.err uhttpd[848]: No such wireless device: eth0.3975
Wed Jan 30 13:04:17 2019 daemon.err uhttpd[848]: command failed: No such device (-19)
Wed Jan 30 13:04:17 2019 daemon.err uhttpd[848]: command failed: No such device (-19)
Wed Jan 30 13:04:18 2019 daemon.info vtund[29579]: Denied connection from 64.253.211.83:37371

**********************************
here is the start of the hosts_oslr
### this /etc/hosts file is overwritten regularly by olsrd
### do not edit

127.0.0.1   localhost
::1       localhost

10.76.213.112   KG4IKT-ARHP-202-BRADYVILLE   # myself
10.205.87.12   chupacabra   # myself
10.205.87.7   PiICS   # myself
...
...

The entry 10.76.213.112 is for that nodes' RF which is turned off.

Wed, 01/30/2019 - 23:51

(Reply to #3) #4

AE6XE

'How about that "bad address

'How about that "bad address at /var/run/hosts_olsr line 2"?'
line 2 is a comment line that dnsmasq doesn't expect. It does no harm.

'The entry 10.76.213.112 is for that nodes' RF which is turned off."

When the nodes' RF is turned off (interface is typically wlan0), then another sudo interface is defined instead, which is up and live. It is still a valid routable IP address, and the primary address used on the mesh, to route to this node.

Joe AE6XE

Wed, 01/30/2019 - 15:29

K5DLQ

looks like a password

looks like a password mismatch. Doublecheck the password entries on the tunnel server and client to ensure a match. Make sure that the server has the connections enabled.

Wed, 01/30/2019 - 18:58

(Reply to #5) #6

KG4IKT

passwords are fine, same one

passwords are fine, same one i use for the other existing tunnels on my server.

After issuing the "telnet ip 5525", are there other commands i might issue?

Wed, 01/30/2019 - 20:26

K5DLQ

Interesting. Can you copy

Interesting. Can you copy the following file from both the tunnel server and the tunnel client (/etc/config/vtun) and email it to me at k5dlq@arednmesh.org?
DO NOT POST IT HERE as it contains sensitive information!

I'll take a look and see if I can determine what's going on with the issue.

Thanks,
Darryl - K5DLQ

Thu, 01/31/2019 - 11:08

k1ky

Can't connect to same Tunnel Domain

Not sure if it applies in this case, but I have found that I cannot connect to my domain from within my domain - if that makes any sense. If you are using the Microtik as a "client" that is connected to your Cellphone which is supplying the internet connection - that "should" work. Just make sure that there isn't a connection to your Wi-Fi or anything that looks like a connection to your local network from the tunnel client that is attempting to connect. What happens if you try to connect to an external Tunnel server?

Thu, 01/31/2019 - 11:39

AE6XE

Make sure the hostname of the

Make sure the hostname of the tunnel client is identical to the hostname the server knows it as. As I recall, both the hostname and the password need to be exact, like user and password login. Since we can do a telnet client->server, we know the network is ruled out.

Joe AE6XE

Thu, 01/31/2019 - 13:35

#10

k1ky

The solution - (for now)

Working with Jeff on this - we reduced the Tunnel Client Node name from 28 characters to 24 characters. This took care of the issue, so there still seems to be problems with long tunnel client node names for connection to a tunnel server. I had once thought the limit was around 31 characters, but I never really experimented with it to see "where" the cutoff was. Maybe someone else can shed some light on this matter.

Amateur Radio Emergency Data Network

Menu SF

You are here

Can I tunnel thru my Verizon cel phone?

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Can I tunnel thru my Verizon cel phone?