On 03/01/18 00:30, David Gwynne wrote:
On 1 Mar 2018, at 02:22, Andreas Bartelt wrote:
On 02/27/18 22:35, Pavel Korovin wrote:
On 02/28, David Gwynne wrote:
what is the status of sysctl net.inet.ipip ?
David, thank you! That was easy :)
Sorry for the noise.
$ sysctl net.inet.ipip.allow
net
> On 1 Mar 2018, at 02:22, Andreas Bartelt wrote:
>
> On 02/27/18 22:35, Pavel Korovin wrote:
>> On 02/28, David Gwynne wrote:
>>> what is the status of sysctl net.inet.ipip ?
>> David, thank you! That was easy :)
>> Sorry for the noise.
>> $ sysctl net.inet.ipip.allow
>> net.inet.ipip.allow=0
>
On 02/27/18 22:35, Pavel Korovin wrote:
On 02/28, David Gwynne wrote:
what is the status of sysctl net.inet.ipip ?
David, thank you! That was easy :)
Sorry for the noise.
$ sysctl net.inet.ipip.allow
net.inet.ipip.allow=0
# sysctl -w net.inet.ipip.allow=1
net.inet.ipip.allow: 0 -> 1
$ ping6 w
On 02/28, David Gwynne wrote:
> what is the status of sysctl net.inet.ipip ?
David, thank you! That was easy :)
Sorry for the noise.
$ sysctl net.inet.ipip.allow
net.inet.ipip.allow=0
# sysctl -w net.inet.ipip.allow=1
net.inet.ipip.allow: 0 -> 1
$ ping6 www.google.com
PING www.google.com (2a00:14
> On 27 Feb 2018, at 4:10 am, Pavel Korovin wrote:
>
> Dear all,
>
> After upgrading several hosts to -current I noticed that all my IPv6 tunnels
> via tunnelbroker stopped working. Recently introduced changes to gif(4)
> (since
> late December 2017) are too complex for me to grasp, maybe an
Dear all,
After upgrading several hosts to -current I noticed that all my IPv6 tunnels
via tunnelbroker stopped working. Recently introduced changes to gif(4) (since
late December 2017) are too complex for me to grasp, maybe anybody on the list
can advise.
--
With best regards,
Pavel Korovin
6 matches
Mail list logo
