Linux network is unreachable

• network is unreachable. как исправить?, alexmasz, 00:48 , 07-Фев-13, ( 1 )
  • network is unreachable. как исправить?, 3e2, 01:15 , 07-Фев-13, ( 2 )
    • network is unreachable. как исправить?, ACCA, 01:31 , 07-Фев-13, ( 3 )
• network is unreachable. как исправить?, Mr. Mistoffelees, 20:31 , 07-Фев-13, ( 4 )
  • network is unreachable. как исправить?, 3e2, 23:26 , 07-Фев-13, ( 5 )

в netconfig указал шлюз .
но дело похоже не в нем, даже локальные адреса недоступны, т.е. ping 10.1.*.* опять выдает
network is unreachable.. такие дела 🙁

> 10.1.*.* опять выдает
> network is unreachable.. такие дела 🙁

ifconfig
netstat -rn

> и всеравно на ping *.*.*.* выдает network is unreachable.

Ping ничего не выдает. Destination net unreachable — это сообщение, что маршрут на данный адрес не найден (не пингом, а либо неким маршрутизатором по дороге, либо вашич собственный ядром). Шлюз по умолчанию прописан? Ping до него работает? Покажите вывод /sbin/route -n

посмотрел netstat -rn и route. действительно шлюз не прописан.

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
178.162.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
=====================================================================
прописал «route -v add -net 0.0.0.0 gw 178.162.38.1 netmask 0.0.0.0 «
заработало.

Благодарю за помощь,постепенно ухожу с виндовс. млин эмоций вагон! спасибо мужики!

Источник

Linux network is unreachable

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.

Are you new to LinuxQuestions.org? Visit the following links:
Site Howto | Site FAQ | Sitemap | Register Now

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.

Introduction to Linux — A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author’s experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Источник Linux network is unreachable

А как вам тогда подсказывать если вы не пишете свои данные?

Смотри маскИ проверяется 2 раза. При этом каждый раз разная. Первая при отправке вторая при приходе ответного пакета.
Плюс МСЭ тоже фильтрует.

tcpdump можно посмотреть приход пакетов он не только tcp ловит. Или WireShark поставить.
Так вот проверяешь прохождение цепочки в 1 сторону потом в обратную.

Так что проверяйте маски и IP
Выполняем ping 10.1.0.xx

Пакет сверяется по таблицы роутинга. На неё накладывается маска если результат совпадает IP адресом, то пакет отправляется на роутер у вас cтоит * это значит что широквещательно отправляется на сеть ETh1.

А вот обратно берётся маска из ip addr и если пакет не совпадает, то адрес отбрасывается.

Источник

Arch Linux — connect: Network is unreachable

After five unsuccessful Arch Linux installations, I’ve got two that installed correctly. The first time, the network worked fine, and I was even installing Arch Linux over SSH.

After booting from the installed system instead of the live CD, it can’t connect to the network, I get the following message when I try to ping anything, even my router:

connect: Network is unreachable

I’ve tried installing Arch again, because nothing on the Internet seemed to fix my issue. After installing, I’m getting the same issue.

It appears it’s failing to start eth0 because it times out.

4 Answers 4

The problem I was facing was that there was no eth0 (from what I can understand.) Run the command ip link , this should output your interfaces. I did not have the eth0 interface. Instead I had enp1s8 .

Because I was using static, I copied the example profile with cd /etc/netctl then cp examples/ethernet-static my-network . After that, I edited my-network with nano my-network , and changed the Interface from eth0 to en1s8 (or whatever your adapter is in ip link ). Finally, I enabled it to use that profile on startup with netctl enable my-network .

Enabling the profile will ensure that it starts upon boot, but there is no need to reboot the system, simply run netctl start my-network to initialize it immediately.

I was able to get help on the official Arch Linux forums, you can view my topic there.

Network unreachable means you don’t have a route to the network. If you can’t even ping the local router, either you don’t have an IP address or your network interface is down.

netctl is the standard utility for managing network interfaces in Arch. If you haven’t set that (or something else) up, you won’t have any network. Not even DHCP.

Network setup for ArchLinux is well documented in the ArchLinux wiki at https://wiki.archlinux.org/index.php/Netctl

One important clarification of the answer with the highest number of votes — there is NO need to restart. If only network interface is present and proper interface name and configuration used in the profile file in /etc/netcl (let the example copy is named mynet1), then

will start the network profile mynet1 and network route shall work.

will enable system service to be started by systemd service manager with every boot, i.e. it will create a unit file in /etc/systemd/system/netc@[mynetprofilename].service with the unit details (device binding and dependency).

Note also that if network profile is modified it would have to be netctl reenable’d.

Archlinux says, try dhcpcd in case your installer can’t connect automatically. This worked on the spot for me AFTER installation. Just type «dhcpcd» as a command, wait a few seconds, and then «ip route» or «ping 8.8.8.8» to check if it works. I even used «watch ip address» to see how fast these inet and inet6 addresses pop up.

Instead of using dhcpcd, I can also connect from zero with:

e1000e is a «Network Driver», says modinfo. By loading this module I get a eth0 link (no, don’t look for it in /dev). The «ip» commands activate the link, choose an address and define a local (subnet) and then a default gateway. It took me quite some time to test this out (ip link help, ip address help, ip route help. ).

So this is instructive, but «dhcpcd» is faster to type, and probably more robust. And you can stop it cleanly with «dhcpcd -x».

With a working ping and the mirrorlist in /etc/pacman.d/ you have all you need for pacman or pacstrap.

And yes, I saw a kernel message renaming eth0 to enoxxx, so you have to check first with «ip link» what interfaces are already set up by systemd. It happens here:

The .16 in my address is just any (free) number, and 192.168.0.1 should always be the gateway. Maybe I was lucky, but it is good news that you can hack around under systemd and inet6. I will try netctl, though.

And right now I have booted with systemd and have dhcpcd started. I got address .15 on «eno1» and three inet6 addresses, but apart from that the result is quite the same as with above «ip»-hack.

Источник