similar to: Specifying an IPv6 wildcard in the interfaces directive?

On 4/20/2019 1:08 PM, Nico Kadel-Garcia wrote: > On Sat, Apr 20, 2019 at 3:32 PM Jeff Morris via samba > <samba at lists.samba.org> wrote: >> My network uses reserved IPv4 addresses (192.168.2.0/24) behind a NAT >> firewall, but public IPv6 addresses behind a filtering firewall. >> >> My ISP (Comcast) assigns both IPv4 and IPv6 addresses dynamically. >>

On Sat, Apr 20, 2019 at 3:32 PM Jeff Morris via samba <samba at lists.samba.org> wrote: > > > My network uses reserved IPv4 addresses (192.168.2.0/24) behind a NAT > firewall, but public IPv6 addresses behind a filtering firewall. > > My ISP (Comcast) assigns both IPv4 and IPv6 addresses dynamically. > > As a result, the IPv4 address of my internal Samba server is

Apologies, one more question. With the edited icecast configuration I provided in my previous reply, netstat now shows the IPV6 binds but not the IPV4 binds. To your knowledge, does this seem correct? The Icecast server seems to be working properly and is accepting listener connections with IPV4 addresses. Just trying to understand why I don?t see 0.0.0.0:8000 for instance. -------------- next

Hi, I would like to run a network firewall as a VM on a KVM host. There are ~ 25 VLANs delivered to the KVM host on three dedicated links, no LACP or other things. I have the VLANs 100-180 on the host's enp1s0, the VLANs 200-280 on the host's enp2s0 and the VLANs 300-380 on the host's enp3s0. To save myself from configuring all VLANs on the KVM host, I'd like to hand the entire

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me

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 :::*

Hi There is a Centos 7 up-to-date box with 2 interfaces, let's say 192.168.1.12 - enp2s0, 192.168.1.13 on enp3s0. Default gateway on enp2s0. The gateway is pfsense, IP is 192.168.1.1 with 2 WAN connections On the gateway the outgoing traffic is routed by source ip to different WAN, 192.168.1.12 to WAN1 and 192.168.1.13 to WAN2 On the centos box are set all the route and routing rules:

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

Thanks for the response. I can confirm that the recommended settings worked and now IPV6 is working as it should. If anyone is interested, these are the <listen-socket> settings I am using. <!-- You may have multiple <listen-socket> elements?> <listen-socket> <port>8000</port> <bind-address>0.0.0.0</bind-address> </listen-socket>

I have setup a CentOS 6.3 VPS with ONLY IPv6 access simply for testing at this point. It browses the Internet with lynx fine on most major sites that are IPv6 enabled. Yum does not seem to work though. Always tries to connect to an IPv4 mirror and gives an error. Is there a way specify an IPv6 mirror to yum?

Hi, My local server is running CentOS 7. The machine has two NICs and is acting as a gateway. For DHCP and DNS, I'm using Dnsmasq. I have a strange little problem with local hostname resolution. Before going into more details, here's my configuration. [root at nestor:~] # ifconfig enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.2 netmask

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

http://www.realvnc.com/products/enterprise/4.1/ipv6.html IPv6 support in VNC Server E4.1.7/P4.1.2 VNC Server E4.1.7 & P4.1.2 are fully IPv6-aware, but is shipped with IPv6 support disabled by default, for security reasons. IPv6 can be enabled by setting "InTransports=IPv6,IPv4" (the default being IPv4 only), either on the command-line when starting vncserver under Unix Ok.

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, 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

I noticed that samba is listening on IPv6, so I became curious and wondered if I could actually use it, and so far, it looks like it isn't usable. Running nbtstat -A fe80::216:3eff:fe6f:1f3a on Windows returns the stupid message that the address must be in the a.b.c.d format. I then tried using nbtlookup from linux: nmblookup -S -U '[fe80::216:3eff:fe6f:1f3a]' \* 10.1.1.232

I have just moved a host from a network that supports static IPv4 and IPv6. The IPv4 addr is set in ifcfg-eth0, and the IPv6 via RA (I set the MAC so I get an IPv6 addr that I like). I just moved the host to a network that supports static IPv4, but only dymanic IPv6, so at this time (until I get static IPv6), I need to disable the global IPv6 addressing. So in the ifcfg-eth0 file I set:

Hi, I realise this might be a Debian-specific question. I've got access to two hosts which have IPv6 connectivity, both of which are running Icecast 2.3.2. One is still running Debian Lenny and can be reached via IPv6 just fine, but the other is running Debian Squeeze and cannot. In addition, my local server which does not have IPv6 conectivity to the Internet but which can be reached

-----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?