| 1 |
On Thu, Jul 6, 2017 at 2:44 PM, Francisco Ares <frares@×××××.com> wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> 2017-07-06 13:07 GMT-03:00 R0b0t1 <r030t1@×××××.com>: |
| 5 |
>> |
| 6 |
>> On Thu, Jul 6, 2017 at 10:51 AM, Francisco Ares <frares@×××××.com> wrote: |
| 7 |
>> > Hi, All. |
| 8 |
>> > |
| 9 |
>> > This is a bit odd, because of a non conventional hardware platform: |
| 10 |
>> > Odroid |
| 11 |
>> > (Hardkernel). |
| 12 |
>> > |
| 13 |
>> > But I guess overall rules apply to all. |
| 14 |
>> > |
| 15 |
>> > I need a second network interface, the original and single one present |
| 16 |
>> > on |
| 17 |
>> > the board is to be connected to a GigE camera, so I use a USB/ethernet |
| 18 |
>> > adapter to have SSH remote access. |
| 19 |
>> > |
| 20 |
>> > I have set up the boot manager so that network interfaces would be named |
| 21 |
>> > according to the predictable names rules. If not, the USB/eth adapter |
| 22 |
>> > gets |
| 23 |
>> > "eth0" if the device is present at boot, otherwise, it is "eth1". |
| 24 |
>> > |
| 25 |
>> > But if I disconnect the USB/ethernet adapter to leave the system alone, |
| 26 |
>> > and |
| 27 |
>> > after a while I need to take a look on what's going on and plug back the |
| 28 |
>> > USB/ethernet adapter, it comes up as "eth0" again. |
| 29 |
>> > |
| 30 |
>> > Anyone could give me a hint on where to look at it? Why the new |
| 31 |
>> > interface |
| 32 |
>> > is named in a way during boot and another during normal use? |
| 33 |
>> > |
| 34 |
>> > Thank you! |
| 35 |
>> |
| 36 |
>> Your question doesn't seem to involve any mixing of the naming schemes |
| 37 |
>> at all, and it looks like the kernel you are using simply uses the old |
| 38 |
>> style names. Can you compile your own kernel which supports the new |
| 39 |
>> naming convention, remove net.ifnames=0 from the kernel command line |
| 40 |
>> if it is present, or check for udev rules that perform naming that |
| 41 |
>> overrides the default? You may wish to refer to |
| 42 |
>> |
| 43 |
>> https://wiki.gentoo.org/wiki/Handbook:X86/Networking/Advanced#Network_interface_naming |
| 44 |
>> though it is not very information dense. |
| 45 |
>> |
| 46 |
>> Unfortunately my experience with hardkernel devices is that the |
| 47 |
>> developers put most of their effort behind the Android release and |
| 48 |
>> will make an Ubuntu release, if it exists, barely work. I would |
| 49 |
>> strongly recommend not buying their devices. They barely support them |
| 50 |
>> and without their help the devices are unsupportable. |
| 51 |
>> |
| 52 |
>> R0b0t1. |
| 53 |
>> |
| 54 |
> |
| 55 |
> |
| 56 |
> Thanks for the tip. I've checked in /etc/udev files and directories, and |
| 57 |
> there is no rule for naming interfaces. |
| 58 |
> |
| 59 |
> Instead of removing "net.ifnames=0" from the kernel command line, I have |
| 60 |
> altered it to "net.ifnames=1". Gonna try removing it at once. |
| 61 |
> |
| 62 |
|
| 63 |
I would expect that to work as you did, are you using their kernel? If |
| 64 |
you are I believe there is an option to force the old-style naming by |
| 65 |
effectively removing the code which does the new-style naming. That's |
| 66 |
why I asked. |
| 67 |
|
| 68 |
> But, imho, Odroid is a good hardware, and I have learned a lot about Linux - |
| 69 |
> not Android - in their Odroid magazine. And their Ubuntu image works very |
| 70 |
> good. And, as always, there are a lot of guys in the community. |
| 71 |
> |
| 72 |
|
| 73 |
It is some of the best available hardware, but the support its |
| 74 |
manufacturer provides isn't amazing. It's the bare minimum to get it |
| 75 |
to work. Admittedly they did have a bit more customer involvement than |
| 76 |
I've seen elsewhere at first (e.g. signing user-provided code with |
| 77 |
Samsung keys to enable ARM TrustZone for QEMU) but they are still |
| 78 |
focused on making money, and sell whatever it is they can as quickly |
| 79 |
as possible and then move on to the next thing and avoid supporting |
| 80 |
past products. |
| 81 |
|
| 82 |
R0b0t1. |
Archives