Re: [ovs-discuss] using FQDN for Controller name

2017-07-31 Thread Ben Pfaff
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

Re: [ovs-discuss] using FQDN for Controller name

2017-07-31 Thread Shivaram Mysore
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,

Re: [ovs-discuss] using FQDN for Controller name

2017-07-31 Thread Ben Pfaff
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 >

[ovs-discuss] using FQDN for Controller name

2017-07-31 Thread Shivaram Mysore
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