Issue obtaining IP Address - Link is up/down?

[JohnXovox]

I recently purchased a Tetra (had an excellent experience with the Nano for a year now) and followed the video directions. It recognizes the hardware, and i get a string of carrier on/carrier off's I'm guessing as the interface is coming up and down? syslog shows dhcp/Network manager can't get a bead on it. I've tried this on 3 other machines (Mint, Kali and Debian Workstation) with basically identical results. Doing a watch -n1 ifconfig eth1 shows it under UP,BROADCAST,RUNNING,MULTICAST and bouncing RUNNING up and down. 

I have a suspicion that it has something to do with NetworkManager, but i'm not totally sure. But I would not be surprised.

I've checked through the messages and can't seem to find a similar issue, so I created an account and am doing The Ask. Hopefully someone can point me in the right direction. I was about to dig out an old windows machine to try it on, but my main driver is my linux machines. Any help would be appreciated! I've posted the relevant dmesg output, please feel free to let me know if other information would be helpful!

Thanks

J

----------------------------

[643918.115628] usb 1-8: new high-speed USB device number 38 using xhci_hcd
[643918.269893] usb 1-8: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=92.24
[643918.269899] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[643918.269902] usb 1-8: Product: USB2.0 Hub
[643918.269905] usb 1-8: Manufacturer: GenesysLogic
[643918.271262] hub 1-8:1.0: USB hub found
[643918.271951] hub 1-8:1.0: 4 ports detected
[643918.505840] usb 1-8: USB disconnect, device number 38
[643918.511876] usb 1-8-port1: attempt power cycle
[643918.671677] usb 2-8: USB disconnect, device number 4
[643960.759626] usb 1-8: new high-speed USB device number 43 using xhci_hcd
[643960.912552] usb 1-8: New USB device found, idVendor=0bda, idProduct=8152, bcdDevice=20.00
[643960.912557] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[643960.912561] usb 1-8: Product: USB 10/100 LAN
[643960.912563] usb 1-8: Manufacturer: Realtek
[643960.912566] usb 1-8: SerialNumber: ZZXYZ
[643961.043911] usb 1-8: reset high-speed USB device number 43 using xhci_hcd
[643961.220421] r8152 1-8:1.0: skip request firmware
[643961.248669] r8152 1-8:1.0 eth1: v1.11.11
[643963.516018] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[643963.516348] r8152 1-8:1.0 eth1: carrier on
[643965.108889] r8152 1-8:1.0 eth1: carrier off
[643966.620351] r8152 1-8:1.0 eth1: carrier on
[643969.656602] r8152 1-8:1.0 eth1: carrier off
[643971.164565] r8152 1-8:1.0 eth1: carrier on
[643971.284831] r8152 1-8:1.0 eth1: carrier off
[643972.988202] r8152 1-8:1.0 eth1: carrier on
[643988.308890] r8152 1-8:1.0 eth1: carrier off
[643989.788609] r8152 1-8:1.0 eth1: carrier on
[644009.364886] r8152 1-8:1.0 eth1: carrier off
[644010.844310] r8152 1-8:1.0 eth1: carrier on
[644012.504738] r8152 1-8:1.0 eth1: carrier off
[644015.388159] r8152 1-8:1.0 eth1: carrier on
[644017.048884] r8152 1-8:1.0 eth1: carrier off
[644018.556459] r8152 1-8:1.0 eth1: carrier on
[644021.588843] r8152 1-8:1.0 eth1: carrier off
[644023.100334] r8152 1-8:1.0 eth1: carrier on
[644023.224492] r8152 1-8:1.0 eth1: carrier off
[644024.700584] r8152 1-8:1.0 eth1: carrier on
[644031.179652] device wlan0 entered promiscuous mode  --- > That one was weird..
[644040.244912] r8152 1-8:1.0 eth1: carrier off
[644041.725191] r8152 1-8:1.0 eth1: carrier on
 

...etc...ad nausium..

 

Thanks!

[JohnXovox]

Update: I have hooked it into my windows machine and a similar issue occurs, the interface begins to bounce up and down over and over. I'm a bit concerned I got a bad unit.

[JohnXovox]

Final Update: I have fixed it. Not sure if it was just my unit or all units, but the Tetra won't start correctly off of just USB power. The device came up after some complaints after I also plugged in the power supply. The setup video indicates that the USB Y cable plugged into two USB 3.0 supplies the required 10W, but that does not appear to be the case, at least for me. I'm not sure if the specs have changed, but if so Hak5 may want to update their video or make some sort of overlay note.

 

Otherwise, hopefully if someone else comes across this, this will help diagnose the issue!