Re: [systemd-devel] Policy Routing on a machine using systemd-networkd

2015-12-22 Thread Brendan Horan
- On 20 Dec, 2015, at 9:52 PM, Marc Haber mh+systemd-de...@zugschlus.de 
wrote:

> *nudge*
> 
> Is there really no option about this rather common issue?

Maybe you can post your work around for policy routing? (if you have one)
I would love to know as well.



> 
> Greetings
> Marc
> 
> 
> On Tue, Dec 15, 2015 at 01:20:34PM +0100, Marc Haber wrote:
>> I would like to do policy routing on a router with ~ 10 interfaces
>> running Debian Linux and systemd. Networking is managed with ferm and
>> systemd-networkd.
>> 
>> I now need Policy Routing. What is the recommended way to handle the
>> usual knot of iptables, ip rule and ip route statement in a clear and
>> beautiful way in a systemd environment?
>> 
>> As far as I know, systemd-network has not yet implemented policy
>> routing, so the canonical way (for me, as a systemd newbie) to
>> implement this would be a sysv init script containing the needed
>> commands.
>> 
>> What would be the "correct" way to do this in a systemd setup?
>> 
>> Actually, I need something that does the following:
>> 
>> o prevent a default route from being present in the main table (either
>>   by preventing it from being set in the first place or removing it
>>   idempotently)
>> o Establish a number of iptables rules to set fwmarks
>> o Establish a number of extra routing tables with a set of rules
>> o Establish a number of ip rule rules regarding source IP ranges or
>>   fwmarks.
>> 
>> How would I do that in systemd? Am I doing ok with a Type=oneshot
>> service unit with a bunch of ExecStart Options? Or is there another
>> recommended way?
> 
> --
> -
> Marc Haber | "I don't trust Computers. They | Mailadresse im Header
> Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] VLAN's not coming up systemd-networkd.service loaded failed + systemd-networkd seg fault

2015-02-03 Thread Brendan Horan
On Thu, 20.11.14 15:28, Brendan Horan (brendanho...@basstech.net) wrote:

  No one has any clue?
  Or do I need to provide more information? (if so what?) 

 Hmm, somehow this thread got lost. Is this still an issue with current
 git? If so could you repost, and we'll have a look at it.

Unsure if this is still an issue with the current git.
When I can test this again and if it is still an issue I will repost to the 
list.

 Sorry for not responding more timely and for resurrecting this months
 old thread!

No problem. Thank you for your time to reply.

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] VLAN's not coming up systemd-networkd.service loaded failed + systemd-networkd seg fault

2014-11-19 Thread Brendan Horan
No one has any clue?
Or do I need to provide more information? (if so what?) 

Thanks once again,
Brendan

- Original Message -
From: Brendan Horan brendanho...@basstech.net
To: systemd-devel systemd-devel@lists.freedesktop.org
Sent: Thursday, 13 November, 2014 11:59:49 AM
Subject: [systemd-devel] VLAN's not coming up systemd-networkd.service loaded 
failed + systemd-networkd seg fault

Hi,

I am trying configure VLAN sub interfaces with networkd.

When the machine boots the physical interface never seems to come UP.
Thus all the sub interface VLAN's also do not get activated.

I also notice systemd-networkd seg faults during boot, example message :

[7.036581] systemd-network[677]: segfault at 255 ip 7f88955634c9 sp 
7fffb34fd8b0 error 4 in systemd-networkd[7f8895559000+86000]
[7.093289] systemd-network[682]: segfault at 255 ip 7f3cd632e4c9 sp 
7fff25936ed0 error 4 in systemd-networkd[7f3cd6324000+86000]


If I then manually bring up my physical interface the VLAN sub interfaces get 
created. 
I am not sure what I am doing wrong and what is causing systemd-networkd to seg 
fault.


My configs are as follows : 

::
::
20-physical-int1.network
::
[Match]
MACAddress=XX:XX:XX:XX:XX:XX

[Network]
VLAN=PI-vlan.8
VLAN=PI-vlan.76
VLAN=PI-vlan.86
VLAN=PI-vlan.243
::
30-PI-vlan-8.netdev
::
[NetDev]
Name=PI-vlan.8
Kind=vlan

[VLAN]
Id=8
::
31-PI-vlan-76.netdev
::
[NetDev]
Name=PI-vlan.76
Kind=vlan

[VLAN]
Id=76

::
32-PI-vlan-86.netdev
::
[NetDev]
Name=PI-vlan.86
Kind=vlan

[VLAN]
Id=86
::
33-PI-vlan-243.netdev
::
[NetDev]
Name=PI-vlan.243
Kind=vlan

[VLAN]
Id=243
::
40-PI-vlan-8.network
::
[Match]
Name=PI-vlan.8

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
41-PI-vlan-76.network
::
[Match]
Name=PI-vlan.76

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
42-PI-vlan-86.network
::
[Match]
Name=PI-vlan.86

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
43-PI-vlan-.243.network
::
[Match]
Name=PI-vlan.243

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
::


If you need more info I am happy to try provide it.

Thank you, (and thanks for systemd!)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] VLAN's not coming up systemd-networkd.service loaded failed + systemd-networkd seg fault

2014-11-12 Thread Brendan Horan
Hi,

I am trying configure VLAN sub interfaces with networkd.

When the machine boots the physical interface never seems to come UP.
Thus all the sub interface VLAN's also do not get activated.

I also notice systemd-networkd seg faults during boot, example message :

[7.036581] systemd-network[677]: segfault at 255 ip 7f88955634c9 sp 
7fffb34fd8b0 error 4 in systemd-networkd[7f8895559000+86000]
[7.093289] systemd-network[682]: segfault at 255 ip 7f3cd632e4c9 sp 
7fff25936ed0 error 4 in systemd-networkd[7f3cd6324000+86000]


If I then manually bring up my physical interface the VLAN sub interfaces get 
created. 
I am not sure what I am doing wrong and what is causing systemd-networkd to seg 
fault.


My configs are as follows : 

::
::
20-physical-int1.network
::
[Match]
MACAddress=XX:XX:XX:XX:XX:XX

[Network]
VLAN=PI-vlan.8
VLAN=PI-vlan.76
VLAN=PI-vlan.86
VLAN=PI-vlan.243
::
30-PI-vlan-8.netdev
::
[NetDev]
Name=PI-vlan.8
Kind=vlan

[VLAN]
Id=8
::
31-PI-vlan-76.netdev
::
[NetDev]
Name=PI-vlan.76
Kind=vlan

[VLAN]
Id=76

::
32-PI-vlan-86.netdev
::
[NetDev]
Name=PI-vlan.86
Kind=vlan

[VLAN]
Id=86
::
33-PI-vlan-243.netdev
::
[NetDev]
Name=PI-vlan.243
Kind=vlan

[VLAN]
Id=243
::
40-PI-vlan-8.network
::
[Match]
Name=PI-vlan.8

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
41-PI-vlan-76.network
::
[Match]
Name=PI-vlan.76

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
42-PI-vlan-86.network
::
[Match]
Name=PI-vlan.86

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
43-PI-vlan-.243.network
::
[Match]
Name=PI-vlan.243

[Network]
Address=xxx.xxx.xxx.xxx/24

[Route]
Gateway=xxx.xxx.xxx.xxx
::
::


If you need more info I am happy to try provide it.

Thank you, (and thanks for systemd!)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel