Okay, so the problem is that your router, or whatever, has only assigned an IPv6 address to the Kiwi Ethernet. An IPv4 address is also needed (i.e. an IPv6 address alone won't work).
Sorry, once again I can't remember the total history here. Dozens of emails each day.
So this is a new Kiwi-2. Has the Ethernet ever worked? Since you used the fixer sd card does it now display the Kiwi LED pattern mentioned on the Operation Information webpage?
@WA2TP Well, about all I can suggest is to wait a bit longer for me to finish making the new Debian 11 image and then re-flash from that. It should put everything back into DHCP mode.
It's takes forever to construct one of these distro images..
@bob53bob So you said earlier you were using Win32DiskManager to copy the image file onto the sd card (I think you meant to say Win32DiskImager).
After you've downloaded the KiwiSDR_BBG_BBB_EEPROM_fixer.img.xz file from kiwisdr.com you're using a decompression utility to then create a file called KiwiSDR_BBG_BBB_EEPROM_fixer.img correct? And using the .img file with Win32DiskImager?
I was using what was in the zipped folder. I just tried unzipping it and used this with DiscImager and the lights now flash but within 30 seconds go into the double flash mode. Again, I know so little about these matters but want to keep trying.
@bob53bob That's great. My apologies for being a bit short tempered about this. Things are totally out of control around here. I've got lots of very cool stuff waiting to be released in an update and I can't seem to make any progress on it because of all the unrelated things happening. But we'll get there I suppose..
Your patience with me was beyond the call of duty....and appreciated. The S9+20 noise floor was caused by the old BeagleBone. Meter is now around S1 with no antenna. Thanks again.
Really? Wow! I'd sure like to understand what about the BB is causing that level of RFI. I think the small EMI loop probes I have here are up to the task.
If you're up to shipping it to me I'll reimburse you double what it costs you..
Comments
@bob53bob Well, I don't know what to tell you at this point. My guess is that your ISP is throttling the download. Let me guess, a cable provider?
edited: left space out of cat command initially.
debian@kiwisdr:~$ cat /etc/systemd/network/eth0.network
[Match]
Name=eth0
Type=ether
[Link]
RequiredForOnline=yes
[Network]
DHCP=ipv4
debian@kiwisdr:~$ networkctl status
● State: routable
Address: 192.168.7.2 on usb0
fe80::a04:b4ff:fea0:3cf on eth0
fe80::5645:38ff:fe3c:82fe on usb0
Mar 10 16:30:09 kiwisdr systemd-networkd[572]: usb0: Gained carrier
Mar 10 16:33:33 kiwisdr systemd-networkd[572]: usb0: Lost carrier
Mar 10 16:33:33 kiwisdr systemd-networkd[572]: usb0: DHCPv6 lease lost
Mar 10 16:37:27 kiwisdr systemd-networkd[572]: usb0: Gained carrier
Mar 10 17:07:47 kiwisdr systemd-networkd[572]: eth0: Lost carrier
Mar 10 17:07:47 kiwisdr systemd-networkd[572]: eth0: DHCPv6 lease lost
Mar 10 17:09:51 kiwisdr systemd-networkd[572]: eth0: Gained carrier
Mar 10 17:10:33 kiwisdr systemd-networkd[572]: eth0: Lost carrier
Mar 10 17:10:34 kiwisdr systemd-networkd[572]: eth0: DHCPv6 lease lost
Mar 10 17:16:39 kiwisdr systemd-networkd[572]: eth0: Gained carrier
debian@kiwisdr:~$ ip
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
ip [ -force ] -batch filename
where OBJECT := { link | address | addrlabel | route | rule | neigh | ntable |
tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |
netns | l2tp | fou | macsec | tcp_metrics | token | netconf | ila |
vrf | sr | nexthop | mptcp }
OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
-h[uman-readable] | -iec | -j[son] | -p[retty] |
-f[amily] { inet | inet6 | mpls | bridge | link } |
-4 | -6 | -I | -D | -M | -B | -0 |
-l[oops] { maximum-addr-flush-attempts } | -br[ief] |
-o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
-rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] |
-c[olor]}
debian@kiwisdr:~$
Try
ifconfig eth0debian@kiwisdr:~$ ifconfig eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a04:b4ff:fea0:3cf prefixlen 64 scopeid 0x20<link>
ether 08:04:b4:a0:03:cf txqueuelen 1000 (Ethernet)
RX packets 334 bytes 68515 (66.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 270 bytes 56133 (54.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Okay, so the problem is that your router, or whatever, has only assigned an IPv6 address to the Kiwi Ethernet. An IPv4 address is also needed (i.e. an IPv6 address alone won't work).
its odd. I connect an old BBG and the router assigns IP and shows the DHCP reservation.
This BBG it does not show up. I have even tried created a static ip/mac reservation and nothing.
fe80:: is a link local adress, it assigns that itself.
@WA2TP
Does that ethernet cable/connector work on other clients?
can you show the output of
"ethtool eth0"
Yes this cable is a known good cable.
debian@kiwisdr:~$ ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 0
Transceiver: external
MDI-X: Unknown
netlink error: Operation not permitted
Current message level: 0x00000000 (0)
Link detected: yes
debian@kiwisdr:~$
Well that's odd.
Does it get an ip address with "dhclient eth0" ?
dhclient eth0
operation not permitted
sudo dhclient eth0
hangs for a long time still doens not take an IP
i have now connected it to an old off network ax6000 router and same results. my laptop takes an IP immediately beagle does not.
i have even swapped the cables.
Sorry, once again I can't remember the total history here. Dozens of emails each day.
So this is a new Kiwi-2. Has the Ethernet ever worked? Since you used the fixer sd card does it now display the Kiwi LED pattern mentioned on the Operation Information webpage?
This is a new KIWI-2
It worked out of the box until i assigned a static IP and disabled "register at kiwi sdr.com"
after the fix.sh sd card the correct kiwi led pattern now shows
I can access the kiwi via usb only via putty.
i can get to the kiwi web page via usb but not the admin page
If I run:
it says it takes the IP, but no traffic passes - it cannot ping and does not show up in routing table.
I got it downloaded but even with a new card, the LED's don't start flashing in the first 15 seconds.
@WA2TP Well, about all I can suggest is to wait a bit longer for me to finish making the new Debian 11 image and then re-flash from that. It should put everything back into DHCP mode.
It's takes forever to construct one of these distro images..
@bob53bob So you said earlier you were using Win32DiskManager to copy the image file onto the sd card (I think you meant to say Win32DiskImager).
After you've downloaded the
KiwiSDR_BBG_BBB_EEPROM_fixer.img.xzfile from kiwisdr.com you're using a decompression utility to then create a file calledKiwiSDR_BBG_BBB_EEPROM_fixer.imgcorrect? And using the .img file with Win32DiskImager?will do. I have two spare old BBG from the KIWI-1.
I was able to successfully reflash two of them and they work just fine.
I was using what was in the zipped folder. I just tried unzipping it and used this with DiscImager and the lights now flash but within 30 seconds go into the double flash mode. Again, I know so little about these matters but want to keep trying.
Even though it did the double flash, it eventually powered off and my.kiwi.sdr found it !
@bob53bob That's great. My apologies for being a bit short tempered about this. Things are totally out of control around here. I've got lots of very cool stuff waiting to be released in an update and I can't seem to make any progress on it because of all the unrelated things happening. But we'll get there I suppose..
Your patience with me was beyond the call of duty....and appreciated. The S9+20 noise floor was caused by the old BeagleBone. Meter is now around S1 with no antenna. Thanks again.
Really? Wow! I'd sure like to understand what about the BB is causing that level of RFI. I think the small EMI loop probes I have here are up to the task.
If you're up to shipping it to me I'll reimburse you double what it costs you..
@jks
Is it safe to keep the kiwis on the old debian 11 image if my KIWISDR10 kiwis didn't had problems?
(So the part number will not be overwritten with blank spaces in the future)
Yes.