de company), or tunnel mode
(a guy outside of company transmits tunnel mode AH packet to
the company gateway, company gateway decapsulates the packet)?
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "un
I am trying to chose between Linux and FreeBSD implementations.
Do you have any suggestions or possibly some ineternet references
about comparition between them?
dropped cc: to 6bone as it seems less suitable.
for day-to-day use, i believe you should pick whichever you are
Just received the following but regret there is no-one with the names of
JINMEI or Tatuya at peters.house.cx
Someone, somehow has made an error :-(
Can someone help me fix it??
I believe this was because of some MIME handling error on Sugianto's
MUA.
itojun
, as you are
outside of IETF IPv6 network, and the quake server is also outside.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
|
==+===+==
| |
mchar clientEXTRA
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
and production" or whatever.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
? Any pointers?
Appreciate any help.
IPsec over IPv6: there are multiple implementations.
flow label:
there are couple of proposed usage. based on these
proposals, there are test implementations. for example,
KAME code (= *BSD) follows draft-itojun-ipv6
for actual implementation, see totd from Feico Dillema.
http://www.vermicelli.pasta.cs.uit.no/ipv6/software.html
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
... it is unfortunate RFC2874 does not cover it.
it has A6 reference from leaf customer A6 record to ISP A6 record,
and 5 levels of indirection.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users"
to assign static address for these
networks?
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
Host: header. is my understanding correct?
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
Someone knows if exist any implementation of the Bump-in-the-Stack (RFC
2765) and
Stateless IP/ICMP Translation Algorithm (RFC 2765) ?
the the former technique is used for hitachi's Win95/98 in-driver IPv6
implementation. I forgot the URL.
itojun
-implementations.html.
if you use PCs as routers, *BSD should work just fine.
NIC, switches and hubs - normally they work just fine, unless
there's some IPv4-specific tricks implemented.
itojun
-
The IPv6 Users Mailing
You can stop reading here if you like, but one of the things that prompted
the question is this:
I read an interview with itojun, and he said that he thinks people are
wasting their time using NAT (he says IPv6 is a simpler solution). But if
IPv6-only doesn't allow communication with IPv4-only
Apache have failed at
run-time (some parts of the ABI change, mod_ssl doesn't
cope).
it is rumored that someone (outside of KAME) has IPv6+SSL patch.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending
with
IPsec. use them in separate boxes, or use IPsec filter rules
for packet filter (using "discard" policy).
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
/network/ipsec/#ipf-interaction
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
SD running rock solid :0(.
checking - did you have kernel panics in kernel IPsec code (then pls
send-pr), or you are just talking about an example?
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "un
,
and have a proper IPsec policy rule for the first and second,
you should be okay.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
how about using zebra ripngd? (www.zebra.org)
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
of
other warnings i see from kernel compilation. why don't you attack
other folks as well.
itojun
PS: i have unsubscribed from the list. i can't take this stress any more.
-
The IPv6 Users Mailing List
Unsubscribe
-sn /tmp/2
% diff -c /tmp/1 /tmp/2
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
it.
whoever you are, if you are reading it, please stop it. thanks.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
/include -I/usr/include -c comms.c
comms.c: In function `recv_sock_init':
comms.c:486: `IPV6_ADD_MEMBERSHIP' undeclared (first use in this function)
IPV6_ADD_MEMBERSHIP is deprecated. use IPV6_JOIN_GROUP.
itojun
-
The IPv6
the
behavior of your web crawlers carefully.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
mean by wouldn't recognize my routers? you have another
option - /usr/sbin/route6d. my guess is that you have some
configuration problem, or ethernet-layer multicas tproblem.
itojun
-
The IPv6 Users Mailing List
no record:
reverses-dotted-nibbles.ip6.int
it will take time if there's no ip6.arpa records, but i guess it is the
most trouble-free way.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending
a subnet must always be /64.
Why?
we have decided so in address architecture document (at least under
2000::/3 space), fixed boundary gives us ease of management.
or do you really plan to connect more than 2^64 devices on a single
subnet?
itojun
it
to reduce the amount of support calls.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
pseudo interface and ethernet), and routers cannot be autoconfigured
(ipv6_network_interfaces=auto does not work).
try looking at:
http://www.netbsd.org/Documentation/network/ipv6/
(it cannot help you set up freebsd rc.conf but should be of some help)
itojun
of messages in my logs. OS=fbsd 4.5-STABLE
yes, faithd monitors inactive connections, and terminates it after 30
minutes. at this moment there's no command line option to change
the behavior. you may want to change FAITH_TIMEOUT parameter in
faithd.h.
itojun
worked on at
IETF ipv6wg (ipngwg) so we cannot really define API yet.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
://developer.apple.com/wwdc2002/descriptions.html#803
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
output
if it exceeds max_gif_nesting (sys/net/if_gif.c). if you want to, you
may try increasing the parameter - but if you increase it too much,
kernel can panic if you create certain routing table setup.
itojun
all tunnelling inputs.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
-local address to the
p2p interface, at least.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
experimental stuff.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
I have an apache-2 server running on
ServerName ruby-v6.chalmers.com.au
Listen [2002:cb01:6005:2:240:5ff:fe4e:a982]:80
but connection to it simply gives an error.
check if apache is listening at the right address/port, by netstat -an.
itojun
::1
# route change -inet6 default ::1 -ifp gif0
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
for sshd. you need -i flag at the end.
# faithd ssh /usr/sbin/sshd sshd -i
itojun
--
-i Specifies that sshd is being run from inetd. sshd is normally
not run from inetd because it needs to generate the server key
before it can respond to the client
v6 kit and
compile beforehand.
i guess you can skip the check entirely. the check was useful when
IPv6 library was shipped separately from libc with kame kit, but is
now obsolete (functions are incorporated into libc). SOCKS64 package
should be upgraded.
itojun
/
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
in Feb 2002.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
.
i guess the best way to fight this issue is to raise it in NANOG.
will do so.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
here's how you can enable IPv6 on Sharp Linux-Zaurus PDA.
http://www.kame.net/newsletter/20020425/
Linux-Zaurus developer info is here:
http://developer.sharpsec.com/
itojun
-
The IPv6 Users
client resolvers try then A (therefore, it won't
try A).
please correct the bug as soon as possible, and if possible make
announcement at [EMAIL PROTECTED] or other appropriate forum. thanks.
itojun
hello, i'm writing to you with respect to bug in lbnamed, which is
rather serious.
in lbnamed 1.2 perl5/lbnamed.conf{,.example}, it returns NXDOMAIN
oh, and perl4/lbnamed.pl.
itojun
-
The IPv6 Users
gethostbyaddr() ?
Eeeek.
What happened to getnameinfo() ?
unforfunately sendmail still uses gethostbyname2/gethostbyaddr.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL
as it
will prevent any of IPv6-ready client resolvers from contacting you.
itojun
% dig spaceflight.nasa.gov.
; DiG 9.2.1rc2 spaceflight.nasa.gov.
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 1362
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1
to discuss it
with them.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
). He wants to change
this (a little confusing at the moment), but to what? Any best current
practice? So far I have seen
[2001:768:1001:1::218]:3456---
2001:768:1001:1::218.3456
Comments appreciated.
[addr]:port, definitely. there's prior art - RFC2732.
itojun
is set up to use fec0:2100::/24, this is the source of
the problem. change it to /64.
all subnet prefixes are supposed to be /64 (because of the interface
ID boundary), and solaris is generating error because 64 != 24.
itojun
with the following protocol action, /A6 confusion have finally gone.
http://www1.ietf.org/mail-archive/ietf-announce/Current/msg19416.html
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending
now forget about A6 for your daily IPv6 operation.
use .
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
I'm not sure how to publish it, but this is what I see from a lot of
web services with load balancing products. any comments?
(bullet 1 is not very IPv6 specific, but will bite us since PMTUD is
on by default)
itojun
---
1. PMTUD blocked by load balancing
subnets needs to have /64 by default.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
you can't use /96. all subnets needs to have /64 by default.
*clear throat* hrmhrm...
..why?
read RFC2460 to RFC2463.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL
The must be a lot of things to be done at linux world for ipv6 :-)
you must be running IPv4-only ftpd from inetd.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
I'm using a six-to-four setup (2002:cf1:d877::1 is my router's
address), and I'm having serious connectivity problems. I can ping my
default router (2002:4371:c5a::1) and the following addresses:
better contact admin of your 6to4 gateway directly (67.113.12.90).
itojun
the above is not the intended use in the standard documents. you
(or Click Router) shouldn't use these /96 prefix like this.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL
what are the equivalents for inet_ntoa and inet_aton
in the IPv6 API?
use getaddrinfo(3) and getnameinfo(3).
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
. What code precaautions will I have to take?
use getaddrinfo.
itojun
char *dst;
char *port;
int s;
struct addrinfo hints, *res, *res0;
memset(hints, 0, sizeof(hints));
hints.ai_socktype = SOCK_STREAM;
error = getaddrinfo(dst, port
of a SYN,ACK in the three-way handshake. My cuestion
is, what could be causing this behavior? could it be some problem
with the tranlation of the packet(updating secuence number,
translating IP/TCP headers...)?
i guess you want to check endian handling of port number.
itojun
RFC 2765 - Stateless IP/ICMP Translation Algorithm (SIIT)
FreeBSD + KAME
we do not implement SIIT.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
with it that it can't be
trusted yet?
because it is still under development and we expect to have tons
of improvements, and config syntax changes. with freebsd 4.1, racoon
is supplied as a "ports".
itojun
-
The
, but i have no time yet to
finish it...
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
That's what the faith thing does doesn't it? I haven't used it yet.
freebsd faithd(8) is documented in the following internet draft:
draft-ietf-ngtrans-tcpudp-relay-01.txt
itojun
-
The IPv6 Users Mailing List
... ;-))
the router came back online. sorry for the trouble last night.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
are using
% ifconfig gif0 inet6 A B prefixlen 64
change it to one of them:
% ifconfig gif0 inet6 A prefixlen 64
% ifconfig gif0 inet6 A B prefixlen 128
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending &q
generated due to DNSsec signatures, additional
records on A6 chain queries, and other things.
i cannot speak for them, but this is what i heard so far.
itojun
-
The IPv6 Users Mailing List
Unsubscribe
using host:
- non-IPless virtual hosting using extra IP addresses
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
this should be okay.
itojun
#include sys/types.h
#include sys/socket.h
#include stdio.h
#include netdb.h
int
main(argc, argv)
int argc;
char **argv;
{
char hbuf[NI_MAXHOST];
struct addrinfo hints, *res;
int error;
#ifdef NI_WITHSCOPEID /*KAME
just checking, of course you have configured "alpha" side too?
huh? i did the configuration on alpha, not on ph-sfc-sat (the
other endpoint)? should i do "gifconfig" on both ends?
you need to configur
with tunnelled packet.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
/cgi/cvsweb.cgi/src/sys/sys/protosw.h
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/sys/protosw.h
http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/sys/protosw.h
itojun
-
The IPv6 Users Mailing List
Unsubscribe
, therefore, it is misleading to say many freebsd hackers.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
. is the easiest for most of the people today.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
Kame NATPT translation mechanism is a bidirectional mechanism?
no. just like IPv4 NAT, it is unidirectional, and IPv6-to-IPv4 only.
(you cannot identify IPv6 host from IPv4 host)
itojun
-
The IPv6 Users
.
allocation size from ISP to customer should be /48, but some ISPs
do different things.
itojun
-
The IPv6 Users Mailing List
Unsubscribe by sending unsubscribe users to [EMAIL PROTECTED]
A/B ICMPv6 redirects.
for ICMPv6 to work correctly, you MUST use link-local addresses
(fe80::blah) for the gateway setting. this is a hidden rule in
the RFCs.
itojun
___
Users mailing list
Users@ipv6.org
https://lists.ipv6.org
does anybody have IPv6 plans/status lists for content distribution
providers, like Akamai?
I happened to be in Boston this week and I can visit Akamai if
there's a contact point, as a preacher:-)
itojun
in
router renumbering RFC, which changes an IPv6 host into IPv6 router.
i was suggesting to filter out bad ICMPv6, based on ICMPv6 type/code,
not by the prefix. sorry if i wasn't clear enough.
itojun
-
The IPv6 Users
82 matches
Mail list logo
