[U-Boot] Ping failure

[Paul Nader]

I'll try without the switch using a crossover cable to link the board and
the host running wireshark directly and let you know.

On Tue, Nov 6, 2018 at 10:19 AM Paul Nader <paul.nader at gmail.com> wrote:

>
>
> On Tue, Nov 6, 2018 at 9:45 AM Chris Packham <judge.packham at gmail.com>
> wrote:
>
>>
>>
>> On Tue, 6 Nov 2018, 6:09 AM Paul Nader <paul.nader at gmail.com wrote:
>>
>>> Hi,
>>>
>>> I'm trying to get an olinuxino-a64 board to boot using bootp but it
>>> failed
>>> to send any DHCP packets so I reduced the problem to trying to get it to
>>> ping another host but that fails as well.
>>>
>>> I tried it both with 2018.09 and then the head of master given there were
>>> some recent commits to the net area to fix handling asynchronous
>>> responses.
>>>
>>> I'm testing this  by having the board ethernet connected to a switch and
>>> another port of the switch to a host running wireshark snooping packets
>>> in
>>> promiscuous mode.
>>>
>>
>> Could the switch be dropping the packets? Are the ports in the same vlan?
>> Is your monitoring host the same host you're trying to ping? (if not you'll
>> need to configure your switch for mirroring)
>>
>
>
> The switch is a unmanaged TP-Link SG105
> <https://www.tp-link.com/uk/products/details/cat-42_TL-SG105.html> which
> as far as I can tell has no configuration.
>
> The host I am pinging is the same host that is running wireshark.
>
>
>>
>>> In:    serial
>>> Out:   serial
>>> Err:   serial
>>> Net:   phy interface7
>>> eth0: ethernet at 1c30000
>>> starting USB...
>>> No controllers found
>>> Hit any key to stop autoboot:  0
>>> => setenv ipaddr 192.168.0.2
>>> => log level 10
>>> => setenv netmask 255.255.255.0
>>>
>>
>> What do you end up with for a mac address? I'm not familiar with the
>> olinuxino hardware does it have an eeprom for the mac or does it just come
>> from the environment.
>>
>>>
>>>
> I tried overwriting the mac address using setenv but it wouldn't allow it
> so I think it is coming from an eeprom. I didn't set it up in the u-boot
> environment.
>
> Also, just to reiterate, this all works fine once the kernel has booted. I
> can configure the interface within linux and ping the host without any
> problems.
>
>
>