Hi Kirill, That is probably accurate, although I’ve never tried it. The rules table does apply to listeners but the listener lookup logic (see app_listener_lookup) will just use the action_index to find an app listener. So if there is an app listener with that index, bind will report port is in use.
Could you provide a bit more details about your usecase? Regards, Florin > On Nov 20, 2025, at 4:35 AM, Kirill Shileev via lists.fd.io > <[email protected]> wrote: > > Hi folks > > I'm trying to do something like that: > vppctl ses rule add appns default proto tcp 0.0.0.0/0 <http://0.0.0.0/0> 443 > {ssl}/32 443 action 3 > > then bind some VCL app to port 443, this fails. > > According to GPT: > > The bind fails because: > > Port 443 is reserved by a VPP session rule > → VCL apps cannot bind to ports controlled by rules. > > Fix: > > vppctl session rule del lcl 0.0.0.0/0 443 rmt 30.22.0.201/32 443 > > please confirm that this is indeed impossible! And if GPT's wrong, please > point me in the right direction with some good example? > > -- > Best wishes, Kirill > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#26540): https://lists.fd.io/g/vpp-dev/message/26540 Mute This Topic: https://lists.fd.io/mt/116389781/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
