Main Area and Open Discussion > N.A.N.Y. 2024
NANY 2024 - Network Adapter Info by KodeZwerg
KodeZwerg:
@4wd, I attached another version of my main app, replace the .exe with this new one, the libraries are not included.
App will run its normal job but
- i fixed the interpretation for "Local IP: "
- i added a new "PowerShell IPs: "
The app needs now longer to parse and compute the new PowerShell input.
Tell me if this version would be okay so I can update my first post and close this issue.
4wd:
@4wd, I attached another version of my main app, replace the .exe with this new one, the libraries are not included.
App will run its normal job but
- i fixed the interpretation for "Local IP: "
- i added a new "PowerShell IPs: "
The app needs now longer to parse and compute the new PowerShell input.
Tell me if this version would be okay so I can update my first post and close this issue.
-KodeZwerg (July 14, 2023, 10:05 AM)
--- End quote ---
Sorry for the delay, completely slipped my mind :-[
That worked :Thmbsup:
BTW, would it be a good idea to indicate which interface the local IP is applicable to?
eg.
Local IP: 192.168.0.99 (WiFi)
In the case of multiple connected NICs it might help identify which is the one with the highest metric.
KodeZwerg:
Sorry for the delay, completely slipped my mind :-[
-4wd (July 16, 2023, 09:11 PM)
--- End quote ---
No worries :-*
That worked :Thmbsup:
-4wd (July 16, 2023, 09:11 PM)
--- End quote ---
Amazing to hear :-*
BTW, would it be a good idea to indicate which interface the local IP is applicable to?
eg.
Local IP: 192.168.0.99 (WiFi)
-4wd (July 16, 2023, 09:11 PM)
--- End quote ---
Everything is possible :-*
In the case of multiple connected NICs it might help identify which is the one with the highest metric.
-4wd (July 16, 2023, 09:11 PM)
--- End quote ---
This is what "Local IP" shows :D
Updated my first post
- added tested features to final version
- tinkered a little with the text that it display, now more informations for the last things included (ip + name (if it has one))
I hope now everything works everywhere like it should.
Cheers,
Your KodeZwerg!
4wd:
--- Code: Text ---Host: MainPCLocal IP: 192.168.0.99 (WiFi)Public IP: 111.222.333.444Searching for physical connected Network Interface Card(s), please wait ...NIC(s): , 169.254.82.44 (Ethernet 3)
Slight problem ... the physical NIC isn't connected that's why it was assigned an APIPA IP, (169.254.x.x).
KodeZwerg:
I really wonder now why "NICs:" starting with a comma, shouldnt be possible at all. :'(
It is physical connected to your Pc, no?
FWIW a little bit of PowerShell:
--- Code: PowerShell ---(Get-NetAdapter -Name * -Physical | % { Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $_.Name }) | Format-Table -Property InterfaceAlias, IPAddress-4wd (July 14, 2023, 03:24 AM)
--- End quote ---
What my app parse for NICs is similar to the PowerShell command you gave me.
So when my app list it, PowerShell would do the same. Please verify again.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version