From: Maciej Żenczykowski
Date: Tue, 7 Nov 2017 21:52:09 -0800
> From: Maciej Żenczykowski
>
> Add a per-device sysctl to specify the default traffic class to use for
> kernel originated IPv6 Neighbour Discovery packets.
>
> Currently this includes:
>
> - Router Solicitation (ICMPv6 type 1
From: Maciej Żenczykowski
Add a per-device sysctl to specify the default traffic class to use for
kernel originated IPv6 Neighbour Discovery packets.
Currently this includes:
- Router Solicitation (ICMPv6 type 133)
ndisc_send_rs() -> ndisc_send_skb() -> ip6_nd_hdr()
- Neighbour Solicit
Thanks.
Signed-off-by: Erik Kline
On 7 November 2017 at 16:59, Maciej Żenczykowski wrote:
> From: Maciej Żenczykowski
>
> Add a per-device sysctl to specify the default traffic class to use for
> kernel originated IPv6 Neighbour Discovery packets.
>
> Currently this includes:
>
> - Router So
From: Maciej Żenczykowski
Add a per-device sysctl to specify the default traffic class to use for
kernel originated IPv6 Neighbour Discovery packets.
Currently this includes:
- Router Solicitation (ICMPv6 type 133)
ndisc_send_rs() -> ndisc_send_skb() -> ip6_nd_hdr()
- Neighbour Solicit
atically allocated memory. Additionally, it subtly changes behavior
> of how certain ipv6 sysctl values are inherited from the default net
> namespace to the child namespaces. Before a79ca223e029, the default
> namespace would directly modify the values in statically allocated
> struct ipv6_devconf
Hi guys,
Commit a79ca223e029 ('ipv6: fix bad free of addrconf_init_net')
introduced in linux 3.9 tries to fix an issue involving free-ing
statically allocated memory. Additionally, it subtly changes behavior
of how certain ipv6 sysctl values are inherited from the default net
namesp
Konstantin Khlebnikov writes:
> IPv6 initialized with default. That's ok.
> IPv4 makes a copy from init_net. Looks like a bug, here
> v2.6.24-2577-g752d14dc6aa9
>
> root@zurg:~# sysctl net.ipv4.conf.all.forwarding=0
> net.ipv6.conf.all.forwarding=0
> net.ipv4.conf.all.forwarding = 0
> net.ipv6.co
IPv6 initialized with default. That's ok.
IPv4 makes a copy from init_net. Looks like a bug, here
v2.6.24-2577-g752d14dc6aa9
root@zurg:~# sysctl net.ipv4.conf.all.forwarding=0
net.ipv6.conf.all.forwarding=0
net.ipv4.conf.all.forwarding = 0
net.ipv6.conf.all.forwarding = 0
root@zurg:~# unshare -n s
From: Andy Gospodarek
Date: Thu, 13 Aug 2015 10:39:01 -0400
> Like the ipv4 patch with a similar title, this adds a sysctl to allow
> the user to change routing behavior based on whether or not the
> interface associated with the nexthop was an up or down link. The
> default setting preserves th
Like the ipv4 patch with a similar title, this adds a sysctl to allow
the user to change routing behavior based on whether or not the
interface associated with the nexthop was an up or down link. The
default setting preserves the current behavior, but anyone that enables
it will notice that nextho
Like the ipv4 patch with a similar title, this adds a sysctl to allow
the user to change routing behavior based on whether or not the
interface associated with the nexthop was an up or down link. The
default setting preserves the current behavior, but anyone that enables
it will notice that nextho
From: Erik Kline
Date: Wed, 22 Jul 2015 16:38:25 +0900
> Per RFC 6724, section 4, "Candidate Source Addresses":
>
> It is RECOMMENDED that the candidate source addresses be the set
> of unicast addresses assigned to the interface that will be used
> to send to the destination (the "o
Per RFC 6724, section 4, "Candidate Source Addresses":
It is RECOMMENDED that the candidate source addresses be the set
of unicast addresses assigned to the interface that will be used
to send to the destination (the "outgoing" interface).
Add a sysctl to enable this behaviour.
Signe
From: Erik Kline
Date: Mon, 20 Jul 2015 16:06:34 +0200
> I thought perhaps "use_oif_addr_only" was a slightly clearer sysctl name.
>
> (Maybe it should be plural, "use_oif_addrs_only"?)
I think plural would be better too, please respin with that change.
Thanks.
--
To unsubscribe from this list
I thought perhaps "use_oif_addr_only" was a slightly clearer sysctl name.
(Maybe it should be plural, "use_oif_addrs_only"?)
On 20 July 2015 at 16:04, Erik Kline wrote:
> Per RFC 6724, section 4, "Candidate Source Addresses":
>
> It is RECOMMENDED that the candidate source addresses be the s
Per RFC 6724, section 4, "Candidate Source Addresses":
It is RECOMMENDED that the candidate source addresses be the set
of unicast addresses assigned to the interface that will be used
to send to the destination (the "outgoing" interface).
Add a sysctl to enable this behaviour.
Signe
Per RFC 6724, section 4, "Candidate Source Addresses":
It is RECOMMENDED that the candidate source addresses be the set
of unicast addresses assigned to the interface that will be used
to send to the destination (the "outgoing" interface).
Add a sysctl to enable this behaviour.
Signe
David Miller wrote:
> So we should look at a way at making the new behavior the default, and
> in fact that makes sense and we can even optimize this piece of saddr
> selection code to not do an iteration over all devices in the system
> for no reason at all. It can just do a quick dev_get_by_ind
From: Erik Kline
Date: Wed, 8 Jul 2015 21:41:58 +0900
>> I really would like to come up with a sane works-always behavior for
>> this, but besides doing a retry on the complete source address selection
>> algorithm I currently cannot come up with an idea.
>>
>> Maybe we can tweak saddr_eval a bit
> I really would like to come up with a sane works-always behavior for
> this, but besides doing a retry on the complete source address selection
> algorithm I currently cannot come up with an idea.
>
> Maybe we can tweak saddr_eval a bit.
I think it all comes down to this: source address selectio
On Wed, Jul 8, 2015 at 5:43 PM, Hannes Frederic Sowa
wrote:
>> For example, consider the case where you have an IPv6 default route
>> but not an IPv6 address on one interface (e.g., wifi), and a working
>> configuration (IPv6 default route and IPv6 address) on another
>> interface (e.g., cellular
On Wed, 2015-07-08 at 17:19 +0900, Lorenzo Colitti wrote:
> On Wed, Jul 8, 2015 at 5:09 PM, Hannes Frederic Sowa
> wrote:
> > I wonder a little bit, because addresses which match the outgoing
> > interface should get a higher score in saddr_eval, thus be
> > automatically
> > preferred. Is this c
On Wed, Jul 8, 2015 at 5:09 PM, Hannes Frederic Sowa
wrote:
> I wonder a little bit, because addresses which match the outgoing
> interface should get a higher score in saddr_eval, thus be automatically
> preferred. Is this check not strong enough?
It isn't strong enough because the "prefer outgo
On Wed, 2015-07-08 at 10:29 +0900, Lorenzo Colitti wrote:
> On Mon, Jul 6, 2015 at 12:05 PM, Erik Kline wrote:
> > Per RFC 6724, section 4, "Candidate Source Addresses":
> >
> > It is RECOMMENDED that the candidate source addresses be the set
> > of unicast addresses assigned to the inter
On Mon, Jul 6, 2015 at 12:05 PM, Erik Kline wrote:
> Per RFC 6724, section 4, "Candidate Source Addresses":
>
> It is RECOMMENDED that the candidate source addresses be the set
> of unicast addresses assigned to the interface that will be used
> to send to the destination (the "outgoin
Reworked with "use_oif_addr".
Thanks,
-Erik
On 3 July 2015 at 16:03, YOSHIFUJI Hideaki
wrote:
> Hi,
>
> Erik Kline wrote:
>> Per RFC 6724, section 4, "Candidate Source Addresses":
>>
>> It is RECOMMENDED that the candidate source addresses be the set
>> of unicast addresses assigned to t
Per RFC 6724, section 4, "Candidate Source Addresses":
It is RECOMMENDED that the candidate source addresses be the set
of unicast addresses assigned to the interface that will be used
to send to the destination (the "outgoing" interface).
Add a sysctl to enable this behaviour.
Signe
Hi,
Erik Kline wrote:
> Per RFC 6724, section 4, "Candidate Source Addresses":
>
> It is RECOMMENDED that the candidate source addresses be the set
> of unicast addresses assigned to the interface that will be used
> to send to the destination (the "outgoing" interface).
>
> Add a sy
Per RFC 6724, section 4, "Candidate Source Addresses":
It is RECOMMENDED that the candidate source addresses be the set
of unicast addresses assigned to the interface that will be used
to send to the destination (the "outgoing" interface).
Add a sysctl to enable this behaviour.
Signe
In article <[EMAIL PROTECTED]> (at Fri, 25 Jan 2008 14:32:23 +0100), Daniel
Lezcano <[EMAIL PROTECTED]> says:
> Move ipv6_icmp_sysctl_init and ipv6_route_sysctl_init into
> the right ifdef section otherwise that does not compile when
> CONFIG_SYSCTL=yes and CONFIG_PROC_FS=no
>
> Signed-off-by: D
Subject: fix sysctl compilation error
From: Daniel Lezcano <[EMAIL PROTECTED]>
Move ipv6_icmp_sysctl_init and ipv6_route_sysctl_init into
the right ifdef section otherwise that does not compile when
CONFIG_SYSCTL=yes and CONFIG_PROC_FS=no
Signed-off-by: Daniel Lezcano <[EMAIL PROTECTED]>
---
i
The initialization of the sysctl for the ipv6 protocol is changed to
a network namespace subsystem. That means when a new network namespace
is created the initialization function for the sysctl will be called.
That do not change the behavior of the sysctl in case of the kernel
with the network nam
The initialization of the sysctl for the ipv6 protocol is changed to
a network namespace subsystem. That means when a new network namespace
is created the initialization function for the sysctl will be called.
That do not change the behavior of the sysctl in case of the kernel
with the network nam
The initialization of the sysctl for the ipv6 protocol is changed to
a network namespace subsystem. That means when a new network namespace
is created the initialization function for the sysctl will be called.
That do not change the behavior of the sysctl in case of the kernel
with the network nam
From: Pavel Emelyanov <[EMAIL PROTECTED]>
Date: Tue, 04 Dec 2007 13:13:11 +0300
> I have already done this for core, ipv4 and tr tables, so
> repeat this for the ipv6 ones.
>
> This makes the ipv6.ko smaller and creates the ground needed
> for net namespaces support in ipv6.ko ssctls.
>
> Signed
I have already done this for core, ipv4 and tr tables, so
repeat this for the ipv6 ones.
This makes the ipv6.ko smaller and creates the ground needed
for net namespaces support in ipv6.ko ssctls.
Signed-off-by: Pavel Emelyanov <[EMAIL PROTECTED]>
---
diff --git a/net/ipv6/sysctl_net_ipv6.c b/ne
This makes the ipv6.ko smaller and creates the ground needed
for net namespaces support in ipv6.ko ssctls.
Signed-off-by: Pavel Emelyanov <[EMAIL PROTECTED]>
---
diff --git a/net/ipv6/sysctl_net_ipv6.c b/net/ipv6/sysctl_net_ipv6.c
index 227efa7..0b5bec3 100644
--- a/net/ipv6/sysctl_net_ipv6.c
++
37 matches
Mail list logo
