#1195 closed request (pending)

ticket 1185 - additional info

Reported by: furry13@… Owned by: panda@…
Priority: tbd Milestone: ietf-100
Component: nat64 Keywords:
Cc: Clemens, Schrimpe, <csch@…> My Current Location:
My MAC Address: My OS:

Description

So, I'm in the plenary room now (the same one where 6man was).
With the default router lifetime set now to 9000 I do not expect to
lost the default gateway. however my Wireshark does not show me any
multicast ("to all nodes, ff02::1) RAs for the last 9 mins.
And I assume you have not turned on unicast solisited RAs yet, so I'd
say I should be seeing them, right? I've just re-connect my other
device to make sure it sends an RS...

Ifconfig output:
furry@Wintermute:~>ifconfig en0
en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
    ether 98:01:a7:b8:74:ad
    inet6 fe80::142a:14cd:27d:4bf0%en0 prefixlen 64 secured scopeid 0x4
    inet6 2001:67c:370:1998:92:df1b:7132:26fb prefixlen 64 autoconf secured
    inet6 2001:67c:370:1998:cd4:e8e1:d98e:2633 prefixlen 64 autoconf temporary
    nd6 options=201<PERFORMNUD,DAD>
    media: autoselect
    status: active

BSSID: fc:5b:39:53:d5:ec

I wonder what does the AP think about my device re: converting mcast to unicast?

-- 
SY, Jen Linkova aka Furry

Change history (4)

comment:1 Changed 10 months ago by llynch@…

Cc: If you have additional input on this issue please update the ticket if see new issues open tickets. Also see: https://tickets.meeting.ietf.org/wiki/nat64 for a list of known issues! Thanks - added
Owner: changed from < default > to panda@…
Status: newassigned

If you have additional input on this issue please update the ticket,
if you see new issues please open additional tickets.

Also see: https://tickets.meeting.ietf.org/wiki/nat64
for a list of known issues!

Thanks -

comment:2 in reply to:  2 ; Changed 10 months ago by furry13@…

hmmm...just got two multicast packets so maybe the issue disappeared ;(

On Wed, Nov 15, 2017 at 8:55 PM, IETF Tickets/NOC
<tickets@meeting.ietf.org> wrote:
> #1195: ticket 1185 - additional info
> ----------------------------+-----------------------------------
>       Reporter:  furry13@…  |                Owner:  < default >
>           Type:  request    |               Status:  new
>       Priority:  tbd        |            Milestone:  ietf-100
>      Component:  incoming   |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+-----------------------------------
>  {{{
>  So, I'm in the plenary room now (the same one where 6man was).
>  With the default router lifetime set now to 9000 I do not expect to
>  lost the default gateway. however my Wireshark does not show me any
>  multicast ("to all nodes, ff02::1) RAs for the last 9 mins.
>  And I assume you have not turned on unicast solisited RAs yet, so I'd
>  say I should be seeing them, right? I've just re-connect my other
>  device to make sure it sends an RS...
>
>  Ifconfig output:
>  furry@Wintermute:~>ifconfig en0
>  en0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu
>  1500
>      ether 98:01:a7:b8:74:ad
>      inet6 fe80::142a:14cd:27d:4bf0%en0 prefixlen 64 secured scopeid 0x4
>      inet6 2001:67c:370:1998:92:df1b:7132:26fb prefixlen 64 autoconf
>  secured
>      inet6 2001:67c:370:1998:cd4:e8e1:d98e:2633 prefixlen 64 autoconf
>  temporary
>      nd6 options=201<PERFORMNUD,DAD>
>      media: autoselect
>      status: active
>
>  BSSID: fc:5b:39:53:d5:ec
>
>  I wonder what does the AP think about my device re: converting mcast to
>  unicast?
>
>  --
>  SY, Jen Linkova aka Furry
>  }}}
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1195>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages



-- 
SY, Jen Linkova aka Furry

comment:3 Changed 10 months ago by llynch@…

Cc: Clemens Schrimpe <csch@…> added; If you have additional input on this issue please update the ticket if see new issues open tickets. Also see: https://tickets.meeting.ietf.org/wiki/nat64 for a list of known issues! Thanks - removed
Component: incomingnat64

comment:4 Changed 10 months ago by jim@…

Resolution: pending
Status: assignedclosed

Closing this as 1185 is now closed. The issue has been narrowed down to a Cisco misbehavior and is being worked by Cisco.

Note: See TracTickets for help on using tickets.