New clean installation on SSD only OS (no dual boot)
AMD CPU
ASUS (NVIDIA) Video card
4 Gb mem
Gigabyte mobo
Wired connection directly to my router configured as DHCP
Disable IP v6 since i read somewhere that it was causing issues (only IP v4). no luck
Not able to connect to network, status says link active, network manager simply can’t connect.
ip addr
1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 bdr 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0 <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether fc:aa:14:2a:6d:89 bdr ff:ff:ff:ff:ff:ff
inet fe80::feaa:14ff:fe2a:6d89/64 scope link
valid_lft forever preferred_lft forever
ip -s link
1: lo <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 bdr 00:00:00:00:00:00
RX: bytes packets errors dropped overrun mcast
3888 48 0 0 0 0
TX: bytes packets errors dropped overrun mcast
3888 48 0 0 0 0
2: eth0 <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether fc:aa:14:2a:6d:89 bdr ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped overrun mcast
60 1 0 0 0 0
TX: bytes packets errors dropped overrun mcast
432 2 0 1739 0 0
Your wired network interface is not picking up network settings, and is not assigned an IP address.
So,
You can investigate why you’re not picking up a network settings from DHCP if that is your configuration
You can configure a static IP address and other network settings. As long as your configuration is valid and unique on your network, ordinarily it should work.
You can enable IPv6 generally, nowadays in most parts of the world IPv6 is common and expected. But, if you have a problem with networking enabling IPv6 can just be an additional confusing factor.
You should consider whether any other devices are successfully using DHCP on your network (phones? other computing devices?), this can suggest whether the problem is individual to your machine or generally affecting all the devices on your network.
You should inspect the physical network connection (and observe blinking indicator NIC lights) to be sure your link layer is functioning properly before considering higher level issues.
I have not set static IP because i do not want to start adding configuration to this (usually this causes more trouble when someone is trying to help you)
IPv6 was already active i tried disabling via the network manager i am not too familiar with this OS but understand enough not to make absurd changes.
All my other devices in my network 3 laptops, 1 desktop (besides the one i am trying to fix) and all my wireless devices use DHCP, so i will put the blame on my comp, which before this had win 7 and Remix OS installed in with no network issues.
The blinking lights on the NIC all all active seems to be creating a proper ling, just not getting IP from the router. access my router setting and i can’t see the computer.
No need to type…
Except for xterm, all openSUSE consoles are “enhanced” to support a number of extra features, including the ability to select text, then do a CTL-SHFT-C to copy to your clipboard, which can then be pasted wherever you want, including into your forum post.
Unlike others, I don’t suspect something related to the network service and related, at most you might have a configuration issue (since you’re using Network Manager, inspect the connection properties).
If you make changes and want to try to refresh your network settings, simply restart your networking service with the following
systemctl restart network
You can configure a static address temporarily as part of your troubleshooting process, if successful it verifies that everything except DHCP is working correctly.
At the moment I suspect that when you installed your new OS, the DHCP lease for your old OS still hasn’t expired, preventing your new machine from acquiring a new lease (The DHCP server sees the same MAC address that was used by your old OS so thinks your machine already knows its network settings).
If the above netowrk restart doesn’t work, you can force acquiring an address from your DHCP server by first removing the lease associated with your machine’s MAC address. Then, restart the network service on your machine threby forcing the DHCP server to set up a new lease.
don’t mean to sound like an idiot or anything, but if I could copy paste directly from console to the forums, this thread would be stupid.
Unlike others, I don’t suspect something related to the network service and related, at most you might have a configuration issue (since you’re using Network Manager, inspect the connection properties).
i have double checked the connection properties, what specific would you like me to check?
If you make changes and want to try to refresh your network settings, simply restart your networking service with the following
systemctl restart network
that doesn’t seem to have any effect.
the result of the command was nothing.
You can configure a static address temporarily as part of your troubleshooting process, if successful it verifies that everything except DHCP is working correctly.
setting up a static IP didn’t work
At the moment I suspect that when you installed your new OS, the DHCP lease for your old OS still hasn’t expired, preventing your new machine from acquiring a new lease (The DHCP server sees the same MAC address that was used by your old OS so thinks your machine already knows its network settings).
To prevent any issues with lease i have factory reset my router, recreated all my wireless connection, and all my wired devices are connecting with no issues except for my lin box.
If the above netowrk restart doesn’t work, you can force acquiring an address from your DHCP server by first removing the lease associated with your machine’s MAC address. Then, restart the network service on your machine threby forcing the DHCP server to set up a new lease.
TSU
how do i force acquire an address? by resetting my router i presume all leases were released. also i have restarted the network service and no luck
The NetworkManager log shows the point at which you connect the ethernet cable, with ‘Wired connection 1’ (d3f8f6d3-63de-47de-9f21-ec5dd9415812) being activated, and and dhclient is started
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> (eth0): link connected
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> (eth0): device state change: un
available -> disconnected (reason 'carrier-changed') [20 30 40]
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> Auto-activating connection 'Wir
ed connection 1'.
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> (eth0): Activation: starting co
nnection 'Wired connection 1' (d3f8f6d3-63de-47de-9f21-ec5dd9415812)
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> (eth0): device state change: di
sconnected -> prepare (reason 'none') [30 40 0]
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> NetworkManager state is now CON
NECTING
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> (eth0): device state change: pr
epare -> config (reason 'none') [40 50 0]
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> (eth0): device state change: co
nfig -> ip-config (reason 'none') [50 70 0]
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> Activation (eth0) Beginning DHC
Pv4 transaction (timeout in 45 seconds)
Jun 27 17:41:52 linux-ee40 NetworkManager[1035]: <info> dhclient started with pid 1644
but nothing further shown. There is a 45 second window for the valid DHCPv4 lease to be obtained, but your log doesn’t show such a lease obtained.
Assuming it is is your DSL router that provides the DHCP server for your LAN, try restarting that, and see if you get a new lease.
dmartin@linux-hi6j:~> sudo dhclient -v eth0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/08:00:27:ed:72:ae
Sending on LPF/eth0/08:00:27:ed:72:ae
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x5b3b6b38)
DHCPACK from 172.20.10.1 (xid=0x5b3b6b38)
bound to 172.20.10.11 -- renewal in 33555 seconds.
sudo dhclient -v eth0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/fc:aa:14:2a:6d:89
Sending on LPF/eth0/fc:aa:14:2a:6d:89
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0x75654585)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0x75654585)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x75654585)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x75654585)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 (xid=0x75654585)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 (xid=0x75654585)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 (xid=0x75654585)
No DHCPOFFERS received.
No working lease in persistent database - sleeping.
ls: cannot access /var/run/netconfig//eth0/: No such file or directory
Hope that helps, I can see that the lease is not being provided, however i do not know what could be causing that
Okay, so that confirms no DHCP lease given. This just leads me to ask more questions…difficult when we’re remote from your network environment.
All other devices are using DHCP and obtain valid addresses I assume?
What is the make/model of your router?
Are you connected to a LAN port?
If this machine is dual boot, does it get a valid IP address when booting from other OS? Maybe worth testing via a live distro as well eg Live distro on USB stick.
Yes all my wired (3 other computers) receive IP with no problem and my around 10 other wireless device also receive an Ip with no problem.
What is the make/model of your router?
my router is an Verizon FIOS Actiontec MI424WR (the router is mine not lease) so i can throw it against the wall if need be
Are you connected to a LAN port?
Yes i am connected via wired to port 3 on my router (LAN ethernet Port 3) just in case
If this machine is dual boot, does it get a valid IP address when booting from other OS? Maybe worth testing via a live distro as well eg Live distro on USB stick.
No this box is currently set up as a single OS, I had Win 7 and Remix OS on it as a dual boot system prior to this.
just to check the port is that not the root of the error changed from port 3 to port 2
The computer now on port 3 got an IP right away.
Did a reboot of the Suse box (now on port 2), and ran
sudo dhclient -v etho
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/fc:aa:14:2a:6d:89
Sending on LPF/eth0/fc:aa:14:2a:6d:89
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 (xid=0x3c6a5ae1)
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 (xid=0x3c6a5ae1)
No DHCPOFFERS received.
No working lease in persistent database - sleeping.
ls: cannot access /var/run/netconfig//eth0/: No such file or directory
Verizon FIOS router/modem
|
--------------------------------------------------------------------------------
| | | |
Personal router* Suse Box Laptop Private router**
| | | | | | |
NAS*** Work Laptop 1 Work Laptop 2
Personal router currently disconnected since i wasn’t getting an IP on it either. also moved all devices to VZ FIOS wired and wireless
** Private router due to work
*** NAS temporarily moved in place of Personal router in VZ router
My personal router is an old school Netgear WGT624 v3
My Private router is a Netgear WNR834B v2
It seems to relate to RFC3442 (Classless Static Route Option for DHCPv4), and the way dhclient may be interacting with this router. A bug report may be needed. One workaround I’ve stumbled cross mentions commenting out the option rfc3442 line in /etc/dhclient.conf, but I’m not sure if this will work for you or not. Anyway, /etc/dhclient.conf contains this entry
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
which could be commented out by adding ‘#’ at the beginning of the line. The file will need to be edited as root eg using nano editor
sudo nano /etc/dhclient.conf
Here’s where I read of the workaround being employed successfully
There are many other threads discussing similar if you care to search. Others may be able to offer further advice here.
This is not an openSUSE-specific issue (IMO), and I’m not sure that dhclient is really at fault, but it might be due the DHCP implementation in the router, so you could try swapping the router out as that is likely to resolve as well.
Consider configuring NM with a static IP address, gateway (router IP address), and DNS server. Then DHCP is not involved.
/etc/dhclient.conf line 43: no option named rfc3442-classless-static-routes in spce dhcp rfc3442-classless-static-routes.
/etc/dhclient.conf line 48: ntp-servers: expected option name.
netbios-node-type, netbios-scope, ntp-servers;
i will look at those threads really quick and see if i can configure the actual router, i did went trought the settings and realized the IPv6 was disabled so i enabled that in the router.
