Skip to content

[help/docs] Ethernet support (having issues on existing network) #32

Description

@rgon

My Wi-Box came with the wrong credentials in the box (as confirmed by the hostapd.conf...), so that + #31 (still investigating) forced me to do more tinkering than usual to get the device working.

This issue will track a documentation PR on how to enable Ethernet support. However, I'm having issues with it.

eth0 is unusable on real network

The eth0 interface has the static IP address 192.168.1.10, and it works perfectly when connected directly to a computer, and is stable.

However, when I connect it into an unmanaged gigabit switch, on an isolated network along with existing IoT devices, the device locks up randomly and even the telnet connection is unusable. Yes, the rest of the devices on that switch work perfectly (including my test computer). As an example, this is how the device responds to pings: randomly taking several seconds then returning to being instant.

PING 192.168.20.123 (192.168.20.123) 56(84) bytes of data.
64 bytes from 192.168.20.123: icmp_seq=1 ttl=64 time=1.582 ms
64 bytes from 192.168.20.123: icmp_seq=2 ttl=64 time=1.484 ms
64 bytes from 192.168.20.123: icmp_seq=3 ttl=64 time=1.507 ms
64 bytes from 192.168.20.123: icmp_seq=4 ttl=64 time=2461 ms
64 bytes from 192.168.20.123: icmp_seq=5 ttl=64 time=1.486 ms

It seems that some broadcast/multicast requests are hogging the device. I need some help to sort this out, does anybody have any idea what could be going on, or any clues on how I should proceed to debug it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions