Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-03 Thread Thakur, Anagha
Yes, you are right. The show error counters.
vpp# show errors
   Count  Node  Reason  
 Severity
34dhcp-client-process DHCP discover packets sent
   error

Count  Node  Reason   
Severity
   357dhcp-client-process DHCP discover packets sent
   error

Do you know how to read in detail about this errors?
Can I read something from these files?
ls l /var/run/vpp/
api.sockcli.sockmemif.sock  stats.sock

I captured fresh eventlogs and pcap trace again.

Best Regards,
Anagha


From: vpp-dev@lists.fd.io  On Behalf Of Dave Barach via 
lists.fd.io
Sent: Friday, March 3, 2023 1:58 AM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02

The dhcp client has a number of “show error” counters. Do you see any of the 
error counters increasing?

The packet trace I’d like to see would be from “trace add  1000” … 
“show trace max 1000” or similar. The pcap trace implies that the dhcp offer 
packets are dropped, but we need to work out why…

D.

From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> 
mailto:vpp-dev@lists.fd.io>> on behalf of hemant via 
lists.fdio mailto:hemant=mnkcg@lists.fd.io>>
Date: Thursday, March 2, 2023 at 7:13 PM
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02
There is something in the DHCP OFFER the client does not like and moves back to 
new DHCP session. Or the DHCP OFFER never made it to the client.

Hemant


From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> 
mailto:vpp-dev@lists.fd.io>> On Behalf Of Thakur, Anagha
Sent: Thursday, March 02, 2023 4:02 PM
To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02

I do see DHCP Offer in the packet tracer from the Server which I have set up on 
the other side.
But VPP does not send any DHCP Request out, instead I always see that VPP 
continuously keeps sending DHCP Discovery.

I have attached tx and rx pcap trace in my prevous email.

Best Regards,
Anagha


From: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> 
mailto:vpp-dev@lists.fd.io>> on behalf of Dave Barach via 
lists.fd.io mailto:vpp=barachs@lists.fd.io>>
Sent: Thursday, 2 March 2023, 19:15
To: vpp-dev@lists.fd.io<mailto:vpp-...@listsfd.io> 
mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02

Do you see a response to the DHCP Discover packets?

What does the vpp packet tracer show?
Thanks... Dave

On Mar 2, 2023, at 7:03 AM, Thakur, Anagha 
mailto:anagha.tha...@siemens.com>> wrote:


Hello,

I am testing DHCP client feature from VPP stack (v22.02) onto our system.

My setup is: I run k8s cluster on x86 system in which I have a pod which uses 
VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There 
are two physical interfaces which we use in VPP, one of them is with static IP 
(eno2) and other one with as DHCP client (eno1).

I expect this interface shall act as a DHCP Client and we run a DHCP server on 
the other end of the system. But unfortunately, the VPP does not send any DHCP 
REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a DHCP 
Offer.
But VPP does not send further DHCP REQUEST to the DHCP server. I do not expect 
that it is a problem from lower layer and it should be an issue from VPP side. 
Please let me know if I need to enable any extra plugin other than the ones in 
the attached file.
I attached pcap file recorded vpp trace of tx and rx.


Our versions are currently as follows:
-> DPDK 22.03
-> VPP 22.02
-> VPP library 22.02

Version Information attached.


plugins

{

  path /opt /vpp/lib/vpp_plugins

  plugin default { disable }

  plugin dpdk_plugin.so { enable }

  plugin memif_plugin.so { enable }

  plugin ping_plugin.so { enable }

  plugin router_plugin.so { enable }

  plugin upffp_plugin.so { enable }

  plugin dhcp_plugin.so { enable }

}


Commands used:

set intfc VPP-N6-0 state up

set int mac address eno1 00:11:22:33:44:66
set dhcp client intfc eno1

sh dhcp client verbose

[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)

  retry-count:346, next-xmt:2416.87

broadcast adjacency:20

sh log

2023/02/27 16:11:03:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:03:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)

retry-count:439, next-xmt:255827.12

broadcast ad

Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread Dave Barach
The dhcp client has a number of “show error” counters. Do you see any of the error counters increasing? The packet trace I’d like to see would be from “trace add  1000” … “show trace max 1000” or similar. The pcap trace implies that the dhcp offer packets are dropped, but we need to work out why… D.  From: vpp-dev@lists.fd.io  on behalf of hemant via lists.fdio Date: Thursday, March 2, 2023 at 7:13 PMTo: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02There is something in the DHCP OFFER the client does not like and moves back to new DHCP session. Or the DHCP OFFER never made it to the client. Hemant  From: vpp-dev@lists.fd.io  On Behalf Of Thakur, AnaghaSent: Thursday, March 02, 2023 4:02 PMTo: vpp-dev@lists.fd.ioSubject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02 I do see DHCP Offer in the packet tracer from the Server which I have set up on the other side.But VPP does not send any DHCP Request out, instead I always see that VPP continuously keeps sending DHCP Discovery. I have attached tx and rx pcap trace in my prevous email. Best Regards,Anagha From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> on behalf of Dave Barach via lists.fd.io <vpp=barachs@lists.fd.io>Sent: Thursday, 2 March 2023, 19:15To: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io>Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02Do you see a response to the DHCP Discover packets?   What does the vpp packet tracer show?Thanks... Dave On Mar 2, 2023, at 7:03 AM, Thakur, Anagha <anagha.tha...@siemens.com> wrote:  Hello, I am testing DHCP client feature from VPP stack (v22.02) onto our system. My setup is: I run k8s cluster on x86 system in which I have a pod which uses VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There are two physical interfaces which we use in VPP, one of them is with static IP (eno2) and other one with as DHCP client (eno1). I expect this interface shall act as a DHCP Client and we run a DHCP server on the other end of the system. But unfortunately, the VPP does not send any DHCP REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a DHCP Offer.But VPP does not send further DHCP REQUEST to the DHCP server. I do not expect that it is a problem from lower layer and it should be an issue from VPP side. Please let me know if I need to enable any extra plugin other than the ones in the attached file.I attached pcap file recorded vpp trace of tx and rx.  Our versions are currently as follows:-> DPDK 22.03-> VPP 22.02-> VPP library 22.02 Version Information attached. plugins{  path /opt /vpp/lib/vpp_plugins  plugin default { disable }  plugin dpdk_plugin.so { enable }  plugin memif_plugin.so { enable }  plugin ping_plugin.so { enable }  plugin router_plugin.so { enable }  plugin upffp_plugin.so { enable }  plugin dhcp_plugin.so { enable }}  Commands used:set intfc VPP-N6-0 state upset int mac address eno1 00:11:22:33:44:66set dhcp client intfc eno1sh dhcp client verbose[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)  retry-count:346, next-xmt:2416.87broadcast adjacency:20sh log2023/02/27 16:11:03:986 notice dhcp/client    sm active session 02023/02/27 16:11:03:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)retry-count:439, next-xmt:255827.12broadcast adjacency:112023/02/27 16:11:08:986 notice dhcp/client    sm active session 02023/02/27 16:11:08:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)retry-count:440, next-xmt:255832.12broadcast adjacency:112023/02/27 16:11:13:986 notice dhcp/client    sm active session 02023/02/27 16:11:13:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address  lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255837.12)  retry-count:441, next-xmt:255837.12broadcast adjacency:112023/02/27 16:11:18:986 notice dhcp/client    sm active session 02023/02/27 16:11:18:986 notice dhcp/client    send: type:discover bcast:1 [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no addresslease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)retry-count:442, next-xmt:255842.12  broadcast adjacency:11show interface addresseno2 (up):   L3 172.31.254.17/29eno1 (up):host-vpp1out (up):   L3 128.0.129.144/24local0 (dn):memif0/502 (up):  Thank you in advance. Best Regards,Anagha

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22657): https://lists.fd.io/g/vpp-dev/message/22657
Mute This Topic

Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread hemant via lists.fd.io
There is something in the DHCP OFFER the client does not like and moves back to 
new DHCP session. Or the DHCP OFFER never made it to the client.

 

Hemant

 

 

From: vpp-dev@lists.fd.io  On Behalf Of Thakur, Anagha
Sent: Thursday, March 02, 2023 4:02 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02

 

I do see DHCP Offer in the packet tracer from the Server which I have set up on 
the other side.

But VPP does not send any DHCP Request out, instead I always see that VPP 
continuously keeps sending DHCP Discovery.

 

I have attached tx and rx pcap trace in my prevous email.

 

Best Regards,

Anagha

 

  _  

From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> > on behalf of Dave Barach via lists.fd.io 
mailto:vpp=barachs@lists.fd.io> >
Sent: Thursday, 2 March 2023, 19:15
To: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>  mailto:vpp-dev@lists.fd.io> >
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02


Do you see a response to the DHCP Discover packets?  

 

What does the vpp packet tracer show?

Thanks... Dave





On Mar 2, 2023, at 7:03 AM, Thakur, Anagha mailto:anagha.tha...@siemens.com> > wrote:

 

 

Hello,

 

I am testing DHCP client feature from VPP stack (v22.02) onto our system.

 

My setup is: I run k8s cluster on x86 system in which I have a pod which uses 
VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There 
are two physical interfaces which we use in VPP, one of them is with static IP 
(eno2) and other one with as DHCP client (eno1).

 

I expect this interface shall act as a DHCP Client and we run a DHCP server on 
the other end of the system. But unfortunately, the VPP does not send any DHCP 
REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a DHCP 
Offer.

But VPP does not send further DHCP REQUEST to the DHCP server. I do not expect 
that it is a problem from lower layer and it should be an issue from VPP side. 
Please let me know if I need to enable any extra plugin other than the ones in 
the attached file.

I attached pcap file recorded vpp trace of tx and rx.

 

 

Our versions are currently as follows:

-> DPDK 22.03

-> VPP 22.02

-> VPP library 22.02

 

Version Information attached.

 

plugins

{

  path /opt /vpp/lib/vpp_plugins

  plugin default { disable }

  plugin dpdk_plugin.so { enable }

  plugin memif_plugin.so { enable }

  plugin ping_plugin.so { enable }

  plugin router_plugin.so { enable }

  plugin upffp_plugin.so { enable }

  plugin dhcp_plugin.so { enable }

}

 

 

Commands used:

set intfc VPP-N6-0 state up

set int mac address eno1 00:11:22:33:44:66

set dhcp client intfc eno1

sh dhcp client verbose

[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)

  retry-count:346, next-xmt:2416.87

broadcast adjacency:20

sh log

2023/02/27 16:11:03:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:03:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)

retry-count:439, next-xmt:255827.12

broadcast adjacency:11

2023/02/27 16:11:08:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:08:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)

retry-count:440, next-xmt:255832.12

broadcast adjacency:11

2023/02/27 16:11:13:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:13:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

  lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255837.12)

  retry-count:441, next-xmt:255837.12

broadcast adjacency:11

2023/02/27 16:11:18:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:18:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)

retry-count:442, next-xmt:255842.12

  broadcast adjacency:11

show interface address

eno2 (up):

   L3 172.31.254.17/29

eno1 (up):

host-vpp1out (up):

   L3 128.0.129.144/24

local0 (dn):

memif0/502 (up):

 

 

Thank you in advance.

 

Best Regards,

Anagha

 

 









 



smime.p7s
Description: S/MIME cryptographic signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22656): https://lists.fd.io/g/vpp-dev/message/22656
Mute This Topic: https://lists.fd.io/mt/97336867/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.

Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread Thakur, Anagha
I do see DHCP Offer in the packet tracer from the Server which I have set up on 
the other side.
But VPP does not send any DHCP Request out, instead I always see that VPP 
continuously keeps sending DHCP Discovery.

I have attached tx and rx pcap trace in my prevous email.

Best Regards,
Anagha


From: vpp-dev@lists.fd.io  on behalf of Dave Barach via 
lists.fd.io 
Sent: Thursday, 2 March 2023, 19:15
To: vpp-dev@lists.fd.io 
Subject: Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP 
v22.02

Do you see a response to the DHCP Discover packets?

What does the vpp packet tracer show?

Thanks... Dave

On Mar 2, 2023, at 7:03 AM, Thakur, Anagha  wrote:



Hello,

I am testing DHCP client feature from VPP stack (v22.02) onto our system.

My setup is: I run k8s cluster on x86 system in which I have a pod which uses 
VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There 
are two physical interfaces which we use in VPP, one of them is with static IP 
(eno2) and other one with as DHCP client (eno1).

I expect this interface shall act as a DHCP Client and we run a DHCP server on 
the other end of the system. But unfortunately, the VPP does not send any DHCP 
REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a DHCP 
Offer.
But VPP does not send further DHCP REQUEST to the DHCP server. I do not expect 
that it is a problem from lower layer and it should be an issue from VPP side. 
Please let me know if I need to enable any extra plugin other than the ones in 
the attached file.
I attached pcap file recorded vpp trace of tx and rx.


Our versions are currently as follows:
-> DPDK 22.03
-> VPP 22.02
-> VPP library 22.02

Version Information attached.


plugins

{

  path /opt /vpp/lib/vpp_plugins

  plugin default { disable }

  plugin dpdk_plugin.so { enable }

  plugin memif_plugin.so { enable }

  plugin ping_plugin.so { enable }

  plugin router_plugin.so { enable }

  plugin upffp_plugin.so { enable }

  plugin dhcp_plugin.so { enable }

}


Commands used:

set intfc VPP-N6-0 state up

set int mac address eno1 00:11:22:33:44:66
set dhcp client intfc eno1

sh dhcp client verbose

[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)

  retry-count:346, next-xmt:2416.87

broadcast adjacency:20

sh log

2023/02/27 16:11:03:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:03:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)

retry-count:439, next-xmt:255827.12

broadcast adjacency:11

2023/02/27 16:11:08:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:08:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)

retry-count:440, next-xmt:255832.12

broadcast adjacency:11

2023/02/27 16:11:13:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:13:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

  lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255837.12)

  retry-count:441, next-xmt:255837.12

broadcast adjacency:11

2023/02/27 16:11:18:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:18:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)

retry-count:442, next-xmt:255842.12

  broadcast adjacency:11

show interface address

eno2 (up):

   L3 172.31.254.17/29

eno1 (up):

host-vpp1out (up):

   L3 128.0.129.144/24

local0 (dn):

memif0/502 (up):


Thank you in advance.

Best Regards,
Anagha









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22655): https://lists.fd.io/g/vpp-dev/message/22655
Mute This Topic: https://lists.fd.io/mt/97336867/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]
-=-=-=-=-=-=-=-=-=-=-=-



Re: [vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread Dave Barach
Do you see a response to the DHCP Discover packets? 

What does the vpp packet tracer show?

Thanks... Dave

> On Mar 2, 2023, at 7:03 AM, Thakur, Anagha  wrote:
> 
> 
>  
> Hello,
>  
> I am testing DHCP client feature from VPP stack (v22.02) onto our system.
>  
> My setup is: I run k8s cluster on x86 system in which I have a pod which uses 
> VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There 
> are two physical interfaces which we use in VPP, one of them is with static 
> IP (eno2) and other one with as DHCP client (eno1).
>  
> I expect this interface shall act as a DHCP Client and we run a DHCP server 
> on the other end of the system. But unfortunately, the VPP does not send any 
> DHCP REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a 
> DHCP Offer.
> But VPP does not send further DHCP REQUEST to the DHCP server. I do not 
> expect that it is a problem from lower layer and it should be an issue from 
> VPP side. Please let me know if I need to enable any extra plugin other than 
> the ones in the attached file.
> I attached pcap file recorded vpp trace of tx and rx.
>  
>  
> Our versions are currently as follows:
> -> DPDK 22.03
> -> VPP 22.02
> -> VPP library 22.02
>  
> Version Information attached.
>  
> plugins
> {
>   path /opt /vpp/lib/vpp_plugins
>   plugin default { disable }
>   plugin dpdk_plugin.so { enable }
>   plugin memif_plugin.so { enable }
>   plugin ping_plugin.so { enable }
>   plugin router_plugin.so { enable }
>   plugin upffp_plugin.so { enable }
>   plugin dhcp_plugin.so { enable }
> }
>  
>  
> Commands used:
> set intfc VPP-N6-0 state up
> set int mac address eno1 00:11:22:33:44:66
> set dhcp client intfc eno1
> sh dhcp client verbose
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)
>   retry-count:346, next-xmt:2416.87
> broadcast adjacency:20
> sh log
> 2023/02/27 16:11:03:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:03:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)
> retry-count:439, next-xmt:255827.12
> broadcast adjacency:11
> 2023/02/27 16:11:08:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:08:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)
> retry-count:440, next-xmt:255832.12
> broadcast adjacency:11
> 2023/02/27 16:11:13:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:13:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
>   lease: lifetime:0 renewal-interval:0 expires:0.00 
> (now:255837.12)
>   retry-count:441, next-xmt:255837.12
> broadcast adjacency:11
> 2023/02/27 16:11:18:986 notice dhcp/clientsm active session 0
> 2023/02/27 16:11:18:986 notice dhcp/clientsend: type:discover bcast:1 
> [0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address
> lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)
> retry-count:442, next-xmt:255842.12
>   broadcast adjacency:11
> show interface address
> eno2 (up):
>L3 172.31.254.17/29
> eno1 (up):
> host-vpp1out (up):
>L3 128.0.129.144/24
> local0 (dn):
> memif0/502 (up):
>  
>  
> Thank you in advance.
>  
> Best Regards,
> Anagha
>  
>  
> 
> 
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22652): https://lists.fd.io/g/vpp-dev/message/22652
Mute This Topic: https://lists.fd.io/mt/97336867/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]
-=-=-=-=-=-=-=-=-=-=-=-



[vpp-dev] FW: Bug: DHCP Client not sending DHCP REQUEST using VPP v22.02

2023-03-02 Thread Thakur, Anagha

Hello,

I am testing DHCP client feature from VPP stack (v22.02) onto our system.

My setup is: I run k8s cluster on x86 system in which I have a pod which uses 
VPP stack and it accesses physical NIC interface using DPDK and SR-IOV. There 
are two physical interfaces which we use in VPP, one of them is with static IP 
(eno2) and other one with as DHCP client (eno1).

I expect this interface shall act as a DHCP Client and we run a DHCP server on 
the other end of the system. But unfortunately, the VPP does not send any DHCP 
REQUEST. It keeps sending DHCP DISCOVERY every interval. It receives a DHCP 
Offer.
But VPP does not send further DHCP REQUEST to the DHCP server. I do not expect 
that it is a problem from lower layer and it should be an issue from VPP side. 
Please let me know if I need to enable any extra plugin other than the ones in 
the attached file.
I attached pcap file recorded vpp trace of tx and rx.


Our versions are currently as follows:
-> DPDK 22.03
-> VPP 22.02
-> VPP library 22.02

Version Information attached.


plugins

{

  path /opt /vpp/lib/vpp_plugins

  plugin default { disable }

  plugin dpdk_plugin.so { enable }

  plugin memif_plugin.so { enable }

  plugin ping_plugin.so { enable }

  plugin router_plugin.so { enable }

  plugin upffp_plugin.so { enable }

  plugin dhcp_plugin.so { enable }

}


Commands used:

set intfc VPP-N6-0 state up

set int mac address eno1 00:11:22:33:44:66
set dhcp client intfc eno1

sh dhcp client verbose

[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:2412.35)

  retry-count:346, next-xmt:2416.87

broadcast adjacency:20

sh log

2023/02/27 16:11:03:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:03:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255827.12)

retry-count:439, next-xmt:255827.12

broadcast adjacency:11

2023/02/27 16:11:08:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:08:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255832.12)

retry-count:440, next-xmt:255832.12

broadcast adjacency:11

2023/02/27 16:11:13:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:13:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

  lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255837.12)

  retry-count:441, next-xmt:255837.12

broadcast adjacency:11

2023/02/27 16:11:18:986 notice dhcp/clientsm active session 0

2023/02/27 16:11:18:986 notice dhcp/clientsend: type:discover bcast:1 
[0] VPP-N6-0 state DHCP_DISCOVER installed 0 no address

lease: lifetime:0 renewal-interval:0 expires:0.00 (now:255842.12)

retry-count:442, next-xmt:255842.12

  broadcast adjacency:11

show interface address

eno2 (up):

   L3 172.31.254.17/29

eno1 (up):

host-vpp1out (up):

   L3 128.0.129.144/24

local0 (dn):

memif0/502 (up):


Thank you in advance.

Best Regards,
Anagha


Version:  v22.02
Compiled by:  root
Compile host: ubuntu-22
Compile date: 2022-12-16T10:32:54
Compile location: /root/upf/upfv3/fastpath/build-vpp/vpp
Compiler: Clang/LLVM 11.0.1
Current PID:  70
Command line arguments:
  /opt/upf_fp/vpp/bin/vpp
  unix
{
nodaemon
log
/tmp/vpp.log
full-coredump
cli-listen
/run/vpp/cli.sock
}
  api-trace
{
on
}
  cpu
{
main-core
1
corelist-workers
2-4
}
  dpdk
{
dev
:02:09.0
  {
  name
  VPP-N3-0
  num-rx-queues
  1
  num-tx-queues
  2
  num-rx-desc
  1024
  num-tx-desc
  1024
  }
dev
:02:01.0
  {
  name
  VPP-N6-0
  num-rx-queues
  1
  num-tx-queues
  2
  num-rx-desc
  1024
  num-tx-desc
  1024
  }
socket-mem
256,256
}
  plugins
{
path
/opt/upf_fp/vpp/lib/vpp_plugins
plugin
default
  {
  disable
  }
plugin
dpdk_plugin.so
  {
  enable
  }
plugin
memif_plugin.so
  {
  enable
  }
plugin
ping_plugin.so
  {
  enable
  }
plugin
router_plugin.so
  {
  enable
  }
plugin
upffp_plugin.so
  {
  enable
  }
plugin
dhcp_plugin.so
  {
  enable
  }
}
  plugin_path
  /opt/upf_fp/vpp/lib/vpp_plugins
  logging
{
default-log-level
debug
default-syslog-log-level
info
}
  tap-inject
{
enable
}


trace_tx_rx.pcap
Description: trace_tx_rx.pcap

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all