Displaying 8 results from an estimated 8 matches for "cid_ani".
Did you mean:
cid_any
2020 Apr 27
4
[PATCH net-next 0/3] vsock: support network namespace
Hi David, Michael, Stefan,
I'm restarting to work on this topic since Kata guys are interested to
have that, especially on the guest side.
While working on the v2 I had few doubts, and I'd like to have your
suggestions:
1. netns assigned to the device inside the guest
Currently I assigned this device to 'init_net'. Maybe it is better
if we allow the user to decide which
2020 Apr 27
4
[PATCH net-next 0/3] vsock: support network namespace
Hi David, Michael, Stefan,
I'm restarting to work on this topic since Kata guys are interested to
have that, especially on the guest side.
While working on the v2 I had few doubts, and I'd like to have your
suggestions:
1. netns assigned to the device inside the guest
Currently I assigned this device to 'init_net'. Maybe it is better
if we allow the user to decide which
2020 Apr 27
0
[PATCH net-next 0/3] vsock: support network namespace
On Mon, Apr 27, 2020 at 04:25:18PM +0200, Stefano Garzarella wrote:
> Hi David, Michael, Stefan,
> I'm restarting to work on this topic since Kata guys are interested to
> have that, especially on the guest side.
>
> While working on the v2 I had few doubts, and I'd like to have your
> suggestions:
>
> 1. netns assigned to the device inside the guest
>
>
2020 Apr 28
0
[PATCH net-next 0/3] vsock: support network namespace
On 2020/4/27 ??10:25, Stefano Garzarella wrote:
> Hi David, Michael, Stefan,
> I'm restarting to work on this topic since Kata guys are interested to
> have that, especially on the guest side.
>
> While working on the v2 I had few doubts, and I'd like to have your
> suggestions:
>
> 1. netns assigned to the device inside the guest
>
> Currently I
2019 Nov 28
5
[RFC PATCH 0/3] vsock: support network namespace
Hi,
now that we have multi-transport upstream, I started to take a look to
support network namespace (netns) in vsock.
As we partially discussed in the multi-transport proposal [1], it could
be nice to support network namespace in vsock to reach the following
goals:
- isolate host applications from guest applications using the same ports
with CID_ANY
- assign the same CID of VMs running in
2019 Nov 28
5
[RFC PATCH 0/3] vsock: support network namespace
Hi,
now that we have multi-transport upstream, I started to take a look to
support network namespace (netns) in vsock.
As we partially discussed in the multi-transport proposal [1], it could
be nice to support network namespace in vsock to reach the following
goals:
- isolate host applications from guest applications using the same ports
with CID_ANY
- assign the same CID of VMs running in
2019 Dec 03
0
[RFC PATCH 0/3] vsock: support network namespace
On Thu, Nov 28, 2019 at 06:15:16PM +0100, Stefano Garzarella wrote:
> Hi,
> now that we have multi-transport upstream, I started to take a look to
> support network namespace (netns) in vsock.
>
> As we partially discussed in the multi-transport proposal [1], it could
> be nice to support network namespace in vsock to reach the following
> goals:
> - isolate host
2010 Oct 22
0
CEL ODBC problem in 1.8.0
...res_odbc.c:1502 odbc_obj_connect: res_odbc: Connected to PostgreSQL-asterisk [asterisk-connector]
[Oct 22 21:46:09] WARNING[952]: cel_odbc.c:733 odbc_log: Insert failed on 'PostgreSQL-asterisk:celnew'. CEL failed: INSERT INTO celnew (uniqueid,linkedid,eventtime,userdeftype,cid_name,cid_num,cid_ani,cid_rdnis,cid_dnid,exten,context,channame,appname,appdata,accountcode,peeraccount,userfield,peer,amaflags) VALUES ('co-1287780365.0','co-1287780365.0',{ ts '2010-10-22 21:46:06' },'','135','441XXXXXXXXX','441XXXXXXXXX','','136'...