This is mostly for historical reasons, by the way. We'd accept a patch
that adds DNS support. (It's nontrivial though because it would have to
be asynchronous.)
On Mon, Jul 31, 2017 at 01:16:36PM -0700, Shivaram Mysore wrote:
> Thanks Ben for clarification. Much appreciated.
>
> On Mon, Jul 31
Ben,
Can we request this feature for OVS? It greatly helps if we use SSL as
connectivity protocol and we need to use it also for identity.
Thanks
On Mon, Jul 31, 2017 at 1:16 PM, Shivaram Mysore
wrote:
> Thanks Ben for clarification. Much appreciated.
>
> On Mon, Jul 31, 2017 at 1:15 PM, Ben
Thanks Ben for clarification. Much appreciated.
On Mon, Jul 31, 2017 at 1:15 PM, Ben Pfaff wrote:
> On Mon, Jul 31, 2017 at 01:09:07PM -0700, Shivaram Mysore wrote:
> > Hello,
> >
> > I am trying to use FQDN for controller name - example:
> >
> > # ovs-vsctl set-controller ovs-br0 ssl:faucet.ex
On Mon, Jul 31, 2017 at 01:09:07PM -0700, Shivaram Mysore wrote:
> Hello,
>
> I am trying to use FQDN for controller name - example:
>
> # ovs-vsctl set-controller ovs-br0 ssl:faucet.example.com:6653
>
> Per OVS logs, I see the below errors:
>
> Address family not supported by protocol
> connec
Hello,
I am trying to use FQDN for controller name - example:
# ovs-vsctl set-controller ovs-br0 ssl:faucet.example.com:6653
Per OVS logs, I see the below errors:
Address family not supported by protocol
connection failed (Address family not supported by protocol)
*Question*: can we not set FQ
Hi,
I have a hypervisor with Fedora 25 on a few machines and ever since
upgrading I started getting occasional messages:
[321428.168903] WARNING: CPU: 0 PID: 2279 at net/core/dev.c:2562
skb_warn_bad_offload+0xc4/0x110
[321428.168906] san0: caps=(0x04009fbb58e9, 0x)
len=6769 da
