[strongSwan] swanctt + dhcp + dns

[Kamil Jońca]

Noel Kuntze
<noel.kuntze+strongswan-users-ml-eJe4+7AOuxYyzzc7d281tti2O/JbrIOy at public.gmane.org>
writes:

> 1. Never did that with swanctl. You have to play around with the pools or dig around. Maybe it's as simple as "connections.<conn>.pools = dhcp" or "connections.<conn>.pools = %dhcp". Maybe it's not.

Well, this can be done by simply 
pools = dhcp
and alone is not a problem, but ...

> 2. You can't.

So there is no an equivalent of 

"rightdns=192.168.200.200"

in swanctl, and the only way to send DNS server is to return to old starter-based approach?

Am I wrong?
KJ


> On 18.12.2017 15:21, Kamil Jońca wrote:
>> Noel Kuntze
>> <noel.kuntze+strongswan-users-ml-eJe4+7AOuxYyzzc7d281tti2O/JbrIOy at public.gmane.org>
>> writes:
>>
>>> Use a pool. Look at the UsableExamples[1] page.
>>> You can't pass dns servers from DHCP at all. It has nothing to do with
>>> the configuration backend you're using.
>> I was not too clear probably.
>>
>> I want to do with swanctl:
>> 1. have client addres taken from dhcp
>> 2. somehow configure dns to pass (how? )
>>
>> ie. how to translate from old config:
>>
>>
>> conn xxx
>>         left=192.168.200.200
>>         leftsubnet=192.168.200.0/24
>>         leftid=xxx
>>         leftca=yyy
>>         leftcert=....
>>         rightdns=192.168.200.200
>>         right=%any
>>         compress=yes
>>         rightsourceip=%dhcp
>>
>>
>>
>> KJ
>>
>

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Mencken and Nathan's Fifteenth Law of The Average American:
	The worst actress in the company is always the manager's wife.