that could be a reason in any case i manage to do something creative actually
here is a screen shot of the wireshark output from my Suse box the snapshot is taken n a win computer but with the output of the Suse machine so don’t be confused.
here is a screenshot of the device connecting to my router
and this are my DHCP setting on my router
Hi
Interesting wireshark, it’s all ipv6, no ipv4…
Is it possible to temporarily remove all devices from the network, reboot the router and see if the openSUSE computer connects.
I would have thought the limit is 5 devices obtaining an external ip address, not an internal private ip address? But hopefully the above will help?
All strange…
Try the lspci command without the grep command and identify the ethernet device and driver and post those lines. Just the type of ethernet and pci id and driver is enough.
Oh ok i reviewed this, it has to do with not actual network is more for on-demand content, so that you can only register a certain number of devices for on-demand
Okay, that makes sense.
Hello, from post #21
# /sbin/lspci | grep thernet
05:00:00 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Remove all device!!! :S somebody will have my head for that, but i guess i can remove a few some of them are required to the actual set-top-box
Hi
OK, I have two of those devices and another on this box (3 ethernet and one wireless), all ethernet are using the r8169 driver fine, now there are some that work better with the r8168 driver can you provide the pci id eg for mine it’s [10ec:8168].
Ok i have deleted all but this laptop and my NAS
and no the Suse box didn’t connect 
Actually mine is also the same [10ec:8168]
oh and i didn’t know i had to use
lspci -nn
live and learn 
but now i have no excuse why this is not working
Hi
The kernel-firmware package is installed?
Tried a different cable? Does the openSUSE box cable work with the NAS?
how do i check the kernel firmware version?
sadly the ethernet cable is not the culprit. I will see if can factory reset and try to set up the router again. maybe removing all those connected devices might do some magic.
Hi
Ensure your install medium is present and run;
zypper in kernel-firmware
Well nothing seems to be working, i am going to reformat my drive and do a clean install once more. and keeping only the latest network set up with my work router of course connected.
If this doesn’t work i guess i have to get back on to Win, or maybe try Debian i have not used that in such a long time, last i remember set up for it was very cumbersome.
Will let you know how it goes.
Ok, nothing worked. same results as before.
But i had a crazy idea i have an old wireless USB adapter netgear WPN111. I know it works, i hooked it to my daughter desktop and it was able to acquire an IP with no problems.
so plug it into my Suse box still nothing, i presume is autoconfigure, correct, when wireless is enable wired disables? or is there something i should do??
Hi
The driver might need firmware, again check with the output from lsusb -vv, you may also need to install rfkill and check as well as journalctl.
So open a terminal and switch to root user;
su -
zypper in rfkill
rfkill list
journalctl -f
Now unplug the device and then re-plug and check the output from the journalctl command for errors… ctrl+c to exit the journalctl command.
You are correct, after reading a little it seems i need the drivers for the chipset Atheros AR5005UG. and after running lsusb -vv it confirms that it is an Atheros Communication chip.
While trying to install rfkill, all my repos fail, it seems is only trying my online repo not my local.
when accessing my repo list via YAST2 GUI i can see my dvd there as an active repo
Hi
So temporarily disable the online ones, then try again.
What’s the PCI ID of the device?
Yes i tried that but no results, this is just absurd :X
What’s the PCI ID of the device?
This i am not sure of, i cannot see a USB profiles that matches what i was given before.
running
lsusb -vv
Bus 005 Device 003: ID 1385:5F01 Netgear, Inc WPN111 (no firmware)
Device Descriptor:
bLength 18
bDescriptoratype 1
bcdUSB 2.00
bDeviceCLass 255 Vendoer Specific Class
and a lot of extra info
however running
lspci -nn
i do not see that device in the list.
If a usb device it will be in lsusb not lspci, or at least should What does networkmanager see? need that for wifi at least for the most part
I agree it shoud be in the lsusb list.
Also at this point hte NM sees nothing since i do not have the drivers for the USB adapter so right now i am attempting to gt my system to recognize my DVD as a repo. once i get the driver install then we can worry about what the NM sees. IMHO.