윈도우 - (네트워크 어댑터의 우선순위로 인한) 열거되는 IP 주소 순서를 조정하는 방법
예를 들어, 다음과 같은 코드를,
using System;
using System.Net.NetworkInformation;
using System.Net.Sockets;
namespace ConsoleApp1
{
class Program
{
static void Main(string[] args)
{
foreach (NetworkInterface item in NetworkInterface.GetAllNetworkInterfaces())
{
if (item.NetworkInterfaceType == NetworkInterfaceType.Ethernet
&& item.OperationalStatus == OperationalStatus.Up)
{
foreach (UnicastIPAddressInformation ip in item.GetIPProperties().UnicastAddresses)
{
if (ip.Address.AddressFamily == AddressFamily.InterNetwork)
{
Console.WriteLine(ip.Address.ToString());
}
}
}
}
}
}
}
실행하면 이렇게 출력이 되는 시스템을 가정해보겠습니다.
C:\test> ConsoleApp1.exe
172.26.48.6
192.168.0.167
저 순서는 ipconfig을 했을 때와 동일합니다.
PS C:\WINDOWS\system32> ipconfig
Windows IP Configuration
Ethernet adapter Ethernet 4:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::8162:af6a:2f6c:ec60%13
IPv4 Address. . . . . . . . . . . : 172.26.48.6
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
Ethernet adapter Ethernet 5:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::b5d3:1eaa:1fd3:6197%12
IPv4 Address. . . . . . . . . . . : 192.168.0.167
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
PS C:\WINDOWS\system32> Get-NetIPInterface | where {$_.ConnectionState -eq "Connected" -and $_.AddressFamily -eq "IPv4" } | select ifIndex,InterfaceAlias,InterfaceMetric,AddressFamily,ConnectionState | sort InterfaceMetric | FT
ifIndex InterfaceAlias InterfaceMetric AddressFamily ConnectionState
------- -------------- --------------- ------------- ---------------
13 Ethernet 4 15 IPv4 Connected
12 Ethernet 5 35 IPv4 Connected
1 Loopback Pseudo-Interface 1 75 IPv4 Connected
이 순서를 바꾸는 방법은 전에 한 번 설명한 적이 있습니다. ^^
윈도우 10에서 사라진 "Adapters and Bindings" 네트워크 우선순위 조정 기능 - 두 번째 이야기
; https://www.sysnet.pe.kr/2/0/11782
위의 글에서 설명했지만, 결국 중요한 것은 ROUTE 테이블에서 보이는 Metric 수치가 낮아야 우선 순위가 높으므로, 차이가 얼마나 나는지 확인을 해야 합니다.
C:\WINDOWS\system32> route PRINT -4
===========================================================================
Interface List
12...00 15 5d 00 13 33 ......Microsoft Hyper-V Network Adapter #5
13...00 15 5d 00 13 34 ......Microsoft Hyper-V Network Adapter #4
1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.167 35
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
172.26.48.0 255.255.240.0 On-link 172.26.48.6 271
172.26.48.6 255.255.255.255 On-link 172.26.48.6 271
172.26.63.255 255.255.255.255 On-link 172.26.48.6 271
192.168.0.0 255.255.255.0 On-link 192.168.0.167 291
192.168.0.167 255.255.255.255 On-link 192.168.0.167 291
192.168.0.255 255.255.255.255 On-link 192.168.0.167 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.0.167 291
224.0.0.0 240.0.0.0 On-link 172.26.48.6 271
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.0.167 291
255.255.255.255 255.255.255.255 On-link 172.26.48.6 271
===========================================================================
Persistent Routes:
None
172.26.48.0 네트워크의 Metric이 271, 192.168.0.0 네트워크가 291이므로 20의 차이가 납니다. 따라서 172.26.48.0 네트워크의 InterfaceMetric 값을 +21 이상으로 설정해 준다면 192.168.0.0 네트워크의 우선 순위가 더 높아질 수 있습니다. 기존 값이 "15"니까, (보기 좋게 ^^;) 5 단위로 떨어지게 +25를 해 "40"으로 설정한 후,
PS C:\WINDOWS\system32> Set-NetIPInterface -InterfaceIndex 13 -InterfaceMetric 40
PS C:\WINDOWS\system32> Get-NetIPInterface | where {$_.ConnectionState -eq "Connected" -and $_.AddressFamily -eq "IPv4" } | select ifIndex,InterfaceAlias,InterfaceMetric,AddressFamily,ConnectionState | sort InterfaceMetric | FT
ifIndex InterfaceAlias InterfaceMetric AddressFamily ConnectionState
------- -------------- --------------- ------------- ---------------
12 Ethernet 5 35 IPv4 Connected
13 Ethernet 4 40 IPv4 Connected
1 Loopback Pseudo-Interface 1 75 IPv4 Connected
ROUTE 테이블을 확인하면,
C:\WINDOWS\system32> route PRINT -4
===========================================================================
Interface List
12...00 15 5d 00 13 33 ......Microsoft Hyper-V Network Adapter #5
13...00 15 5d 00 13 34 ......Microsoft Hyper-V Network Adapter #4
1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.167 35
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
172.26.48.0 255.255.240.0 On-link 172.26.48.6 296
172.26.48.6 255.255.255.255 On-link 172.26.48.6 296
172.26.63.255 255.255.255.255 On-link 172.26.48.6 296
192.168.0.0 255.255.255.0 On-link 192.168.0.167 291
192.168.0.167 255.255.255.255 On-link 192.168.0.167 291
192.168.0.255 255.255.255.255 On-link 192.168.0.167 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 192.168.0.167 291
224.0.0.0 240.0.0.0 On-link 172.26.48.6 296
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 192.168.0.167 291
255.255.255.255 255.255.255.255 On-link 172.26.48.6 296
===========================================================================
Persistent Routes:
None
정상적으로 우선 순위에 변동이 생겼으니, 이제 우리의 C# 프로그램에서도 IP 순서가 바뀌어서 나오게 됩니다.
C:\test> ConsoleApp1.exe
192.168.0.167
172.26.48.6
[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]