Ping cannot expand address alias when specifying interface [closed] - linux

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed yesterday.
Improve this question
Ping cannot expand an alias (foo) if ALSO specifying an interface (enp5s0f1):
> ping foo%enp5s0f1
ping: foo%enp5s0f1: Name or service not known
I have this alias in /etc/hosts:
fe80:<snip>:dc57 foo
It works when I use the IP instead of the alias:
> ping fe80:<snip>:dc57%enp5s0f1
PING fe80:<snip>:dc57%enp5s0f1(fe80:<snip>:dc57%enp5s0f1) 56 data bytes
It also works if I just use the alias:
> ping foo
PING foo(foo (fe80:<snip>:dc57)) 56 data bytes
I don't understand why the combination of alias AND interface fails.

Related

what does -d 0/0 mean? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 4 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I came across a rule:
iptables -A INPUT -p tcp -s 17.3.3.5/24 -d 0/0 --dport 22 -j DROP
and I was just wondering if someone could explain what this rule is doing. More importantly, I would like to know what the
-d 0/0
part means, in the whole rule (I know its destination specification, so the 0/0 part should be an IP address, but why is it 0/0?).
Im speculating that the rule is dropping that one source address when it arrives at destination port 22, but I'm not sure.
If someone could explain, that would be great.
Couldn't find an answer when searching the interwebs :C
Just like -s 17.3.3.5/24 means any source within the CIDR block 17.3.3.5/24, -d 0/0 means any destination within the CIDR block 0.0.0.0/0. Since there are no bits in the network number, every address is inside this network. So it means any destination at all.

WindRiver - eth0: error fetching interface information: Device not found [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
In the "ifconfig" I don't see eth0 appears.
When I tried to type:
dmesg | grep eth0
I got the following message
eth0: PHY ID 200xx5c99 at 1 IRQ ) (stmmac-1:01) active
And when I typed:
cat /etc/udev/ruled.d/70-persistentnet.rules
I got the following message
# PCI device 0x8086:0x0937 (stmmaceth)
SUBSYSTEM=="net" , ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:97:55:ff:b8", ATTR{dev_id}=="0x0",ATTR{type}=="1",KERNEL=="eth*",NAME="eth0"
I dont get any idea why eth0 does not appear,please let me know if you may have any idea.
The typical reason why ifconfig does not show an interface is because this interface is not in the "UP" state, and the typical (again) reason for this is that the interface does not have an IP address.
For ifconfig to "display all interfaces which are currently available, even if down" (quoting the man page), use ifconfig -a.

How to open Public IPv6 IP on browser without DNS [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am trying to open IPv6 on browser .
For localhost , i tried :
http://::1
--> does not work
I try :
http://[::1]
--> it works
Howerver , i try to open a public IP (google.com IP6 , see $ host google.com output) :
http://2a00:1450:4006:803::200e
i try also :
http://[2a00:1450:4006:803::200e]
--> All attempts make failure .
Without altering /etc/hosts configuration file, how can we open this version of IPs ?
To make firefox use ipv6 enter -> about:config in the adress-bar. In the field beside -> Filter: enter ipv6. There is an option named network.dns.disable.IPv6. Doubleclick on it so it value turns to false and firefox will check about IPv6 now.
You should use the bracket notation like you did
http://[2a00:1450:4006:803::200e]/

What does /etc/hosts do in linux? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I understand domain names here will resolve to the IP shown on the left. But can someone elaborate on this subject and explain what each column does? From what I found, ::1 is IPv6 shorthand?
[root#stack]# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 stack.corp.com stack localhost6.localdomain6 localhost6
Thanks!
The first field is the IP address, the second the canonical host name, and any remaining fields are just aliases that will also resolve to the IP address in the first field.
::1 is, indeed, an IPv6 address, which is short for
0000:0000:0000:0000:0000:0000:0000:0001
(the :: stands in for as many zeros as possible while making the result a valid IPv6 address).

How to get the previous hostname of my linux system? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have accidentally changed my system to host name. Now i want to change it to my previous host name. But i don't know the previous host name.
Have a look at these files:
/etc/hostname
/etc/hosts
/etc/ssh/ssh_host_*_key.pub
$HOME/.ssh/id_*.pub
In these typically the host name appears and it might be still unchanged by your renaming action (however you did that).
Also these might contain the old name:
/var/log/Xorg.failsafe.log
/var/log/auth.log.1
/var/log/pm-suspend.log.1
/var/log/Xorg.1.log.old
/var/log/lightdm/x-0.log
/var/log/lightdm/x-1.log
/var/log/lightdm/x-2.log
/var/log/pm-suspend.log
/var/log/Xorg.0.log.old
/var/log/Xorg.1.log
/var/log/syslog
/var/log/Xorg.2.log
/var/log/auth.log
/var/log/kern.log.1
/var/log/kern.log
/var/log/Xorg.failsafe.log.old
/var/log/syslog.1
/var/log/Xorg.0.log
In most cases HOSTNAME is defined in /etc/sysconfig/network file, to be set when boot. In some cases you can find it in /etc/hostname

Resources