Hello …
I have one small problem.
Specifically, on a desktop computer at work, I use openSUSE and
Yast → Network Settings → Global Options → Network Setup Method
I selected “Traditional Method with ifup”
My computer has been added to the Windows domain and everything works beautifully.
For a desktop computer is not problem that ifup is selected because it’s connected with wire.
I’ve installed openSUSE on a laptop and initially I also setup settings like desktop computer
and all my work when my laptop is plugged in via the cable network.
However a problem is with wireless device.
If you add wireless via ifup-a, then Internet is not working,
but domain normally work and i have rights that have as a domain user.
If in Yast -> Network Settings -> Global Options -> Network Setup Method
I select “User Controlled with NetworkManager” that creates problems.
Now I have the KDE NetworkManagement widget to select the wireless and Internet is working, there is a problem with the domain.
When “User Controlled with NetworkManager” is selected then neither LAN or WLAN did not work during boot.
And it occurs to me that when I log on with a domain account, then my username is taken from the cache from laptop, and does not find the domain and i don’t have rights as domain user because the network just fallen upon boot.
What interests me: How can I get the “User Controlled with NetworkManager” settings works on boot so i can login with domain user and not with the account from the cache?
Well, I hope I was clear.
PS: I was looking for some solutions already on the net, but all we tested did not work.
When configuring network connections with NetworkManager, you can also define system connections that can be shared by all users. In contrast to user connections, system connections are made available right after NetworkManager is started—before any users log in. For more details about both types of connections, refer to Section 25.7.1, “User and System Connections”.
On 2014-07-22 09:06, deano ferrari wrote:
>
> If you really prefer to use NM, then I suppose you need to set the
> connection up as a ‘System Connection’ instead.
Not only that, you need to make NM delay boot till the connection is
established.
In my case, I notice that services like “postfix” fail to start for this
reason. I have not yet investigated how to solve it.
Have a look at the following option in /etc/sysconfig/network/config:
## Type: int
## Default: 0
#
# When using NetworkManager you may define a timeout to wait for NetworkManager
# to connect in /etc/init.d/network(-remotefs) script. Other network services
# may require the system to have a valid network setup in order to succeed.
#
# This variable has no effect if NETWORKMANAGER=no.
#
NM_ONLINE_TIMEOUT="0"
And NetworkManager-wait-online.service has to be enabled (but it should be by default).
On 2014-07-22 12:56, wolfi323 wrote:
>
> robin_listas;2655187 Wrote:
>> In my case, I notice that services like “postfix” fail to start for this
>> reason. I have not yet investigated how to solve it.
>>
> Have a look at the following option in /etc/sysconfig/network/config:
>
> Code:
> --------------------
> ## Type: int
> ## Default: 0
> #
> # When using NetworkManager you may define a timeout to wait for NetworkManager
> # to connect in /etc/init.d/network(-remotefs) script. Other network services
> # may require the system to have a valid network setup in order to succeed.
> #
> # This variable has no effect if NETWORKMANAGER=no.
> #
> NM_ONLINE_TIMEOUT=“0”
>
> --------------------
I already had it at 30…
> And NetworkManager-wait-online.service has to be enabled (but it should
> be by default).
Ah, that one is disabled. Maybe because the laptop is not a fresh install, but upgraded from 11.4 and earlier.
Question: what would happen if there really is no network, would it continue after 30 seconds, or would “NetworkManager-wait-online.service” wait for ever?
…] Ah, I can find that out myself: it waits just that timeout:
