search for: ipv4only

Hello Walter, On Mon, 15 May 2017 09:22:54 +0200 "Walter H." <walter.h at mathemainzel.info> wrote: > On Sun, May 14, 2017 11:00, wwp wrote: > > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." > > <Walter.H at mathemainzel.info> wrote: > > > >> On 13.05.2017 00:29, Robert Moskowitz wrote: > >> > I have been working,

...r box, on top of > firewalld/iptables, in order to setup and administrate the NAT/rooting > (and eventually proxy) rules? I've configured it quite simple ... /etc/sysconfig/network_scripts: ifcfg-eth0 and ifcfg-wlan0 have this: BRIDGE=br0 ifcfg-br0 is LAN (Dual-Stack) ifcfg-eth1 is WAN (IPv4only) ifcfg-sit1 is an HE IPv6 tunnel (IPv6only) /etc/hostapd/hostapd.conf has this: interface=wlan0 bridge=br0 /etc/sysconfig/ip(6)tables have at the last lines this: # Log all other -A INPUT -j LOG --log-prefix "IP(v6)[IN]: " --log-level 7 -A FORWARD -j LOG --log-prefix "IP(v6)[FWD]:...

On 16.06.2016 20:51, Warren Young wrote: > On Jun 16, 2016, at 12:41 PM, Walter H.<walter.h at mathemainzel.info> wrote: >> On 16.06.2016 19:40, Frank Cox wrote: >>> On Thu, 16 Jun 2016 19:34:09 +0200 >>> Walter H. wrote: >>> >>>> Yes, but doesn't help ... >>>> the same before ... >>>> >>>> by the way, I

On 10.05.2016 18:57, ????????? ???????? wrote: >> this seems to be relevant in chroot environments; >> >> as I noticed when configuring the DDNS-feature, that this is a little >> bit >> weired, when running in a chroot environment; I saw the >> recommendation not >> to use a chroot in the man-page and removed bind-chroot and then the >> zone