Is this anything

[jz]

http://www.vi2.com/maxForumFiles/fwlog2.jpg

I don't recognize the address. At first I thought it might be a port scan, but they scan a variety of ports, not just one.

Also, isn't there a log analyzer for Tiny Firewall? I remember hearing about somewhere.

[blebs]

I'm uncertain on this one. It could be a scan from your ISP, but why those ports? You didn't have the firewall locked down and your ISP was in the process of trying to renew your lease did you?
One big ? mark for me, sorry. :(

[Croc]

Question....

Is anything unusual happening after the firewall blocked to those ports?

Answer = No?

The event is over and from what I can see the attempt was only small if indeed it was an attempt.
Large numbers of attacks over a wide range of ports during a short space of time I would be concerned about if there was a change in the way my system was operating (subsequent outbound requests from the firewall), but until then just thank your firewall for doing it's job and get on with what you were doing before you found out what was on the log.

Croc.

[Matt615]

Maybe im wrong but looks to me like DHCP. When my firewall logged my DHCP server the adress started with a 10 like that and it was on UDP port 68 also.

[rmrucker]

I agree. Those look like DHCP responses. The port 67 is a giveaway. It is likely the server responding back to DHCP requests. Since they are usually sent as "Broadcast" UDP packets to 255.255.255.255, Tiny must be picking those up.

Since they are from a 10.x.x.x address, I would guess you are on a cable connection. The 10.x.x.x address is likely the local address of your DHCP server.

I would think there is nothing to worry about.

[hoov]

Agree with Matt615 and Rmrucker in that I see the same dhcp hits on my netgear router to port 68 with a 10.x.x.x address.