long time no post, been waiting on replacement parts but Pocket’s back alive, and in that time i bought an RJ-45 to IX Industrial cable, 8M long, and just got it plugged into my Pocket, but Gnome says the cable’s not plugged in.
is there a driver i need to grab to get the IX industrial running? or manual configuration i need to do? ip link show gives no difference in output between plugged in or not. did i maybe just get a bad cable?
any help is greatly appreciated
I have the same problem, no matter what CPU I use (I tried 2 different cables). I was thinking it’s my fault so didn’t investigate it further.
The cable should just be like a normal RJ45 cable with no special components inside, it’s just a different connector on one side.
You didn’t specify which CPU modules (@jirka), so it’s hard for me to help effectively.
I know that for a311d we have a workaround for the ethernet reset in /bin/reform-hw-setup, if you run that manually, does it complete without errors?
8m is a non trivial length for a first test. Also, what is on the other side, a switch, or a computer? What if you restrict the link to 100mbit/s in Gnome Settings → Network? Please give as much context as possible.
Initially the original CPU, then then RCORE. I use a short blue cable and a longer one (from Crowdsupply, I think). Should I try the way which you have for a311d?
OK, lets stick to RCORE here.
strangely enough i’ve rebooted since then and it’s automatically just, working again. idk what happened but it seems to be working now.
one thing i noticed is i can’t set it to the same MAC address as my wifi. i use static IPs so it’d be really annoying to have two different IPs for SSH purposes, might just have to make wifi mirror IX Industrial’s MAC, but idk if that’s something you can advise on?
Glad that the issue resolved itself. Why would you set two network interfaces to the same MAC address? Is this some “galaxy brain” technique I haven’t encountered yet? I lack the fantasy to understand how ARP would work in that case, and also I don’t understand the utility of that approach.
yeah same
as for the MACs, i’m trying to use the same MAC on a specific network (my home network) since when ethernet is connected wifi is automatically disabled temporarily so there’s no issue there for connectivity from the device end, and that way the MAC shown to the network is always the same so you always get the same static IP.
now technically i could set the two MACs to use the same reservation in the router’s DHCP settings since it’s the same device so it realistically wouldn’t have the duplicate device issue, but it feels nicer this way, and also this way it’ll avoid the router freaking out if for some reason in the handoff from wifi to ethernet they both wind up connected at the same time for a few seconds, however if they’re the same MAC, as far as the network’s concerned, there’s just two paths to the same MAC, through my AP and the ethernet switches, which networks are designed to tolerate on L2.
to put simply: this way the router doesn’t have a panic attack and the network at large handles the stress instead
I think this is broadly not a great idea.
That said, I think the right way to handle this is probably with a bridging interface; set the bridge interface MAC to the MAC that you wish to receive whatever IP it receives, and then put both of your physical interfaces on the bridge, but unbound to IP.
The disadvantage is that your dual-homed device might form part of the spanning tree, but maybe you can ask the bridge to decline that negotiation.
I actually put a custom static MAC address on my network interfaces all the time. Even right now. Why? Because it seems to be really popular in the universities I’ve worked at (Sweden and Germany) to use MAC addresses to check whether a device is allowed in the employee-only network or not. Yes, this is silly of the employer, I know. For my first employer I gave them the MAC address 10:00:00:00:00:00 (i learned that day that it cannot be all zeroes) to show them how silly their approach is. But of course this was a policy decided by the higher-ups that they just had to follow. It’s for the security, you know. With my next employer I was smart and got a USB ethernet dongle and gave my employer the MAC address of that dongle. That way, I could use their network with any device which has a USB port without going through the hassle of setting up a custom mac address even. Just plug and play. Why the same MAC address for wifi and ethernet? Because for security reasons, each employee was only allowed a single MAC address. Why? Because as an employee you only had one computer, so if you ever need two MAC addresses, then you must be doing something that’s not allowed like trying to bring a second device to work even though you are only allowed one, right? Sigh…