IPv6 Link local address use with syslog-ng
Hello, Running syslog-ng-2.0.5 on a Linux host 2.6.22.9. syslog-ng.conf entry as follows: source s_all { tcp6(ip(2001:470:1f00:1288:220:abff:febe:4dac) port(1468)); }; When syslog-ng is started, the Global address (2001:470:1f00:1288:220:abff:febe:4dac) binds and connects fine. If I have the Link Local Address configured below: source s_all { tcp6(ip(fe80::220:abff:febe:4dac) port(1468)); }; And start syslog-ng, it either errors on the bind or the connect(g_connect in gsockaddr.c) with an errno of 22 (Invalid Argument). Looking at the code shows that there is no use of the sockaddr_in6 "sin6_scope_id", which is required to be set when using Link Local addresses since they need to use the interface number (sin6_scope_id). Has anyone run into this issue? If so, is there a workaround or a code patch for this? Thanks, Phil Bellino Phil Bellino Software Engineer MRV Communications, Inc. 295 Foster Street Littleton, MA. 01460 Phone: 978-952-4807 Fax: 978-952-5444 Email: pbellino@mrv.com <http://www.mrv.com/>
On Fri, 2007-11-16 at 10:38 -0500, Philip Bellino wrote:
Hello,
Running syslog-ng-2.0.5 on a Linux host 2.6.22.9.
syslog-ng.conf entry as follows:
source s_all {
tcp6(ip(2001:470:1f00:1288:220:abff:febe:4dac) port(1468));
};
When syslog-ng is started, the Global address (2001:470:1f00:1288:220:abff:febe:4dac) binds and connects fine.
If I have the Link Local Address configured below:
source s_all {
tcp6(ip(fe80::220:abff:febe:4dac) port(1468));
};
And start syslog-ng, it either errors on the bind or the connect(g_connect in gsockaddr.c) with an errno of 22 (Invalid Argument).
Looking at the code shows that there is no use of the sockaddr_in6 “sin6_scope_id”, which is required to be set when using Link Local addresses since they need to use the interface number (sin6_scope_id).
Has anyone run into this issue?
If so, is there a workaround or a code patch for this?
I don't know about any. In fact I'm not using the ipv6 parts myself, so there might be some quirks here and there. To be honest, I've absolutely no clue how scope id is usually set. Can you recommend something? -- Bazsi
On 19/11/07 09:39, Balazs Scheidler wrote:
On Fri, 2007-11-16 at 10:38 -0500, Philip Bellino wrote:
Hello,
Running syslog-ng-2.0.5 on a Linux host 2.6.22.9.
syslog-ng.conf entry as follows:
source s_all {
tcp6(ip(2001:470:1f00:1288:220:abff:febe:4dac) port(1468));
};
When syslog-ng is started, the Global address (2001:470:1f00:1288:220:abff:febe:4dac) binds and connects fine.
If I have the Link Local Address configured below:
source s_all {
tcp6(ip(fe80::220:abff:febe:4dac) port(1468));
};
And start syslog-ng, it either errors on the bind or the connect(g_connect in gsockaddr.c) with an errno of 22 (Invalid Argument).
Looking at the code shows that there is no use of the sockaddr_in6 “sin6_scope_id”, which is required to be set when using Link Local addresses since they need to use the interface number (sin6_scope_id).
Has anyone run into this issue?
If so, is there a workaround or a code patch for this?
I don't know about any. In fact I'm not using the ipv6 parts myself, so there might be some quirks here and there.
To be honest, I've absolutely no clue how scope id is usually set. Can you recommend something?
For: tcp6(ip(fe80::220:abff:febe:4dac%eth0) port(1468)); (address with %eth0 appended) You'd set the scope id on the address you use to bind (if any), and again on the destination: ...->sin6_scope_id = if_nametoindex("eth0"); -- Simon Arlott
Simon, I tried "tcp6(ip(fe80::220:abff:febe:4dac%eth0) port(1468));" in my earlier testing and received the syslog error: "Error binding socket" addr='AF_INET6(fe80::220:abff:febe:4dac)', error='Invalid argument (22)' Phil Bellino -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Simon Arlott Sent: Monday, November 19, 2007 12:41 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 Link local address use with syslog-ng On 19/11/07 09:39, Balazs Scheidler wrote:
On Fri, 2007-11-16 at 10:38 -0500, Philip Bellino wrote:
Hello,
Running syslog-ng-2.0.5 on a Linux host 2.6.22.9.
syslog-ng.conf entry as follows:
source s_all {
tcp6(ip(2001:470:1f00:1288:220:abff:febe:4dac) port(1468));
};
When syslog-ng is started, the Global address (2001:470:1f00:1288:220:abff:febe:4dac) binds and connects fine.
If I have the Link Local Address configured below:
source s_all {
tcp6(ip(fe80::220:abff:febe:4dac) port(1468));
};
And start syslog-ng, it either errors on the bind or the connect(g_connect in gsockaddr.c) with an errno of 22 (Invalid Argument).
Looking at the code shows that there is no use of the sockaddr_in6 “sin6_scope_id”, which is required to be set when using Link Local addresses since they need to use the interface number (sin6_scope_id).
Has anyone run into this issue?
If so, is there a workaround or a code patch for this?
I don't know about any. In fact I'm not using the ipv6 parts myself, so there might be some quirks here and there.
To be honest, I've absolutely no clue how scope id is usually set. Can you recommend something?
For: tcp6(ip(fe80::220:abff:febe:4dac%eth0) port(1468)); (address with %eth0 appended) You'd set the scope id on the address you use to bind (if any), and again on the destination: ...->sin6_scope_id = if_nametoindex("eth0"); -- Simon Arlott
On Mon, 2007-11-19 at 12:57 -0500, Philip Bellino wrote:
Simon, I tried "tcp6(ip(fe80::220:abff:febe:4dac%eth0) port(1468));" in my earlier testing and received the syslog error:
"Error binding socket" addr='AF_INET6(fe80::220:abff:febe:4dac)', error='Invalid argument (22)'
It does not work yet, Simon has only suggested a configuration interface. Can you enlighten me what is a link-local address? Am I right to assume that it is an address that can only be used on the local LAN? Can you explain why it is useful? (to restrict packets to the local LAN?) syslog-ng supports an option named ip_ttl() and it lets you set the maximum hop count on the packet. Isn't this a substitute? Can you point me to a package that supports link-local addresses? -- Bazsi
Bazsi, Linux 2.6.x, Windows XP, Windows Vista, FreeBSD, Solaris 8 and up. All support IPv6 which of course supports Link Local addresses. Execute the following commands to see the IPv6 configuration: Linux/FreeBSD - /sbin/ifconfig Windows - ipconfig /all Solaris - ifconfig -a You are correct in that the Link Local address is only valid on the local Lan and it is not routable. A link local address is derived from the kernel at boot time. It is denoted by the leading "fe80::". What follows is the ethernet address of the host with an ff:fe stuffed in. For example, is the ethernet address of host is 02:a1:9d:00:ae:44, then the link local address will be fe80::2a1:9dff:fe00:ea44. Please note that :: denotes that the next field(s) are all zeros. Also leading zeros can be dropped. I believe the theory behind link local addresses was to have basic native IPv6 connectivity right out of the box without any user configuration. When IPv6 was still in its infancy, there were no IPv6 routers available and tunneling had(and still is) to be used which basically wrapped the IPv6 packet inside an IPv4 packet that could be routed and then be unwrapped once it was received at the final destination. Why the IPv6 gurus require the link local address to be scoped is still a mystery to me, but since it is, the rule is that the stack needs to know which interface to send the IPv6 packet out of, so "ip_ttl" does not apply here. Please note that the scope_id is not needed for Link Global IPv6 addresses. I could be wrong in what follows, but since the syslog-ng code uses the "Zorp" style code for bind(g_bind) and connect(g_connect), it seems that it doesn't have the necessary info needed in the "GSockAddr" structure in gsockaddr.h to accommodate the sin6.sin6_scope_id. I hope this helps. Phil -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Tuesday, November 20, 2007 5:56 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 Link local address use with syslog-ng On Mon, 2007-11-19 at 12:57 -0500, Philip Bellino wrote:
Simon, I tried "tcp6(ip(fe80::220:abff:febe:4dac%eth0) port(1468));" in my earlier testing and received the syslog error:
"Error binding socket" addr='AF_INET6(fe80::220:abff:febe:4dac)', error='Invalid argument (22)'
It does not work yet, Simon has only suggested a configuration interface. Can you enlighten me what is a link-local address? Am I right to assume that it is an address that can only be used on the local LAN? Can you explain why it is useful? (to restrict packets to the local LAN?) syslog-ng supports an option named ip_ttl() and it lets you set the maximum hop count on the packet. Isn't this a substitute? Can you point me to a package that supports link-local addresses? -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Tue, 2007-11-20 at 08:41 -0500, Philip Bellino wrote:
Bazsi,
Linux 2.6.x, Windows XP, Windows Vista, FreeBSD, Solaris 8 and up. All support IPv6 which of course supports Link Local addresses. Execute the following commands to see the IPv6 configuration: Linux/FreeBSD - /sbin/ifconfig Windows - ipconfig /all Solaris - ifconfig -a
This is not what I had mind when I requested packages to support link local addresses. Of course ifconfig does it, otherwise it would not be possible to configure interfaces. I meant something like a telnet client, how do you tell telnet to connect to a link local address? When I tried to do that I got an error: telnet fe80::290:f5ff:fe28:b55e Trying fe80::290:f5ff:fe28:b55e... telnet: Unable to connect to remote host: Invalid argument The reason I asked is to have a peek at the interface they provide for configuring the scope id. I've now tried using telnet/ssh/ping6, and neither could connect to a link-local address. I don't see its use then, it should be used without further configuration, but it turned out it is not possible.
Why the IPv6 gurus require the link local address to be scoped is still a mystery to me, but since it is, the rule is that the stack needs to know which interface to send the IPv6 packet out of, so "ip_ttl" does not apply here. Please note that the scope_id is not needed for Link Global IPv6 addresses.
The reason I mentioned ip_ttl() is, that when setting that to 1 means that the given packet will never leave the network. I originally thought this was the reason to use link-local addresses in the first place. -- Bazsi
Hi Bazsi, On Tue, 20 Nov 2007, Balazs Scheidler wrote:
I meant something like a telnet client, how do you tell telnet to connect to a link local address?
When I tried to do that I got an error:
telnet fe80::290:f5ff:fe28:b55e Trying fe80::290:f5ff:fe28:b55e... telnet: Unable to connect to remote host: Invalid argument
The reason I asked is to have a peek at the interface they provide for configuring the scope id.
I've now tried using telnet/ssh/ping6, and neither could connect to a link-local address. I don't see its use then, it should be used without further configuration, but it turned out it is not possible.
If you want to use a link-local address, you *must* specify the interface too - otherwise it'd be not unique. ping6 has got the '-I' flag for this, but apparently telnet does not support specifying the interface. Best regards, Jozsef - E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary
Bazsi, On the Linux 2.6.22.9 Redhat 4.1.0-3 Fedora Core 6 from CDs at my disposal, you can edit the "/etc/xinetd.d/telnet" file and change "flags" from IPv4 to IPv6. Note: You will still have IPv4 connectivity. telnet fe80::zzzz:zzzz:zzzz:zzzz%interface_name - interface_name on most Linux is "eth0" Ping6 has a "-I" switch: Ping6 -Ieth0 fe80::zzzz:zzzz:zzzz:zzzz Ssh -6 -l username fe80::zzzz:zzzz:zzzz:zzzz%eth0 On Freebsd, I believe that their telnet,ping6, and ssh client supports IPv6 by default and uses the same syntax above. On Windows XP, look for the output of the ipconfig /all command for the "Ethernet Adaptor Local Area Connection" and look for its Link local address. That address will have a "%x" after it, where x is its interface number. XP has a telnet and ping6 client. The syntax for those are: telnet fe80::zzzz:zzzz:zzzz:zzzz%x ping6 fe80::zzzz:zzzz:zzzz:zzzz%x Solaris 8 and greater have telnet and ping that support IPv6 built in. telnet fe80::zzzz:zzzz:zzzz:zzzz Somehow Solaris knows how to add the scope internally, so specifying the interface is not needed. Ping -A inet6 fe80::zzzz:zzzz:zzzz:zzzz The -A option denotes the address family to use. I hope this helps. Phil -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Tuesday, November 20, 2007 9:15 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 Link local address use with syslog-ng On Tue, 2007-11-20 at 08:41 -0500, Philip Bellino wrote:
Bazsi,
Linux 2.6.x, Windows XP, Windows Vista, FreeBSD, Solaris 8 and up. All support IPv6 which of course supports Link Local addresses. Execute the following commands to see the IPv6 configuration: Linux/FreeBSD - /sbin/ifconfig Windows - ipconfig /all Solaris - ifconfig -a
This is not what I had mind when I requested packages to support link local addresses. Of course ifconfig does it, otherwise it would not be possible to configure interfaces. I meant something like a telnet client, how do you tell telnet to connect to a link local address? When I tried to do that I got an error: telnet fe80::290:f5ff:fe28:b55e Trying fe80::290:f5ff:fe28:b55e... telnet: Unable to connect to remote host: Invalid argument The reason I asked is to have a peek at the interface they provide for configuring the scope id. I've now tried using telnet/ssh/ping6, and neither could connect to a link-local address. I don't see its use then, it should be used without further configuration, but it turned out it is not possible.
Why the IPv6 gurus require the link local address to be scoped is still a mystery to me, but since it is, the rule is that the stack needs to know which interface to send the IPv6 packet out of, so "ip_ttl" does not apply here. Please note that the scope_id is not needed for Link Global IPv6 addresses.
The reason I mentioned ip_ttl() is, that when setting that to 1 means that the given packet will never leave the network. I originally thought this was the reason to use link-local addresses in the first place. -- Bazsi _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
Thanks for the detailed information. The reward is a patch that fixes the issue for me: diff --git a/src/afinet.c b/src/afinet.c index 40dc5b9..05dbe62 100644 --- a/src/afinet.c +++ b/src/afinet.c @@ -92,7 +92,7 @@ afinet_resolve_name(GSockAddr *addr, gchar *name) break; #if ENABLE_IPV6 case AF_INET6: - g_sockaddr_inet6_set_address(addr, &((struct sockaddr_in6 *) res->ai_addr)->sin6_addr); + *g_sockaddr_inet6_get_sa(addr) = *((struct sockaddr_in6 *) res->ai_addr); break; #endif default: This makes syslog-ng support the same '%eth0' syntax that all the other tools know. Slowly I might gather enough knowledge about IPv6 to actually try to deploy it on our local network. :) On Tue, 2007-11-20 at 10:48 -0500, Philip Bellino wrote:
Bazsi,
On the Linux 2.6.22.9 Redhat 4.1.0-3 Fedora Core 6 from CDs at my disposal, you can edit the "/etc/xinetd.d/telnet" file and change "flags" from IPv4 to IPv6. Note: You will still have IPv4 connectivity.
telnet fe80::zzzz:zzzz:zzzz:zzzz%interface_name - interface_name on most Linux is "eth0"
-- Bazsi
On 20/11/07 13:41, Philip Bellino wrote:
Bazsi, You are correct in that the Link Local address is only valid on the local Lan and it is not routable.
Link local addresses are only valid on, and unique to, one link which is why the link has to be specified using the scope id.
I believe the theory behind link local addresses was to have basic native IPv6 connectivity right out of the box without any user configuration.
This sounds like nonsense to me...
Please note that the scope_id is not needed for Link Global IPv6 addresses.
However it may be useful to allow setting it anyway.
I hope this helps. Phil
-- Simon Arlott
-----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Simon Arlott Sent: Tuesday, November 20, 2007 12:41 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 Link local address use with syslog-ng On 20/11/07 13:41, Philip Bellino wrote:
Bazsi, You are correct in that the Link Local address is only valid on the local Lan and it is not routable.
Link local addresses are only valid on, and unique to, one link which is why the link has to be specified using the scope id.
I believe the theory behind link local addresses was to have basic native IPv6 connectivity right out of the box without any user configuration.
This sounds like nonsense to me... Simon, Please read the book "Top Down Design" by Priscilla Oppenheimer. Page 207 reads "A link local address serves as a method for connecting devices on the same local network without the need for site-local or globally unique addresses." Of course, we all know that site-local addresses have been deprecated and that the way to get global addresses is through configuration commands or the use of a "radvd" server. My Linux Redhat 2.6.22.9 box boots up with the link local address present without any extra user configuration. My FreeBSD 5.4 and 6.2 boxes boots up with the link local address present without any extra user configuration. My Windows XP PC boots up with the link local address present without any extra user configuration. My Solaris 8 and 9 systems boots up with the link local address present without any extra user configuration. This is why I wrote the "nonsense". Phil
Please note that the scope_id is not needed for Link Global IPv6 addresses.
However it may be useful to allow setting it anyway.
I hope this helps. Phil
-- Simon Arlott
Simon, Here are many other sources on the use of the IPv6 Link-Local address that seem to support my original "nonsense", which I also include here:
I believe the theory behind link local addresses was to have basic native IPv6 connectivity right out of the box without any user configuration.
I have included the text from these sources as well in case you cannot reach them. http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_7-2/ipv6_auto... Creation of the Link-Local Address An IPv6 address is 128 bits long. It has two parts: a subnet prefix representing the network to which the interface is connected and a local identifier, sometimes called token. In the simple case of an Ethernet medium, this identifier is usually derived from the EUI-48 Media Access Control (MAC) address using an algorithm described later in this article. The subnet prefix is a fixed 64-bit length for all current definitions. Because IPv4 manual configuration is a well-known pain, one could hardly imagine manipulating IPv6 addresses that are four times longer. Moreover, a DHCP server is not always necessary or desired; in the case of a remote control finding the DVD player, a DHCP environment is not always suitable. Because the prefix length is fixed and well-known, during the initialization phase of IPv6 NICs, the system builds automatically a link-local address. After a uniqueness verification, this system can communicate with other IPv6 hosts on that link without any other manual operation.” http://www.tcpipguide.com/free/t_IPv6AutoconfigurationandRenumbering.htm IPv6 Autoconfiguration and Renumbering One of the most interesting and potentially valuable addressing features implemented in IPv6 is a facility to allow devices on an IPv6 to actually configure themselves independently. In IPv4 hosts were originally configured manually. http://technet2.microsoft.com/windowsserver/en/library/b05f98ef-2561-4a0a-af... By default, the IPv6 protocol for the Windows Server 2003 family and Windows XP configures link-local addresses for each interface that corresponds to installed Ethernet network adapters. Link-local addresses have the prefix of FE80::/64. The last 64 bits of the IPv6 address is known as the interface identifier. It is derived from the 48-bit MAC address of the network adapter. For more information, see IPv6 interface identifiers . http://www.microsoft.com/technet/technetmag/issues/2007/08/CableGuy/ IPv6 is about more than extending the address space from 32 bits in IPv4 to 128 bits. IPv6hosts can also automatically configure themselves, even without the use of an address configuration protocol such as DHCP for IPv6 (DHCPv6). http://www.windowsnetworking.com/kbase/WindowsTips/WindowsVista/AdminTips/Tr... It's important to start learning how to identify IPv6 addresses if you want to be able to troubleshoot network connectivity issues on IPv6 networks, and this is especially important as IPv4 to IPv6 migrations accelerate in different parts of the world. One common type of IPv6 address is the link-local address, a unicast address that is used by neighboring nodes on the same network link (that is, not separated by routers). Think of link-local addresses as the IPv6 form of Automatic IP Address Allocation (APIPA), a mechanism used by Windows computers to automatically assign themselves address of the form 169.254.x.y when a DHCP server is unavailable and no static addresses have been assigned. Link-local addresses are similarly self-assigned, and you can always recognize them by opening a command prompt on your computer and typing ipconfig. If the IP address displayed for your computer starts with fe80:: then you've got a link-local address that has been self-assigned using the Neighbor Discovery process used by IPv6. You can test this in Windows Vista, for example, since this platform has IPv6 enabled by default. The limitation of link-local addresses is that IPv6 routers cannot forward link-level traffic outside the link. http://www.enterprisenetworkingplanet.com/netsp/article.php/3633211 Link-local addresses are akin to the private, non-routable addresses in IPv4 (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16). They are not meant to be routed, but confined to a single network segment. Link-local addresses mean you can easily throw together a temporary LAN, such as for conferences or meetings, or set up a permanent small LAN the easy way. http://www.ipv6.de/ipv6-basics.html Special IPv6 address ranges • fe80::/10 linklocal: every host has at least one IPv6 address on any interface that does IPv6, and that is the linklocal address. Linklocal addresses are defined to not be routable on any account. As there are as many linklocal 'networks' for a machine as there are interfaces with different media behind them, one may need to have to discern between, say, fe80::1 on interface hme0 and fe80::1 on qfe2; the name of the area of validity of a linklocal address is 'scope', and is often written as %if, so eg I might have fe80::1%qfe2. That doesn't work quite that way on Solaris, therefore if one plans to have IPv6 running on more than one physical interface it's a very good idea to make sure that the interfaces have differing IPv6 addresses (easiest by making them have different MAC addresses). With linklocal, the prefix is implicitly known, and the host part gets built using DAD (see below). http://msdn2.microsoft.com/en-us/library/ms737595.aspx Configuration 1: Single Subnet with Link-local Addresses The first configuration requires no additional configuration beyond installing the Microsoft® IPv6 Technology Preview protocol. This configuration consists of at least two nodes on the same subnet. In IPv6 terminology, the two nodes are on the same link with no intermediate routers. Testing Connectivity Between Two Link-local Hosts You can do a simple ping (an exchange of ICMPv6 Echo Request and Echo Reply messages) using IPv6 between two link-local hosts. http://docs.sun.com/app/docs/doc/816-4554/6maoq0281?a=view Data Addresses Data addresses are the conventional IPv4 and IPv6 addresses that are assigned to an interface of a NIC at boot time or manually, through the ifconfig command. The standard IPv4 and, if applicable, IPv6 packet traffic through an interface is considered to be data traffic. http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzai2... Link-local address Link-local addresses are designed for use on a single local link (local network). Link-local addresses are automatically configured on all interfaces. The prefix used for a link-local address is fe80::/10. Routers do not forward packets with a destination or source address containing a link-local address. http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/faq.asp By default, Microsoft IPv6 configures link-local IPv6 addresses for each interface that corresponds to an installed Ethernet network adapter. Link-local addresses have the prefix FE80::/64. You can see your link local addresses by typing the ipv6 if command and looking for an interface with a link-level address of the form aa-bb-cc-dd-ee-ff. The preferred address is the link-local address for the interface. http://en.wikipedia.org/wiki/Link-local_address Link-local addresses are network addresses which are intended only for use in a local data link layer network, and not for routing beyond that network. Link-local addresses are often used for network address autoconfiguration where no external source of network addressing information is available. If you need more examples, I am sure I can email more to you. I hope this helps. Phil -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Simon Arlott Sent: Tuesday, November 20, 2007 12:41 PM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] IPv6 Link local address use with syslog-ng On 20/11/07 13:41, Philip Bellino wrote:
Bazsi, You are correct in that the Link Local address is only valid on the local Lan and it is not routable.
Link local addresses are only valid on, and unique to, one link which is why the link has to be specified using the scope id.
I believe the theory behind link local addresses was to have basic native IPv6 connectivity right out of the box without any user configuration.
This sounds like nonsense to me...
Please note that the scope_id is not needed for Link Global IPv6 addresses.
However it may be useful to allow setting it anyway.
I hope this helps. Phil
-- Simon Arlott
participants (4)
-
Balazs Scheidler
-
Jozsef Kadlecsik
-
Philip Bellino
-
Simon Arlott