Sorry I misread your mail. To do this, either you need to enter your docker 
container with privileged access: 

- docker exec -it -u 0 <docker-name-or-id> bash

Either you configure the host running the SDNC container with the proper route. 
because K8S rely on the host routing table.

Alexis


> On Feb 9, 2018, at 5:35 PM, FREEMAN, BRIAN D <[email protected]> wrote:
> 
>  
> For the vCPE Use Case we add a static route from the SDNC controller to the 
> vBNG  so that we can to the vBRG to create the tunnels to the vGMUX.
>  
> The command we use on regular docker seems to fail on the K8 based image.
>  ip route add 10.3.0.0/24 via 10.0.101.10 dev eth0
> RTNETLINK answers: Operation not permitted
>  
> Other ip config data below.
>  
> Do we need to add this static route from the K8 side ?
>  
> Brian
>  
> root@sdnc-1507781456-qpp77:/# ifconfig
> eth0      Link encap:Ethernet  HWaddr 02:f2:9c:4e:8e:03
>           inet addr:10.42.105.196  Bcast:0.0.0.0  Mask:255.255.0.0
>           inet6 addr: fe80::c461:2eff:fe28:5ab8/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1402  Metric:1
>           RX packets:452850 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:374275 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:72235413 (72.2 MB)  TX bytes:53479210 (53.4 MB)
>  
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>           RX packets:10453 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:10453 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1155768 (1.1 MB)  TX bytes:1155768 (1.1 MB)
>  
>  
>  
>  
> root@sdnc-1507781456-qpp77:/# ip route
> default via 10.42.0.1 dev eth0
> 10.42.0.0/16 dev eth0  proto kernel  scope link  src 10.42.105.196
> 169.254.169.250 via 10.42.0.1 dev eth0
> _______________________________________________
> onap-discuss mailing list
> [email protected] <mailto:[email protected]>
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> <https://lists.onap.org/mailman/listinfo/onap-discuss>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to