I have a headless system that I cannot connect to. So I was thinking to put a direct connection to it and my notebook. Both ethernets would use the zeroconf (169.254.0.0/16) addresses. I could then use fping
fping -g 169.254.0.0/16
And SHOULD be able to get its address, and then SSH into the box.
Any other thoughts? I can't get to the box to recable it and reboot it (as that is the only way I can figure out for it to readdress eth0) until this evening.
On Mon, 2014-07-21 at 10:55 -0400, Robert Moskowitz wrote:
I have a headless system that I cannot connect to. So I was thinking to put a direct connection to it and my notebook. Both ethernets would use the zeroconf (169.254.0.0/16) addresses. I could then use fping
fping -g 169.254.0.0/16
And SHOULD be able to get its address, and then SSH into the box.
I was under the impression that zeroconf did some rudimentary name resolution, and you ought to be able to connect to hostname.local (replacing "hostname" with the actual hostname).
It'd be a bit dopey if a zero-configuration scheme required you to configure things...
Any other thoughts? I can't get to the box to recable it and reboot it (as that is the only way I can figure out for it to readdress eth0) until this evening.
Only that: Are you on the same network? 169.254 connections can't be expected to be reachable outside of their own net.
On 07/21/2014 11:25 AM, Tim wrote:
On Mon, 2014-07-21 at 10:55 -0400, Robert Moskowitz wrote:
I have a headless system that I cannot connect to. So I was thinking to put a direct connection to it and my notebook. Both ethernets would use the zeroconf (169.254.0.0/16) addresses. I could then use fping
fping -g 169.254.0.0/16
And SHOULD be able to get its address, and then SSH into the box.
I was under the impression that zeroconf did some rudimentary name resolution, and you ought to be able to connect to hostname.local (replacing "hostname" with the actual hostname).
It'd be a bit dopey if a zero-configuration scheme required you to configure things...
I am doing a little testing, and zeroconf does not seem to be working. I am seeing the link up light on my ethernet port. I am seeing a local-scope v6 address, but no v4 address:
p6p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::ea9a:8fff:fe8d:7b56 prefixlen 64 scopeid 0x20<link> ether e8:9a:8f:8d:7b:56 txqueuelen 1000 (Ethernet) RX packets 7 bytes 2130 (2.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 46 bytes 4948 (4.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note that it is receiving packets from the other system. It also has a local-scope ipv6 addr, but no zeroconf addr (both systems are Fedora 20).
So how do I start zeroconf? Of course on the other system, I can't do that...
So given ipv6 local-scope, how do I learn the other system's addr. Trying to figure out fping6. How do I restrict it to the desired interface?
Any other thoughts? I can't get to the box to recable it and reboot it (as that is the only way I can figure out for it to readdress eth0) until this evening.
Only that: Are you on the same network? 169.254 connections can't be expected to be reachable outside of their own net.
Crossover cable. Is that enough of a 'same network'? :)
And I have considerable routing and addressing knowledge. Besides being one of the authors of rfc 1918, and worked on CIDR, here at IETF I contribute to ipv6ops and ipv6man.
Kind of.
No zeroconf. For some reason. But at least ipv6 local-scope.
Used wireshark to capture dhcp probes to get MAC address.
Converted MAC address into IPv6 local scope address.
ssh ipv6%interface
and I am in!
Now to later do this later to the actual box rather than between two notebooks. But it should work the same!
On 07/21/2014 12:34 PM, Robert Moskowitz wrote:
On 07/21/2014 11:25 AM, Tim wrote:
On Mon, 2014-07-21 at 10:55 -0400, Robert Moskowitz wrote:
I have a headless system that I cannot connect to. So I was thinking to put a direct connection to it and my notebook. Both ethernets would use the zeroconf (169.254.0.0/16) addresses. I could then use fping fping -g 169.254.0.0/16 And SHOULD be able to get its address, and then SSH into the box.
I was under the impression that zeroconf did some rudimentary name resolution, and you ought to be able to connect to hostname.local (replacing "hostname" with the actual hostname).
It'd be a bit dopey if a zero-configuration scheme required you to configure things...
I am doing a little testing, and zeroconf does not seem to be working. I am seeing the link up light on my ethernet port. I am seeing a local-scope v6 address, but no v4 address:
p6p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::ea9a:8fff:fe8d:7b56 prefixlen 64 scopeid 0x20<link> ether e8:9a:8f:8d:7b:56 txqueuelen 1000 (Ethernet) RX packets 7 bytes 2130 (2.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 46 bytes 4948 (4.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Note that it is receiving packets from the other system. It also has a local-scope ipv6 addr, but no zeroconf addr (both systems are Fedora 20).
So how do I start zeroconf? Of course on the other system, I can't do that...
So given ipv6 local-scope, how do I learn the other system's addr. Trying to figure out fping6. How do I restrict it to the desired interface?
Any other thoughts? I can't get to the box to recable it and reboot it (as that is the only way I can figure out for it to readdress eth0) until this evening.
Only that: Are you on the same network? 169.254 connections can't be expected to be reachable outside of their own net.
Crossover cable. Is that enough of a 'same network'? :)
And I have considerable routing and addressing knowledge. Besides being one of the authors of rfc 1918, and worked on CIDR, here at IETF I contribute to ipv6ops and ipv6man.
Hi,
So given ipv6 local-scope, how do I learn the other system's addr.
According to http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/x1162.html
ip -6 neigh show
Regards, Fernando.
On 07/21/2014 02:19 PM, Fernando Gozalo wrote:
Hi,
So given ipv6 local-scope, how do I learn the other system's addr.
According to http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/x1162.html
ip -6 neigh show
Oow. that works! Will note that down for next time!
thanks
On Mon, 2014-07-21 at 12:34 -0400, Robert Moskowitz wrote:
I have considerable routing and addressing knowledge. Besides being one of the authors of rfc 1918, and worked on CIDR, here at IETF I contribute to ipv6ops and ipv6man.
Sorry, didn't mean to impune you, but I don't remember who's done what, so I just took the easy route of asking the obvious question.
The other thing that occurred to me, much later, was zeroconf probably requires broadcasting to be allowed through the firewall, so that clients can announce themselves, and the rest can notice their arrival.
On 07/22/2014 12:16 AM, Tim wrote:
On Mon, 2014-07-21 at 12:34 -0400, Robert Moskowitz wrote:
I have considerable routing and addressing knowledge. Besides being one of the authors of rfc 1918, and worked on CIDR, here at IETF I contribute to ipv6ops and ipv6man.
Sorry, didn't mean to impune you, but I don't remember who's done what, so I just took the easy route of asking the obvious question.
The other thing that occurred to me, much later, was zeroconf probably requires broadcasting to be allowed through the firewall, so that clients can announce themselves, and the rest can notice their arrival.
avahi-autoipd -D <interface>
worked on one end. Can't figure out why it did not on the other. Fortunately that is my own notebook where I just:
ifconfig enp0s18f2u1 169.254.7.246 netmask 255.255.0.0 route add -net 169.254.0.0 netmask 255.255.0.0 dev enp0s18f2u1 metric 99
On 07/22/14 00:34, Robert Moskowitz wrote:
Crossover cable. Is that enough of a 'same network'?
FWIW, I've not seen the need to use crossover cables in years. Even when connected peer-to-peer the HW is now capable to detect this situation and auto configure itself using standard cables.
On Jul 22 22:19, Ed Greshko wrote:
On 07/22/14 00:34, Robert Moskowitz wrote:
Crossover cable. Is that enough of a 'same network'?
FWIW, I've not seen the need to use crossover cables in years. Even when connected peer-to-peer the HW is now capable to detect this situation and auto configure itself using standard cables.
Depends on the network speed of the involved NICs, usually. 10 or 100 Mbit/s NICs typically need crossover cables, 1G NICs and faster provide auto-negotiation(*).
Corinna
(*) http://en.wikipedia.org/wiki/Medium_Dependent_Interface#Auto_MDI-X
On 07/22/14 22:27, Corinna Vinschen wrote:
On Jul 22 22:19, Ed Greshko wrote:
On 07/22/14 00:34, Robert Moskowitz wrote:
Crossover cable. Is that enough of a 'same network'?
FWIW, I've not seen the need to use crossover cables in years. Even when connected peer-to-peer the HW is now capable to detect this situation and auto configure itself using standard cables.
Depends on the network speed of the involved NICs, usually. 10 or 100 Mbit/s NICs typically need crossover cables, 1G NICs and faster provide auto-negotiation(*).
Not at all my experience. Unless you've got really old 10 and 100 mbs HW.
On 07/22/2014 10:27 AM, Corinna Vinschen wrote:
On Jul 22 22:19, Ed Greshko wrote:
On 07/22/14 00:34, Robert Moskowitz wrote:
Crossover cable. Is that enough of a 'same network'?
FWIW, I've not seen the need to use crossover cables in years. Even when connected peer-to-peer the HW is now capable to detect this situation and auto configure itself using standard cables.
Depends on the network speed of the involved NICs, usually. 10 or 100 Mbit/s NICs typically need crossover cables, 1G NICs and faster provide auto-negotiation(*).
(*) http://en.wikipedia.org/wiki/Medium_Dependent_Interface#Auto_MDI-X
There are SOME 100Mb that work OK. But watch for the 2 wire 100Mb with POE coming out probably in a year or two. The target market is for sensors (in buildings) or car networks. Vastly lowered wire costs.
No crossover needed, as it is all on 1 pair of wires!
The 1 pair PoDL is 802.3bu. The 100Mb is still a study group. I think the PAR will be ready for the November meeting.
On 07/22/2014 10:19 AM, Ed Greshko wrote:
On 07/22/14 00:34, Robert Moskowitz wrote:
Crossover cable. Is that enough of a 'same network'?
FWIW, I've not seen the need to use crossover cables in years. Even when connected peer-to-peer the HW is now capable to detect this situation and auto configure itself using standard cables.
Well, yes. It IS a standard cable and the card(s) are doing the crossover operation. I call it a crossover cable to be clear that there is no physical switch hardware between the systems.
On 07/21/14 22:55, Robert Moskowitz wrote:
I have a headless system that I cannot connect to. So I was thinking to put a direct connection to it and my notebook. Both ethernets would use the zeroconf (169.254.0.0/16) addresses. I could then use fping
fping -g 169.254.0.0/16
And SHOULD be able to get its address, and then SSH into the box.
Any other thoughts? I can't get to the box to recable it and reboot it (as that is the only way I can figure out for it to readdress eth0) until this evening.
To turn on zeroconf you need to modify the link to use BOOTPROTO=autoip. (Shows as "Local-Link" in the nm gui)
You'll then have something along the lines of...
[egreshko@f20f ~]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 p2p1 224.0.0.0 0.0.0.0 240.0.0.0 U 1 0 0 p2p1
On 07/22/2014 12:35 AM, Ed Greshko wrote:
On 07/21/14 22:55, Robert Moskowitz wrote:
I have a headless system that I cannot connect to. So I was thinking to put a direct connection to it and my notebook. Both ethernets would use the zeroconf (169.254.0.0/16) addresses. I could then use fping
fping -g 169.254.0.0/16
And SHOULD be able to get its address, and then SSH into the box.
Any other thoughts? I can't get to the box to recable it and reboot it (as that is the only way I can figure out for it to readdress eth0) until this evening.
To turn on zeroconf you need to modify the link to use BOOTPROTO=autoip. (Shows as "Local-Link" in the nm gui)
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
You'll then have something along the lines of...
[egreshko@f20f ~]$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 p2p1 224.0.0.0 0.0.0.0 240.0.0.0 U 1 0 0 p2p1
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
I use network-manager, as I have no fear or need to have my interfaces named something other than ethX, and on one system the wired adapter is p2p1 and another p128p1. The wireless links show up as wlXXXXXX.
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
I use network-manager, as I have no fear or need to have my interfaces named something other than ethX, and on one system the wired adapter is p2p1 and another p128p1. The wireless links show up as wlXXXXXX.
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
On 07/22/14 22:24, Robert Moskowitz wrote:
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
I don't regularly use gnome. KDE is my preferred desktop.....
But I did bring up gnome in a VM and and when I go to "settings" for my wired connection I can go to the IPv4 settings and under "Addresses" I am given the choice of Automatic (DHCP), manual, and "Local Link".
For zeroconf you want to choose "local link"
On 07/22/2014 10:40 AM, Ed Greshko wrote:
On 07/22/14 22:24, Robert Moskowitz wrote:
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
I don't regularly use gnome. KDE is my preferred desktop.....
But I did bring up gnome in a VM and and when I go to "settings" for my wired connection I can go to the IPv4 settings and under "Addresses" I am given the choice of Automatic (DHCP), manual, and "Local Link".
For zeroconf you want to choose "local link"
I don't want a permanent change. If no DHCP, I want zeroconf. If DHCP use it. This option does not seem to be available.
On 07/22/14 22:52, Robert Moskowitz wrote:
I don't want a permanent change. If no DHCP, I want zeroconf. If DHCP use it. This option does not seem to be available.
Oh, I've never seen a case where you could have a "fall back" position.
On 07/22/2014 10:55 AM, Ed Greshko wrote:
On 07/22/14 22:52, Robert Moskowitz wrote:
I don't want a permanent change. If no DHCP, I want zeroconf. If DHCP use it. This option does not seem to be available.
Oh, I've never seen a case where you could have a "fall back" position.
This is what Windoz has always done! M$ is the author of the zeroconf B-class network and how to compute your address; they even patented it and made it available to the workgroup. I worked in that IETF group long ago.
The idea of zeroconf was to get local networking working automagically when nothing exists to provide routeable addressing. The whole point of 'zeroconf'. Of course this lead into discovering your devices on the network and adopting the Bounjour Apple work.
On 07/22/14 23:32, Robert Moskowitz wrote:
On 07/22/2014 10:55 AM, Ed Greshko wrote:
On 07/22/14 22:52, Robert Moskowitz wrote:
I don't want a permanent change. If no DHCP, I want zeroconf. If DHCP use it. This option does not seem to be available.
Oh, I've never seen a case where you could have a "fall back" position.
This is what Windoz has always done! M$ is the author of the zeroconf B-class network and how to compute your address; they even patented it and made it available to the workgroup. I worked in that IETF group long ago.
The idea of zeroconf was to get local networking working automagically when nothing exists to provide routeable addressing. The whole point of 'zeroconf'. Of course this lead into discovering your devices on the network and adopting the Bounjour Apple work.
Well, I should have said I've not seen that in Linux. And I don't do windows. :-)
On 07/22/2014 01:25 PM, Ed Greshko wrote:
On 07/22/14 23:32, Robert Moskowitz wrote:
On 07/22/2014 10:55 AM, Ed Greshko wrote:
On 07/22/14 22:52, Robert Moskowitz wrote:
I don't want a permanent change. If no DHCP, I want zeroconf. If DHCP use it. This option does not seem to be available.
Oh, I've never seen a case where you could have a "fall back" position.
This is what Windoz has always done! M$ is the author of the zeroconf B-class network and how to compute your address; they even patented it and made it available to the workgroup. I worked in that IETF group long ago.
The idea of zeroconf was to get local networking working automagically when nothing exists to provide routeable addressing. The whole point of 'zeroconf'. Of course this lead into discovering your devices on the network and adopting the Bounjour Apple work.
Well, I should have said I've not seen that in Linux. And I don't do windows. :-)
If I go back far enough with my linux testing, I remember zeroconf working. Or at least I think so; am going back quite a while. Probably before adding avahi.
On 07/23/14 01:41, Robert Moskowitz wrote:
If I go back far enough with my linux testing, I remember zeroconf working. Or at least I think so; am going back quite a while. Probably before adding avahi.
Now that you mention it, you are most probably right. I recall there always being a 169.254.0.0 in my routing table. But by force of habit I always placed nozeroconf=yes in my network scripts.
On 22.07.2014 16:24, Robert Moskowitz wrote:
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
:)
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[keyfile] ...
# ll /etc/NetworkManager/system-connections/ # rpm -ql NetworkManager | grep man # rpm -qi $(rpm -qf /usr/lib/systemd/system/avahi-daemon.service)
poma
On 07/22/14 22:43, poma wrote:
file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[egreshko@meimei ~]$ file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: ASCII text
[egreshko@meimei ~]$ cat /etc/NetworkManager/conf.d/keyfile-plugin.conf cat: /etc/NetworkManager/conf.d/keyfile-plugin.conf: No such file or directory
So?
On 07/22/2014 10:49 AM, Ed Greshko wrote:
On 07/22/14 22:43, poma wrote:
file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[egreshko@meimei ~]$ file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: ASCII text
[egreshko@meimei ~]$ cat /etc/NetworkManager/conf.d/keyfile-plugin.conf cat: /etc/NetworkManager/conf.d/keyfile-plugin.conf: No such file or directory
So?
My files are different than yours. No symlink.
On 22.07.2014 16:43, poma wrote:
On 22.07.2014 16:24, Robert Moskowitz wrote:
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
:)
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[keyfile] ...
# ll /etc/NetworkManager/system-connections/ # rpm -ql NetworkManager | grep man # rpm -qi $(rpm -qf /usr/lib/systemd/system/avahi-daemon.service)
in addition # grep ^hosts /etc/nsswitch.conf # man 5 nsswitch.conf http://0pointer.de/lennart/projects/nss-mdns/ # man 5 avahi.hosts # man 5 avahi-daemon.conf
In the end it turns out that 'ZeroConf' ain't really configless. :)
poma
On 07/22/2014 10:54 AM, poma wrote:
On 22.07.2014 16:43, poma wrote:
On 22.07.2014 16:24, Robert Moskowitz wrote:
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote: > But what file is this in now? /etc/sysconfig/network-scripts is > a mess now with scripts for each wifi connection and I can't > find any for my ethernet adapter. Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
:)
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[keyfile] ...
# ll /etc/NetworkManager/system-connections/ # rpm -ql NetworkManager | grep man # rpm -qi $(rpm -qf /usr/lib/systemd/system/avahi-daemon.service)
in addition # grep ^hosts /etc/nsswitch.conf # man 5 nsswitch.conf http://0pointer.de/lennart/projects/nss-mdns/ # man 5 avahi.hosts # man 5 avahi-daemon.conf
In the end it turns out that 'ZeroConf' ain't really configless. :)
Today
avahi-autoipd -D p6p1
is working. Well yesterday, I had to use my internal ethernet on my notebook for internet connection, as WiFi was down, so I was using a D-link USB ethernet. Today, WiFi is up so using the internal ethernet. Must be something about the drivers or such. Anyway if you want zeroconf for a 'one time' thing, this is the command. What I really want is if no DHCP, use zeroconf. I think it use to work this way.
Though I can see why not to move fully into the IPv6 world. "There is no DHCPv4 stupid because there is no IPv4 here!" :)
From the 'driver' behind rfc1918 and a big backer of IPv6 (use Teredo if you must!). :)'
On 22.07.2014 17:27, Robert Moskowitz wrote:
On 07/22/2014 10:54 AM, poma wrote:
On 22.07.2014 16:43, poma wrote:
On 22.07.2014 16:24, Robert Moskowitz wrote:
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote: > On 07/22/14 21:22, Robert Moskowitz wrote: >> But what file is this in now? /etc/sysconfig/network-scripts is >> a mess now with scripts for each wifi connection and I can't >> find any for my ethernet adapter. > Well, "ip link" will/should give a list of links. ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
:)
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[keyfile] ...
# ll /etc/NetworkManager/system-connections/ # rpm -ql NetworkManager | grep man # rpm -qi $(rpm -qf /usr/lib/systemd/system/avahi-daemon.service)
in addition # grep ^hosts /etc/nsswitch.conf # man 5 nsswitch.conf http://0pointer.de/lennart/projects/nss-mdns/ # man 5 avahi.hosts # man 5 avahi-daemon.conf
In the end it turns out that 'ZeroConf' ain't really configless. :)
Today
avahi-autoipd -D p6p1
is working. Well yesterday, I had to use my internal ethernet on my notebook for internet connection, as WiFi was down, so I was using a D-link USB ethernet. Today, WiFi is up so using the internal ethernet. Must be something about the drivers or such. Anyway if you want zeroconf for a 'one time' thing, this is the command. What I really want is if no DHCP, use zeroconf. I think it use to work this way.
Though I can see why not to move fully into the IPv6 world. "There is no DHCPv4 stupid because there is no IPv4 here!" :)
From the 'driver' behind rfc1918 and a big backer of IPv6 (use Teredo if you must!). :)'
Don't worry about it. Lennart 'll figure it out for us. :) [systemd-devel] mdns support to networkd http://lists.freedesktop.org/archives/systemd-devel/2014-June/020362.html
systemd fan club
On 07/22/2014 10:43 AM, poma wrote:
On 22.07.2014 16:24, Robert Moskowitz wrote:
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote:
But what file is this in now? /etc/sysconfig/network-scripts is a mess now with scripts for each wifi connection and I can't find any for my ethernet adapter.
Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
:)
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[keyfile] ...
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: ASCII text # cat /etc/NetworkManager/conf.d/keyfile-plugin.conf cat: /etc/NetworkManager/conf.d/keyfile-plugin.conf: No such file or directory
#cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-rh
On 22.07.2014 16:57, Robert Moskowitz wrote:
On 07/22/2014 10:43 AM, poma wrote:
On 22.07.2014 16:24, Robert Moskowitz wrote:
On 07/22/2014 09:57 AM, Ed Greshko wrote:
On 07/22/14 21:49, Robert Moskowitz wrote:
On 07/22/2014 09:33 AM, Ed Greshko wrote:
On 07/22/14 21:22, Robert Moskowitz wrote: > But what file is this in now? /etc/sysconfig/network-scripts is a > mess now with scripts for each wifi connection and I can't find > any for my ethernet adapter. Well, "ip link" will/should give a list of links.
ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p6p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether e8:9a:8f:8d:7b:56 brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether ac:81:12:9c:e0:95 brd ff:ff:ff:ff:ff:ff
But I cannot find a script file for p6p1. Perhaps it only exists when the link is up, so where do I put this option?
Odd. First off, NO-CARRIER would suggest the link is not connected. I just pulled the plug on one of my systems and I see....
Well this is on my notebook and the ethernet was not connected at the time. So now it is plugged in via crossover to the server and link is up.
[egreshko@f20f ~]$ ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: p2p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 08:00:27:b7:04:4a brd ff:ff:ff:ff:ff:ff
But the config file still exists.
[egreshko@f20f ~]$ ls /etc/sysconfig/network-scripts/ifcfg-p2p1 /etc/sysconfig/network-scripts/ifcfg-p2p1
But still:
ls /etc/sysconfig/network-scripts/ifcfg-p* ls: cannot access /etc/sysconfig/network-scripts/ifcfg-p*: No such file or directory
Do you have access to the system to use the GUI tools of network manager? (I'm assuming you are using nm).
I cannot see anyplace to specify use zeroconf if no dhcp.
This is gnome3 on F20...
:)
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: symbolic link to `/etc/NetworkManager/conf.d/keyfile-plugin.conf'
# cat /etc/NetworkManager/conf.d/keyfile-plugin.conf [main] plugins=keyfile
[keyfile] ...
# file /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf: ASCII text # cat /etc/NetworkManager/conf.d/keyfile-plugin.conf cat: /etc/NetworkManager/conf.d/keyfile-plugin.conf: No such file or directory
#cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-rh
:)
# ls /etc/sysconfig/network-scripts/ifcfg* /etc/sysconfig/network-scripts/ifcfg-lo
poma
-
Corinna Vinschen -
Ed Greshko -
Fernando Gozalo -
poma -
Robert Moskowitz -
Tim