On Thu, Nov 24, 2016 at 20:52 +0100, Mike Belopuhov wrote:
> On Wed, Nov 23, 2016 at 21:52 +0100, Stefan Fritsch wrote:
> > On Wed, 23 Nov 2016, Mike Belopuhov wrote:
> > > This fixes up tsleep priorities in vio(4) and makes sleeps
> > > interruptable so that ifconfig can be killed with ^C. Tested
Diff below removes the 'struct route_in6' argument from in6_selectsrc().
It is only used by in6_pcbselsrc() so move the code there. This reduces
differences with IPv4 and help me to get rid of 'struct route*'.
ok?
Index: net/if_vxlan.c
===
On Sat, Nov 05, 2016 at 12:41:39PM +0100, Vincent Gross wrote:
> Updated diff, I reworked the logic to handle the if_get/if_put dance in
> vxlan_multicast_join(), and fixed an uninitialized variable.
>
> Ok ?
Some nits inline.
>
> Index: net/if_vxlan.c
>
Hi,
If the BROADCAST flag is set on a BOOTREPLY, the RFC specifies that
we SHOULD forward the packet not only as L3 broadcast, but also as
L2 broadcast. Apparently that helps on older machines that can't
handle L2 unicast replies.
ok?
Patrick
diff --git a/usr.sbin/dhcrelay/dhcrelay.c b/usr.sbi
Hi,
DHCP requests can be relayed through multiple relays. There are two parts in
the RFC that we don't oblige and thus make dhcrelay impossible to use through
multiple relays.
The BOOTREQUEST message has a gateway ip addr attribute (giaddr). This is
used by the DHCP server to correlate which su
On 2016-11-28, Martin Pieuchot wrote:
> vether(4) has a long name. Let's extend to output of these tools to
> 80 chars to make vetherX fit in the columns.
There was a historical reason for avoiding 80-column-wide output.
On a terminal without the "VT100 glitch" feature, after you write
to the 8
Remi Locherer writes:
> On Sat, Nov 26, 2016 at 09:39:40AM +0100, Jeremie Courreges-Anglas wrote:
>> Remi Locherer writes:
>>
>> > Hi,
>> >
>> > I ran into problems with mtu sizes on interfaces (gif in my case) and
>> > ospfd. mtu was not the same on both sites so adjacency could not be
>> > fo
