search for: fe80

...eBSD( RELEASE 4.11) systems with KAME IPSec implementation. I tried to establish the connection, but it has some problems which are explained below. |----------------->| host1-[mohan]| |host2-[ram] |<-----------------| host1 IPv6 address : fe80::2b0:d0ff:fe6f:dfa0 host2 IPv6 address : fe80::2b0:d0ff:fe48:7ce7 The 'ipsec.conf' file at Host1 and Host2 are attached along with this email.(you can refer them) IPsec is started with the following commands at both systems:(ipsec SA & SPD are set according to ipsec.conf files at bot...

...two FreeBSD systems using IPv6 addresses.The connetcion is host-to-host between two FreeBSD( RELEASE 4.11) systems with KAME IPSec implementation. |----------------->| host1-[mohan]| |host2-[ram] |<-----------------| host1 IPv6 address : fe80::2b0:d0ff:fe6f:dfa0 host2 IPv6 address : fe80::2b0:d0ff:fe48:7ce7 The 'ipsec.conf' file at Host1 and Host2 are attached along with this email.(you can refer them) IPsec is started with the following commands at both systems: *******at Host1******* mohan# /usr/local/etc/rc.d/setkey.sh sta...

..._________ How much free photo storage do you get? Store your friends 'n family snaps for FREE with Yahoo! Photos http://in.photos.yahoo.com -------------- next part -------------- ########The 'ipsec.conf' file at Host2 ######### # flush configs flush ; spdflush ; # add a SAD entry add fe80::2b0:d0ff:fe48:7ce7 fe80::2b0:d0ff:fe6f:dfa0 esp 0xFEAD -m transport -E 3des-cbc "ipv6readylogo3descbcout1" -A hmac-sha1 "ipv6readylogsha1out1"; add fe80::2b0:d0ff:fe6f:dfa0 fe80::2b0:d0ff:fe48:7ce7 esp 0xFEED -m transport -E 3des-cbc "ipv6readylogo3descbcin01" -A hmac...

...NSEC backend 'sasl-DIGEST-MD5' registered GENSEC backend 'schannel' registered GENSEC backend 'spnego' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered added interface eth0 ip=fe80::20c:29ff:fef7:cd62%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff:: added interface eth1 ip=fe80::20c:29ff:fef7:cd6c%eth1 bcast=fe80::ffff:ffff:ffff:ffff%eth1 netmask=ffff:ffff:ffff:ffff:: added interface eth1 ip=192.168.42.1 bcast=192.168.42.255 netmask=255.255.255.0 added...

https://bugzilla.mindrot.org/show_bug.cgi?id=3631 Bug ID: 3631 Summary: ssh fe80 -b invalid argument failure Product: Portable OpenSSH Version: 8.9p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org...

...SEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'schannel' registered GENSEC backend 'spnego' registered GENSEC backend 'ntlmssp' registered GENSEC backend 'krb5' registered GENSEC backend 'fake_gssapi_krb5' registered added interface eth0 ip=fe80::216:3eff:fe7b:420a%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff:: added interface eth0 ip=192.168.169.47 bcast=192.168.169.255 netmask=255.255.255.0 added interface eth0 ip=fe80::216:3eff:fe7b:420a%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff:: add...

...> ip -6 nei >> I am using two different IPv6 addresses for the two different machines. >> I am unable to ping outside from the VM or connect otherwise via IPv6 >> from the VM. I am also unable to ping the link-local addresses of the >> eth1 interface on the VM (via `ping6 fe80::5054:aaff:fe00:f057/64`). >> ip -6 nei on the VM gives me: >> `fe80::5054:ff:fe1d:a4bb dev eth1 lladdr 52:54:00:1d:a4:bb router STALE` >> >> > Hi, > > Your setup shows > virbr2 and br0 both on the same network 2607:5300:60:1156::2/64 which > will cause issu...

...:33:bc UHLW 1 16 em0 951 192.168.16.254 00:07:e9:80:33:bc UHLW 2 0 em0 1002 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#5 UHL lo0 ff01:5::/32 fe80::1%lo0 UC lo0 ff02::%lo0/32 fe80::1%lo0...

...es this command output look like ? > ip -6 nei I am using two different IPv6 addresses for the two different machines. I am unable to ping outside from the VM or connect otherwise via IPv6 from the VM. I am also unable to ping the link-local addresses of the eth1 interface on the VM (via `ping6 fe80::5054:aaff:fe00:f057/64`). ip -6 nei on the VM gives me: `fe80::5054:ff:fe1d:a4bb dev eth1 lladdr 52:54:00:1d:a4:bb router STALE` -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (MingW32) iQIcBAEBAgAGBQJUMFUEAAoJEEhc1G8ZKSOxaigQAKAQ7oJ3kBtxjOGHoOb5K+1K Y09DL8RjiR20F752a9SNEVOXo+GaAAGXkh2e9/...

...r address option has null length on tun0. Treat as not included. checking if tun0 is ready... tun0 is ready set timer for tun0 to 0:359377 New timer is 0:00359258 timer expiration on tun0, state = 1 send RS on tun0, whose state is 2 set timer for tun0 to 4:0 New timer is 4:00000671 received RA from fe80::2d0:baff:fef4:e80 on tun0, state is 2 stop timer for tun0 there is no timer axxem.hide:~# tethereal -i tun0 ip6 Capturing on tun0 0.000000 fe80::290:27ff:fe78:9275 -> ff02::2 ICMPv6 Router solicitation 0.050048 fe80::2d0:baff:fef4:e80 -> ff02::1 ICMPv6 Router advertisement...

...ho Request 129/0 # Echo Reply 133/0 # Router Solicitation (NDP) 134/0 # Router Advertisement (NDP) 135/0 # Neighbor Solicitation (NDP) 136/0 # Neighbor Advertisement (NDP) ) ICMPV6_LEGAL_DEST=( ::1 # Localhost 2000::/3 # Global Unicast addrs fe80::/10 # Link-local Unicast addrs ff00::/8 # Multicast addrs ) ipset -! destroy legal_icmpv6_list ipset -! create legal_icmpv6_list hash:net,port family inet6 ipset flush legal_icmpv6_list for dest in ${ICMPV6_LEGAL_DEST[@]} ; do for icmp in ${ICMPV6_TYPES[@]} ; do...

...my network xml file. virsh version reports this: Compiled against library: libvirt 1.2.4 Using library: libvirt 1.2.4 Using API: QEMU 1.2.4 Running hypervisor: QEMU 2.0.0 Routing on the guest looks like this: $ ip -6 route 2a01:4f8:200:2265:5054:ff:febe:e8e6 dev eth0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 default via fe80::5054:ff:fe32:e58 dev eth0 metric 1024 Routing on the host looks like this: $ ip -6 route 2a01:4f8:200:2265::/64 dev eth0 proto kernel metric 256 2a01:4f8:200:2265::/64 dev virbr0 proto kernel metric 256 fe80::/64 dev eth0 proto kern...

...5 Component: ip6_tables (kernel) AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: mailxiening at gmail.com Estimated Hours: 0.0 I am using ip6tables to allow/disallow connection from clients with specific IP address. My client's IPv6 address is "fe80::e91b:befe:97dc:9df5". The "-m iprange --src-range" detects the client is in or out of the specified range as follows. I create the rules and set log prefix. ip6tables -I INPUT -m iprange --src-range 1000::0-ffff::0 -j LOG --log-level 7 --log-prefix "1000" ip6tables -I INP...

Well where do I start...I have a domU (ubuntu) booting and appears well but I don''t have an eth0 listed at all, dom) looks good. DomU: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3014 errors:0 dropped:0 overruns:0 frame:0 TX packets:2744 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2290550 (2.1 MiB)...

Hello, shorewall6 seem to have problems duplicating the main routing table. shorewall6 tries to add the fe80::/64 route of every ipv6 configured interface to routing table 1. The first route applies but the other ones not. If i try to add the routes manually to routing table 1 i have to add the first fe80::/64 route and append not add the other ones. does not work: ip -6 route add table 1 fe80::/64 dev...

...39;s just the 3 latest domU''s which is causing a problem. Here''s the dom0''s network config: root@zaxen01:[~]$ ifconfig eth0 Link encap:Ethernet HWaddr 00:1C:C0:75:19:EE inet addr:196.34.x.x Bcast:196.34.x.x Mask:255.255.255.224 inet6 addr: fe80::21c:c0ff:fe75:19ee/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1540 errors:0 dropped:0 overruns:0 frame:0 TX packets:241 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:260529 (254.4 KiB)...

...9;, ''phy:/dev/vgxen/happoswap,sda3,w''] root = "/dev/sda1 ro" extra = ''4'' Here is ifconfig from dom0: eth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3422 errors:0 dropped:0 overruns:0 frame:0 TX packets:2133 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:347388 (339.2 K...

...packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link eth2 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link xenbr0 Link encap:Ethernet...

...look like ? >> ip -6 nei > I am using two different IPv6 addresses for the two different machines. > I am unable to ping outside from the VM or connect otherwise via IPv6 > from the VM. I am also unable to ping the link-local addresses of the > eth1 interface on the VM (via `ping6 fe80::5054:aaff:fe00:f057/64`). > ip -6 nei on the VM gives me: > `fe80::5054:ff:fe1d:a4bb dev eth1 lladdr 52:54:00:1d:a4:bb router STALE` > > Hi, Your setup shows virbr2 and br0 both on the same network 2607:5300:60:1156::2/64 which will cause issues with routing. This however must not...

...d "Jump" Host both have public IPv6 addresses. 2. Target host has only Link Local IPv6 address on same link as Jump Host. In principal, I believe the following incantation (or some similar form) should work (assuming Jump Host with address 2001:db8:f3f4::2ae0 and target host with address fe80::2001:db8:3 on common link interface enp0s31f6 (interface ID on jump host): ssh -J '[2001:db8:f3f4::2ae0]' '[fe80::2001:db8:3%enp0s31f6]' However, this results in the following: % ssh -J '[2001:db8:f3f4::2ae0]' '[fe80::2001:db8:3]'...