network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 10 months |
| seen | Apr 20 at 6:25 | |
| stats | profile views | 8 |
|
May 24 |
comment |
Permanently assigning IP address for an embedded device Okay, my new approach is to, on boot, obtain an link-local address one time using the implementation at zeroconf.org/AVH-IPv4LL.c. I then do an ifconfig add eth0:0 user_configurable_ip_address to add an alias. This is not so robust if I move my device to another network while powered, but it's powered by its Ethernet cable, so it should almost always follow the link-local address acquisition rules. (reboots upon disconnect) |
|
May 23 |
comment |
Permanently assigning IP address for an embedded device A collision only happens if communication is attempted with the duplicate address, right? Nothing will attempt to use this address except for the ARP queries from link-local address negotiation, which is meant to happen. What's the practical effect of this collision? |
|
May 22 |
asked | Permanently assigning IP address for an embedded device |
|
Jul 19 |
awarded | Editor |
|
Jul 19 |
revised |
Embedded device configured with bad IP address, can I still connect? added 232 characters in body |
|
Jul 19 |
comment |
Embedded device configured with bad IP address, can I still connect? We build these devices. :) |
|
Jul 18 |
awarded | Supporter |
|
Jul 18 |
awarded | Scholar |
|
Jul 18 |
accepted | Embedded device configured with bad IP address, can I still connect? |
|
Jul 18 |
awarded | Student |
|
Jul 18 |
comment |
Embedded device configured with bad IP address, can I still connect? This is my main problem. I do not know what address and mask the embedded device's interface is actually using, if any. What steps can I take to diagnose this, and can I use Zeroconf to help? |
|
Jul 18 |
asked | Embedded device configured with bad IP address, can I still connect? |
