Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
DebianNovice wrote: ↑2023-10-05 07:41
When I run the SSH command on laptop through root and type the IP Address I set in the /network/interfaces I get "port 22: No route to host".
So yeah I am stuck in this step.
Edit : Tried checking for firewall , ufw is not installed , tried installing it using apt , was getting an error like "Can't resolve "deb.debian.org"".
Now you find the culprit, your network is not configured right. Try
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo ....
and post the result, just remember to use code tags
DebianNovice wrote: ↑2023-10-05 07:41
When I run the SSH command on laptop through root and type the IP Address I set in the /network/interfaces I get "port 22: No route to host".
So yeah I am stuck in this step.
Edit : Tried checking for firewall , ufw is not installed , tried installing it using apt , was getting an error like "Can't resolve "deb.debian.org"".
Now you find the culprit, your network is not configured right. Try
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo ....
and post the result, just remember to use code tags
Hi , I did -> I ran the command on the server I am trying to connect to
I use only systemd network for wired, and iwd/systemd newtork for wireless, but the older iproute & /etc/network/interfaces and wpasupplicant are still valid options.
Hallvor wrote: ↑2023-10-06 15:18
Check that your Ethernet cable is in order and properly connected. Then try requesting an IP-address with dhclient <interface name>, for instance:
DebianNovice wrote: ↑2023-11-01 12:34
Same thing as before except the Interface name got changed for reason , it was eno1 before now it's eth0 and it is still written no carrier.
DebianNovice wrote: ↑2023-11-01 12:34
Same thing as before except the Interface name got changed for reason , it was eno1 before now it's eth0 and it is still written no carrier.
Hallvor wrote: ↑2023-11-08 14:32
If I knew the answer, I would reply already. Apart from checking that your cable works and is well connected, I have no idea.
You would probably get more and better help on your networking problems if you start a new thread in the appropriate forum: viewforum.php?f=5
I understand that this must be frustrating, but hang in there a little longer and I'll bet someone has an answer.
Is it possible just to reinstall debian and try doing this again?