similar to: How to bind to ipv4 & ipv6

Hello, I am doing some tests with asterisk on a dual-stack environment. I have some doubts regarding asterisk binding addresses on a server with 2 network cards. According to asterisk documentation: /; With the current situation, you can do one of four things:/ /; a) Listen on a specific IPv4 address. Example: bindaddr=192.0.2.1/ /; b) Listen on a specific IPv6 address.

Hello, I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und IPv6 in order to be able to have Samba acting as IPv6 DNS Server. However since I have problem with sysprep domain join as soon as Samba advertises its own Domain Controller Hostname as IPv4 and IPv6 address, I would like to tell Samba to run on both protocols but only resolve to an IPv4 address. So in short: When I

Hello all, I just found a bug a nice bug that can be turned into a real feature on systems (usually Linux) that are built with --with-ipv4-default. If you enable IPv6 in kernel, and enable both listenaddress 0.0.0.0 and ::, sshd will error out 'address family not supported'. However, you can work around this error by starting sshd with 'sshd -4 -6'. As far as man page is

Hello, How do I find out what is happening to my packets thru my ipsec tunnel. They just seem to disappear on the remote side. I have successfully got the pings thru when everything has an ipv6 address, but am not successful when trying to connect two ipv4 lans across an ipv6 ipsec tunnel. All fw chains both 4 and 6 are set to ACCEPT. NAT is turned off. eth0 eth1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a CentOS 6 box with a single IPv6 and a /64 IPv6 I would like to have on the same box a name-based virtual host of Apache with IPv4 and an IP-based virtual host with IPv6. The only solution I have found so far is to run two instances of Apache, one on IPv4 and the other on IPv6. In your opinion, are there other solutions to this problem?

Dear list, I'm trying to get Asterisk to work dual-stack on Linux and I'm left with a question. Imagine that a user (on the road) connects to Asterisk from various places. Many of them probably don't have IPv6 support yet. However, his house and office do have IPv6 connectivity. I would like to make sure that whenever IPv6 is available, the connection will be made over IPv6, but

Signed-off-by: Olaf Hering <olaf@aepfle.de> --- Untested in this environment. appliance/init | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/appliance/init b/appliance/init index b25ea26..cc8c978 100755 --- a/appliance/init +++ b/appliance/init @@ -71,6 +71,10 @@ for f in /sys/block/{h,s,ub,v}d*/queue/scheduler; do echo noop > $f; done # Update the system clock. hwclock -u -s

Hello! I am having a strange issue with CentOS 5.4 that I cannot seem to solve. Every DNS lookup results in AAAA records being requested first before A records. As a result, this causes a large amount of unnecessary DNS traffic on the network. IPv6 has been completely disabled on these servers: /etc/modprobe.conf, ipv6 off and net-pf-10 off /etc/sysconfig/network, NETWORKING_IPV6=no lsmod |

On Fri, Jan 24, Richard W.M. Jones wrote: > However I don't understand why disabling IPv6 should be necessary. If > sites resolve to AAAA+A records, then presumably it's going to choose > the A (IPv4) route since no IPv6 route exists. If a site resolves to > only an AAAA record, then it's not reachable whatever we do. For me the code tries to reach the ipv6 address,

Good day I would like to setup a SMB file server and DC that uses IPv4 and IPv6 dual stack. However I see certain problems; for instance, when the IPv6 prefix is dynamic, this means the IPv6 of the DC would also dynamically change. Is there something special I should consider when provisioning a SAMBA AD DC with IPv6, or will it "just work" ? Thanks, best Tobias

I wanted to change this test so it tries connections on both IPv4 & IPv6. Having it connect on both is the easy bit. Harder was making it not fail on machines that don't have IPv6 stack (or IPv4 in some rare cases). TBH I wasn't able to test this, but it seems like this should work. In the end we want to modify nbdkit so it can listen on only certain interfaces, but that's a

Hi, I'm having a really really strange problem. After upgrading from 1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect to the services using IPv4 anymore. dovecot happily binds to the IPv6 wildcard socket which should accept IPv4 connections as well. root at vs02:~# netstat -lnp --tcp | grep dovecot tcp6 0 0 :::993 :::*

Take 2 at bouncing this to the rest of the original recipients through a different MTA, since mail.zytor.com refused to accept it the first time. Please re-add Jason Gunthorpe <jgg at obsidianresearch.com> and 793921 at bugs.debian.org to the CC for replies. On Wed, Jul 29, 2015 at 05:34:00PM +0930, Ron wrote: > > Hi Jason, > > On Tue, Jul 28, 2015 at 03:45:30PM -0600, Jason

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address

openssh 7.6p1-lp150.7.4 on OpenSuse Leap 15 (both server and client) Hi all, first post to list, hopefully on-topic. Haven't found anything on the net, tried to ask at first in OpenSuse forums a while ago (https://forums.opensuse.org/showthread.php/533588-rsnapshot-rsync-massive-performance-decrease) and today opened a bug in OpenSuse's Bugzilla

Servus Philipp, Unfortunately the traceroute(6) results are both more or less random. Sometimes traceroute "hangs" a while, wherever, sometimes traceroute6. Sometimes traceroute is faster, sometimes traceroute6. Not reliable. Your MTU question, tried as adviced: Maximum size for IPv4 is 1466, and max size for IPv6 is 1444. Exceeding these values leads to a "ping: local error:

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I've recently found that at least on my test box the `LISTEN *` line had > only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for > `upsd`. Interesting. On one system I checked, I have 4 explicit directives for 127.0.0.1, ::1, and the LAN on v4/v6. On another, I have an empty

Jim Klimov via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I've recently found that at least on my test box the `LISTEN *` line had > only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for > `upsd`. Interesting. On one system I checked, I have 4 explicit directives for 127.0.0.1, ::1, and the LAN on v4/v6. On another, I have an empty

Cheers all, TL;DR version: I've recently found that at least on my test box the `LISTEN *` line had only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for `upsd`. In fact, at least on a "dual-stack" system, it seems impossible to bind to both - so depending on binding order I either lose IPv6 or lose IPv4 directly (but have it practically as IPv4-over-IPv6).

Cheers all, TL;DR version: I've recently found that at least on my test box the `LISTEN *` line had only set up an IPv4 `0.0.0.0` listener but not an IPv6 `::0` listener for `upsd`. In fact, at least on a "dual-stack" system, it seems impossible to bind to both - so depending on binding order I either lose IPv6 or lose IPv4 directly (but have it practically as IPv4-over-IPv6).