Curiouser

Common internet noise. You cluttering up your logfile with noise.

I know it is common, and I am not worried about it, just curious.

Am I being pinged by the office of the president of University of California?

I don't know your exact log format, but isn't the "80" the tcp.dst-port? Someone might have assumed your computer runs a webserver. For whatever reason.

Rick, you post something without context, and incompletely researched, and you expect positive results?

Not enough context. 169.229.252.77 is a web/mail/index server at UC Bezerkeley - do you have some Cal alums that might be checking their mail, seeing if their grades are in or some other reason to be connecting to the Physics department there? Ask them.

A poorly explained log snippet is otherwise just a waste of your time. As a very wild guess, you've got the firewall set aggressively, and this MIGHT be a delayed response (notice the flags, port and sequence numbers). But with a complete lack of details and context - who knows.

and you're using some shiny crappy toy instead of tools that are found on nearly all competently installed *nix boxes, and as usual - the crap tool is providing misleading information. "UCSD-NET-169-228" is a parent assignment, and not the final (which is UC Berkeley ISTDATA) - though a simple host lookup would be even more informative.

Old guy

This is not actually a *nix newsgroup - my sample happens to be from a Win XP firewall And the "firewall" provides no context. FYI, I am NOT running any service/server from this location (behind router w. all ports closed that can be closed)

I accept that it may be a "waste" of my time, and I thank you for responding to my curiousity.

I think I see what you mean by a "delayed response" and maybe that is just that.

Thanks,

Rick

-Told my grandson i was 65 - he says, "Did you start at one?" ;-)

Do yourself a favor and get a real firewall. If this is a windoze "firewall" it's almost certainly one of the brain-dead variety. We see posts where the "firewall" is screaming about attacks, but when you look at the data, it's a slow response that the firewall assumed had gone missing and forgot about it.

No - it looks more like a client behind your firewall, connecting to

Old guy