Opened 2 years ago

Closed 2 years ago

Last modified 21 months ago

#1137 closed request (not broken)

port scan report on "ietf" SSID LAN

Reported by: dave@… Owned by: < default >
Priority: tbd Milestone: ietf-099
Component: incoming Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Hi NOC folks,

In case you care, I received the attached notification while on SSID
"ietf" with my address being the following:

$ host 31.133.140.203
203.140.133.31.in-addr.arpa domain name pointer dhcp-8ccb.meeting.ietf.org.

Thanks,
Dave

-- 
dave@plonka.us  http://www.cs.wisc.edu/~plonka/

Screen Shot 2017-07-19 at 12.31.24 PM.png

Attachments (1)

Screen Shot 2017-07-19 at 12.31.24 PM.png (60.5 KB) - added by dave@… 2 years ago.
Added by email2trac

Download all attachments as: .zip

Change history (5)

Changed 2 years ago by dave@…

Added by email2trac

comment:1 Changed 2 years ago by jim@…

Resolution: not broken
Status: newclosed

Dave,

Thanks for the heads up, but as we basically run a completely open net with no explicit AUP this is just part of the experience. The only real oddness is that it actually came from within rather than from the greater Internet.

I'm going to resolve this as no-action-required, but feel free to reply if you disagree!

  • Jim

comment:2 in reply to:  3 Changed 2 years ago by dave@…

Resolution: not broken
Status: closedreopened
Cool. I'll see if it happens ever on nat64. ;)
On Jul 19, 2017 1:18 PM, "IETF Tickets/NOC" <tickets@meeting.ietf.org>
wrote:

> #1137: port scan report on "ietf" SSID LAN
> ---------------------------+-----------------------------------
>       Reporter:  dave@…    |                Owner:  < default >
>           Type:  request   |               Status:  closed
>       Priority:  tbd       |            Milestone:  ietf-99
>      Component:  incoming  |           Resolution:  not broken
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+-----------------------------------
> Changes (by jim@…):
>
>  * status:  new => closed
>  * resolution:   => not broken
>
>
> Comment:
>
>  Dave,
>      Thanks for the heads up,  but as we basically run a completely open
>  net with no explicit AUP this is just part of the experience. The only
>  real oddness is that it actually came from within rather than from the
>  greater Internet.
>
>      I'm going to resolve this as no-action-required, but feel free to
>  reply if you disagree!
>
>      - Jim
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1137#comment:1>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:3 Changed 2 years ago by jim@…

Resolution: not broken
Status: reopenedclosed

Enjoy!

Re-resolving.

comment:4 Changed 21 months ago by Rick Alfvin

Milestone: ietf-99ietf-099

Milestone renamed

Note: See TracTickets for help on using tickets.