similar to: transition to ip6

Today I received an allocation of IP6 addresses for some servers. I can 'play' with the last 2 of the 8 IP6 address segments. I always thought, mistakenly, IP6 was 6 segments, because it was IP6. IP4 had 4 segments. However IP6 is actually IP version 6 and it has 8 segments. The other interesting discovers are: :: means one or more 0 segments, example :: can mean 0:0:0: or just 0:0: or

Hello all, I''m somewhat new to networking, and I''m having trouble masquerading connections that are coming over a bridge. The bridge only has a single port for now, but I''m going to add more ports later. I''m basing my configuration on the two-interface quick start guide. I''m using Shorewall 3.0.4 on Ubuntu Dapper. My network looks like this: * The

Hello, I am trying to assign an IPv6 address to one of my guests. I followed the following guide, unsuccessfully: https://www.berrange.com/posts/2011/06/16/providing-ipv6-connectivity-to-virtual-guests-with-libvirt-and-kvm/ . I have the following config files: dumpxml of the guest `deb`: http://sprunge.us/iUef net-dumpxml of network `default`: http://sprunge.us/WTfH net-dumpxml of network `ip6`:

https://bugzilla.netfilter.org/show_bug.cgi?id=1371 Bug ID: 1371 Summary: Concatenations Literal sets Product: nftables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at netfilter.org Reporter:

Dear List I fear I stumbled over a bug in asterisk 13.14.1. My 'phones' are roaming around, sometimes some are connecting from ipv6 enabled networks, another time they are not. If a connection is ipv6 I would prefer to use ipv6 to avoid ipv4-nat problems. I have not specified a transport in the endpoint section, so that the appropriate transport which corresponds to the registration

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/4/2014 8:46 PM, Bhasker C V wrote: > On 04/10/14 15:36, The Cop wrote: >> Hello, >> >> I am trying to assign an IPv6 address to one of my guests. I followed the >> following guide, unsuccessfully: >> https://www.berrange.com/posts/2011/06/16/providing-ipv6-connectivity-to-virtual-guests-with-libvirt-and-kvm/

CentOS 5.5, fully patched. I have a HE tunnel (tunnelbroker.net) IPv6 tunnel. This works pretty well and is simple to setup. Everything works fine. Until I try to set up an ip6tables firewall. eg if I try to view https://dnssec.surfnet.nl/?p=464 then the page never displays and the firewall shows kernel: IN=sit1 OUT=eth0 SRC=2001:0610:0001:40cd:0145:0100:0186:0033 DST=my.machine LEN=80 TC=0

On 10/23/18 14:45, Phil Perry wrote: > On 23/10/18 19:05, mark wrote: >> Been looking, and haven't found the answer: in c7, is there a firewall-cmd >> command, or a systemctl cmd, to check whether ip6tables firewall is >> running > > Yes, the same as for any other service: > > systemctl status ip6tables.service > Um, no. I've discovered that on our

I know I have some quirky behavior involving my layer two tinc host, and the IPv6 subnet that runs off of it. Facebook just issued a kernel patch that changes the behavior of the IPv6 tunnel mechanism: I can't tell from the patch itself, if it might also improve functionality for non IP6-IP6 tunnels.

On 02/16/2017 03:28 AM, James Hogarth wrote: > On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 02:32 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:03 AM, James Hogarth wrote: >>>>>

On 10/5/2014 1:56 AM, Bhasker C V wrote: > On 04/10/14 21:13, The Cop wrote: >> On 10/4/2014 8:46 PM, Bhasker C V wrote: >>> On 04/10/14 15:36, The Cop wrote: >>>> Hello, >>>> >>>> I am trying to assign an IPv6 address to one of my guests. I followed the >>>> following guide, unsuccessfully: >>>> >>

Hi all, I have a user who is reporting one-way audio, but only when a call is made to or from particular PSTN (cell) numbers. Their phones are behind a NAT router and my server is on the open Internet. Calls within their office sound fine. Calls to/from most numbers sound fine. When they took their phones home, those same phone numbers still had problems. So, I don't think it's

On 10/15/20 2:02 PM, jeremy ardley wrote: >> how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4? > > It appears your host has A and AAAA records in your DNS. The clients will try IPV6 first if they see an AAAA record. > > If you don't need IPV6 for your host remove the AAAA record. All connections will then only use

what is weird is that i have not changed it for about 2 years, only apt update, upgrade. no other change, ipv4 and ipv6 address working correctly. now there is this bug, that i have not changed anything and suddenly, DLZ generates an unknown not connected , working, live ip4 and ip6. and all because it tried an nslookup p3x-dc.patrikx3.com that was the correct for over 2 years. the only thing that

On 16 February 2017 at 11:46, James Hogarth <james.hogarth at gmail.com> wrote: > On 16 February 2017 at 11:35, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 03:28 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:42, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:32 AM, James

https://bugzilla.netfilter.org/show_bug.cgi?id=1730 Bug ID: 1730 Summary: nft does not handle IPv6 addresses with embedded IPv4 addresses Product: nftables Version: 1.0.x Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: nft

On 02/16/2017 02:32 AM, James Hogarth wrote: > On 16 February 2017 at 10:17, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 02:03 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 09:09, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>>>>

If I leave the "listen" value as the default in /etc/dovecot.conf I'll get a message similar to the following on each port that it tries to open during startup: # dovecot -F Fatal: listen(::, 143) failed: Address already in use If I set either: listen = * or listen = [::] then it will start up fine. Perhaps it is as though the code tries to open the port twice for both

http://bugzilla.netfilter.org/show_bug.cgi?id=751 Summary: IPv6 bridging bug Product: iptables Version: unspecified Platform: x86_64 OS/Version: Gentoo Status: NEW Severity: normal Priority: P3 Component: ip6tables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: david at

On 10/26/18, Andrew Pearce <andrew at andew.org.uk> wrote: > On 2018-10-26 16:25, mark wrote: > I believe this should remove any ipv6 rules (rules and chains) > > ip6tables -F > ip6tables -X You might want to clear the other tables, too: for x in filter nat mangle raw security "" do ip6tables ${x:+-t $x} -F ip6tables ${x:+-t $x} -X done > You may need to