Firewall logged entry puzzling

I see this over and over despite what I thought was an atempt, by me, to allow UDP port 514

Stealth Mode connection attempt to UDP 10.0.1.2:514 from 10.0.1.1:514


isn't 514 syslog ?? What is the connection attempt? How can I allow it with a rule? or should I forget about it?

thanks

Macbook Pro, Mac OS X (10.4.8)

Posted on Oct 19, 2006 3:49 PM

Reply
15 replies

Oct 20, 2006 3:44 AM in response to BDAqua

thanks.
I have, in place, a rule I called Syslog. I just checked it, UDP 514 is allowed. This doesn't seem to work though ... vis-a-vis the Mac's Firewall rules.

I saw 'Remote logIN' but not "Remote Logging" for choices in preferences|services ... and the former is the SSH, different than the Syslog stuff.

Since 10....1 and 10...2 are bot 'me' , I don't understand why I can't set a Firewall rule on the mac to allow 514 ....

Oct 20, 2006 8:24 AM in response to Anthony Cunningham

well ... it appears the 514 entry is down in there. Mind you, I am not sure how to handle en0 versus en1 ... but, here is the list:
01000 allow ip from any to any via lo*
01003 check-state
01005 allow ip from any to any frag
01006 allow icmp from any to any icmptypes 0,3,4,11,12,13,14
03000 allow udp from any 67-68 to any dst-port 67-68 via en0
03001 allow udp from any to 255.255.255.255 dst-port 67-68 via en0
03002 reject log logamount 65535 ip from any to any ipoptions ssrr,lsrr via en0
03003 allow udp from any 123 to any dst-port 1024-65535,123 via en0
03004 allow udp from any 5353 to any dst-port 5353 via en0
03005 allow icmp from any to any via en0
03006 allow tcp from any 20-21 to any dst-port 1024-65535 in via en0
03007 allow udp from any to any dst-port 53 out via en0 keep-state
05000 allow udp from any 67-68 to any dst-port 67-68 via en1
05001 allow udp from any to 255.255.255.255 dst-port 67-68 via en1
05002 reject log logamount 65535 ip from any to any ipoptions ssrr,lsrr via en1
05003 allow udp from any 123 to any dst-port 1024-65535,123 via en1
05004 allow udp from any 5353 to any dst-port 5353 via en1
05005 allow icmp from any to any via en1
05006 allow tcp from any 20-21 to any dst-port 1024-65535 in via en1
05007 allow udp from any to any dst-port 53 out via en1 keep-state
05008 allow udp from any 514 to any dst-port 514 out via en1 keep-state
53008 allow ip from any to any out via en0 keep-state
53009 deny log logamount 65535 ip from any to any in via en0
55009 allow ip from any to any out via en1 keep-state
55010 deny log logamount 65535 ip from any to any in via en1
65535 allow ip from any to any


Macbook Pro Mac OS X (10.4.8)

Oct 21, 2006 6:27 PM in response to Running Shoes

Running firewall in 'stealth mode' has been known to cause more trouble than it's worth sometimes.
Do things work properly when Stealth is turned off?
Do things work, even though this (514) is being logged?

If you're behind a hardware item like a router, (your IP address is 192.x.x.x or 10.1.x.x, as provided by the router)...you have less to worry about than someone who connects the Mac directly to cable/DSL modem...

I'd disable stealth for a while and see how things go.
Or, leave it enabled and ignore the logs for a while...see if things work

Oct 22, 2006 6:27 PM in response to Running Shoes

OK.
So somewhere in the rules, there appears to still be a reason that you set to block 514 (deny).

This "deny" msg you're seeing seems to be in your Tigr logs, so it's your Tiger FW, or some other firewall on your Mac.

Your Airport BaseStation is likely 10.0.1.1...your mac is 1-dot-2.
en1 is the wireless ethernet (wifi).
And we don't really know why you'd run Stealth inside a modem, inside an AEBS with NAT running. Only you know why you'd want to run stealth.

If you leave that '514' blocked, and everything's working, ignore it and get back to work.
If something is NOT working in your daily functions, then start worrying about why 514 is being denied.

Oct 22, 2006 8:02 PM in response to Rick Van Vliet

OK.
So somewhere in the rules, there appears to still be
a reason that you set to block 514 (deny).

Well, you led me to take a look at ordering of the filter lines. I'd D/L'd "Flying Buttress" FW as indirectly mentioned within a previous posters reply, upthread
http://order.kagi.com/?5MG

This showed me the 'Deny' on several items and I could see 514 got blocked near the top of the listed filters... I read that the first match and the rule-search stopped ... so that ansered my query ...


And we don't really know why you'd run Stealth.....


Indeed. And I had to laugh at that reply ... shame on me ... but I believe it started when I tried Shields Up (GRC) and got all Stealth except replying to their Ping. Couldn't understand it since I hadn't seen log entries in the DSL Modem's log nor attempts inbound to me in the ipfw.log.

So I set myself to Stealth to see if that was the problem.

New to the Mac ... a convert recently from the ugliness of the Windows system ... not an excuse, just an explanation of why I am swimming around trying to get some way on.

Oct 23, 2006 4:55 AM in response to Running Shoes

Glad to hear that you found it!

And don't kick yourself about being a recent convert.
I still use Windows for 99% of the things I do.
My macMini is just "nice to have" when I need to see what mac users have done to get themselves in trouble.

Network stuff is network stuff...that's what I do.
And the minor differences between mac & PC's as far as TCP/IP, firewalls, etc...well, it's just cosmetic.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Firewall logged entry puzzling

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.