Commit
Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com> Signed-off-by: John Crispin <john@phrozen.org>
- Loading branch information
There are no files selected for viewing
4 comments
on commit 2530951
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blogic I don't know what's the problem, but for me is the same problem, I see traffic on eth0.1 and eth0.2 with tcpdump but is not working
before bootm
a tftp image the network worked, not anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
something is really wired on my device, tried changing some things about led triggering, and I had it all working, but after 2 reboot with the same image, is not working anymore !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blogic is the tl-wr1043nd-v1
port working?
Lot of fixes landed since this commit (currently at: 512c57e) , but I am unable to get this working.
Lot of things works:
- it compiles successfuly
- it boots successfully
pwr
,sys
,lan1..4
,wan
andusb
LEDs working- failsafe works
But it's unreachable: no dhcp server, no reply to ping from static address, even in failsafe mode.
Sadly I have no serial access, so I am unable to provide any boot log.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried changing the pll values, even tried the network adapter ar7100-eth, all work when I boot from ram, as soon as I flash the image the only thing that is working is tcpdump
root@OpenWrt:/# tcpdump -i eth0.2
[ 130.023753] device eth0.2 entered promiscuous mode
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0.2, link-type EN10MB (Ethernet), capture size 262144 bytes
10:02:12.157237 IP 192.168.123.247.62520 > 239.255.255.250.1900: UDP, length 173
10:02:13.157925 IP 192.168.123.247.62520 > 239.255.255.250.1900: UDP, length 173
10:02:13.158437 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:14.158301 IP 192.168.123.247.62520 > 239.255.255.250.1900: UDP, length 173
10:02:15.661840 LLDP, length 167: lede
10:02:16.160918 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:16.487196 IP 192.168.0.5.59785 > 192.168.0.255.1947: UDP, length 40
10:02:18.697342 IP 192.168.123.1 > 224.0.0.5: OSPFv2, Hello, length 44
10:02:19.698964 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:20.493556 IP 192.168.1.100.59785 > 192.168.1.255.1947: UDP, length 40
10:02:20.595070 IP 192.168.0.5.59780 > 239.255.255.250.1900: UDP, length 137
10:02:22.597657 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:23.596572 IP 192.168.0.5.59780 > 239.255.255.250.1900: UDP, length 137
10:02:24.500112 IP 192.168.123.118.59785 > 192.168.123.255.1947: UDP, length 40
10:02:25.501765 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:26.596616 IP 192.168.0.5.59780 > 239.255.255.250.1900: UDP, length 137
10:02:28.599221 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:28.697867 IP 192.168.123.1 > 224.0.0.5: OSPFv2, Hello, length 44
10:02:29.600211 IP 192.168.0.5.59780 > 239.255.255.250.1900: UDP, length 137
10:02:31.602813 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:32.601246 IP 192.168.0.5.59780 > 239.255.255.250.1900: UDP, length 137
10:02:34.603604 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
10:02:35.602144 IP 192.168.0.5.59780 > 239.255.255.250.1900: UDP, length 137
10:02:36.611895 IP 192.168.123.1.137 > 192.168.123.255.137: UDP, length 50
10:02:37.613587 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from f4:ec:38:e9:c1:66 (oui Unknown), length 300
^C
25 packets capture[ 156.470998] device eth0.2 left promiscuous mode
25 packets received by filter
0 packets dropped by kernel
@lucize phy-handle isn't needed because eth0 here only need a fixed link. (And a phy-handle will be ignored because fixed-link is defined below.)