Why I can't upgrade system from computer LAN?

kerogaz

kerogaz

I use compuer of LAN ip 10.44.55.55 Internet from 10.44.55.55 work

sudo freebsd-update upgrade -r 15.0-RELEASE
Password:
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... none found.
Fetching metadata signature for 14.3-RELEASE from update.FreeBSD.org... failed.
No mirrors remaining, giving up.

This may be because upgrading from this platform (amd64)
or release (14.3-RELEASE) is unsupported by freebsd-update. Only
platforms with Tier 1 support can be upgraded by freebsd-update.
See https://www.freebsd.org/platforms/ for more info.

If unsupported, FreeBSD must be upgraded by source.
 
VladiBG said:
You don't have Internet access or your DNS is not working.
Click to expand...
ping google.com
PING google.com (142.251.98.100): 56 data bytes
64 bytes from 142.251.98.100: icmp_seq=0 ttl=115 time=14.324 ms
64 bytes from 142.251.98.100: icmp_seq=1 ttl=115 time=14.329 ms
 
It may be a temporary glitch because the system is overloaded with so many people try to update to the newly released version.
 
This computer's system is a copy of a computer with NAT. I swap them, and sometimes one works, sometimes the other. I just recently changed the local IP and didn't connect the NAT output. Maybe the data from one is stored in some cache and is preventing the other from upgrading?
 
Just because ping works doesn't mean a HTTP(S) connection can be made, ping google.com working really only means routing and DNS works (still a valuable test, if these don't work everything else certainly won't).

You might want to check your firewall rules and make sure you can actually open a HTTP or HTTPS connection.

Try fetch http://update.freebsd.org/14.3-RELEASE/amd64/latest.ssl does that work? Time-out?


kerogaz said:
Maybe the data from one is stored in some cache and is preventing the other from upgrading?
Click to expand...
TCP/IP packets aren't cached. You might have some ARP issues, but then you wouldn't be able to ping either.
 
kerogaz said:
This computer's system is a copy of a computer with NAT. I swap them, and sometimes one works, sometimes the other. I just recently changed the local IP and didn't connect the NAT output. Maybe the data from one is stored in some cache and is preventing the other from upgrading?
Click to expand...
One prevents the other from upgrading sounds unrealistic to me. If any, the machine's own cache would prevent itself from upgrading. However,
Point is, your machine simply does not get a decent internet connection.
I don't know your set-up, but first to me 10.44.55.55 does not look as a good choice for an IP for a computer behind a LAN router.
And second, since you said both computers are (identical) copies of each other, and you switch them sometimes, and by my understanding LAN routers do the designation of a machine within a LAN by its MAC address, which for sure on both machines differ, while as I understand you you gave them the same IP, I presume your router is somehow "confused".
I would simply try to give one machine another IP that differs from the other's, and see what happens.
 
Maturin said:
One prevents the other from upgrading sounds unrealistic to me. If any, the machine's own cache would prevent itself from upgrading. However,
Point is, your machine simply does not get a decent internet connection.
I don't know your set-up, but first to me 10.44.55.55 does not look as a good choice for an IP for a computer behind a LAN router.
And second, since you said both computers are (identical) copies of each other, and you switch them sometimes, and by my understanding LAN routers do the designation of a machine within a LAN by its MAC address, which for sure on both machines differ, while as I understand you you gave them the same IP, I presume your router is somehow "confused".
I would simply try to give one machine another IP that differs from the other's, and see what happens.
Click to expand...
Local ip NAT 10.44.1.1 mask 255.255.0.0 this computer now 10.44.55.55 mask 255.255.0.0 .I only changed 10.44.1.1 to 10.44.55.55
 
I can't understand why the internet connection from computer 10.44.55.55 works through NAT, but the upgrade from freebsd.org doesn't work.
 
For example, I go from 10.44.55.55 to an internet speed test website and I see the download and upload speeds.I can access the freebsd.org website through NAT, but I can't perform an upgrade through NAT.I have to turn off the computer with NAT, put this computer in its place, and perform the upgrade using a direct address.
 
Just going to repeat myself.
SirDice said:
ust because ping works doesn't mean a HTTP(S) connection can be made, ping google.com working really only means routing and DNS works (still a valuable test, if these don't work everything else certainly won't).

You might want to check your firewall rules and make sure you can actually open a HTTP or HTTPS connection.

Try fetch http://update.freebsd.org/14.3-RELEASE/amd64/latest.ssl does that work? Time-out?
Click to expand...
 
kerogaz said:
I can't understand why the internet connection from computer 10.44.55.55 works through NAT, but the upgrade from freebsd.org doesn't work.
Click to expand...

Does your employer use a transparent HTTP proxy? My previous employer did. If they insert their own https proxy using their certs, so they can see the traffic unencrypted, you may have some issues.

Try the fetch advice above. Also try to fetch the file using a browser.

I have one virtual machine on my employer's laptop here at home that performs freebsd-update through NAT, my own NAT. I have no problems. I do not have a transparent HTTP proxy. When I take my employer's laptop laptop to the office I must adjust the proxy settings on the FreeBSD VM to use their NTLM authenticated proxy. Otherwise it times out.

You need to find out more about your employer's network and adjust your proxy settings accordingly.
 
Today I tried to install FreeBSD 15.0 from computer on the local network via NAT. It was impossible, so I had to turn on the switch with direct IP addresses.
 
And what's interesting is that Windows and Linux are updated through this NAT.And I think that the problem here is not NAT, but rather inadequate software interaction between the internal and external network cards that are installed on the computer. I installed the system via a network card with a direct address, but I'm trying to update via a network card with a local address. I don't remember exactly, but I think in versions 10 or 11 I updated the system via NAT
 
Try this:

host -t srv _http._tcp.update.FreeBSD.org

and see if you get a result like this:

_http._tcp.update.FreeBSD.org has SRV record 1 50 80 update2.freebsd.org.
_http._tcp.update.FreeBSD.org has SRV record 100 50 80 dualstack.aws.update.freebsd.org.
_http._tcp.update.FreeBSD.org has SRV record 1 50 80 update1.freebsd.org.

I've never used freebsd-update, but it's very similar internally to portsnap which I have used. Both use SRV records to find mirrors.
 
You must log in or register to reply here.
Back
Top