digitalmars.D.learn - How to get the client's MAC address in Vibe
- Alexander Zhirov (5/5) Feb 07 Is there a way to identify a client by MAC address when using the
- Mengu (10/15) Feb 07 That doesn't have anything to do with the server side if I am not
- Alexander Zhirov (3/17) Feb 09 It is at the packet level to monitor the address. Not at all what
- Steven Schveighoffer (6/11) Feb 08 Mac is a hardware address. By the time the packets get to your
- Alexander Zhirov (5/15) Feb 09 You are right, information is lost at the packet level and
Is there a way to identify a client by MAC address when using the Vibe library? The `NetworkAddress` [structure](https://vibed.org/api/vibe.core.net/NetworkAddress) does not provide such features. Or did I miss something?
Feb 07
On Wednesday, 7 February 2024 at 22:16:54 UTC, Alexander Zhirov wrote:Is there a way to identify a client by MAC address when using the Vibe library? The `NetworkAddress` [structure](https://vibed.org/api/vibe.core.net/NetworkAddress) does not provide such features. Or did I miss something?That doesn't have anything to do with the server side if I am not mistaken as you should receive that via the browser that actually allows you to receive the mac address -via an extension- or some private API exposed by the browser. I don't know the use case but you may be better off with browser fingerprinting if you'd like to have a unique way of identifying the visitors. Or, if it's a local network, maybe you can use tcpdump/libpcap.
Feb 07
On Thursday, 8 February 2024 at 01:05:57 UTC, Mengu wrote:On Wednesday, 7 February 2024 at 22:16:54 UTC, Alexander Zhirov wrote:It is at the packet level to monitor the address. Not at all what I would like. Thanks for the tip:)Is there a way to identify a client by MAC address when using the Vibe library? The `NetworkAddress` [structure](https://vibed.org/api/vibe.core.net/NetworkAddress) does not provide such features. Or did I miss something?That doesn't have anything to do with the server side if I am not mistaken as you should receive that via the browser that actually allows you to receive the mac address -via an extension- or some private API exposed by the browser. I don't know the use case but you may be better off with browser fingerprinting if you'd like to have a unique way of identifying the visitors. Or, if it's a local network, maybe you can use tcpdump/libpcap.
Feb 09
On Wednesday, 7 February 2024 at 22:16:54 UTC, Alexander Zhirov wrote:Is there a way to identify a client by MAC address when using the Vibe library? The `NetworkAddress` [structure](https://vibed.org/api/vibe.core.net/NetworkAddress) does not provide such features. Or did I miss something?Mac is a hardware address. By the time the packets get to your server, that info is long gone. Even if you could get it, it likely is the MAC address of your router, not the peer. -Steve
Feb 08
On Thursday, 8 February 2024 at 14:21:13 UTC, Steven Schveighoffer wrote:On Wednesday, 7 February 2024 at 22:16:54 UTC, Alexander Zhirov wrote:You are right, information is lost at the packet level and nothing reaches the browser anymore. I will look for another way. Thanks!Is there a way to identify a client by MAC address when using the Vibe library? The `NetworkAddress` [structure](https://vibed.org/api/vibe.core.net/NetworkAddress) does not provide such features. Or did I miss something?Mac is a hardware address. By the time the packets get to your server, that info is long gone. Even if you could get it, it likely is the MAC address of your router, not the peer. -Steve
Feb 09