I am using Kiwi syslog and a Pix, it's an inherent objectity of the Pix to block my internal syslog messages (?) and I am trying to get them from my Pix to my syslog server.
Kiwi help docs, even make a statement that the Pix blocks connection to the syslog server. I know some have accomplished this task based on other threads on the same discussion. What is the trick to get this up and running??
Here is my Pix command statment, it takes this syntax without a specification for the type of protocol used UDP/TCP but once I try and force a protocal to the syslog server it tells me I am out of range, even if I try and force a specific port for offloading the syslog messages. Oh and I am using the pix default Local4 pipe. IPs are made up for discussion.
pix# logging host inside 192.1.10.234
the pix takes that but I don't see anything on the syslog server at 192.1.10.234 runing KiWi
now if i force UDP
pix# logging host inside 192.1.10.34 UDP
I get an error on the pix "port out of range: 1025-65535
ok so I figure pix is blocking ports. So I try and force UDP to use port 5514. Not clear on the syntax so I try
pix# logging host inside 192.1.10.234:5514 UDP
bad syntax all together, syntax in documentation suggests protocol/port
so,
pix# logging host inside 192.1.10.34 UDP 5514
That produces the same out of range error. Hmmmm? Any PixGrus out there figured out my brain hole in the understanding of syslog. I do know 2 things about it. It can use TCP or UDP. and there are pipes and levels. Ok maybe three things, what am I missing?
TIA




Reply With Quote