Your second option is closer. I want to receive syslog messages over the WAN port and log them locally on the Mango.
This is a double router situation.
Router 1 is the ISP router (LAN network: 192.168.252.0/24). It is publishing syslog messages. I am interested in capturing the published ISP connection messages in a log.
Router 2 is a Mango. Its WAN port is connected to a LAN port on the ISP router with static IP address 192.168.252.210 which is the ISP router’s syslog destination. Using the standard syslog UDP port 514. The Mango’s LAN network is 192.168.251.0/24 and the Mango is 192.168.251.1.
I am running rsyslog daemon on the Mango and recording syslog traffic to an attached USB device.
I opened port 514 on the Mango to allow traffic in using the gl-iNet UI.
Everything is set up. Rsyslog captures and records all the Mango messages. If I use netcat to send a message to the Mango router from a Mango LAN port, it is recorded. If I send a message from an ISP LAN port to the Mango’s WAN address, it is NOT recorded. I have verified that the messages are NOT received by using a netcat listener instead of rsyslog.
Rsyslog, by default listens on all interfaces. I tried using netcat, specifying the IP bind address for the Mango’s WAN port, but no difference.
I also ran tcpdump on the Mango and it does show receipt of the message on the WAN port, but I cannot tell if it’s getting through the firewall.
Attached is an IPTABLES dump and a copy of the UCI configuration. One particular section:
suggests that port 514 is open into the Mango.
Just looks like traffic isn’t getting into the Mango.
BTW… I’m also running an OpenVPN server on the Mango (hence the extra interfaces) with a port forwarding rule on the ISP router to forward its traffic to the Mango (same IP address as syslog) and that is working just fine.
Just trying to figure out what is happening here. Or what the next steps in troubleshooting should be.
Club Mango Info.txt.zip (8.7 KB)