On Thu, Jan 11, 2018 at 11:51:25AM +0100, Peter Hessler wrote:
> On 2018 Jan 11 (Thu) at 20:41:19 +1000 (+1000), David Gwynne wrote:
> :vlan and trunk are definitely ethernet interfaces.
> :
>
> Is there anything in OpenBSD that isn't an ethernet inteface?
>
How about gif(4), gre(4), tun(4), ppp
On 2018 Jan 11 (Thu) at 11:51:25 +0100 (+0100), Peter Hessler wrote:
:On 2018 Jan 11 (Thu) at 20:41:19 +1000 (+1000), David Gwynne wrote:
::vlan and trunk are definitely ethernet interfaces.
::
:
:Is there anything in OpenBSD that isn't an ethernet inteface?
:
based on a simplistic grep: upl(4),
> On 11 Jan 2018, at 8:51 pm, Peter Hessler wrote:
>
> On 2018 Jan 11 (Thu) at 20:41:19 +1000 (+1000), David Gwynne wrote:
> :vlan and trunk are definitely ethernet interfaces.
> :
>
> Is there anything in OpenBSD that isn't an ethernet inteface?
carp :)
>
> --
> It is impossible to travel
On 2018 Jan 11 (Thu) at 20:41:19 +1000 (+1000), David Gwynne wrote:
:vlan and trunk are definitely ethernet interfaces.
:
Is there anything in OpenBSD that isn't an ethernet inteface?
--
It is impossible to travel faster than light, and certainly not
desirable, as one's hat keeps blowing off.
> On 11 Jan 2018, at 5:53 pm, Jonathan Gray wrote:
>
> On Thu, Jan 11, 2018 at 08:25:26AM +0100, Matthieu Herrb wrote:
>> On Thu, Jan 11, 2018 at 10:29:17AM +1000, David Gwynne wrote:
>>> carp interfaces output using ether_output, so it is reasonable to
>>> require that they only get configured
On Thu, Jan 11, 2018 at 08:25:26AM +0100, Matthieu Herrb wrote:
> On Thu, Jan 11, 2018 at 10:29:17AM +1000, David Gwynne wrote:
> > carp interfaces output using ether_output, so it is reasonable to
> > require that they only get configured on top of ethernet interfaces
> > rather than just !IFT_CAR
> On 11 Jan 2018, at 08:25, Matthieu Herrb wrote:
>
>> On Thu, Jan 11, 2018 at 10:29:17AM +1000, David Gwynne wrote:
>> carp interfaces output using ether_output, so it is reasonable to
>> require that they only get configured on top of ethernet interfaces
>> rather than just !IFT_CARP.
>>
> Hi
On Thu, Jan 11, 2018 at 10:29:17AM +1000, David Gwynne wrote:
> carp interfaces output using ether_output, so it is reasonable to
> require that they only get configured on top of ethernet interfaces
> rather than just !IFT_CARP.
>
Hi,
in this context are vlan interfaces also considered as IFT_ETH
