Why on earth does my OS want to access the network when I reconfigure my network connection? How do I stop it?
I am sincerely hoping the answer does not have me enabling and disabling my repositories every time I change the static IP address. I would configure it through network manager, but it fails to make any change for me and tells me to use Yast. Just to try to follow all of these stupid rules, I connected to the internet and changed my connection and it still didn’t work! I set it for a static IP in Yast, and after I saved it networkmanager still wanted dhcp, and it disabled networking when it didn’t get it.
I can’t believe this is broken in three different ways. This is a wired ethernet connection. This has been working in linux for decades. I’m speechless. (it’s probably just as well)
For the second half of my problem, I found the global options tab in network settings which allows me to not use NetworkManager, which appears to be broken on SUSE 11 'cause it can’t operate in conjunction with YAST. Now it uses ifup instead, which is much more appropriate for a static wired configuration.
I’m still looking to disconnect the repository lookup from network settings configuration. Does anyone know why I have to download a file if I change my ip address? Know how to fix this bug?
> For the second half of my problem, I found the global options tab in
> network settings which allows me to not use NetworkManager, which
> appears to be broken on SUSE 11 'cause it can’t operate in conjunction
> with YAST. Now it uses ifup instead, which is much more appropriate for
> a static wired configuration.
>
> I’m still looking to disconnect the repository lookup from network
> settings configuration. Does anyone know why I have to download a file
> if I change my ip address? Know how to fix this bug?
I wish I could help, but I do not have a clue what you are talking about.
Going into YaST->Network Devices->Network Settings does not cause any
repository interaction on my system. While I use ifup on my desktop
machine (wired connection), NetworkManager also works just fine on my
notebook (both wired and wireless capabilities).
Maybe if you supplied a bit more information about your setup, someone
(smarter than I) might spot an issue you can modify to get your system
working more the way you want it.
It doesn’t happen when ifup is used, but when networkmanager is selected then during the activate network services step of “saving network configuration” you get an error:
Why do I need to download repomd.xml in order to configure my NIC? Is it expected that every network connection will be an internet connection? Really? And why is this only a problem when networkmanager is running?
I looked though bugzilla, but didn’t find this. There are other forum threads, but the only advice I’ve seen is to disable online repositories.
When you configure your network without an active connection you get this problem. The solution is to only enable the install media dvd in the repo’s list. When Yast looks for packages in the configuration, now it will only look at the dvd - which will be available.
Once done and with luck, an active network. You can re-enable the other repo’s…
> When you configure your network without an active connection you get
> this problem. The solution is to only enable the install media dvd in
> the repo’s list. When Yast looks for packages in the configuration, now
> it will only look at the dvd - which will be available.
>
> Once done and with luck, an active network. You can re-enable the other
> repo’s…
But you can count on seeing the problem over and over if you have only a
wireless connection available - just about every time you make any change
to the Yast config function. When you hit finish, the whole networking
setup is re-initialized and all you have is a non-initialized wifi channel.
Royal PITA and no good reason for it to exist.
Reminds me of my first formation landing: in order to make one, you had to
be certified. To be certified, you had to have made one. And that was
before Dilbert!
By solution, you mean work-around, right? You would hit this again the next time your system thought the metadata needed updating and you had the bad luck to change your ip address.
In fact, I think I’ll disable all repos, including the DVD. In my typical use case, none of them will be available when my connection is active. It’s wrong to assume they will be. I’ll enable them again manually when I need to do an update. It’s not the ideal arrangement, but I can avoid the error messages that way.
Thanks for the reply. I wonder why this happens, and why it only happens with networkmanager. If a repo update is mandatory, why does ifup work the way it should?
Strictly speaking the DVD is not a repo, at least not in the sense that the others (eg; updates) are.
You should leave the DVD enabled, you don’t need an active internet connection for it to work.
When using Yast to configure something - it will need access to the DVD or the online equivalent.
But as you don’t have a working connection, it can’t go online. But if you have ONLINE repo’s in your config it still attempts to access them.
It’s nothing to do with metadata or your IP address.
That can’t be right. That’s a bug in YaST then. The only software I know of that requires you to leave your cd/dvd in the drive is game software using copy protection. It should copy what it needs to be able to change and IP address without external media. This is a basic function.
Secondly, it may want to check a repository whenever there’s any update, but it shouldn’t throw an error. The configuration works fine afterward, so it wasn’t really required, was it? Having 6 pop-up error messages makes this problem all the more obvious - or so I thought. I’m baffled by the matter-of-fact reply.
Config of devices may require the installation of Packages which are not currently installed on your system. They have to come from somewhere. So unless you have an .iso image of the dvd on your HD acting as a repo then you will need to use the dvd.
If it is the case that you have setup the network, but then at a later date you go back and change a setting say, and it still requests media access - then it does sound buggy.
(it’s probably just as well)