Hmm, looking into the code Kannel should connect just fine even DNS resolves to IPV4 and IPV6.
Please check in your logs in debug mode for: Connecting to <%s> AND connect to <%s> failed Thanks, Alex > Am 20.07.2020 um 08:48 schrieb Alexander Malysh <amal...@kannel.org>: > > Hi, > > Kannel always take the first IP from DNS response. Therefore you have to make > sure IPV4 > address is the first address, > > Alex > > >> Am 19.07.2020 um 15:43 schrieb Antony Stone >> <antony.st...@kannel.open.source.it >> <mailto:antony.st...@kannel.open.source.it>>: >> >> On Sunday 19 July 2020 at 15:04:45, Alexander Malysh wrote: >> >>> Hi, >>> >>> kannel doesn’t support IPV6 yet. >> >> Hm, it appears to be even worse than I thought... >> >> I was switching from a config file which contained the hostname of a server >> which only had an IPv4 address, to a hostname which only resolves to an IPv6 >> address. >> >> Since kannel doesn't do IPv6 yet, that didn't work. >> >> However today I seem to have found that if you give kannel a hostname which >> resolves to both IPv4 and IPv6 addresses, it still can't connect to the IPv4 >> address! >> >> Just the existence of an IPv6 address in the hostname lookup is enough to >> prevent kannel from being able to connect to the IPv4 address alongside it. >> >> >> Can anyone else confirm this finding, or is it just me and my networking >> setup >> (which works fine for other services connecting to both IPv4 and IPv6 >> addresses >> for the same hostname)? >> >> >> Thanks, >> >> >> Antony. >> >> -- >> "When you talk about Linux versus Windows, you're talking about which >> operating system is the best value for money and fit for purpose. That's a >> very >> basic decision customers can make if they have the information available to >> them. Quite frankly if we lose to Linux because our customers say it's >> better >> value for money, tough luck for us." >> >> - Steve Vamos, MD of Microsoft Australia >> >> Please reply to the list; >> please *don't* CC me. >> >> >
