Re: Problems with rdomain and net/if.c v1.455

On 11/10/16 20:36, Andreas Bartelt wrote: On 11/09/16 11:55, Martin Pieuchot wrote: ... I'm going to commit this fixed diff unless somebody has something to add. I've tested this - it works for me. Sorry, I probably was too fast - I've observed a problem with smtpd in rdomain 0 (which

Re: Problems with rdomain and net/if.c v1.455

On 11/09/16 11:55, Martin Pieuchot wrote: ... I'm going to commit this fixed diff unless somebody has something to add. I've tested this - it works for me. Best regards Andreas

Re: Problems with rdomain and net/if.c v1.455

On Wed, Nov 09, 2016 at 11:55:19AM +0100, Martin Pieuchot wrote: > On 08/11/16(Tue) 17:23, Claudio Jeker wrote: > > On Tue, Nov 08, 2016 at 03:36:22PM +0100, Martin Pieuchot wrote: > > > [...] > > > To add 127.0.0.1 properly it's another story as currently netstart(8) > > > sets it. > > > > I

Re: Problems with rdomain and net/if.c v1.455

On 09/11/16(Wed) 17:31, Andreas Bartelt wrote: > [...] > I'm actually not using 127.0.0.1 as IP address on lo1 in my specific setup > -- I'm using the same LAN-visible IP address which unbound listens on in > rdomain 0 (due to the nameserver IP entries in /etc/resolv.conf which, by > design, are

Re: Problems with rdomain and net/if.c v1.455

On 11/09/16 16:43, Martin Pieuchot wrote: On 09/11/16(Wed) 16:29, Andreas Bartelt wrote: On 11/09/16 15:11, Martin Pieuchot wrote: ... Fair point. What about adding backward compatible goo to help people doing the transition: # ifconfig lo1 create # ifconfig vether0 rdomain 1 warning: lo1

Re: Problems with rdomain and net/if.c v1.455

On 09/11/16(Wed) 16:29, Andreas Bartelt wrote: > On 11/09/16 15:11, Martin Pieuchot wrote: > ... > > Fair point. What about adding backward compatible goo to help people > > doing the transition: > > > > # ifconfig lo1 create > > # ifconfig vether0 rdomain 1 > > warning: lo1 cannot be used for

Re: Problems with rdomain and net/if.c v1.455

On 11/09/16 15:11, Martin Pieuchot wrote: ... Fair point. What about adding backward compatible goo to help people doing the transition: # ifconfig lo1 create # ifconfig vether0 rdomain 1 warning: lo1 cannot be used for rdomain 1 # ifconfig lo lo0: flags=8049 mtu

Re: Problems with rdomain and net/if.c v1.455

On 09/11/16(Wed) 12:18, Stuart Henderson wrote: > On 2016/11/09 12:55, Martin Pieuchot wrote: > > > > > > I'm using that, and I think many people using an IGP will be too (you > > > want services - e.g. ssh, snmp, ntp, bgp - to stay working even when a > > > physical interface is down - and at

Re: Problems with rdomain and net/if.c v1.455

* Martin Pieuchot [2016-11-09 11:55]: > On 08/11/16(Tue) 17:23, Claudio Jeker wrote: > > On Tue, Nov 08, 2016 at 03:36:22PM +0100, Martin Pieuchot wrote: > > > I'm not sure to understand the benefit. What's the use case for loop(4)? > > 2 name spaces, so that I don't have a

Re: Problems with rdomain and net/if.c v1.455

On 09/11/16(Wed) 11:41, Stuart Henderson wrote: > On 2016/11/09 11:55, Martin Pieuchot wrote: > > On 08/11/16(Tue) 17:23, Claudio Jeker wrote: > > > On Tue, Nov 08, 2016 at 03:36:22PM +0100, Martin Pieuchot wrote: > > > > [...] > > > > To add 127.0.0.1 properly it's another story as currently

Re: Problems with rdomain and net/if.c v1.455

On Tue, Nov 08, 2016 at 03:36:22PM +0100, Martin Pieuchot wrote: > On 04/11/16(Fri) 10:45, Claudio Jeker wrote: > > On Wed, Nov 02, 2016 at 05:44:14PM +0100, Martin Pieuchot wrote: > > > [..] > > > Diff below should fix that by automagically creating a loopback > > > interface when a new routing

Re: Problems with rdomain and net/if.c v1.455

On 04/11/16(Fri) 10:45, Claudio Jeker wrote: > On Wed, Nov 02, 2016 at 05:44:14PM +0100, Martin Pieuchot wrote: > > [..] > > Diff below should fix that by automagically creating a loopback > > interface when a new routing domain is created. That mean loX will > > now correspond to routing domain

Re: Problems with rdomain and net/if.c v1.455

On Wed, Nov 02, 2016 at 05:44:14PM +0100, Martin Pieuchot wrote: > On 28/10/16(Fri) 16:27, Claudio Jeker wrote: > > On Fri, Oct 28, 2016 at 04:19:35PM +0200, Nils Frohberg wrote: > > > I currently cannot access the local IP of an interface on rdomain 1: > > > > > > Script started on Fri Oct 28

Re: Problems with rdomain and net/if.c v1.455

On 28/10/16(Fri) 16:27, Claudio Jeker wrote: > On Fri, Oct 28, 2016 at 04:19:35PM +0200, Nils Frohberg wrote: > > I currently cannot access the local IP of an interface on rdomain 1: > > > > Script started on Fri Oct 28 15:02:20 2016 > > $ doas pfctl -d > > pfctl: pf not enabled > > $ doas

Re: Problems with rdomain and net/if.c v1.455

On Fri, Oct 28, 2016 at 04:27:51PM +0200, Claudio Jeker wrote: > On Fri, Oct 28, 2016 at 04:19:35PM +0200, Nils Frohberg wrote: > > I currently cannot access the local IP of an interface on rdomain 1: > > > > Script started on Fri Oct 28 15:02:20 2016 > > $ doas pfctl -d > > pfctl: pf not

Re: Problems with rdomain and net/if.c v1.455

On Fri, Oct 28, 2016 at 04:19:35PM +0200, Nils Frohberg wrote: > I currently cannot access the local IP of an interface on rdomain 1: > > Script started on Fri Oct 28 15:02:20 2016 > $ doas pfctl -d > pfctl: pf not enabled > $ doas ifconfig vether0 > vether0: no such interface > $

Problems with rdomain and net/if.c v1.455

I currently cannot access the local IP of an interface on rdomain 1: Script started on Fri Oct 28 15:02:20 2016 $ doas pfctl -d pfctl: pf not enabled $ doas ifconfig vether0 vether0: no such interface $ doas ifconfig vether0 rdomain 1 $ doas ifconfig vether0 inet 192.168.42.2