[B! network] nobyukiã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

nobyuki id:nobyuki

networkã«é–¢ã™ã‚‹nobyukiã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (353)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

LANå†…ã§ä½¿ã‚ã‚Œã¦ã„ã‚‹IPã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’èª¿ã¹ã‚‹6ã¤ã®æ–¹æ³•(Linux/Windows) | ä¿ºçš„å‚™å¿˜éŒ² ã€œãªã‚“ã‹ã„ã‚ã„ã‚ã€œ
ä»Šå›žã¯ã€LANå†…ã§åˆ©ç”¨ã•ã‚Œã¦ã„ã‚‹IPã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’èª¿ã¹ã‚‹æ–¹æ³•ã«ã¤ã„ã¦ã‚’ã¾ã¨ã‚ã¦ã¿ãŸã€‚ ç’°å¢ƒã«ã‚ˆã£ã¦ã¯ä½¿ç”¨ã•ã‚Œã¦ã„ã‚‹OSãŒè¤‡æ•°ã‚ã‚‹å ´åˆãŒã‚ã‚‹(ã¨ã„ã†ã‹ã€ãã®æ–¹ãŒå¤šã„)ã®ã§ã€Linuxã¨Windowsã§åˆ†ã‘ã¦è¨˜è¼‰ã™ã‚‹ã€‚ 1.Linuxã®å ´åˆ 1-1.ping + arpã§èª¿ã¹ã‚‹ åŸºæœ¬çš„ãªã‚³ãƒžãƒ³ãƒ‰ã—ã‹ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚Œã¦ã„ãªã„ç’°å¢ƒã§ã¯ã€ã‚„ã¯ã‚Špingã¨arpã‚³ãƒžãƒ³ãƒ‰ã‚’çµ„ã¿åˆã‚ã›ãŸæ–¹æ³•ãŒè‰¯ãåˆ©ç”¨ã•ã‚Œã‚‹ã ã‚ã†ã€‚ ä»¥ä¸‹ã®ã‚ˆã†ã«forã‚³ãƒžãƒ³ãƒ‰ã¨çµ„ã¿åˆã‚ã›ã¦å®Ÿè¡Œã™ã‚‹ã“ã¨ã§ã€IPã‚¢ãƒ‰ãƒ¬ã‚¹ã¨ãã‚Œã«å¯¾å¿œã™ã‚‹MACã‚¢ãƒ‰ãƒ¬ã‚¹ã‚’å–å¾—ã™ã‚‹ã“ã¨ãŒå‡ºæ¥ã‚‹ã€‚ for a in `seq 1 254`; do ping -c 1 -w 0.5 å¯¾è±¡ã‚»ã‚°ãƒ¡ãƒ³ãƒˆ(ç¬¬ï¼“ã‚ªã‚¯ãƒ†ãƒƒãƒˆã¾ã§).$a > /dev/null && arp -a å¯¾è±¡ã‚»ã‚°ãƒ¡ãƒ³ãƒˆ(ç¬¬ï¼“ã‚ªã‚¯ãƒ†ãƒƒãƒˆã¾ã§).$a | grep ether; done test@ubuntu
nobyuki 2018/08/21
Tips

network
ãƒªãƒ³ã‚¯
listen backlog ã€3.6ã€‘ - Linuxã‚«ãƒ¼ãƒãƒ«ãƒ¡ãƒ¢
(*1) backlog(512)ã¯tcp_max_syn_backlog(400)ã‚ˆã‚Šå¤§ãã„ã®ã§ã€400ã‚’åˆ‡ã‚Šä¸Šã’ãŸ512ãŒsyn backlogã®ã‚µã‚¤ã‚ºã«ãªã‚‹ã€‚ syn backlogã®ã‚µã‚¤ã‚ºã‚’å¤§ããã—ã‚ˆã†ã¨ã™ã‚‹ã«ã¯ã€ä»¥ä¸‹ã®ç‚¹ã«æ³¨æ„ã™ã‚‹ã€‚ (a) net.ipv4.tcp_max_syn_backlogã‚’å¤§ããã™ã‚‹ (b) listen()ã§æŒ‡å®šã™ã‚‹backlogå€¤ã‚’å¤§ããã™ã‚‹(apacheãªã‚‰ListenBackLogãƒ‡ã‚£ãƒ¬ã‚¯ãƒ†ã‚£ãƒ–ã§æŒ‡å®šã§ãã‚‹) (c) backlogã®å€¤è‡ªä½“ã¯net.core.somaxconnã«åˆ‡ã‚Šè©°ã‚ã‚‰ã‚Œã‚‹ãŸã‚ã€net.core.somaxconnã®æ–¹ã‚‚å¤§ããã—ã¦ãŠãã€‚ syn backlogã®æœ€å¤§ã‚µã‚¤ã‚ºã¯backlogã‚µã‚¤ã‚ºã«åŸºã¥ã„ã¦æ±ºã¾ã‚‹ãŸã‚ã€net.ipv4.tcp_max_syn_backlogã‚’å¤§ããã™ã‚‹ã ã‘ã§ãªãã€backlogè‡ªä½“ãŒå¤§ãããªã‚‹ã‚ˆã†
nobyuki 2016/12/13
kernel

network
ãƒªãƒ³ã‚¯
statãƒ•ã‚¡ãƒŸãƒªï¼ã®ãƒ¡ãƒ¢ã¨ã€ã‚«ãƒ¼ãƒãƒ«ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚° - Qiita
èª¿æŸ»ã‚’ã™ã‚‹ã¨ãã«ä½¿ã†ãŒã€æ¯Žå›žå¿˜ã‚Œã¦ã—ã¾ã†ã®ã§è‡ªåˆ†ç”¨ã«ãƒ¡ãƒ¢ statãƒ•ã‚¡ãƒŸãƒªãƒ¼ã¾ã¨ã‚ dstat ç¾Žã—ã„ï¼ã€€ç›®ã§è¦‹ã‚‹ãªã‚‰ã“ã‚Œã€‚ æœ€ã‚‚å½¹ã«ç«‹ã¤å‚è€ƒã‚µã‚¤ãƒˆï¼šhttp://qiita.com/harukasan/it ems/b18e484662943d834901 vmstat ãƒ¡ãƒ¢ãƒªã‚„CPUã‚’è¦‹ã‚‹æ™‚ã«ä½¿ã†ã€‚ iostat ãƒ‡ã‚£ã‚¹ã‚¯IOã‚’è¦‹ã‚‹ã¨ãã«ä½¿ã†ã€‚ netstat ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®çŠ¶æ…‹ã‚’è¦‹ã‚‹ã¨ãã«ä½¿ã†ã€‚ ã‚«ãƒ¼ãƒãƒ«ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ã¨KVSè¨å®š net.core.somaxconn TCPã®max connectionæ•°ã€‚ å‚è€ƒã‚µã‚¤ãƒˆï¼šhttp://d.hatena.ne.jp/tetsuyai/20111220/1324466655 ä¾‹ãˆã°memcacheã‚„Redisç‰ã®KVSã‚’ä½¿ã†ã¨ãã¯ã€memcachedã®tcp_backlogã‚„ã€Redisã®maxclientsã®æ•°å€¤ä»¥ä¸Šã«ã‚ã’ãŸã»ã†ãŒã„ã„ã€‚
nobyuki 2016/11/28
Linux

network

kernel
ãƒªãƒ³ã‚¯
net.core.somaxconnã«ã¤ã„ã¦èª¿ã¹ã¦ã¿ãŸ - ç¥ˆã‚Œã€ãã—ã¦åƒã‘ ï½ž Ora et labora
æ¦‚è¦ â†“ memcachedã®tcp_backlogã®ãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã¯1024ã§ã€stats settingsã«ã‚‚1024ã¨è¡¨ç¤ºã•ã‚Œã¦ã„ã‚‹ã®ã§ã™ãŒã€ stats settings ... STAT tcp_backlog 1024 ... ENDâ†“ net.core.somaxconnãŒãƒ‡ãƒ•ã‚©ãƒ«ãƒˆå€¤ã®ã¾ã¾ã ã¨128ã«åˆ‡ã‚Šè©°ã‚ã‚‰ã‚Œã¦ã—ã¾ã„ã€ # cat /proc/sys/net/core/somaxconn 128è² è·ãŒé«˜ã„ã‚µãƒ¼ãƒãƒ¼ã§ã¯æŽ¥ç¶šè¦æ±‚ã‚’å–ã‚Šã“ã¼ã—ã¦ã—ã¾ã†ã“ã¨ãŒã‚ã‚‹ãã†ã§ã™ã€‚ ã“ã®net.core.somaxconnã€Memcacheã‚„MySQLãªã©ã€é«˜è² è·æ™‚ã«å¤šãã®æŽ¥ç¶šè¦æ±‚ã‚’å—ã‘ä»˜ã‘ã‚‹ã‚µãƒ¼ãƒãƒ¼ã§ã¯ãƒãƒ¥ãƒ¼ãƒ‹ãƒ³ã‚°ãŒå¿…è¦ãªã‚«ãƒ¼ãƒãƒ«ãƒ‘ãƒ©ãƒ¡ãƒ¼ã‚¿ã®ã‚ˆã†ã§ã™ã€‚ã„ã£ãŸã„ã©ã†ã„ã†å€¤ãªã®ã‹ã€èª¿ã¹ã¦ã¿ã¾ã—ãŸã€‚ net.core.somaxconnã¨ã¯ TCPã‚½ã‚±ãƒƒãƒˆã¯listen()é–¢æ•°ã®ç¬¬äºŒå¼•æ•° ba
nobyuki 2016/11/25
Linux

kernel

network
ãƒªãƒ³ã‚¯
curlã§SSLã§ã¤ãªã„ã ã¨ãã®SSLã®ãƒ˜ãƒƒãƒ€ã‚’èªã¿ãŸã„ã®ã§ã™ãŒã€ã©ã®ã‚ˆã†ãªæ–¹æ³•ãŒã‚ã‚‹ã§ã—ã‚‡ã†ã‹
curlã§SSLã§ã¤ãªã„ã ã¨ãã®SSLã®ãƒ˜ãƒƒãƒ€ã‚’èªã¿ãŸã„ã®ã§ã™ãŒã€ã©ã®ã‚ˆã†ãªæ–¹æ³•ãŒã‚ã‚‹ã§ã—ã‚‡ã†ã‹
nobyuki 2016/11/24
network

security

Tips
ãƒªãƒ³ã‚¯
How TCP backlog works in Linux
When an application puts a socket into LISTEN state using the listen syscall, it needs to specify a backlog for that socket. The backlog is usually described as the limit for the queue of incoming connections. Because of the 3-way handshake used by TCP, an incoming connection goes through an intermediate state SYN RECEIVED before it reaches the ESTABLISHED state and can be returned by the accept s
nobyuki 2016/11/07
network

Linux
ãƒªãƒ³ã‚¯
ç›¸æ‰‹ãŒã„ãªã„ã®ã« ESTABLISHED ã«ãªã£ã¦ã‚‹ TCP ãƒãƒ¼ãƒˆ - tmtms ã®ãƒ¡ãƒ¢
æœ€è¿‘ ParallelServer ã¨ã„ã†ãƒ©ã‚¤ãƒ–ãƒ©ãƒªã‚’ä½œã£ãŸã®ã§ã™ãŒã€ãã®æœ€ä¸ã«å¥‡å¦™ãªçŠ¶æ…‹ã«ãªã£ã¦ã‚‹ TCP ãƒãƒ¼ãƒˆã‚’è¦‹ã¤ã‘ãŸã®ã§ã€ãƒ¡ãƒ¢ã£ã¦ãŠãã¾ã™ã€‚ Ruby ã§ã¯ TCP ã‚µãƒ¼ãƒãƒ¼ã¯æ¬¡ã®ã‚ˆã†ãªæ„Ÿã˜ã§ä½œã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ãŠæ‰‹è»½ã§ã™ãã€‚ require 'socket' Socket.tcp_server_loop(12345) do |socket, client_addr| socket.puts "Your IP address: #{client_addr.ip_address}" name = socket.gets socket.puts "Hello, #{name}" socket.close end ã“ã‚Œã¯ 12345 ãƒãƒ¼ãƒˆã§ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‹ã‚‰ã®æŽ¥ç¶šã‚’å¾…ã¡ã€æŽ¥ç¶šã•ã‚ŒãŸã‚‰ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã®IPã‚¢ãƒ‰ãƒ¬ã‚¹ã¨ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‹ã‚‰ã®å…¥åŠ›ã‚’ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã«é€ä¿¡ã—ã¦åˆ‡æ–ã™ã‚‹ã ã‘ã®ç°¡å˜ãªãƒ—ãƒã‚°ãƒ©ãƒ
nobyuki 2016/11/07
network

Linux
ãƒªãƒ³ã‚¯
tcpdumpã‚„wiresharkã§TCPåˆ¶å¾¡ãƒ•ãƒ©ã‚°ã‚’æŒ‡å®šã—ã¦ãƒ‘ã‚±ãƒƒãƒˆã‚’åŽé›†ã™ã‚‹æ–¹æ³• - Eiji James Yoshidaã®è¨˜éŒ²
tcpdumpã‚„wiresharkã§TCPåˆ¶å¾¡ãƒ•ãƒ©ã‚°ã‚’æŒ‡å®šã—ã¦ãƒ‘ã‚±ãƒƒãƒˆã‚’åŽé›†ã™ã‚‹æ–¹æ³•ã‚’å¿˜ã‚Œã‚‹ã“ã¨ãŒå¤šã„ã®ã§ãƒ¡ãƒ¢ã€‚ SYNãƒ•ãƒ©ã‚°ãŒè¨å®šã•ã‚ŒãŸãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 2 != 0" SYNãƒ•ãƒ©ã‚°ãŒè¨å®šã•ã‚Œã¦ã„ãªã„ãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 2 == 0" SYNãƒ•ãƒ©ã‚°ã®ã¿è¨å®šã•ã‚ŒãŸãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 255 == 2" ACKãƒ•ãƒ©ã‚°ãŒè¨å®šã•ã‚ŒãŸãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 16 != 0" ACKãƒ•ãƒ©ã‚°ãŒè¨å®šã•ã‚Œã¦ã„ãªã„ãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 16 == 0" ACKãƒ•ãƒ©ã‚°ã®ã¿è¨å®šã•ã‚ŒãŸãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 255 == 16" ACKãƒ•ãƒ©ã‚°ã¨SYNãƒ•ãƒ©ã‚°ãŒè¨å®šã•ã‚ŒãŸãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 18 == 18" ACKãƒ•ãƒ©ã‚°ã¨SYNãƒ•ãƒ©ã‚°ã®ã¿è¨å®šã•ã‚ŒãŸãƒ‘ã‚±ãƒƒãƒˆã®åŽé›† "tcp[13] & 255 ==
nobyuki 2016/10/31
network

tcpdump

Tips
ãƒªãƒ³ã‚¯
ãƒªã‚»ãƒƒãƒˆãƒ‘ã‚±ãƒƒãƒˆã‚’æŠ•ã’ãŸã®ã¯èª°ã ï¼Ÿï½œNetwiz LLC
ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æŽ¥ç¶šä½œæ¥ã‚’è¡Œã†ã¨æ¯Žå›žã®ã‚ˆã†ã«ä½•ã‚‰ã‹ã®å•é¡ŒãŒç™ºç”Ÿã—ã¾ã™ã€‚ pingã¯é€šã‚‹ã®ã«å¯¾å‘å…ˆã®ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯æ©Ÿå™¨ã«TCPã‚³ãƒã‚¯ã‚·ãƒ§ãƒ³ãŒå¼µã‚Œãªã„ã€é€šä¿¡ãŒçªç„¶åˆ‡æ–ã•ã‚ŒãŸã€ãã‚“ãªçµŒé¨“ã‚’ã—ãŸã“ã¨ã¯ã‚ã‚Šã¾ã›ã‚“ã‹ï¼Ÿãã†ã„ã£ãŸäº‹æ…‹ã«éé‡ã—ãŸã¨ãã€æœ¬è¨˜äº‹ãŒãƒˆãƒ©ãƒ–ãƒ«ã®å…ƒã‚’çªãæ¢ã‚ã‚‹æ‰‹æ®µã®ã²ã¨ã¤ã¨ã—ã¦å‚è€ƒã«ãªã‚Œã°å¹¸ã„ã§ã™ã€‚ ãƒ‘ã‚±ãƒƒãƒˆã‚ãƒ£ãƒ—ãƒãƒ£ã§åŽŸå› ã‚’æŽ¢ã‚‹å•é¡Œç™ºç”Ÿã®çŠ¶æ³ã¨ã—ã¦ã€ã‚µãƒ¼ãƒãƒ¼ã¸pingã¯é€šã‚‹ã‘ã‚Œã©sshæŽ¥ç¶šãŒã§ããªã„çŠ¶æ…‹ã‚’æƒ³å®šã—ã¾ã™ã€‚ ã“ã®ã‚ˆã†ãªå ´åˆã€æ¬¡ã®ã‚ˆã†ãªåŽŸå› ãŒè€ƒãˆã‚‰ã‚Œã¾ã™ã€‚ ã‚µãƒ¼ãƒãƒ¼ã®ãƒãƒ¼ãƒˆ22ç•ªãŒé–‰ã˜ã¦ã„ã‚‹ ã‚µãƒ¼ãƒãƒ¼ã®FWæ©Ÿèƒ½ã§å¼¾ã„ã¦ã„ã‚‹ çµŒè·¯ä¸Šã®FWã§å¼¾ã„ã¦ã„ã‚‹ åŽŸå› ã‚’æŽ¢ã‚‹ãŸã‚ãƒ‘ã‚±ãƒƒãƒˆã‚ãƒ£ãƒ—ãƒãƒ£ã—ãŸã¨ã“ã‚ã€ã‚µãƒ¼ãƒãƒ¼ã®IPã‚¢ãƒ‰ãƒ¬ã‚¹ã‹ã‚‰ãƒªã‚»ãƒƒãƒˆãƒ‘ã‚±ãƒƒãƒˆãŒé€ä¿¡ã•ã‚Œã¦ã„ã‚‹äº‹ãŒã‚ã‹ã‚Šã¾ã—ãŸã€‚pingã¯å•é¡Œãªãé€šã‚Šã¾ã™ã€‚ ãã“ã§å•é¡Œã§ã™ã€‚ ãƒªã‚»ãƒƒãƒˆãƒ‘ã‚±ãƒƒãƒˆã‚’é€ã£ãŸã®ã¯èª°ã§ã—ã‚‡ã†ã‹ï¼Ÿæ¬¡ã®ãƒ‘ã‚±ãƒƒãƒˆã‚ãƒ£ãƒ—ãƒãƒ£
nobyuki 2016/10/25
network

Tips
ãƒªãƒ³ã‚¯
What causes the ENOTCONN error?
I'm currently maintaining some web server software and I need to perform a lot of I/O operations. The read(), write(), close() and shutdown() calls, when used on a socket, may sometimes raise an ENOTCONN error. What exactly does this error mean? What are the conditions that would trigger it? I can never seem to reproduce it locally but there are users who can. Right now I just ignore ENOTCONN when
nobyuki 2016/10/19
network

*programming

Tips
ãƒªãƒ³ã‚¯
hiboma/getpeernameã‹ã‚™ENOTCONNã‚’è¿”ã™ã‚±ãƒ¼ã‚¹.md at master Â· hiboma/hiboma
nobyuki 2016/10/19
network

*programming

Tips
ãƒªãƒ³ã‚¯
Sep. 2016
#ihatedumbpeople 2016-09-30 [Fri] 12:43 Rant. So I went to this bank with about 10 ATM machines, and they're all filled with people, doing kernel hacking or something. But no, they're just struggling to draw cash. There's a huge line. I was at the bottom and enraged. "WTF ARE THEZE PEOPEL DOIN?!" The whole process took about 10 minutes. What kind of black magic takes you more than a minute to just
nobyuki 2016/09/23
network

*ç¤¾ä¼š
ãƒªãƒ³ã‚¯
ã€ŒOPEN IPv6 ãƒ€ã‚¤ãƒŠãƒŸãƒƒã‚¯ DNS for ãƒ•ãƒ¬ãƒƒãƒ„ãƒ»å…‰ãƒã‚¯ã‚¹ãƒˆã€ã‚µãƒ¼ãƒ“ã‚¹ã‚’å…¬é–‹ - ã‚½ãƒ•ãƒˆã‚¤ãƒ¼ã‚µæ ªå¼ä¼šç¤¾ ä»£è¡¨å–ç· å½¹ ç™» å¤§éŠ
2016 å¹´ 6 æœˆ 14 æ—¥ (ç«) ç‘æ³¢å¤§å¦ç™ºãƒ™ãƒ³ãƒãƒ£ãƒ¼ ã‚½ãƒ•ãƒˆã‚¤ãƒ¼ã‚µæ ªå¼ä¼šç¤¾ ä»£è¡¨å–ç· å½¹ ç™» å¤§éŠ ã€ŒOPEN IPv6 ãƒ€ã‚¤ãƒŠãƒŸãƒƒã‚¯ DNS for ãƒ•ãƒ¬ãƒƒãƒ„ãƒ»å…‰ãƒã‚¯ã‚¹ãƒˆã€ã‚µãƒ¼ãƒ“ã‚¹ã‚’å…¬é–‹ NTT æ±æ—¥æœ¬ã®ãƒ•ãƒ¬ãƒƒãƒ„å›žç·šé–“ã§ VPN æ©Ÿå™¨ã‚„ IoT æ©Ÿå™¨åŒå£«ã®ãƒ•ãƒ¬ãƒƒãƒ„ç¶²å†…ã®é«˜é€Ÿãƒ»ä½Žé…å»¶ã®ç›´æŽ¥é€šä¿¡ã‚’å®Ÿç¾ ã‚½ãƒ•ãƒˆã‚¤ãƒ¼ã‚µæ ªå¼ä¼šç¤¾ã¯ã€æœ¬æ—¥ã€ã€ŒOPEN IPv6 ãƒ€ã‚¤ãƒŠãƒŸãƒƒã‚¯ DNS for ãƒ•ãƒ¬ãƒƒãƒ„ãƒ»å…‰ãƒã‚¯ã‚¹ãƒˆã€ã‚µãƒ¼ãƒ“ã‚¹ (https://i.open.ad.jp/) ã®ãƒ™ãƒ¼ã‚¿ç‰ˆã‚’æä¾›é–‹å§‹ã—ã¾ã—ãŸã€‚ ã“ã®ç„¡å„Ÿã®ãƒ€ã‚¤ãƒŠãƒŸãƒƒã‚¯ DNS (DDNS) ã‚µãƒ¼ãƒ“ã‚¹ã‚’åˆ©ç”¨ã™ã‚‹ã¨ã€NTT æ±æ—¥æœ¬ã®ã™ã¹ã¦ã®ã‚¨ãƒªã‚¢ã® 1,066 ä¸‡æœ¬ã®ã™ã¹ã¦ã®ãƒ•ãƒ¬ãƒƒãƒ„å›žç·šä¸Šã§ã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆã‹ã‚‰çµ¶å¯¾ã«ä¸æ£ä¾µå…¥ã•ã‚Œã‚‹ãŠãã‚Œã®ãªã„ã€å¤§å¤‰é«˜é€Ÿã‹ã¤ä½Žé…å»¶ãª VPN ã‚’ã€ç°¡å˜ã«æ§‹ç¯‰ã§ãã¾ã™ (æ³¨ 1)ã€‚ã¾ãŸã€IoT æ©Ÿå™¨ã‚’ãƒ•ãƒ¬ãƒƒãƒ„ç¶²ã«ç›´
nobyuki 2016/06/14
Technology

VPN

network
ãƒªãƒ³ã‚¯
å…¨å°ä¸é«˜ã«ç„¡ç·šLANã€€é›»åæ•™ç§‘æ›¸ã«å¯¾å¿œã€20å¹´ã¾ã§ã« - æ—¥æœ¬çµŒæ¸ˆæ–°èž
ç·å‹™çœã¯2020å¹´ã¾ã§ã«å…¨å›½ã™ã¹ã¦ã®å°ãƒ»ä¸ãƒ»é«˜æ ¡ã«ç„¡ç·šLANã€ŒWi-Fiã€ã‚’å°Žå…¥ã™ã‚‹æ–¹é‡ã ã€‚æ•™ç§‘æ›¸ã®å†…å®¹ã‚’ã‚¿ãƒ–ãƒ¬ãƒƒãƒˆç«¯æœ«ãªã©ã«åŽã‚ãŸã€Œãƒ‡ã‚¸ã‚¿ãƒ«æ•™ç§‘æ›¸ã€ã®æ™®åŠã«å‘ã‘ã€å°Žå…¥è²»ç”¨ã®åŠåˆ†ã‚’è£œåŠ©ã™ã‚‹ã€‚ç½å®³æ™‚ã«ã¯é¿é›£è€…ã«é–‹æ”¾ã—ã€æºå¸¯é›»è©±ã®åŸºåœ°å±€ãŒæ•…éšœã—ã¦ã‚‚ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆã‚„é›»åãƒ¡ãƒ¼ãƒ«ã‚’ä½¿ãˆã‚‹ã‚ˆã†ã«ã™ã‚‹ã€‚ç¾åœ¨ã€ç„¡ç·šLANã‚’åˆ©ç”¨ã§ãã‚‹å°ãƒ»ä¸ãƒ»é«˜æ ¡ã®æ•™å®¤ã¯24%ã«ã¨ã©ã¾ã‚‹ã€‚ç·å‹™çœã¯ã¾ãšä»Šå¤ã«ã¤ãã‚‹17å¹´åº¦æ”¿åºœäºˆç®—
nobyuki 2016/05/09
*edu

*programming

Technology

network
ãƒªãƒ³ã‚¯
JF: Linux Kernel 2.6 Documentation: bonding.txt
Linux Kernel 2.6 Documentation: /usr/src/linux/Documentation/networking/bonding.txt networking/bonding.txt Linux bonding ãƒ‰ãƒ©ã‚¤ãƒã®è¨å®šæ–¹æ³• [ãƒ—ãƒ¬ã‚¤ãƒ³ãƒ†ã‚ã‚¹ãƒˆç‰ˆ] åŽŸè‘—ä½œè€…: Thomas Davis <tadavis at lbl.gov> ç¿»è¨³è€…: Akira Yoshiyama <yosshy at debian dot or dot jp> ãƒãƒ¼ã‚¸ãƒ§ãƒ³: 2.6.25 ç¿»è¨³æ—¥æ™‚: 2008/02/20 Linux Ethernet Bonding Driver HOWTO % Latest update: 12 November 2007 % æœ€çµ‚æ›´æ–°ï¼š2007å¹´11æœˆ12æ—¥ %Initial release : Thomas Davis <tadavis at
nobyuki 2015/12/25
network

bonding

*reference
ãƒªãƒ³ã‚¯
RHEL6ã®ãƒžãƒ«ãƒã‚ãƒ¥ãƒ¼ã§åŠ¹çŽ‡çš„ãªãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®ä»˜åŠ åˆ†æ•£
ç”³ã—è¨³ã‚ã‚Šã¾ã›ã‚“ã€‚ãŠæŽ¢ã— Dell TechCenterãƒšãƒ¼ã‚¸ãŒè¦‹ã¤ã‹ã‚Šã¾ã›ã‚“ã€‚ ãŠæŽ¢ã—ã®ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã¯åˆ©ç”¨ã§ããªããªã‚Šã¾ã—ãŸãŒã€æ¬¡ã®ãƒªãƒ³ã‚¯ã§é¡žä¼¼ã‚³ãƒ³ãƒ†ãƒ³ãƒ„ãŒè¦‹ã¤ã‹ã‚‹å ´åˆãŒã‚ã‚Šã¾ã™ã€‚ DellãƒŠãƒ¬ãƒƒã‚¸ ãƒ©ã‚¤ãƒ–ãƒ©ãƒªãƒ¼<ã‚’æ¤œç´¢ã—ã¾ã™ã€‚ Dell.com ã«é–¢ã™ã‚‹ ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ ãƒ¼ ãƒ‡ã‚£ã‚¹ã‚«ãƒƒã‚·ãƒ§ãƒ³ã«å‚åŠ ã—ã¾ã—ã‚‡ã†ã€‚ ãã‚Œã§ã‚‚ã€è³ªå•ãŒã‚ã‚Šã¾ã™ã‹? ä¸‹ã®ãƒ•ã‚£ãƒ¼ãƒ‰ãƒãƒƒã‚¯é ˜åŸŸã‹ã‚‰è³ªå•ã‚’é€ä¿¡ã—ã¦ãã ã•ã„ã€‚
nobyuki 2015/12/25
network

bonding
ãƒªãƒ³ã‚¯
Rise of the STUPID Network
The Rise of the Stupid Network was originally written during a single long weekend in May 1997 by David S. Isenberg while he was an employee of AT&T Labs Research. It was officially released onto the Internet by AT&T in June 1997. It was printed (without permission, with some bad editing, and with the last few hundred words truncated) by Computer Telephony in its August 1997 issue. If you want to
nobyuki 2015/07/17
network

*reference
ãƒªãƒ³ã‚¯
ã€ŒStupid Network ã®ã‚ã‘ã¼ã®ã€ rise_of_stupid-j.pdf
Stupid Network (â€œRise of the Stupid Network1â€) David S. Isenberg ([email protected] - www.isen.com) (m-sato@remus.dti.ne.jp) â€¢ â€¢ â€¢ â€¢ â€¢ 20 1000 1 â€¢ 20 2 â€¢ â€¢ Ethernet 1Copyright 1998 by ACM, originally appeared in ACM netWorker, Feb./March 1998 â€¢ 4 Stupid Network â€¢ â€¢ â€¢ Stupid Network : Sprint, MCI, GTE, SNET 70 1979 6 2 2000 11 1000 1 70 4 10,000 510-547-0000, 0001, 0002, 510-547-9999 10,000 10 1 ? SS7
nobyuki 2015/07/16
network
ãƒªãƒ³ã‚¯
srad.jp
Weâ€™re getting things ready Loading your experienceâ€¦ This wonâ€™t take long.
nobyuki 2015/07/16
network
ãƒªãƒ³ã‚¯
World IPv6 Launchã¨NTT IPv6é–‰åŸŸç¶²ã‚’å·¡ã‚‹é§†ã‘å¼•ã - DNSã§ã®AAAAãƒ•ã‚£ãƒ«ã‚¿:Geekãªãºãƒ¼ã˜
ä»Šå¹´ã«å…¥ã£ã¦ãã‚‰ã„ã‹ã‚‰å„ç¨®æ–¹é¢ã§è©±é¡Œã¨ã—ã¦ç™»å ´ã™ã‚‹ã“ã¨ãŒå¢—ãˆã¦ã„ã‚‹NTT IPv6é–‰åŸŸç¶²ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯å•é¡Œã§ã™ãŒã€å®Ÿã¯å˜ãªã‚‹æŠ€è¡“çš„ãªå•é¡Œã¨ã„ã†ã‚ã‘ã§ã¯ãªãã€ã‚ã‚‹ç¨®æ”¿æ²»çš„ãªã€Œé§†ã‘å¼•ãã€ã§ã‚ã‚‹ã¨ã„ã†ã®ãŒç§ã®æ„Ÿæƒ³ã§ã™ã€‚ å¤šãã®æ–¹ã€…ã«ã¨ã£ã¦ã¯ã€ŒWorld IPv6 LaunchãŒé–‹å‚¬ã•ã‚Œã¦ã€ãã‚Œä»¥é™ã¯ãƒ•ãƒ¬ãƒƒãƒ„å…‰ãƒ¦ãƒ¼ã‚¶ãŒå›°ã‚‹ã€ãã‚‰ã„ã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã ã¨æ€ã„ã¾ã™ãŒã€å®Ÿã¯ã‚‚ã†å°‘ã—è¤‡é›‘ã§ã™ã€‚ NTT IPv6é–‰åŸŸç¶²ãƒ•ã‚©ãƒ¼ãƒ«ãƒãƒƒã‚¯å•é¡Œã«å¯¾ã—ã¦ã©ã†å¯¾å‡¦ã™ã‚‹ã®ã‹ã¯ã€ã‚³ãƒ³ãƒ†ãƒ³ãƒ„äº‹æ¥è€…ã€ISPã€JAIPAã€NTTã«ã‚ˆã‚‹ä¸€ç¨®ã®é§†ã‘å¼•ãã¨ãªã‚Šã¤ã¤ã‚ã‚Šã¾ã™ã€‚ å®Ÿã¯ã€ã“ã®è©±é¡Œã«é–¢ã—ã¦çµæ§‹å¤šãã®å…¬é–‹æƒ…å ±ãŒã‚ã‚‹ã®ã§ã™ãŒã€ã‚ã¾ã‚Šãã‚Œã‚‰ã‚’ã¾ã¨ã‚ã¦èªžã£ã¦ã„ã‚‹è¨˜äº‹ãŒãªã•ãã†ãªã®ã§æ›¸ã„ã¦ã¿ã¾ã—ãŸã€‚ 2011å¹´ã®World IPv6 Dayã®è©•ä¾¡ ä»Šå¹´ã®6æœˆ6æ—¥ã«è¡Œã‚ã‚Œã‚‹äºˆå®šã®World IPv6 Launchã‚’å·¡ã‚‹é§†ã‘å¼•ãã‚’çŸ¥ã‚‹ã«ã¯ã€æ˜¨å¹´è¡Œã‚
nobyuki 2015/07/02
network
ãƒªãƒ³ã‚¯
1 2 3 4 5 6 7 8 9 10 æ¬¡ã®ãƒšãƒ¼ã‚¸