Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop

Categories

In this Discussion

Home › Offers
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

★ VirMach ★ Black Friday & Cyber Week 2018 ★ RAID 10 SSD ★ OpenVZ & KVM ★ Check inside for offers!

1…500501503505506…548

Comments

  • donlidonli Member

    @VirMach said:
    Random Raisin update:

    Thanked by 1FrankZ
  • oriendoriend Member

    @ZA_capetown said:
    @oriend did you try the "fix internet / reconfigure network" button in the control panel?

    Yeah, I did. After like half a min or so, I get this message:

    so have no idea does it do anything. It did restart VPS, but as soon as I logged on I saw:

  • ZA_capetownZA_capetown Member

    @oriend said:

    Yeah, I did. After like half a min or so, I get this message:

    Oh no! :-(

    Can you at least ping yourself / localhost : ping 127.0.0.1 with success?

    The not resolving is clearly the DNS settings.
    Unreachable seems like the routing table / wrongly assigned IP etc.

    But if ping to localhost doesn't work it's probably the eth0 / network card drivers malfunctioning.

  • oriendoriend Member

    @ZA_capetown yeah, pinging localhost works. If I ping 1.1.1.1 for example, I get ping:connect: Network is unreachable.

  • imokimok Member

    Is the network port up?

  • JabJabJabJab Member

    Route not configured?
    IP not configured?

    What does ip r s and ip a s shows?

  • oriendoriend Member

    @imok netstat is not found, so I'm not sure is there any other way to check beside these:

  • ZA_capetownZA_capetown Member

    Ok, that's at least good news.

    Look at your /etc/network/interfaces file.
    And compare it to the IP listed in your control panel.
    Let's say your IP is 123.123.123.123
    then your interfaces file should look something like

     auto lo
  iface lo inet loopback

 auto eth0
  iface eth0 inet static
   address 123.123.123.123
   gateway 123.123.123.1
   netmask 255.255.255.0
   dns-nameservers 8.8.8.8 8.8.4.4

    Then also check your /etc/resolv.conf
    It should look something like:

    nameserver 8.8.8.8
nameserver 8.8.4.4

    Do those seem correct on your side?

  • oriendoriend Member

    @JabJab said:
    Route not configured?
    IP not configured?

    What does ip r s and ip a s shows?

    ip r s does nothing

    @ZA_capetown

    /etc/network/interfaces file is completely empty. /etc/resolv.conf has:

    nameserver 127.0.0.53
    options edns0

    And thanks for helping guys!

  • JabJabJabJab Member
    edited December 2021

    ens3 is down, start by brining it up, maybe DHCP/config will kick in. However this should not happen until you messed with things.
    ip link set ens3 up

    You have no IP, gateway, DNS configured. This should not happen.
    Is this fresh install? Did you mess with something? Is this image install? Don't you want to re-install system from the panel?

  • ZA_capetownZA_capetown Member

    ok great...
    So both your IP is not assigned and the routing/gateway is not set

    so taking 123.123.123.123 as your example IP (check in control panel your actual IP)

    So try:

    ifconfig eth0 123.123.123.123 netmask 255.255.255.0 up

    then

    route add default gw 123.123.123.1

    Then test to ping again to an external IP

  • oriendoriend Member

    @JabJab said:
    ens3 is down, start by brining it up, maybe DHCP/config will kick in. However this should not happen until you messed with things.
    ip link set ens3 up

    You have no IP, gateway, DNS configured. This should not happen.
    Is this fresh install? Did you mess with something? Is this image install? Don't you want to re-install system from the panel?

    ip a s now showing

    Yes, fresh install. First, I had Ubuntu 18.04 desktop I think and internet didn't work either, so tried that reconfigure networking button in control panel. I'm not sure did it work, but eventually I noticed there is an internet connection. Also, I noticed main IP is changed, I'm not sure when did that happened. So I though the problem is fixed and wanted to install debian 10. It showed some networking issue in the middle of installer. I thought there is some issue in Debian ISO itself being netinstall edition, so I mounted ubuntu 20.04 ISO and installed it. I did nothing after the installation, except that I changed boot order in the control panel, so it doesn't boot into the installer again.

    @ZA_capetown said:
    ok great...
    So both your IP is not assigned and the routing/gateway is not set

    so taking 123.123.123.123 as your example IP (check in control panel your actual IP)

    So try:

    ifconfig eth0 123.123.123.123 netmask 255.255.255.0 up

    then

    route add default gw 123.123.123.1

    Then test to ping again to an external IP

    Unfortunately, I can't use ifconfig as it's reporting it as not found.

  • ZA_capetownZA_capetown Member

    ok... without ifconfig... use the newer ip command

    I think if you just create the /etc/network/interfaces file as above it should work, but you can also try...

    Assign your IP:

    ip addr add 123.123.123.123 dev eth0

    then create your gateway:

    ip route add default via 123.123.123.1

  • oriendoriend Member

    @ZA_capetown I made /etc/network/interfaces file as you wrote above (with my IP obviously) and edited resolv.conf, but no luck for now.

    If I try first command for assigning IP, I get:

    Cannot find device "eth0"

  • ZA_capetownZA_capetown Member

    oh.. wait yours is ens3 ? ...ok try ens3 instead of eth0 :-)

  • oriendoriend Member
    edited December 2021

    Now ip addr passes without any output, yet ip route shows

    RTNETLINK answers: Network is down

    edit: got

    Error: Nexthop has invalid gateway

  • ZA_capetownZA_capetown Member

    ip link set ens3 up ?

  • oriendoriend Member

    Passed without any output, but ip route returned the same message again.

    Tbh, I can't believe it requires all these stuff to be done just to make internet connection works and yet it still hasn't been set up.

  • ZA_capetownZA_capetown Member

    Yes, all this is supposed to be set automatically as jabjab mentioned earlier... I haven't had to set these by hand in ages...

    re: the "nexthop invalid gateway" error... are you sure you didn't make a typo with the add default line? the IP of the gateway ending in .1 ?

    And that is where I'm assuming it is a 255.255.255.0 subnet mask etc etc...
    ...if it is not, the gateway might be something else, like 123.123.120.1 (and not *.123.1 - if using a different subnet mask)

    hang on a moment I think actually solus has an option to get the correct networking info, will check quick

  • netomxnetomx Moderator, Veteran

    @imok said: I don't like raisins.

    we dont like you

  • oriendoriend Member

    @ZA_capetown said: re: the "nexthop invalid gateway" error... are you sure you didn't make a typo with the add default line? the IP of the gateway ending in .1 ?

    Yeah, it's .1 at the end.

    Gateway is the same as the IP except it has .1 and the end ofc. As you mentioned, solus has that info, it can be found by clicking the IP on Network tab in the control panel.

  • ZA_capetownZA_capetown Member

    @oriend said:
    @ZA_capetown I made /etc/network/interfaces file as you wrote above (with my IP obviously) and edited resolv.conf, but no luck for now.

    If I try first command for assigning IP, I get:

    Cannot find device "eth0"

    Ok... so... did you use eth0 or ens3? And did you reboot after you created the file?

    I'm used to it being "eth0"... but in your case it seems it is using "ens3" - so you have to keep it the same in all those files/commands

    (I do apologise I'm with lack of sleep, so I'm feeling like I'm not being of much help right now :-O )

  • JabJabJabJab Member
    edited December 2021

    @oriend said: Gateway is the same as the IP except it has .1 and the end ofc. As you mentioned, solus has that info, it can be found by clicking the IP on Network tab in the control panel.

    Not always, not everything runs on /24.
    Clicking the IP in Network tab of control panel is correct way to get your 'supposed' IP, netmask and gateway, yes.

    However here I would just reinstall system from one of the provided images. If autoconfig went wrong with IP you have no idea what else is wrong.

    Thanked by 1ZA_capetown
  • ZA_capetownZA_capetown Member

    @oriend said:

    @ZA_capetown said: re: the "nexthop invalid gateway" error... are you sure you didn't make a typo with the add default line? the IP of the gateway ending in .1 ?

    Yeah, it's .1 at the end.

    Gateway is the same as the IP except it has .1 and the end ofc. As you mentioned, solus has that info, it can be found by clicking the IP on Network tab in the control panel.

    Aah, the random VPS I checked just now of mine... in the Solus-> Network->

    I see that one of mine actually uses "255.255.255.224" as the netmask, and not 255.255.255.0

    So... what info does that give you?
    The same as my examples? Or different?
    Use those listed in Solus

  • ZA_capetownZA_capetown Member

    Yes, I thought it cooler to 'quickly' fix it by hand... but I agree with @JabJab that a re-install is the better way to go...

    ...also maybe there is an error in the system right now and by tomorrow it will be fixed and the install will work correctly?

    Might be better than trying for too long now when it's maybe a system wide glitch

  • oriendoriend Member

    Well for my VPS, it looks like this:

    IP Address x.x.x.z
    Gateway x.x.x.1
    Netmask 255.255.255.0
    Nameserver 8.8.8.8
    Nameserver 8.8.4.4

    Anyway, I mounted ISO again and second step on the installer, it shows this:

    At the bottom is the option "Continue without network". So I guess this is the problem, as it was the same thing with previous OSes, what should I do here?

  • donlidonli Member

    503

    Thanked by 1FrankZ
  • JabJabJabJab Member

    @oriend said: At the bottom is the option "Continue without network". So I guess this is the problem, as it was the same thing with previous OSes, what should I do here?

    There should be 'configure manually' somewhere - maybe you need to back and click it screen earlier, I don't remember :)

    also please specify the node (from Solus/panel) you are running on, VirMach probably would want to investigate it one day why DHCP is dead.

  • oriendoriend Member
    edited December 2021

    I'm giving up, honestly. I spent way more time than I planned.

    Once clicked on ens3 eth small menu opens up, where you can pick 'edit IPv4'. Once clicked there, it gives options Automatic (DHCP) which does nothing I guess, because once picked, it shows DHCPv4 and it endlessly "spins", will be possible to see on the screenshot below.

    If I pick manual, I get this:

    Node is AMSKVM5.

  • JabJabJabJab Member

    @oriend said: Node is AMSKVM5.

    @VirMach there seems to be DHCP dead on that node, please fix :)

    @oriend said: If I pick manual, I get this:

    Almost, this is good. The subnet comes as 255.255.255.0, delete the /24 and it should be good - this should match the data in SolusVM -.> Network -> Click IP.

This discussion has been closed.