[SOLVED] Old computer can access internet but new computer has not learnt settings from the modem
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This thread is exactly three months old today - problem still not fixed.
Then learn how to configure an ethernet interface and fix it. Look at the docs for your internet connected device.
Quote:
To be specific I got an internet connection on my older computer, and then unplugged the ethernet cable from the back of the older computer and plugged it into the back of the newer computer
A switch passes packets based on MAC address. An RJ45 port is not meant to be hot swapable. Don't do that. I don't know about the device that you have. But it may associate a MAC address with a port.
Do yourself a favor, Stop. Do a little reading. Then you'll understand more and be able to configure what you have.
I currently have a connection with a LiveCd of Linux Mint 19.3 Tricia Mate 64bit running in my older computer, and am using it to write this post! After months of trying!
I fiddled around with various network settings, making several changes. The last thing I altered was ticking/checking "Use Data Centre Bridging (DCB) for this connection."
Would enabling DCB be enough on its own to get a connection? I have never heard of it before.
Other semi-random changes I made were:
Changing the activation level to 0, from -999.
Choosing the other name for the ethernet device from the drop-down menu.
Setting link-negotiation to Ignore.
Typing in the same DNS servers that I previously used.
Entering a DHCP client ID (supplied by the ISP).
Setting "Require IPv4 addressing for this connection to complete" to blank, i.e. unchecked/unticked.
Setting IPv6 settings to Ignore, as my modem/router is set to ignore them.
None of these worked until I also enabled checked/ticked Use DCB.
I would be interested in opinions as to which of the above may have made a difference.
The activation level of -999 was odd.
Now when I've got time I will install Mint 19.3 Mate onto my newer computer, instead of the Mint 19.2
Mate that's currently there, and see if I can tickle it into making a connection.
Since the next version of Linux Mint 20 Ulyana is due to be published this month (June 2020) with support until 2025 rather than 2023, then I shall wait for that.
I wish Mint would guide the user by the hand through trying different methods of making a connection if the automatic method does not work. Puppy Linux used to do this and perhaps still does, at least Puppy Linux 4.2.1 did, and made a connection when no other distribution would.
Nearly two years after the original posting, I seem to have fixed the problem. Today is a miracle day that shall go down in the annals of my personal history!!!!
I replaced the configuration file for my router/modem with one that I used (and had thankfully backed up) about four years ago, before I started tinkering with it to improve security. And lo, I could barely believe that I was connected to the internet with a different computer and the latest version of Mint!
It will be nice using mint 20.2 rather than mint 17.3 I was forced to use.
While trying to fix it I noticed that the modem config file was changed by the different computer rather than staying the same as I would expect.
Last edited by grumpyskeptic; 08-08-2021 at 09:41 AM.
I noticed that the modem config file was changed by the different computer rather than staying the same as I would expect.
It sounds like you are suggesting that the computer (or rather its operating system) actively went into your modem and changed things, which I find extremely unlikely.
The state of the router/modem was changed, probably temporarily I guess, by the different computer, and when I saved that state to the HD as a config file, then the new saved config file was different.
I should have thought of using the backup config file two years ago.
The state of the router/modem was changed, probably temporarily I guess, by the different computer
Sorry but still no.
It is possible that the router changed its own configuration as a result/reaction to attaching a new computer, but NOT that the computer actually "went in there and changed things". No.
You think I'm nitpicking, but that's an important distiction because if you believe in your version you'll be looking for the problem and its solution in all the wrong places - as the last reply to your other thread shows:
You originally asked "Best way to manually copy all network settings from one computer to another?", but the solution was this in the end:
Quote:
Originally Posted by grumpyskeptic
I eventually got things working by re-loading the modem/router config file that I had backed up years ago. I must have made various security settings so severe that it would not work with another computer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.