search for: docker0

Hello, I have started playing around with docker (https://www.docker.io/) and am having trouble to integrate the "docker0" bridge it creates on the fly into my shorewall setup (version 4.5.16.1) on debian testing. IP forwarding is on and I have defined a "doc" ipv4 zone and the interfaces has an entry like so, > doc docker0 tcpflags,nosmurfs,logmartians,bridge,routeback,optional and "...

...0.0.0/0 tcp dpt:80 state NEW,ESTABLISHED > 0 0 ACCEPT tcp -- eth0 * 0.0.0.0/0 > 0.0.0.0/0 tcp dpt:443 state NEW,ESTABLISHED > 0 0 ACCEPT all -- lo * 0.0.0.0/0 > 0.0.0.0/0 > 0 0 ACCEPT all -- docker0 * 0.0.0.0/0 > 0.0.0.0/0 > 0 0 ACCEPT udp -- eth0 * 0.0.0.0/0 > 0.0.0.0/0 udp spt:53 > 0 0 ACCEPT tcp -- * * 0.0.0.0/0 > 0.0.0.0/0 tcp dpt:80 limit: avg 25/min burst 100 > 0 0 ACCEPT...

Hi, I've been able to get tinc setup when I flush all my iptables, but after enabling iptables and a delay I get a "Destination Net Unknown". I have three host (HOME10.0.3.2, MASTER 10.0.3.1, WEB 10.0.3.3) MASTER and WEB are in Digital ocean in the same data centre. HOME <---> MASTER <---> WEB I've tried multiple forwarding/masquerading/etc rules and

...h0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 state NEW,ESTABLISHED 0 0 ACCEPT tcp -- eth0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 state NEW,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT all -- docker0 * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT udp -- eth0 * 0.0.0.0/0 0.0.0.0/0 udp spt:53 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 limit: avg 25/min burst 100 0 0 ACCEPT udp -- * * 0.0.0....

...2/tcp open? > > You will see it if you check the netfilter rules with: > > iptables -L -n -v --line -t filter > iptables -L -n -v --line -t nat In fact these rules forward port 5432 to docker: $ iptables -L -n -v --line -t filter | grep 5432 1 0 0 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.2 tcp dpt:5432 $ iptables -L -n -v --line -t nat | grep 5432 10 0 0 MASQUERADE tcp -- * * 172.17.0.2 172.17.0.2 tcp dpt:5432 2 0 0 DNAT tcp -- !docker0 * 0.0.0.0/0 0.0.0.0/0 tcp...

Hi, this puzzles me: On one of our developer workstations, all ports with the exception of SSH are closed: $ firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: eno1 sources: services: ssh dhcpv6-client ports: 22/tcp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: $ but still port

Hi, I haven't been to find this (NetworkManager) change documented. On: CentOS Linux release 7.1.1503 (Core) $ /bin/nmcli con NAME UUID TYPE DEVICE ens32 7629e52d-bd42-4cd5-a424-8c58e7e0bf37 802-3-ethernet ens32 On: CentOS Linux release 7.2.1511 (Core) $ /bin/nmcli con NAME UUID TYPE

...S 7.2.1511 boxes or VMs that were recently upgraded: /bin/nmcli con NAME UUID TYPE DEVICE virbr0 ccd9a252-0765-4e88-bb5d-bfc34eb278e3 bridge virbr0 enp5s0 ccbafeb6-ce6c-4713-b1ac-2cd0705bf16e 802-3-ethernet enp5s0 docker0 a4d7d1e6-0eb2-47d7-8c7e-b63cdc9d8f8d bridge docker0 virbr1-nic 9de87ba3-5c90-490a-b7f1-e273b0525fac generic virbr1-nic virbr1 0638f08b-b6c9-4e66-aee2-f64f2764ecf4 bridge virbr1 virbr0-nic b4b74c7e-1571-4a58-a1b4-0a72894e667a generic virbr0-nic cat /etc/centos-r...

...elated to these bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1186757 and https://bugzilla.redhat.com/show_bug.cgi?id=1235726??. RedHat knowledge article https://access.redhat.com/solutions/1562963 b/ Network: same problem as with keyboard. I configured network adapter but after first boot, a docker0 bridge is created with a totally different IP address: 172.17.0.1/16. Why? Another bug? c/ Disk partitions: I have created the following partitions at first stage: /boot, swap, /, /tmp, /var ... and installation fails ... Selecting only /boot, swap and /, installation works ok, like it does with...

...ot; Dez 27 12:46:22 froodo.org dockerd-current[15041]: time="2018-12-27T12:46:22.700417054+01:00" level=info msg="Firewalld running: true" Dez 27 12:46:22 froodo.org dockerd-current[15041]: time="2018-12-27T12:46:22.903025438+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" Dez 27 12:46:22 froodo.org dockerd-current[15041]: Error starting daemon: Error initializing network controller: Error creating default "bridge" network: could not find an av...

...0x20<link> ether 02:42:0d:d5:dd:97 txqueuelen 0 (Ethernet) RX packets 5577 bytes 3892905 (3.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1731 bytes 172505 (172.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:f7:e2:f2:17 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX pack...

...d) chain. All other packets may then be processed by the docker chains. Something like: chain my-forward { type filter hook forward priority -1; policy drop; # The web server lives in a docker container. iifname "eth0" oifname "docker0" tcp dport { 80, 443 } accept } chain DOCKER-USER { # In case the previous decision was drop, then drop it here too. meta previous-decision drop drop # All other packets are procesed by the docker chain(s). } Is it possi...

...Name: p3x-dc.patrikx3.com Address: *2001:470:1f1b:5b5:eeaa:a0ff:fe1b:4d84* Name: p3x-dc.patrikx3.com Address: 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 *no i idea where it gets. it should as if shows in my ifconfig (the blond that it should do with the dlz, where it gives this numbers i have no idea):* docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:29:44:41:78 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes...

On 03/08/2019 11:17, Patrik wrote: > the problem is that dnsupdate is not working becuase i use dlz. i > cannot use dbsupdate with dnsupdate it fails. > *_ > _* What is 'dbsupdate' ? I can assure you that dnsupdate does work with dlz. I think you need to give us more info. Rowland

... From your output below.. >> Uncomment only single database line, depending on your BIND version << Then tell uss, why are 3 lines uncommented? I suggest, run : https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Anonimize it where needed, and show me your server setup. Greetz, Louis > -----Oorspronkelijk bericht----- > Van:

Hi, I want to use samba as AD. everything seemed to be ok so far with the install and the config. STATUS=daemon 'smbd' finished starting up and ready to serve connections Feb 27 10:34:03 ip-1XX winbindd[22083]: [2020/02/27 10:34:03.002858, 0] ../lib/util/become_daemon.c:124(daemon_ready) Feb 27 10:34:03 ip-1XX winbindd[22083]: STATUS=daemon 'winbindd' finished starting up and

...loaded [ 12.639548] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u1u4: link becomes ready [ 12.646186] asix 1-1.4:1.0 enp0s20u1u4: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 12.927334] Netfilter messages via NETLINK v0.30. [ 12.948772] ip_set: protocol 6 [ 13.200117] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready [ 17.446609] tun: Universal TUN/TAP device driver, 1.6 [ 17.446611] tun: (C) 1999-2004 Max Krasnyansky <maxk at qualcomm.com> [ 17.495950] virbr0: port 1(virbr0-nic) entered blocking state [ 17.495954] virbr0: port 1(virbr0-nic) entered disabled state [ 17.496129]...