From: E Shattow <e@freeshell.de>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: LwIP and multiple network interfaces
Date: Thu, 2 Jan 2025 14:26:06 -0800 [thread overview]
Message-ID: <de7bf6b3-fd45-4c8f-a492-bd41db2aa904@freeshell.de> (raw)
Problem: 'dhcp' must be ran twice when the network cable is plugged into
a port other than the first network port.
Network cable plugged into bottom (first) Ethernet port:
1. Power on
2. StarFive # dhcp
ethernet@16030000 Waiting for PHY auto negotiation to complete....... done
DHCP client bound to address 192.168.2.51 (3678 ms)
Network cable plugged into top (second) Ethernet port:
1. Power on
2. StarFive # dhcp
ethernet@16030000 Waiting for PHY auto negotiation to complete.........
TIMEOUT !
phy_startup() failed: -110
FAILED: -110
ethernet@16040000 Waiting for PHY auto negotiation to complete...... done
ethernet@16030000 Waiting for PHY auto negotiation to complete.........
TIMEOUT !
phy_startup() failed: -110
FAILED: -110
Could not start ethernet@16030000
3. StarFive # dhcp
DHCP client bound to address 192.168.2.77 (31 ms)
Bonus Problem: LwIP allergic to IPv6?
1. StarFive # dns ipv6.google.com
Unhandled exception: Load access fault
EPC: 00000000fff91ddc RA: 00000000fff9e20c TVAL: 0000000000000000
EPC: 0000000040278ddc RA: 000000004028520c reloc adjusted
SP: 00000000ff700040 GP: 00000000ff708e30 TP: 0000000000000001
T0: 00000000ff7001ba T1: fffffffffe02a8c0 T2: 676f6f6706367670
S0: 00000000ff700308 S1: 0000000000000000 A0: 0000000000000000
A1: 00000000ffffd988 A2: 0000000000000010 A3: 0000000000000000
A4: 00000000fff9e1fa A5: 0000000000000000 A6: 0000000000000001
A7: 0000000000000001 S2: 0000000000000000 S3: 000000000000fff5
S4: 0000000000010000 S5: 000000000000ffff S6: 00000000000000c0
S7: 00000000ff7001b0 S8: 000000000000000a S9: 0000000000000023
S10: 0000000000000000 S11: 0000000000000000 T3: 00000000ff716d50
T4: 0000000000000035 T5: ffffffffffffffff T6: 00000000ff7001b0
Code: 171b 0187 969b 0106 8f55 bfe9 4501 b749 (411c)
resetting ...
-E
next reply other threads:[~2025-01-02 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 22:26 E Shattow [this message]
2025-01-02 22:47 ` LwIP and multiple network interfaces Tom Rini
2025-01-03 1:34 ` E Shattow
2025-01-03 1:40 ` Tom Rini
2025-01-03 1:52 ` E Shattow
2025-01-03 10:03 ` Jerome Forissier
2025-01-03 17:58 ` E Shattow
2025-01-04 3:05 ` E Shattow
2025-01-06 15:43 ` Jerome Forissier
2025-01-06 19:09 ` E Shattow
2025-01-30 10:23 ` Jerome Forissier
2025-01-31 9:27 ` E Shattow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de7bf6b3-fd45-4c8f-a492-bd41db2aa904@freeshell.de \
--to=e@freeshell.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.