- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I plan to have an application running on a remote system
send UDP syslog messages (default port 514) to my verizon IP where
I expect the MI424-WR Firmware Version: 4.0.16.1.56.0.10.14.4 router to
forward them to host "dahost" which is running a syslog daemon (specifically solarWinds kiwi)
firewall settings: General : typical Security (medium)
Access Control : -none-
forwarding: includes
[x] dahost 192.168.1.6 : Application UDP 514 -> 514 : all broadband devices : Active
Syslog message from another (Mac lion ) host (192.168.1.2 ) from within the LAN
do get to dahost using
syslog -s -r 192.168.1.6 -l 4 "sent trhough LAN -l 4"
Kiwi reports:
2012-04-02 12:43:48 Kernel.Warning Mac.germans syslog[59036]: sent trhough LAN -l 4
However from that same host using the public addres of the router 98.zzz.yyy.xxx
syslog -s -r 98.zzz.yyy.xxx -l 4 "sent from 98.zzz.yyy.xxx -l 4"
do not get to syslogd.
ping 98.zzz.yyy.xxx
PING 98.zzz.yyy.xxx (98.zzz.yyy.xxx): 56 data bytes
64 bytes from 98.zzz.yyy.xxx: icmp_seq=0 ttl=64 time=0.946 ms
traceroute 98.zzz.yyy.xxx
traceroute to 998.zzz.yyy.xxx (98.zzz.yyyxxx), 64 hops max, 52 byte packets
1 rtr (98.zzz.yyy.xxx) 4.168 ms 3.863 ms 1.531 ms
Intestering specifing -d -q 9 ( debug mode , issue 9 queries, ) SOMETIMES results in
1 rtr (98.zzz.yyyxxx) 60 bytes to 192.168.1.2 4.395 ms 3.978 ms 4.048 ms 0.776 ms 0.742 ms 0.718 ms * 3.822 ms 1.510 ms
and sometimes
traceroute -q9 -d 98.zzz.yyyxxx
traceroute to 98.zzz.yyy.xxx (98.zzz.yyy.xxx), 64 hops max, 52 byte packets
1 rtr (98.zzz.yyy.xxx) 4.665 ms 1.401 ms 0.789 ms 0.760 ms 0.877 ms 2.942 ms * 3.710 ms 1.832 ms
also interesting
dig +short rtr
192.168.1.1
98.zzz.yyy.xxx.
Web browser to 98.zzz.yyy.xxx is able to MI424-WR remote contifuration administration
Any thoughts or suggestions would be appreciated.
Private message me if you want rtr's real address .