> Yes, this is a long standing problem in rtnl_talk() api has no max
> length given for the answer.
I changed rtnl_talk API as well. It probably will break some people
who extract libnetlink as a user available library, but compatibility
with internal API's was never guaranteed by iproute2.
From
On Tue, 19 May 2015 10:41:32 +0200
Jetchko Jekov wrote:
> Hello,
>
> I hope this is the right way to report a bug regarding iproute.
>
> While playing with gre[tap] tunnels I run in the following:
I integrated your patch into upcoming release.
--
To unsubscribe from this list: send the line "
On Thu, 2015-05-21 at 09:47 +0200, Jetchko Jekov wrote:
> I am confused by this reply, sorry.
> What does it mean?
> Is my fix correct one or its just workaround which doesn't fix root
> cause of the problem? And if is not, what would be the correct way?
> Because the current state ip command f
On 05/19/2015 03:25 PM, ext Eric Dumazet wrote:
On Tue, 2015-05-19 at 10:41 +0200, Jetchko Jekov wrote:
Hello,
I hope this is the right way to report a bug regarding iproute.
While playing with gre[tap] tunnels I run in the following:
# modprobe ip-gre
# ip l add gre1 type gre remote 1.1.1.
