- 세상의 모든 계산기 자유(질문) 게시판 일반 ()
iptime 공유기 (AX2004T), 유선 핑 테스트 결과 (Ping Test)
-
- 2025.09.27 - 14:20 2025.09.24 - 18:02 5682 11
테스트 장비
- 공유기#1 : Asus AC-68U
- 공유기#2 : iptime AX2004T
ㄴ https://prod.danawa.com/info/?pcode=95848220&keyword=ax2004t&cate=112804
- 노트북 : HP Victus, Realtek RTL8852AE WiFi6, Realtek Gaming GbE Family Controller
테스트 절차
* 정확한 값을 얻기 위해 파이썬 ping3 라이브러리를 활용함.
* 노트북(윈도우11) 에서 ping 을 대략 100회 정도 실시함.
* 노트북과 공유기는 장애물 없이 50cm 정도 떨어져 있음.
* 공유기#2(AX2004T)에는 노트북 외에 물려있는 장치는 없고, 테스트 중 다른 작업 하지 않음.
* 공유기#1(AC-68U)에는 원래 집에서 쓰던 각종 저부하 장치(WIFI) 그대로 연결되어 있음.
테스트 결과
| 테스트 | 경로 | 패킷 손실 | 응답속도(평균) | 응답속도(최소/최대) | 표준편차 |
| 1 | 노트북→유선→공유기#2 (AX2004T) | 0.0% | 1.469 ms | 0.807 / 13.924 ms | 1.763 ms |
| 2 | 노트북→유선→공유기#2→유선→공유기#1 | 0.0% | 1.932 ms | 1.152 / 17.853 ms | 2.219 ms |
| 3 | 노트북→유선→공유기#1 (AC-68U) | 0.0% | 1.095 ms | 0.903 / 2.730 ms | 0.205 ms |
DATA
# 테스트 1 : 노트북 ->유선->공유기#2(192.168.23.1) C:\Users\creer>C:\Users\creer\gemini\ping_us.py 192.168.23.1 -n 100 Pinging 192.168.23.1 with 32 bytes of data: Reply from 192.168.23.1: seq=0 time=1.066ms Reply from 192.168.23.1: seq=1 time=0.963ms Reply from 192.168.23.1: seq=2 time=0.981ms Reply from 192.168.23.1: seq=3 time=0.917ms Reply from 192.168.23.1: seq=4 time=0.911ms Reply from 192.168.23.1: seq=5 time=0.958ms Reply from 192.168.23.1: seq=6 time=0.878ms Reply from 192.168.23.1: seq=7 time=1.043ms Reply from 192.168.23.1: seq=8 time=5.022ms Reply from 192.168.23.1: seq=9 time=0.973ms Reply from 192.168.23.1: seq=10 time=0.990ms Reply from 192.168.23.1: seq=11 time=1.108ms Reply from 192.168.23.1: seq=12 time=0.998ms Reply from 192.168.23.1: seq=13 time=8.056ms Reply from 192.168.23.1: seq=14 time=1.002ms Reply from 192.168.23.1: seq=15 time=1.002ms Reply from 192.168.23.1: seq=16 time=1.093ms Reply from 192.168.23.1: seq=17 time=1.050ms Reply from 192.168.23.1: seq=18 time=1.972ms Reply from 192.168.23.1: seq=19 time=0.946ms Reply from 192.168.23.1: seq=20 time=0.916ms Reply from 192.168.23.1: seq=21 time=1.059ms Reply from 192.168.23.1: seq=22 time=0.997ms Reply from 192.168.23.1: seq=23 time=1.087ms Reply from 192.168.23.1: seq=24 time=0.937ms Reply from 192.168.23.1: seq=25 time=0.973ms Reply from 192.168.23.1: seq=26 time=0.916ms Reply from 192.168.23.1: seq=27 time=0.954ms Reply from 192.168.23.1: seq=28 time=1.122ms Reply from 192.168.23.1: seq=29 time=0.993ms Reply from 192.168.23.1: seq=30 time=0.974ms Reply from 192.168.23.1: seq=31 time=1.022ms Reply from 192.168.23.1: seq=32 time=0.971ms Reply from 192.168.23.1: seq=33 time=1.024ms Reply from 192.168.23.1: seq=34 time=0.912ms Reply from 192.168.23.1: seq=35 time=0.965ms Reply from 192.168.23.1: seq=36 time=1.090ms Reply from 192.168.23.1: seq=37 time=1.240ms Reply from 192.168.23.1: seq=38 time=0.957ms Reply from 192.168.23.1: seq=39 time=1.083ms Reply from 192.168.23.1: seq=40 time=0.944ms Reply from 192.168.23.1: seq=41 time=0.971ms Reply from 192.168.23.1: seq=42 time=1.880ms Reply from 192.168.23.1: seq=43 time=1.020ms Reply from 192.168.23.1: seq=44 time=1.073ms Reply from 192.168.23.1: seq=45 time=0.969ms Reply from 192.168.23.1: seq=46 time=1.091ms Reply from 192.168.23.1: seq=47 time=4.338ms Reply from 192.168.23.1: seq=48 time=1.029ms Reply from 192.168.23.1: seq=49 time=1.070ms Reply from 192.168.23.1: seq=50 time=0.992ms Reply from 192.168.23.1: seq=51 time=1.107ms Reply from 192.168.23.1: seq=52 time=1.043ms Reply from 192.168.23.1: seq=53 time=1.140ms Reply from 192.168.23.1: seq=54 time=1.045ms Reply from 192.168.23.1: seq=55 time=1.039ms Reply from 192.168.23.1: seq=56 time=0.972ms Reply from 192.168.23.1: seq=57 time=1.034ms Reply from 192.168.23.1: seq=58 time=1.005ms Reply from 192.168.23.1: seq=59 time=13.924ms Reply from 192.168.23.1: seq=60 time=1.904ms Reply from 192.168.23.1: seq=61 time=0.911ms Reply from 192.168.23.1: seq=62 time=0.807ms Reply from 192.168.23.1: seq=63 time=1.078ms Reply from 192.168.23.1: seq=64 time=1.008ms Reply from 192.168.23.1: seq=65 time=1.031ms Reply from 192.168.23.1: seq=66 time=1.154ms Reply from 192.168.23.1: seq=67 time=1.020ms Reply from 192.168.23.1: seq=68 time=0.970ms Reply from 192.168.23.1: seq=69 time=6.911ms Reply from 192.168.23.1: seq=70 time=0.966ms Reply from 192.168.23.1: seq=71 time=0.960ms Reply from 192.168.23.1: seq=72 time=0.947ms Reply from 192.168.23.1: seq=73 time=0.971ms Reply from 192.168.23.1: seq=74 time=1.006ms Reply from 192.168.23.1: seq=75 time=1.062ms Reply from 192.168.23.1: seq=76 time=1.950ms Reply from 192.168.23.1: seq=77 time=1.159ms Reply from 192.168.23.1: seq=78 time=0.942ms Reply from 192.168.23.1: seq=79 time=0.979ms Reply from 192.168.23.1: seq=80 time=1.024ms Reply from 192.168.23.1: seq=81 time=1.100ms Reply from 192.168.23.1: seq=82 time=1.002ms Reply from 192.168.23.1: seq=83 time=0.964ms Reply from 192.168.23.1: seq=84 time=0.959ms Reply from 192.168.23.1: seq=85 time=0.941ms Reply from 192.168.23.1: seq=86 time=3.217ms Reply from 192.168.23.1: seq=87 time=1.004ms Reply from 192.168.23.1: seq=88 time=1.031ms Reply from 192.168.23.1: seq=89 time=0.965ms Reply from 192.168.23.1: seq=90 time=0.890ms Reply from 192.168.23.1: seq=91 time=1.139ms Reply from 192.168.23.1: seq=92 time=1.142ms Reply from 192.168.23.1: seq=93 time=8.522ms Reply from 192.168.23.1: seq=94 time=1.317ms Reply from 192.168.23.1: seq=95 time=0.954ms Reply from 192.168.23.1: seq=96 time=0.993ms Reply from 192.168.23.1: seq=97 time=1.010ms Reply from 192.168.23.1: seq=98 time=1.005ms Reply from 192.168.23.1: seq=99 time=1.014ms Reply from 192.168.23.1: seq=100 time=0.981ms Reply from 192.168.23.1: seq=101 time=1.304ms Reply from 192.168.23.1: seq=102 time=0.923ms Reply from 192.168.23.1: seq=103 time=2.283ms Reply from 192.168.23.1: seq=104 time=1.065ms --- Ping statistics --- 105 packets transmitted, 105 received, 0.0% packet loss round-trip min/avg/max/stddev = 0.807/1.469/13.924/1.763 ms # 테스트 2 : 노트북 ->유선->공유기#2(192.168.23.1)->유선->공유기#1(192.168.68.1) C:\Users\creer>C:\Users\creer\gemini\ping_us.py 192.168.68.1 Pinging 192.168.68.1 with 32 bytes of data: Reply from 192.168.68.1: seq=0 time=1.486ms Reply from 192.168.68.1: seq=1 time=2.114ms Reply from 192.168.68.1: seq=2 time=1.337ms Reply from 192.168.68.1: seq=3 time=1.376ms Reply from 192.168.68.1: seq=4 time=1.338ms Reply from 192.168.68.1: seq=5 time=1.470ms Reply from 192.168.68.1: seq=6 time=1.492ms Reply from 192.168.68.1: seq=7 time=1.558ms Reply from 192.168.68.1: seq=8 time=5.329ms Reply from 192.168.68.1: seq=9 time=1.796ms Reply from 192.168.68.1: seq=10 time=1.431ms Reply from 192.168.68.1: seq=11 time=1.303ms Reply from 192.168.68.1: seq=12 time=1.347ms Reply from 192.168.68.1: seq=13 time=4.527ms Reply from 192.168.68.1: seq=14 time=1.243ms Reply from 192.168.68.1: seq=15 time=1.457ms Reply from 192.168.68.1: seq=16 time=1.162ms Reply from 192.168.68.1: seq=17 time=1.440ms Reply from 192.168.68.1: seq=18 time=9.523ms Reply from 192.168.68.1: seq=19 time=1.321ms Reply from 192.168.68.1: seq=20 time=1.229ms Reply from 192.168.68.1: seq=21 time=1.292ms Reply from 192.168.68.1: seq=22 time=1.398ms Reply from 192.168.68.1: seq=23 time=1.239ms Reply from 192.168.68.1: seq=24 time=1.214ms Reply from 192.168.68.1: seq=25 time=5.787ms Reply from 192.168.68.1: seq=26 time=1.301ms Reply from 192.168.68.1: seq=27 time=5.400ms Reply from 192.168.68.1: seq=28 time=2.135ms Reply from 192.168.68.1: seq=29 time=1.203ms Reply from 192.168.68.1: seq=30 time=1.376ms Reply from 192.168.68.1: seq=31 time=1.224ms Reply from 192.168.68.1: seq=32 time=1.766ms Reply from 192.168.68.1: seq=33 time=1.623ms Reply from 192.168.68.1: seq=34 time=1.525ms Reply from 192.168.68.1: seq=35 time=1.261ms Reply from 192.168.68.1: seq=36 time=1.351ms Reply from 192.168.68.1: seq=37 time=1.152ms Reply from 192.168.68.1: seq=38 time=1.892ms Reply from 192.168.68.1: seq=39 time=1.303ms Reply from 192.168.68.1: seq=40 time=1.351ms Reply from 192.168.68.1: seq=41 time=1.439ms Reply from 192.168.68.1: seq=42 time=1.352ms Reply from 192.168.68.1: seq=43 time=1.368ms Reply from 192.168.68.1: seq=44 time=1.391ms Reply from 192.168.68.1: seq=45 time=1.272ms Reply from 192.168.68.1: seq=46 time=1.327ms Reply from 192.168.68.1: seq=47 time=4.642ms Reply from 192.168.68.1: seq=48 time=1.321ms Reply from 192.168.68.1: seq=49 time=1.421ms Reply from 192.168.68.1: seq=50 time=1.328ms Reply from 192.168.68.1: seq=51 time=1.183ms Reply from 192.168.68.1: seq=52 time=1.578ms Reply from 192.168.68.1: seq=53 time=1.339ms Reply from 192.168.68.1: seq=54 time=1.356ms Reply from 192.168.68.1: seq=55 time=1.231ms Reply from 192.168.68.1: seq=56 time=1.391ms Reply from 192.168.68.1: seq=57 time=1.389ms Reply from 192.168.68.1: seq=58 time=1.248ms Reply from 192.168.68.1: seq=59 time=1.406ms Reply from 192.168.68.1: seq=60 time=1.411ms Reply from 192.168.68.1: seq=61 time=1.197ms Reply from 192.168.68.1: seq=62 time=1.227ms Reply from 192.168.68.1: seq=63 time=1.251ms Reply from 192.168.68.1: seq=64 time=1.308ms Reply from 192.168.68.1: seq=65 time=1.314ms Reply from 192.168.68.1: seq=66 time=1.304ms Reply from 192.168.68.1: seq=67 time=1.893ms Reply from 192.168.68.1: seq=68 time=1.217ms Reply from 192.168.68.1: seq=69 time=2.179ms Reply from 192.168.68.1: seq=70 time=1.365ms Reply from 192.168.68.1: seq=71 time=1.297ms Reply from 192.168.68.1: seq=72 time=1.542ms Reply from 192.168.68.1: seq=73 time=1.230ms Reply from 192.168.68.1: seq=74 time=1.349ms Reply from 192.168.68.1: seq=75 time=1.235ms Reply from 192.168.68.1: seq=76 time=1.584ms Reply from 192.168.68.1: seq=77 time=1.527ms Reply from 192.168.68.1: seq=78 time=1.346ms Reply from 192.168.68.1: seq=79 time=1.317ms Reply from 192.168.68.1: seq=80 time=1.237ms Reply from 192.168.68.1: seq=81 time=11.835ms Reply from 192.168.68.1: seq=82 time=1.465ms Reply from 192.168.68.1: seq=83 time=1.471ms Reply from 192.168.68.1: seq=84 time=1.420ms Reply from 192.168.68.1: seq=85 time=1.413ms Reply from 192.168.68.1: seq=86 time=17.853ms Reply from 192.168.68.1: seq=87 time=1.372ms Reply from 192.168.68.1: seq=88 time=1.318ms Reply from 192.168.68.1: seq=89 time=1.292ms Reply from 192.168.68.1: seq=90 time=1.305ms Reply from 192.168.68.1: seq=91 time=1.414ms Reply from 192.168.68.1: seq=92 time=1.292ms Reply from 192.168.68.1: seq=93 time=1.293ms Reply from 192.168.68.1: seq=94 time=1.368ms Reply from 192.168.68.1: seq=95 time=1.199ms Reply from 192.168.68.1: seq=96 time=1.261ms Reply from 192.168.68.1: seq=97 time=1.307ms Reply from 192.168.68.1: seq=98 time=2.218ms Reply from 192.168.68.1: seq=99 time=1.360ms Reply from 192.168.68.1: seq=100 time=1.277ms --- Ping statistics --- 101 packets transmitted, 101 received, 0.0% packet loss round-trip min/avg/max/stddev = 1.152/1.932/17.853/2.219 ms # 테스트 3 : 노트북 ->유선->공유기#1(192.168.68.1) C:\Users\creer>C:\Users\creer\gemini\ping_us.py 192.168.68.1 Pinging 192.168.68.1 with 32 bytes of data: Reply from 192.168.68.1: seq=0 time=1.055ms Reply from 192.168.68.1: seq=1 time=1.056ms Reply from 192.168.68.1: seq=2 time=1.008ms Reply from 192.168.68.1: seq=3 time=1.065ms Reply from 192.168.68.1: seq=4 time=1.099ms Reply from 192.168.68.1: seq=5 time=1.016ms Reply from 192.168.68.1: seq=6 time=1.028ms Reply from 192.168.68.1: seq=7 time=1.110ms Reply from 192.168.68.1: seq=8 time=1.002ms Reply from 192.168.68.1: seq=9 time=1.009ms Reply from 192.168.68.1: seq=10 time=1.023ms Reply from 192.168.68.1: seq=11 time=1.106ms Reply from 192.168.68.1: seq=12 time=0.999ms Reply from 192.168.68.1: seq=13 time=1.083ms Reply from 192.168.68.1: seq=14 time=1.121ms Reply from 192.168.68.1: seq=15 time=0.988ms Reply from 192.168.68.1: seq=16 time=1.112ms Reply from 192.168.68.1: seq=17 time=1.031ms Reply from 192.168.68.1: seq=18 time=0.987ms Reply from 192.168.68.1: seq=19 time=1.135ms Reply from 192.168.68.1: seq=20 time=1.048ms Reply from 192.168.68.1: seq=21 time=1.095ms Reply from 192.168.68.1: seq=22 time=1.725ms Reply from 192.168.68.1: seq=23 time=0.968ms Reply from 192.168.68.1: seq=24 time=0.957ms Reply from 192.168.68.1: seq=25 time=1.109ms Reply from 192.168.68.1: seq=26 time=1.052ms Reply from 192.168.68.1: seq=27 time=1.132ms Reply from 192.168.68.1: seq=28 time=1.453ms Reply from 192.168.68.1: seq=29 time=0.996ms Reply from 192.168.68.1: seq=30 time=0.954ms Reply from 192.168.68.1: seq=31 time=1.069ms Reply from 192.168.68.1: seq=32 time=0.952ms Reply from 192.168.68.1: seq=33 time=1.190ms Reply from 192.168.68.1: seq=34 time=1.168ms Reply from 192.168.68.1: seq=35 time=1.078ms Reply from 192.168.68.1: seq=36 time=1.019ms Reply from 192.168.68.1: seq=37 time=1.041ms Reply from 192.168.68.1: seq=38 time=1.011ms Reply from 192.168.68.1: seq=39 time=1.122ms Reply from 192.168.68.1: seq=40 time=1.015ms Reply from 192.168.68.1: seq=41 time=1.094ms Reply from 192.168.68.1: seq=42 time=1.649ms Reply from 192.168.68.1: seq=43 time=1.072ms Reply from 192.168.68.1: seq=44 time=1.072ms Reply from 192.168.68.1: seq=45 time=1.286ms Reply from 192.168.68.1: seq=46 time=0.969ms Reply from 192.168.68.1: seq=47 time=1.614ms Reply from 192.168.68.1: seq=48 time=1.160ms Reply from 192.168.68.1: seq=49 time=1.120ms Reply from 192.168.68.1: seq=50 time=1.241ms Reply from 192.168.68.1: seq=51 time=1.107ms Reply from 192.168.68.1: seq=52 time=1.004ms Reply from 192.168.68.1: seq=53 time=2.730ms Reply from 192.168.68.1: seq=54 time=1.173ms Reply from 192.168.68.1: seq=55 time=1.075ms Reply from 192.168.68.1: seq=56 time=1.038ms Reply from 192.168.68.1: seq=57 time=1.034ms Reply from 192.168.68.1: seq=58 time=1.036ms Reply from 192.168.68.1: seq=59 time=1.143ms Reply from 192.168.68.1: seq=60 time=1.084ms Reply from 192.168.68.1: seq=61 time=1.067ms Reply from 192.168.68.1: seq=62 time=1.024ms Reply from 192.168.68.1: seq=63 time=0.903ms Reply from 192.168.68.1: seq=64 time=1.062ms Reply from 192.168.68.1: seq=65 time=1.000ms Reply from 192.168.68.1: seq=66 time=1.151ms Reply from 192.168.68.1: seq=67 time=1.084ms Reply from 192.168.68.1: seq=68 time=1.041ms Reply from 192.168.68.1: seq=69 time=1.026ms Reply from 192.168.68.1: seq=70 time=1.125ms Reply from 192.168.68.1: seq=71 time=1.049ms Reply from 192.168.68.1: seq=72 time=1.067ms Reply from 192.168.68.1: seq=73 time=0.952ms Reply from 192.168.68.1: seq=74 time=1.057ms Reply from 192.168.68.1: seq=75 time=1.028ms Reply from 192.168.68.1: seq=76 time=1.108ms Reply from 192.168.68.1: seq=77 time=1.057ms Reply from 192.168.68.1: seq=78 time=0.992ms Reply from 192.168.68.1: seq=79 time=1.020ms Reply from 192.168.68.1: seq=80 time=1.021ms Reply from 192.168.68.1: seq=81 time=1.111ms Reply from 192.168.68.1: seq=82 time=1.088ms Reply from 192.168.68.1: seq=83 time=0.990ms Reply from 192.168.68.1: seq=84 time=1.154ms Reply from 192.168.68.1: seq=85 time=1.081ms Reply from 192.168.68.1: seq=86 time=1.012ms Reply from 192.168.68.1: seq=87 time=1.143ms Reply from 192.168.68.1: seq=88 time=1.094ms Reply from 192.168.68.1: seq=89 time=1.072ms Reply from 192.168.68.1: seq=90 time=1.060ms Reply from 192.168.68.1: seq=91 time=0.936ms Reply from 192.168.68.1: seq=92 time=1.047ms Reply from 192.168.68.1: seq=93 time=1.005ms Reply from 192.168.68.1: seq=94 time=1.072ms Reply from 192.168.68.1: seq=95 time=1.087ms Reply from 192.168.68.1: seq=96 time=0.951ms Reply from 192.168.68.1: seq=97 time=1.071ms Reply from 192.168.68.1: seq=98 time=1.031ms Reply from 192.168.68.1: seq=99 time=1.079ms Reply from 192.168.68.1: seq=100 time=1.041ms Reply from 192.168.68.1: seq=101 time=1.094ms Reply from 192.168.68.1: seq=102 time=1.022ms Reply from 192.168.68.1: seq=103 time=0.907ms --- Ping statistics --- 104 packets transmitted, 104 received, 0.0% packet loss round-trip min/avg/max/stddev = 0.903/1.095/2.730/0.205 ms C:\Users\creer>
-
25
댓글11
-
세상의모든계산기
유선) hrping 핑 테스트
hrping.exe 192.168.23.1 -n 1000
This is hrPING v5.07.1150 by cFos Software GmbH -- https://www.cfos.de
(중략)
Packets: sent=1000, rcvd=1000, error=0, lost=0 (0.0% loss) in 499.511856 sec
RTTs in ms: min/avg/max/dev: 0.618 / 1.679 / 20.264 / 2.347
Bandwidth in kbytes/sec: sent=0.120, rcvd=0.120
- 노트북->유선->AX2004T
- 테스트 중 유튜브 시청함
-
세상의모든계산기
노트북(클라이언트) -> 유선 -> AX2004T -> 유선 -> 데탑(PC, 서버)
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.23.5 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.23.5, port 5000
[ 4] local 192.168.23.4 port 4985 connected to 192.168.23.5 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 188 MBytes 786 Mbits/sec
[ 4] 2.00-4.00 sec 191 MBytes 800 Mbits/sec
[ 4] 4.00-6.00 sec 184 MBytes 771 Mbits/sec
[ 4] 6.00-8.00 sec 184 MBytes 770 Mbits/sec
[ 4] 8.00-10.00 sec 191 MBytes 800 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 936 MBytes 785 Mbits/sec sender
[ 4] 0.00-10.00 sec 936 MBytes 785 Mbits/sec receiver
iperf Done.
C:\iperf-3.1.3-win64> -
세상의모든계산기
무선 2.4G) hrping 핑 테스트
Packets: sent=1000, rcvd=999, error=0, lost=1 (0.1% loss) in 499.507024 sec
RTTs in ms: min/avg/max/dev: 1.103 / 10.756 / 1793.124 / 80.016
Bandwidth in kbytes/sec: sent=0.120, rcvd=0.119
- 노트북->무선(2.4G)->AX2004T
- 테스트 중 유튜브 시청함
-
세상의모든계산기
노트북(클라이언트) -> 무선 2.4G -> AX2004T -> 유선 -> 데탑(PC, 서버)
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.23.5 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.23.5, port 5000
[ 4] local 192.168.23.2 port 5129 connected to 192.168.23.5 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 47.5 MBytes 199 Mbits/sec
[ 4] 2.00-4.00 sec 52.0 MBytes 218 Mbits/sec
[ 4] 4.00-6.00 sec 50.4 MBytes 211 Mbits/sec
[ 4] 6.00-8.00 sec 50.6 MBytes 212 Mbits/sec
[ 4] 8.00-10.00 sec 49.0 MBytes 206 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 250 MBytes 209 Mbits/sec sender
[ 4] 0.00-10.00 sec 249 MBytes 209 Mbits/sec receiver
iperf Done.
C:\iperf-3.1.3-win64> -
세상의모든계산기
비교 : AC-68U
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.01 sec 65.0 MBytes 54.5 Mbits/sec sender
[ 4] 0.00-10.01 sec 65.0 MBytes 54.5 Mbits/sec receiver
이상해서 다시 접속
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.68.36 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.68.36, port 5000
[ 4] local 192.168.68.217 port 12792 connected to 192.168.68.36 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 22.4 MBytes 93.7 Mbits/sec
[ 4] 2.00-4.00 sec 24.5 MBytes 103 Mbits/sec
[ 4] 4.00-6.00 sec 23.6 MBytes 98.9 Mbits/sec
[ 4] 6.00-8.01 sec 24.2 MBytes 101 Mbits/sec
[ 4] 8.01-10.00 sec 24.1 MBytes 102 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 119 MBytes 99.7 Mbits/sec sender
[ 4] 0.00-10.00 sec 119 MBytes 99.7 Mbits/sec receiver
* 공유기 2.4G 연결된 장치가 많아서 연결속도/다운속도가 떨어지는 것이 아닌가 합니다.
-
세상의모든계산기
무선 5G) hrping 핑 테스트
Packets: sent=1000, rcvd=999, error=0, lost=1 (0.1% loss) in 499.511706 sec
RTTs in ms: min/avg/max/dev: 1.509 / 13.751 / 507.855 / 24.991
Bandwidth in kbytes/sec: sent=0.120, rcvd=0.119
- 노트북->무선(5G)->AX2004T
- 테스트 중 유튜브 시청함
-
세상의모든계산기
노트북(클라이언트) -> 무선 5G -> AX2004T -> 유선 -> 데탑(PC, 서버)
C:\iperf-3.1.3-win64>iperf3.exe -c 192.168.23.5 -p 5000 -t 10 -f m -i 2
Connecting to host 192.168.23.5, port 5000
[ 4] local 192.168.23.2 port 5063 connected to 192.168.23.5 port 5000
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-2.00 sec 68.2 MBytes 286 Mbits/sec
[ 4] 2.00-4.00 sec 65.6 MBytes 276 Mbits/sec
[ 4] 4.00-6.00 sec 73.6 MBytes 309 Mbits/sec
[ 4] 6.00-8.00 sec 67.9 MBytes 285 Mbits/sec
[ 4] 8.00-10.00 sec 70.2 MBytes 294 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 346 MBytes 290 Mbits/sec sender
[ 4] 0.00-10.00 sec 346 MBytes 290 Mbits/sec receiver
iperf Done.
C:\iperf-3.1.3-win64>
세상의모든계산기 님의 최근 댓글
- claude AI는 l-c*r^2 을 1-c*r^2 으로 잘못 읽고 표시하고 있습니다. - TI-nspire CAS 계산기에 l-c*r^2 ≥0 을 조건에 추가해 계산해 보아도 결과는 바뀌지 않습니다. 2026 07.20 ⚠️ 경고가 바로 두 번째 방법이 "성공"한 이유와 정확히 연결되어 있습니다. 경고의 의미 "Domain of the result might be larger than the domain of the input"는 CAS가 절댓값(모듈러스)을 계산하는 과정에서 원래 식보다 정의역이 더 넓은 형태로 단순화했다는 뜻입니다. 구체적으로 이 계산은 내부적으로 대략 이런 과정을 거칩니다. $$\left|\frac{er}{e\cdot r}\right| = \sqrt{\left(\frac{er}{e\cdot r}\right)\cdot\overline{\left(\frac{er}{e\cdot r}\right)}}$$ 즉 원래 식(복소수)과 그 켤레복소수를 곱해서 실수부·허수부 제곱합을 만들고, 거기에 다시 제곱근을 씌우는 과정입니다. 이 과정에서 √(x²) → x 또는 √a·√b → √(ab) 같은 규칙들이 쓰이는데, 이런 규칙들은 x가 실수이고 0 이상일 때만 엄밀하게 성립합니다. CAS는 이 조건들을 일일이 다 추적하지 않고 넘어가면서, 원래는 (e≠0, r+l·ω·i ≠ 0 등) 복소수 특유의 좁은 정의역을 가진 식을, r, l, ω가 어떤 실수여도(부호 무관하게) 정의되는 1/√(r²+l²·ω²)라는 더 넓은 정의역의 식으로 바꿔버린 것입니다. CAS는 이 손실을 감지하고 경고를 띄운 것입니다. 이게 왜 조건 대입 성공과 연결되는가 정리하면, 이 경고는 사실상 이런 뜻입니다. "나는 이 결과를 만들면서 원래 식이 가지고 있던 정의역 제약 정보(부호 조건, i 관련 조건 등)를 이미 버렸다." 바로 이 "정의역 정보를 버린" 상태가 이후 con_1 대입을 매끄럽게 만드는 원인입니다. 첫 번째 시도에서는 i가 살아있는 원래 식에 조건을 대입했기 때문에, CAS가 √(1-c·r²)이 실수인지(정의역 조건: 1-c·r² ≥ 0) 계속 추적하려고 했고, 그 정보가 con에 없어서 더 이상 정리를 못 하고 멈췄습니다. 두 번째 시도에서는 절댓값 계산 단계에서 이미 그런 세밀한 정의역 추적을 CAS 스스로 포기(단순화)했기 때문에, 이후 ω에 무리식을 대입해도 "이게 실수가 맞나?" 하는 검증 절차 없이 그냥 대수적으로 치환·정리해 버립니다. 그래서 깔끔하게 √c/√l이 나온 겁니다. 한 줄 요약 절댓값 계산 시 뜬 "정의역이 넓어졌을 수 있다"는 경고는, CAS가 그 순간에 원래 식의 엄밀한 조건(정의역)을 놓쳤다는 신호이고, 바로 그 "조건을 놓친 상태"이기 때문에 뒤에 이어지는 조건식 대입이 막힘없이 진행된 것입니다. 다만 그 대가로, 결과인 1/√(r²+l²·ω²)이나 최종 √c/√l이 원래 회로 조건(i≠0이 되는 경계, 분모가 0이 되는 경우 등)에서는 엄밀히 성립하지 않을 수 있다는 점은 감안하셔야 합니다. 실제 물리적으로는 r, l, c > 0이고 결과도 물리적으로 타당한 형태라 문제없어 보이지만, 수학적 엄밀성 측면에서는 "정의역이 넓어진 근사적 결과"라는 꼬리표가 붙어있는 셈입니다. 2026 07.20 Claude AI 답변 TI-Nspire CAS의 | (such that / 조건대입) 연산자는 대입 시점의 수식 형태를 그대로 두고 기호만 치환하는 연산입니다. 대입 후에 처음부터 다시 "실수부/허수부 분리, 유리화" 같은 재간소화를 자동으로 수행하지 않습니다. 이 차이가 지금 보신 결과 차이의 핵심입니다. 첫 번째 경우 (|er/(e·r)| | con_1 and con → 실패) 이 시점의 식은 아직 r + l·ω·i 형태의 복소수 그대로입니다 (i가 살아있음). 여기에 con_1: ω = √(1-c·r²)/(√c·l)을 대입하면, 분모 안에 i · √(1-c·r²) 라는 항이 새로 생깁니다. 문제는 CAS가 √(1-c·r²)이 실수인지(즉 1-c·r² ≥ 0인지) 판단할 근거가 없다는 겁니다. 저장해 두신 con 조건은 c>0, l>0, r>0뿐이고, 1-c·r²≥0이라는 조건은 포함되어 있지 않습니다. 그래서 CAS는 i와 이 무리식을 더 정리(유리화, 실수부·허수부 재결합)하지 못하고 있는 그대로 남겨둡니다. 결과에 여전히 i가 보이는 이유입니다. 두 번째 경우 (결과값 1/√(r²+l²·ω²)에 대입 → 성공) |er/(e·r)| (절댓값/모듈러스) 연산은 그 자체로 이미 "복소수 → 실수" 변환을 완료한 결과입니다. 즉 1/√(r²+l²·ω²)에는 더 이상 i가 없고, 순수하게 r, l, ω로만 이루어진 실수식입니다. 이 식에 ω = con_1을 대입하는 것은 그냥 실수 대수식에 실수 대입하는 것이므로, i와 무리식이 뒤엉키는 문제 자체가 발생하지 않습니다. 그래서 바로 깔끔하게 √c/√l로 정리됩니다. 정리하면 절댓값(모듈러스) 계산은 "이 값들이 실수다"라는 가정을 이미 내부적으로 써서 i를 제거하는 연산입니다. 그 연산을 조건 대입 이전에 해두면, 이후 대입은 단순 실수 대입이라 문제없이 정리됩니다. 반대로 i가 남아있는 식에 무리식을 포함한 조건을 먼저 대입하면, 그 무리식의 실수성/부호에 대한 가정이 없어서 CAS가 i를 소거하는 재간소화를 못 하고 멈춰버립니다. 실용적 팁: 복소식에 조건을 대입해야 할 때는 가능하면 절댓값·실수화(유리화) 등을 먼저 끝내서 i를 없앤 뒤 조건을 대입하거나, 대입 후 결과에 다시 simplify/expand/combine 같은 명령을 한 번 더 걸어주면 (필요한 도메인 조건과 함께) 정리가 되는 경우가 많습니다. 2026 07.19 저도 어림잡아 추측할 뿐이지 정확한 이유를 알지는 못합니다. 질문하신 사진을 그대로 (Gemini 3.5 Flash / ChatGPT / Claude Sonnet 5) AI에 넣어 보니 claude AI 가 제일 합리적인 답변을 주어서 이를 붙여 넣습니다. 2026 07.19 아 그렇네요. 감사합니다. ^^ 2026 04.28