PhysicalAddress From Endpoint

[Dan Holmes]

How can i get a PhysicalAddress object if i only have an EndPoint object ?

I have an app that is a terminal emulator (vt100). When the telnet app
connects i want to get the MAC of the terminal. I can get the
terminal's IP with the RemoteEndPoint object of the TcpClient.Socket.


Dan

 

[Goran Sliskovic]

How can i get a PhysicalAddress object if i only have an EndPoint object ?

I have an app that is a terminal emulator (vt100). When the telnet app
connects i want to get the MAC of the terminal. I can get the
terminal's IP with the RemoteEndPoint object of the TcpClient.Socket.


Dan

Generally you can't. MAC address is not transferred over TCP/IP
protocol. You could however find out MAC address if request originated
from LAN by issuing ARP request or executing 'arp -a' from command
prompt. Why would you need it? MAC address is something that is of local
arae network significance only.

Regards,
Goran

 

[Dan Holmes]

Generally you can't. MAC address is not transferred over TCP/IP
protocol. You could however find out MAC address if request originated
from LAN by issuing ARP request or executing 'arp -a' from command
prompt. Why would you need it? MAC address is something that is of local
arae network significance only.

Regards,
Goran

It is the best (that i know of) value for uniquely identifing a PC based
terminal (i don't know about WYSE type terminals but the intended
audience won't have those) in the emulation space. The IP could change
if DHCP is used and there isn't another value that is retrievable in the
VT100 emulation commands.

dan

 

[Goran Sliskovic]

Dan Holmes wrote:
....

It is the best (that i know of) value for uniquely identifing a PC based
terminal (i don't know about WYSE type terminals but the intended
audience won't have those) in the emulation space. The IP could change
if DHCP is used and there isn't another value that is retrievable in the
VT100 emulation commands.

....

That's because terminals work at the (low) level of data representation
(keystrokes, screen formatting etc). It's up to the upper layers to
provide identification (consumers of protocol).

Regards,
Goran