4 Apr
2022
4 Apr
'22
12:16 a.m.
Do you have your ISP-leased IP address hard coded somewhere and after the power outage,
they gave you a different IP address?
73 Jim KY2D
-----Original Message-----
From: 44Net <44net-bounces+jim.kutsch=ky2d.com(a)mailman.ampr.org> On Behalf Of Komkit
Listisard via 44Net
Sent: Sunday, April 3, 2022 12:48
To: Ruben ON3RVH via 44Net <44net(a)mailman.ampr.org>
Cc: Komkit Listisard <w3kit(a)yahoo.com>
Subject: Re: [44net] Raspberry Pi AMPRNet IPIP Gateway quit working
Net 44 came though eth0, I have a separate eth1 connecting through
switch and routed Net 44 there. Same as before, everything was working
fine until the power went out yesterday.
On 4/3/2022 12:08 PM, Ruben ON3RVH via 44Net wrote:
Why is your lan and wlan both connected to the same
network?
That’ll give issues, if you want to share your 44 with your radio network then disconnect
the lan interface from your normal network or give it a static ip in your 44 subnet
73,
ON3RVH
Sent from my iPhone
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
On 3 Apr 2022, at 17:50, David Ranch via 44Net
<44net(a)mailman.ampr.org> wrote:
Are you running an iptables firewall and you're allowing protocol 4 allowed through?
Run "sudo iptables -L" to see if a firewall is active and it's loaded
ruleset.
--David
KI6ZHD
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
On 04/03/2022 06:25 AM, Komkit Listisard via
44Net wrote:
Marius,
Yes I did DMZ but 192.168.80.196 (eth0) instead of 191 (wlan0).
73, Kit
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net On 4/3/2022 9:18 AM, Marius Petrescu via 44Net
wrote:
Hi Kit,
It seems you se a router to connect the Pi to the internet. Do you have a protocol 4
forward or a DMZ to 192.168.80.191 set up in that router?
Marius, YO2LOJ
> On 03/04/2022 16:03, Komkit Listisard via 44Net wrote:
> Folks, I have my Gateway up and running for weeks. Yesterday power went out and
after that my Gateway stopped working. Burn new image and starting it all over again, no
cigar.
>
> Swapped new Raspberry Pi, replaced power supply. Internet connections anywhere in
the house are working normally.
>
> Tried running ampr-ripd again but never got past "Waiting for RIPv2
broadcasts..."
>
> What should I be looking into next?
>
> root@44GW:/home/r0ot# ampr-ripd -v -d -i tunl0
> Using metric 0 for routes.
> Using TCP window 840 for routes.
> Using routing table 'main' (254).
> Loaded 733 entries from /var/lib/ampr-ripd/encap.txt
> Max list size: 1000 entries
> Detected tunnel interface address: 44.60.73.14
> Interface detected: lo, IP: 127.0.0.1
> Interface detected: eth0, IP: 192.168.80.196
> Interface detected: eth1, IP: 44.60.73.1
> Interface detected: wlan0, IP: 192.168.80.191
> Interface detected: tunl0, IP: 44.60.73.14
> Assigned tunnel interface index: 5
> Local IPs:
> 127.0.0.1
> 192.168.80.196
> 44.60.73.1
> 192.168.80.191
> 44.60.73.14
> Using gateway 192.168.80.1 for direct 44net endpoints via interface eth0.
> Setting routes (733).
> Creating multicast RIP UDP listening socket.
> Setting up multicast interface.
> Waiting for RIPv2 broadcasts...
>
> ---
>
> 73, Kit
>
> _________________________________________
> 44Net mailing list
> 44Net(a)mailman.ampr.org
> https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net