Ntpd not updating

bathroom-blowjob

With net.ipv6all.forwarding=1 it works for me now and net.ipv6.bindv6only=0 on my system.netstat still shows only tcp6 bind but curl to the ipv4 ip works, so forwarding does the [email protected]:~$ sysctl net.ipv6.bindv6only net.ipv6.bindv6only = 0 [email protected]:~$ sysctl net.ipv6all.forwarding net.ipv6all.forwarding = 1 [email protected]:~$ uname -a Linux vagrant-ubuntu-saucy-64 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [email protected]:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=13.10 DISTRIB_CODENAME=saucy DISTRIB_DESCRIPTION="Ubuntu 13.10" [email protected]:~$ sysctl net.ipv6.bindv6only net.ipv6.bindv6only = 0 [email protected]:~$ sysctl net.ipv6all.forwarding net.ipv6all.forwarding = 1 [email protected]:~$ sudo netstat -tapn Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0. 0.0.0.0:* LISTEN 544/sshd tcp 0 192 192. 192.752 ESTABLISHED 1111/sshd: docker [ tcp 0 0 :::22 :::* LISTEN 544/sshd tcp 0 0 :::8080 :::* LISTEN 567/docker tcp 0 0 :::4243 :::* LISTEN 567/docker [email protected]:~$ telnet 127.0.0.1 8080 Connection closed by foreign host [email protected]:~$ ssh 127.0.0.1 The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.TCP *:8000 (LISTEN) docker 9629 9632 root 7u IPv6 ...TCP *:8000 (LISTEN) docker 9629 9633 root 7u IPv6 ... If I were to do 'telnet -4 localhost 80' in the example above it would connect through.TCP *:8000 (LISTEN) docker 9629 9634 root 7u IPv6 ... (frowny) # uname -a Linux d08-00-27-49-4f-76 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # docker -v Docker version 0.6.4, build # netstat -ntple Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0. 0.0.0.0:* LISTEN 0 7904 898/sshd tcp 0 0 127.0.0. 0.0.0.0:* LISTEN 0 8151 926/sendmail tcp 0 0 :::80 :::* LISTEN 0 8760 966/docker tcp 0 0 :::22 :::* LISTEN 0 7906 898/sshd tcp 0 0 :::443 :::* LISTEN 0 8755 966/docker # docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 51bd237afd47 proxy:latest nginx 14 minutes ago Up 12 minutes 0.0.0.3-/0.7.1. It doesn't work for external connections, but I think that is a different issue.TCP *:8000 (LISTEN) docker 9629 9698 root 7u IPv6 ... sudo netstat -ntple Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0. 0.0.0.0:* LISTEN 520/sshd tcp 0 0 :::49153 :::* LISTEN 684/docker tcp 0 0 :::4243 :::* LISTEN 684/docker tcp 0 0 :::22 :::* LISTEN 520/sshd on linux, by default, net.ipv6.bindv6only is 0, so ipv4 packets could also be received from ipv6 sockets with ipv4-mapped ipv6 address.

UPDATE: yeah, just destroyed and recreated the VM and now it's fine.Yay computers ;) I think (from memory) you can force the binding to IPv4 in the proxy setup function.On my server the NAT rules change the target address and forwards the packet that way. So I still think any issues people are having are caused by something else like firewall rules.ECDSA key fingerprint is :9e:72:dd:fd:0f:37:3b:58:e:3d:c0:7a:30. Are you sure you want to continue connecting (yes/no)? [email protected]:/# netstat -tapn Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0. 0.0.0.0:* LISTEN 15/sshd tcp6 0 0 :::8080 :::* LISTEN 20/java tcp6 0 0 :::22 :::* LISTEN 15/sshd The fact that the same container works on Arch Linux, but not on boot2docker Linux indicates that something may not be configured correctly in boot2docker. The few relevant google results I find indicate that You are having a different issue, and it has nothing to do with this bug.

thus you only need to listen on tcp6 socket and we can support both ipv4 and ipv6.if you want explicitly only listen on ipv4 port, you will have to use net. I tried another box and it worked even though I only had the tcp6 port listed in netstat.

terrem43.ru

72 Comments

  1. Pingback:

  2. eric   •  

    -Embossed on the base is MISSION DRY CORP., some numbers & letters, and a symbol. It is apparent that the answer to Question #1 is "YES" since this bottle has raised embossing in the form of the "swirls" on the shoulder.

  3. eric   •  

    He NEVER fails; something that's important to me right now. Matthew 22:9 NIV 'So go to the street corners and invite to the banquet anyone you find.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>