Hoi,

Linux CP supports  ARP, IPv4 and IPv6. ISIS uses its its own ethertype, as
do other protocols (like LLDP for example). Those will not be punted into
the TAP by the plugin (and it's difficult to uniquely identify the ethernet
frames that should be punted as compared to being handled entirely in the
dataplane).

groet,
Pim


On Mon, Jan 23, 2023 at 4:36 PM <agv...@gmail.com> wrote:

> Dear VPP community,
>
> I'm trying to set up IS-IS neighborship with node running VPP22.10 + LCP
> plugin + FRR as control plane software, with no results.
>
> What I can see, looks like VPP does not pass IIH packet between network
> and TAP interface, both directions.
> On node running VPP, when tcpdumping host TAP interface I see outgoing
> IS-IS IIHs:
> 15:12:27.195439 3c:ec:ef:5f:77:8f > 09:00:2b:00:00:05, 802.3, length 1500:
> LLC, dsap OSI (0xfe) Individual, ssap OSI (0xfe) Command, ctrl 0x03: OSI
> NLPID IS-IS (0x83): p2p IIH, src-id 0000.0000.0001, length 1497
> They are not appears on opposite node (it runs frr/isisd without VPP).
> Only outgoing IIH packets are seen.
> 15:29:13.192912 3c:ec:ef:5f:78:7a > 09:00:2b:00:00:05, 802.3, length 1500:
> LLC, dsap OSI (0xfe) Individual, ssap OSI (0xfe) Command, ctrl 0x03: OSI
> NLPID IS-IS (0x83): p2p IIH, src-id 0000.0000.0002, length 1497
> 15:29:15.942959 3c:ec:ef:5f:78:7a > 09:00:2b:00:00:05, 802.3, length 1500:
> LLC, dsap OSI (0xfe) Individual, ssap OSI (0xfe) Command, ctrl 0x03: OSI
> NLPID IS-IS (0x83): p2p IIH, src-id 0000.0000.0002, length 1497
>
> Meanwhile, IP connectivity between the nodes exist. Here you can see ICMP
> exchane, as we can see it on TAP interface of VPP host
> 15:24:15.169021 3c:ec:ef:5f:77:8f > 3c:ec:ef:5f:78:7a, ethertype IPv4
> (0x0800), length 98: 10.114.1.1 > 10.114.1.100: ICMP echo request, id
> 144, seq 12, length 64
> 15:24:15.169275 3c:ec:ef:5f:78:7a > 3c:ec:ef:5f:77:8f, ethertype IPv4
> (0x0800), length 98: 10.114.1.100 > 10.114.1.1: ICMP echo reply, id 144,
> seq 12, length 64
> 15:24:15.329025 3c:ec:ef:5f:77:8f > 3c:ec:ef:5f:78:7a, ethertype IPv4
> (0x0800), length 98: 10.114.1.1 > 10.114.1.100: ICMP echo request, id
> 122, seq 61503, length 64
> 15:24:15.329304 3c:ec:ef:5f:78:7a > 3c:ec:ef:5f:77:8f, ethertype IPv4
> (0x0800), length 98: 10.114.1.100 > 10.114.1.1: ICMP echo reply, id 122,
> seq 61503, length 64
>
> OSPF neighborship also can be established, so problem is IS-IS related.
> tn3# show ipv6 ospf6 neighbor
> Neighbor ID     Pri    DeadTime    State/IfState         Duration
> I/F[State]
> 20.20.20.1        1    00:00:38     Full/DR              00:07:21
> Ten0.1914[BDR]
> tn3#
>
> What I found, show node counters says osi-input unknown osi protocol
> increasing.
>
>    Count                  Node
> Reason               Severity
>         84             lldp-input            lldp packets received on
> disabled i   error
>       4364             dpdk-input                          no
> error                error
>         20             arp-reply                       ARP replies
> sent            info
>          9             arp-reply             IP4 source address matches
> local in   error
>         19             arp-reply             ARP request IP4 source
> address lear   info
>         43            arp-disabled                       ARP
> Disabled              error
>       1252             osi-input                     unknown osi
> protocol          error
>          4             ip6-input                    ip6 source lookup
> miss         error
>         19        ip6-local-hop-by-hop       Unknown protocol ip6 local
> h-b-h pa   error
>         10             ip4-local                    ip4 source lookup
> miss         error
>          4           ip6-icmp-input          neighbor solicitations for
> unknown    error
>          4           ip6-icmp-input              neighbor advertisements
> sent      info
>        106           ip6-icmp-input           neighbor discovery not
> configured    error
>         42             snap-input                 unknown oui/snap
> protocol        error
>         49           ethernet-input                 unknown ethernet
> type          error
>     623375           ethernet-input                      unknown
> vlan              error
>          1           ethernet-input                   subinterface
> down            error
>
> On the other hand, I can see IS-IS protocol in src/vnet/osi/osi.h
>
>
> #define foreach_osi_protocol                    \
>   _ (null, 0x0)                                 \
>   _ (x_29, 0x01)                                \
>   _ (x_633, 0x03)                               \
>   _ (q_931, 0x08)                               \
>   _ (q_933, 0x08)                               \
>   _ (q_2931, 0x09)                              \
>   _ (q_2119, 0x0c)                              \
>   _ (snap, 0x80)                                \
>   _ (clnp, 0x81)                                \
>   _ (esis, 0x82)                                \
>   _ (isis, 0x83)                                \
>   _ (idrp, 0x85)                                \
>   _ (x25_esis, 0x8a)                            \
>   _ (iso10030, 0x8c)                            \
>   _ (iso11577, 0x8d)                            \
>   _ (ip6, 0x8e)                                 \
>   _ (compressed, 0xb0)                          \
>   _ (sndcf, 0xc1)                               \
>   _ (ip4, 0xcc)                                 \
>   _ (ppp, 0xcf)
>
>
>
> So protocol should not be "unknown".
>
> Any ideas where I need to look at to fix the issue with IS-IS?
>
>
>
> 
>
>

-- 
Pim van Pelt <p...@ipng.nl>
PBVP1-RIPE - http://www.ipng.nl/
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22489): https://lists.fd.io/g/vpp-dev/message/22489
Mute This Topic: https://lists.fd.io/mt/96476162/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to