[Spce-user] networking

[Volodymyr Fedorov]

Hi Tomi,
I think in mr6.3.1 /etc/network/interfaces are still not a part of
ngcpcfg framework. So you have to add route manually in post_up section.
But keep in mind that in mr6.4.1 ngcpcfg framework will generate interfaces
from network.yml

BR,
Volodymyr

On Wed, Oct 3, 2018 at 7:52 PM Tomi Hakkarainen <tomishakkarainen at gmail.com>
wrote:

> Hi Daniel,
>
> Thank you for the correct syntax highly appreciated.
>
> But I’m still not able to get this working.
>
> I was adding new interface to be used but not able to get it enabled with
> adding configuration to network.yml and running ngcpcfg apply
>
> also tried to run separatedly ngcpcfg build ,ngcpcfg commit and systemctl
> daemon-reload without luck.
>
> There is no errors outputted etc… and the configuration on
> /etc/network/interfaces is also intact
>
> what could I be missing here ?
>
> +---------------------------+----------------------------------------------
> 2018-10-03 19:43:32 -+
> | xxx.xxx.xxx.xx            | NGCP: CE mr6.3.1
>                         |
> | spce                      | NGCP: subscribers:2 locations:0 calls:0
>                         |
> | spce.                     |   OS: stretch (9.5) 4.9.0-8-amd64 SMP
> (ext4)                       |
> | (PRODUCTION - ACTIVE)     |  CPU: 8 = 2 x Intel(R) Xeon(R) CPU E5-2620
> v3 @ 2.40GHz (HT)       |
> |                           | BIOS: 6.00 (04/14/2014) by Phoenix
> Technologies...                 |
> |                           |  RAM: 7.8G (used 25%/cache 62%)
> kamailio[9.3%] perl-fcgi[5.2%]     |
> |                           |   LA: system load OK: 0.11 0.24 0.26
>                         |
> |                           |  HDD: space used /[8%]
>                         |
> |                           |  HDD: inodes in use /[4%]
>                         |
> |                           |  CFG: [8f1e7a0] commiting uncommented
> changes  (9 minutes ago)     |
> |                           | NGCP: active node has no registrations,
> strange for production     |
> |                           | NGCP: active node has no calls, strange for
> production             |
> |                           | MODs: License OFF,
>                         |
> +-------------------7 sec---+-----
> ---------------------------------------6.3.1.1+0~mr6.3.1.1---+
>
> Tomi
>
> On 3 Oct 2018, at 11.44, Daniel Grotti <dgrotti at sipwise.com> wrote:
>
> Hi,
> syntax example:
>
> post_up:
>       - route add -net 1.2.3.0/21 gw 192.168.1.1 dev vlan300
>
>
> Cheers,
>
> --
> Daniel Grotti
> Head of Customer Support
> Sipwise GmbH, Campus 21/Europaring F15
> AT-2345 Brunn am Gebirge
>
> Office: +43(0)130120332
> Email: dgrotti at sipwise.com <dgrotti at sipwise.com>
> Website: https://www.sipwise.com
>
> On 10/02/2018 11:55 PM, Tomi Hakkarainen wrote:
>
> Hi U all,
>
> What would be the correct format to make a static ip route on CE network
> interface on /etc/ngcp-config/network.yml ?
>
> I think I should use:
> • post_up: routes can be defined here (interface-based routing)
> but cannot figure how to add destination ip,  mask and  gw
>
> something like this ?
>
> etc1:
> post-up:
>   - to: 192.168.1.1/0
>     via: 10.0.0.1
>
>
>
>
> Regards Tomi
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>


-- 
Best regards,
Volodymyr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20181003/2b593c89/attachment-0001.html>