3 Apr
2022
3 Apr
'22
9:25 a.m.
Marius,
Yes I did DMZ but 192.168.80.196 (eth0) instead of 191 (wlan0).
73, Kit
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