mersenneforum.org  

Go Back   mersenneforum.org > Extra Stuff > Blogorrhea > EdH

Reply
 
Thread Tools
Old 2020-10-22, 14:00   #12
Nick
 
Nick's Avatar
 
Dec 2012
The Netherlands

5DC16 Posts
Default

Quote:
Originally Posted by EdH View Post
If anyone has any thoughts about the Internet issue, I wouldn't mind reading them. I "think" I have all the rest under control, even if it is going to take a long time to get these machines factoring again.
I don't use Ubuntu but the rule of thumb with IP problems is that they are either routing problems or filtering problems.
What does the routing table look like?
Nick is online now   Reply With Quote
Old 2020-10-22, 18:04   #13
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

32·383 Posts
Default

Quote:
Originally Posted by Nick View Post
I don't use Ubuntu but the rule of thumb with IP problems is that they are either routing problems or filtering problems.
What does the routing table look like?
The only difference is a "Metric" value:

Working machine:
Code:
$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG    100    0        0 eno1
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eno1
192.168.0.0     0.0.0.0         255.255.255.0   U     100    0        0 eno1
Non-working machine:
Code:
$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG    20100  0        0 eno1
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eno1
192.168.0.0     0.0.0.0         255.255.255.0   U     100    0        0 eno1
But, I don't know what that signifies.

"ip route" shows the same values:

Working machine:
Code:
$ ip route
default via 192.168.0.1 dev eno1 proto static metric 100 
169.254.0.0/16 dev eno1 scope link metric 1000 
192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.96 metric 100
Non-working machine:
Code:
$ ip route
default via 192.168.0.1 dev eno1 proto static metric 20100 
169.254.0.0/16 dev eno1 scope link metric 1000 
192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.44 metric 100
EdH is offline   Reply With Quote
Old 2020-10-23, 17:02   #14
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

32·383 Posts
Default

On the good side, I have 18 (17) of 20 original machines fully upgraded with all the latest of everything. (One of the 18 didn't fully upgrade the OS.) But, it is fully working for all the factoring packages.

On the bad side, the two that stopped being able to access the Internet have not gotten any better and I haven't been able to determine why. Everything appears to point to them working correctly. However, I don't have any 18.04 machines to compare them directly with ATM.

I'm looking at two approaches:

1. I'm upgrading a 16.04 machine to 18.04 to see if I can match its settings better to the two that don't work.

2. I'm exploring the idea of setting up a proxy server on one of my other machines and using it to reach the Internet. I'm hoping that method will allow me to upgrade them to 20.04 and see if that fixes the Internet issue. Even if it doesn't solve the issue, if I can get these machines fully upgraded for all the packages and they remain able to work within the LAN, all should be good.

For the most part, once I got into a routine, all the upgrading went well for the majority of the machines. I was even able to just "svn up" and recompile some of the packages without starting from scratch although other packages didn't work that way, even after "uninstalls" and "make clean" attempts.

@Xyzzy: The package manager approach sounds good on the surface, but I like to be able to catch all the latest revisions for YAFU, msieve,CADO-NFS, etc.
EdH is offline   Reply With Quote
Old 2020-10-23, 21:18   #15
EdH
 
EdH's Avatar
 
"Ed Hall"
Dec 2009
Adirondack Mtns

32·383 Posts
Default Internet Access Resolved - Maybe. . .

I'm not sure if this is the correct way to resolve the issue, but it worked.

I edited the /etc/systmed/resolved.conf file to replace the:
Code:
#DNS=
line, with:
Code:
DNS=192.168.0.1
However, the OS tells me something is amiss and it can't do a proper upgrade to 20.04. So, there is still trouble with these machines.

Might be time for a new install of the OS!

Edit: Just like magic! After I reported that they wouldn't upgrade properly, I returned to see what could be done. They both started the upgrades without any further complaint. . . yet!

Last fiddled with by EdH on 2020-10-23 at 21:30
EdH is offline   Reply With Quote
Reply

Thread Tools


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrading a cat. 0 box ckdo PrimeNet 3 2018-03-12 15:24
Upgrading a LGA 775 foxmccloud123 Hardware 14 2013-05-19 06:09
Upgrading Ubuntu from 9.04 to 11.04 ET_ Linux 9 2012-03-05 20:04
Screen resolution problem after upgrading ubuntu fivemack Linux 6 2008-05-24 12:51
Problems after upgrading to ubuntu gutsy apocalypse Linux 3 2007-12-22 23:24

All times are UTC. The time now is 15:49.

Fri Nov 27 15:49:43 UTC 2020 up 78 days, 13 hrs, 4 users, load averages: 1.63, 1.30, 1.21

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.