Opened 7 years ago

Closed 7 years ago

Last modified 3 years ago

#644 closed request (fixed)

Hotel wired network lost IPv4?

Reported by: brian.e.carpenter@… Owned by: chelliot@…
Priority: tbd Milestone: ietf-088
Component: incoming Keywords:
Cc: My Current Location:
My MAC Address: My OS:



Right now (08:34 PST) I can't get to IPv4 on wired network from room 1405.
IPv6 seems to be up, and the hotel wireless is up.

C:\windows\system32>ping -4

Pinging [] with 32 bytes of data:
Request timed out.
Reply from Destination net unreachable.
Reply from Destination net unreachable.
Request timed out.

Ping statistics for
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

   Brian Carpenter

Change history (8)

comment:1 Changed 7 years ago by llynch@…

Brian -

The process for this week is for any in-room issues to initially be handled by the standard hotel tech support (which is provided by Roomlinx). If there's an infrastructure issue or something else beyond 1st level support, they will escalate to the IETF NOC via a local phone which rotates through VeriLAN staff.

  • Lucy

comment:2 Changed 7 years ago by cdoyle@…

I'll contact the local support. That unreachable message is coming from a router not on our subnet.

comment:3 Changed 7 years ago by Bill Fenner

Both this ticket and #643 seem to be explained by a rogue DHCP server in someone's room, serving

comment:4 Changed 7 years ago by anonymous

Based on this:
Device or Node
First Seen
Last Seen
Switch Port [ 6 ] (YVRRV-EDGE-02)
Nov 2 22:20 2013
Nov 3 18:25 2013

And a response from RoomLinx?:

Edge -02 port 6 shows as "Above drop ceiling - Room 522"

Joseph Robinson / Technical Support Supervisor

This complicates things a touch. I'll reach out to AMS and see if we can determine who's in that room, if they are with IETF, etc...


comment:5 Changed 7 years ago by cdoyle@…

Chelliot is going to be following up on this with AMS right now.

comment:6 Changed 7 years ago by chelliot@…

Owner: changed from llynch@… to chelliot@…
Status: newaccepted

comment:7 Changed 7 years ago by chelliot@…

Resolution: fixed
Status: acceptedclosed


We believe the same device causing you issues was seen on the wireless subnet. We took it off the network and it has not reappeared. We have alerts set if it does.

I'm going to close this ticket. Please feel free to reopen it if the issue appears again.


comment:8 Changed 3 years ago by Rick Alfvin

Milestone: ietf-88ietf-088

Milestone renamed

Note: See TracTickets for help on using tickets.