FYI, from 44.182.21.1 - your tunnel seems to be up and running:

PING 44.135.148.129 (44.135.148.129) 56(84) bytes of data.
64 bytes from 44.135.148.129: icmp_seq=1 ttl=64 time=191 ms
64 bytes from 44.135.148.129: icmp_seq=2 ttl=64 time=191 ms
64 bytes from 44.135.148.129: icmp_seq=3 ttl=64 time=195 ms
64 bytes from 44.135.148.129: icmp_seq=4 ttl=64 time=191 ms
^C
--- 44.135.148.129 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 191.071/192.306/195.135/1.643 ms

Remember, you also need a forward rule allowing routing from your tun44 interface to eth2 and back.
If your default policy is 'drop', your linux box will not be accessible.

On 18/10/2022 20:43, Marius Petrescu via 44net wrote:

Also it may be a problem that 44.60.44.1 doesn't respond to pings?
You may want to try these hosts for test:
- 44.182.21.1 - my VPS host, home of the mapping tool
- 44.182.21.253 - my edgerouter (user demo, passwd demo to access the dashboard). The description in the wiki was made using this router as reference
- 44.182.21.254 - my mikrotik GW - should allow ping and traceroute

Marius, YO2LOJ

On 18/10/2022 20:18, Stephen Atkins via 44net wrote:
I'm trying to use the instructions at https://wiki.ampr.org/wiki/Setting_up_a_gateway_on_Ubiquiti_EdgeRouter and I thought everything was working but I'm having and issues.

eth0 is my internet at 50.93.51.24
eth1 is my 192.168.1.x network
eth2 is my 44.135.148.129
switch0 is 192.168.1.1/24
tun44 was setup using the instructions (used 44 instead of 0)

I added the protocols (changed next-hop to tun44)
Added all the firewall modifications (keeping table 1)

I have setup in the portal my gateway at 50.93.51.24 (Did this yesterday).

My linux box has two network cards.  One on 192.168.1.110 and the other is set to 44.135.148.130/27.

My problem is I can't ping from the outside world to my linux box on the 44 network.  On my linux box when I try and ping any 44 network (like 44.60.44.10) none of the packets make it through.  I tried pinging 44.60.44.10 from the Edgerouter command line and it won't make it either.  I'm sure I missed something but I don't know what it might be.  Any help would be appreciated.

Stephen Atkins
VE6CPU/VE6STA/VE6SU

Sent with Proton Mail secure email.

_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org

_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org