Re: .sh script code to determine IPv4 or IPv6
I have some scripts that do fairly crude IPv4/6 validation testing. It is generally assumed that the input is coming from someone who knows what they are doing, but even the best of us have fat fingers sometimes :) Having standardized routines for something like this is great! Thanks, -Markham On 13-08-06 11:45 AM, Teske, Devin wrote: > On Aug 6, 2013, at 10:39 AM, Polytropon wrote: > >> On Tue, 6 Aug 2013 16:50:37 +, Teske, Devin wrote: >>> And yes... to clarify... the port is a mirror of what's in 9.x base. >>> (however, see my recent notes in a separate reply; TL;DR: port is >>> 9.x only; proceed only if you know you don't care about the dialog(1) >>> aspects of the library code). >> I think it should be relatively unproblematic to fetch the >> port and only use the subroutines "as is", even if it's just >> for educational purposes. :-) >> > Right. > > Just a warning though, what is "fetched" in ports is actually in the format > of what's in HEAD (read: not in the format of what gets installed). > > For example, there are things that end up in /usr/share/bsdconfig that aren't > in the "bsdconfig/share/" source directory (e.g., all the stuff under > /usr/share/bsdconfig/networking is under the source directory > "bsdconfig/networking/share"). This may be counter-intuitive from an > "exploratory" view if looking at the source directory (what's fetched by > ports). > > And since the port Makefile will prevent you from turning that fetch'ed > source directory into an installed software (putting things where they end > up), it might be easier to grab this pre-built package that I stashed... > > http://druidbsd.sf.net/download/bsdconfig/bsdconfig-0.9.0.tbz > > Because then you can say "pkg_add" and everything will be in the right place > (/usr/share/bsdconfig/ will be flush with everything and you won't have to > hunt-and-peck through the source with a "maintainers" view). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Aug 6, 2013, at 10:39 AM, Polytropon wrote: > On Tue, 6 Aug 2013 16:50:37 +, Teske, Devin wrote: >> And yes... to clarify... the port is a mirror of what's in 9.x base. >> (however, see my recent notes in a separate reply; TL;DR: port is >> 9.x only; proceed only if you know you don't care about the dialog(1) >> aspects of the library code). > > I think it should be relatively unproblematic to fetch the > port and only use the subroutines "as is", even if it's just > for educational purposes. :-) > Right. Just a warning though, what is "fetched" in ports is actually in the format of what's in HEAD (read: not in the format of what gets installed). For example, there are things that end up in /usr/share/bsdconfig that aren't in the "bsdconfig/share/" source directory (e.g., all the stuff under /usr/share/bsdconfig/networking is under the source directory "bsdconfig/networking/share"). This may be counter-intuitive from an "exploratory" view if looking at the source directory (what's fetched by ports). And since the port Makefile will prevent you from turning that fetch'ed source directory into an installed software (putting things where they end up), it might be easier to grab this pre-built package that I stashed... http://druidbsd.sf.net/download/bsdconfig/bsdconfig-0.9.0.tbz Because then you can say "pkg_add" and everything will be in the right place (/usr/share/bsdconfig/ will be flush with everything and you won't have to hunt-and-peck through the source with a "maintainers" view). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Tue, 6 Aug 2013 16:50:37 +, Teske, Devin wrote: > And yes... to clarify... the port is a mirror of what's in 9.x base. > (however, see my recent notes in a separate reply; TL;DR: port is > 9.x only; proceed only if you know you don't care about the dialog(1) > aspects of the library code). I think it should be relatively unproblematic to fetch the port and only use the subroutines "as is", even if it's just for educational purposes. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Aug 6, 2013, at 9:43 AM, Polytropon wrote: > On Tue, 06 Aug 2013 10:20:05 -0600, markham breitbach wrote: >> On 13-08-03 8:04 AM, Teske, Devin wrote: >>> Actually, there's /usr/share/bsdconfig/media/tcpip.subr >>> >>> >> I don't seem to have that (FreeBSD 8.3-RELEASE). >> Where would I get that from? > > Maybe from sysutils/bsdconfig in the ports collection? > I have not checked if this specific subroutine file is > part of the port... > Ah, Polytropon beat me ;D And yes... to clarify... the port is a mirror of what's in 9.x base. (however, see my recent notes in a separate reply; TL;DR: port is 9.x only; proceed only if you know you don't care about the dialog(1) aspects of the library code). -- Devin > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Aug 6, 2013, at 9:20 AM, markham breitbach wrote: > On 13-08-03 8:04 AM, Teske, Devin wrote: >> Actually, there's /usr/share/bsdconfig/media/tcpip.subr >> >> > I don't seem to have that (FreeBSD 8.3-RELEASE). Where would I get that > from? > > It's in up-coming 9.2-R (and present 9.2-* snapshots leading up to 9.2-R). You can snatch a copy of the code by installing sysutils/bsdconfig from the ports tree. However, the port is marked (correctly-so) as requiring FreeBSD 9.0 or higher. But don't let that stop you... the only reason it's marked as requiring 9.0 is because 9.0 brings in a new dialog(1) implementation. However, if you're interested in the TCP validation code... that will work on any release. It's only the dialog(1) stuff that won't work on 8.x or older. Luckily, it'll be pretty easy to avoid the land-mines. All functions starting with f_dialog_* should be avoided on 8.x or older. So here's the latest package to download (in case you're unsuccessful in getting the port to behave -- afterall, it may just balk at you for not running 9.x): fetch http://druidbsd.sourceforge.net/download/bsdconfig/bsdconfig-0.9.0.tbz That's a FreeBSD package. You can download it and say (as root): pkg_add bsdconfig-0.9.0.tbz Just be forewarned (again), on 8.x or older, executing "bsdconfig" will have widely unexpected results (it won't eat your homework, but it may or may not actually *run*). However, doing the above 2-step (fetch & pkg_add) will bring in the files you're looking for and give you the functionality you're wanting on 8.x. -- Devin P.S. I really *can't* make the dialog(1) stuff backward compatible with 8.x's (or any older's) version of dialog(1). The new `cdialog' variant that was brought into 9.x to replace the aging dialog(1)/libdialog pair is has a *lot* of functionality that I depend on. It could potentially take months to make bsdconfig *fully* backward compatible with 8.x. For now, it's safe if you just use the libraries and avoid any/all functions beginning with "f_dialog_". _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Tue, 06 Aug 2013 10:20:05 -0600, markham breitbach wrote: > On 13-08-03 8:04 AM, Teske, Devin wrote: > > Actually, there's /usr/share/bsdconfig/media/tcpip.subr > > > > > I don't seem to have that (FreeBSD 8.3-RELEASE). > Where would I get that from? Maybe from sysutils/bsdconfig in the ports collection? I have not checked if this specific subroutine file is part of the port... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On 13-08-03 8:04 AM, Teske, Devin wrote: > Actually, there's /usr/share/bsdconfig/media/tcpip.subr > > I don't seem to have that (FreeBSD 8.3-RELEASE). Where would I get that from? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Aug 3, 2013, at 5:04 AM, Robert Huff wrote: > > Fbsd8 writes: > >> I have a .sh script that I need to determine if the entered IP >> address is IPv4 or IPv6. >> >> Is there some .sh command that does this? > > Not that I know of. > But ... how hard can it be to figure out whether it uses '.' or > ':'? > Actually, there's /usr/share/bsdconfig/media/tcpip.subr Function family: f_validate_ipaddr6 $ipv6_addr # Should be complete; I digested multiple RFCs on IPv6 f_validate_ipaddr $ipv4_addr [$netmask] # optional netmask to validate IP is within doubly-valid f_validate_hostname $hostname # To RFC specifications 952 and 1123 But if you need to prompt the user to enter a value and then validate it, the above functions return meaningful exit status for determining what's wrong with their entry (why did it fail specification, for example). To help decode the exit status, the functions you want to use are: # In /usr/share/bsdconfig/networking/ipaddr.subr Function family: f_dialog_iperror $status $ipv4_addr f_dialog_ip6error $status $ipv6_addr As is implied with the "_dialog_" in their name, they take the $? exit status from the previously mentioned f_validate_*() functions and display a dialog(1) error appropriate to what's wrong. For example, you might see: ERROR! One or more individual octets within the IPv4 address\n(separated by dots) contains one or more invalid characters.\nOctets must contain only the characters 0-9.\n\nInvalid IP Address: %s or ERROR! The IP address entered has either too few (less than 3), too\nmany (more than 8), or not enough segments, separated by colons.\n\nInvalid IPv6 Address: %s And then, in the same function family above (as the *ip[6]error()): f_dialog_vaildate_ipaddr $ipv4_addr f_dialog_validate_ipaddr6 $ipv6_addr These are like: f_validate_ipaddr $ipv4_addr f_validate_ipaddr6 $ipv6_addr Except as implied by the extra "_dialog_" in their name, they will actually run f_validate_* and then f_dialog_ip[6]error() for you with the result. Finally, last, but not least... The process of actually *getting* the values has been simplified too. In the same family function (as f_dialog_ip[6]error and f_dialog_validate_ipaddr[6]()) is: f_dialog_input_ipaddr $interface $ipaddr # $interface is displayed in the prompt text # $ipaddr is used as default text in the input box If user doesn't press escape or select cancel, $ipaddr will hold the users entry. This function validates, displays errors, and is an all-around solution if you need to prompt the user to enter the info and only proceed if they enter a valid entry (the above function is IPv4 centric and supports CIDR notation). The IPv6 version of the latter (f_dialog_input_ipaddr6) does not yet exist. I'm getting there. For now, if you need to prompt for an entry that could be IPv6, use the generic f_dialog_input() routine and sanitize it with the aforementioned API. -- Cheers, Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: .sh script code to determine IPv4 or IPv6
On Aug 3, 2013, at 4:30 AM, Fbsd8 wrote:
> I have a .sh script that I need to determine if the entered IP address
> is IPv4 or IPv6.
>
> Is there some .sh command that does this?
>
In RELENG_9, soon to be released 9.2-R:
=== FILE: wis ===
#!/bin/sh
DEVICE_SELF_SCAN_ALL=
. /usr/share/bsdconfig/media/tcpip.subr
if f_validate_ipaddr6 "$1"; then
echo "Hey, nice IPv6 addr, great job!"
elif f_validate_ipaddr "$1"; then
echo "Hey, nice IPv4 addr; smiles"
elif f_validate_hostname "$1"; then
echo "Hey, nice hostname"
else
echo "What on Earth wast, _that_?!"
exit 1
fi
=== END FILE ===
dte...@scribe9.vicor.com ~ $ ./wis ::1
Hey, nice IPv6 addr, great job!
dte...@scribe9.vicor.com ~ $ ./wis 0::1
Hey, nice IPv6 addr, great job!
dte...@scribe9.vicor.com ~ $ ./wis 0:::1
What on Earth wast, _that_?!
dte...@scribe9.vicor.com ~ $ ./wis 1.2.3.4
Hey, nice IPv4 addr; smiles
dte...@scribe9.vicor.com ~ $ ./wis 0.2.3.4
Hey, nice IPv4 addr; smiles
dte...@scribe9.vicor.com ~ $ ./wis 256.2.3.4
Hey, nice hostname
dte...@scribe9.vicor.com ~ $ ./wis foo.bar.com
Hey, nice hostname
dte...@scribe9.vicor.com ~ $ ./wis abc-123
Hey, nice hostname
dte...@scribe9.vicor.com ~ $ ./wis abc_123
What on Earth wast, _that_?!
--
Cheers,
Devin
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
.sh script code to determine IPv4 or IPv6
Fbsd8 writes: > I have a .sh script that I need to determine if the entered IP > address is IPv4 or IPv6. > > Is there some .sh command that does this? Not that I know of. But ... how hard can it be to figure out whether it uses '.' or ':'? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
.sh script code to determine IPv4 or IPv6
I have a .sh script that I need to determine if the entered IP address is IPv4 or IPv6. Is there some .sh command that does this? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: reboot after removing ipv6 ?
Frank Bonnet esiee.fr> writes: > > Hello > > Do I have to reboot a server after unvalidating IPv6 in /etc/rc.conf ? > > I seems to use "/etc/rc.d/netif restart" is not suffisant Use 'netstat' to see what service(s) listen for ipv6 traffic and restart them. jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
reboot after removing ipv6 ?
Hello Do I have to reboot a server after unvalidating IPv6 in /etc/rc.conf ? I seems to use "/etc/rc.d/netif restart" is not suffisant Thank you ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 Ready Logo test to Freebsd9.0(host), nd.p2 169-175 failed.
Dear Freebsder： I made a Ipv6 ready logo test to Freebsd9.0,but nd.p2 169-175 items were failed . These failed items are related to Redirection. I find the lack of neighbor solicitation make these items fail . Maybe the existence of neighbor cache of the tester Freebsd cause the lack of 'necessary' neighbor solicitation. I don't know how to make these failed items pass. I am looking forward to receive your reply. Thanks! ps: attachments are the image of tester Freebsd's /etc/rc.conf and some related images about the test. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Question about tunnelling Ethernet traffic over IPv6 using EtherIP protocol
Hi, everyone: I am trying to set up a EtherIP tunnel device to tunnel Ethernet traffic over IPv6 using EtherIP protocol. I have Freebsd 8.3 runs on a i386 machine, and ipv6 enabled. I tried the commands below but no one works... ifconfig gif0 create ifconfig gif0 tunnel 2001:::1 2001:::10 up ifconfig: SIOCSIFPHYADDR: Address family not supported by protocol family ifconfig gif0 tunnel 2001:::1/64 2001:::10/64 up ifconfig: error in parsing address string: host name nor servname provided, or not known Could anyone please teach me why it is? I will be very grateful for any help you can provide. P.S.1 Both 2001:::1 and 2001:::10 are faked, I just use them in my local testing environment. P.S.2 I have assigned 2001:::1/64 on one of ethernet network interface on Freebsd machine, and there is another PC assigned 2001:::10/64. P.S.3 According to the link(http://www.daemon-systems.org/man/etherip.4.html), Freebsd should be able to provide this feature. Best regards, Yang ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 && getaddrinfo(3C)
El día Thursday, July 12, 2012 a las 09:01:50PM -0500, Robert Bonomi escribió:
> > > req.ai_flags = AI_ADDRCONFIG|AI_NUMERICHOST;
> > > req.ai_family = AF_INET6;/* Same as AF_INET6. */
>
> Isn't the setting of 'req.ai_family', above, going to guarantee that
> something that "looks like" an IPv4 address will not be considered valid?
>
> After all, what *POSSIBLE* _IPv6_info_ is there about an IPv4 address?
>
> Per the manpage example, try PF_UNSPEC.
With PF_UNSPEC it works fine now, thanks for the hint; I'm attaching the
code for the client and as well one for a server creating LISTEN on IPv6
and IPv4 at the same time and handling the connections on both ports;
HIH
matthias
/* IPv6 client code using getaddrinfo */
#include
#include
#include
#include
#include
#include
#include
main(int argc, char **argv)
{
struct addrinfo req, *ans;
int code, s, n;
char buf[1024];
memset(&req, 0, sizeof(req));
req.ai_flags = 0; /* may be restricted to
AI_ADDRCONFIG|AI_NUMERICHOST|... */
/* req.ai_family = AF_INET6;/* validates only AF_INET6 */
/* req.ai_family = AF_INET; /* validates only AF_INET, i.e. IPv4 */
req.ai_family = PF_UNSPEC; /* validates IPv4 and IPv6. */
req.ai_socktype = SOCK_STREAM;
/* Use protocol TCP */
req.ai_protocol = IPPROTO_TCP; /* 0: any, IPPROTO_UDP: UDP */
printf("host: %s\n", argv[1]);
if ((code = getaddrinfo(argv[1], "ssh", &req, &ans)) != 0) {
fprintf(stderr, "ssh: getaddrinfo failed code %d: %s\n", code,
gai_strerror(code));
exit(1);
}
/* 'ans' must contain at least one addrinfo, use the first */
s = socket(ans->ai_family, ans->ai_socktype, ans->ai_protocol);
if (s < 0) {
perror("ssh: socket");
exit(3);
}
/* Connect does the bind for us */
if (connect(s, ans->ai_addr, ans->ai_addrlen) < 0) {
perror("ssh: connect");
exit(5);
}
/* just for test: read in SSH' good morning message */
n = read(s, buf, 1024);
printf ("read: %s", buf);
/*
Free answers after use
*/
freeaddrinfo(ans);
exit(0);
}
/* IPv6 server code using getaddrinfo */
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
void doit()
{
printf("child forked end ended\n");
}
main(int argc, char **argv)
{
struct sockaddr_in6 from;
struct addrinfo req, *ans, *ans2;
intcode, sockFd1, sockFd2, len;
/* Set ai_flags to AI_PASSIVE to indicate that return addres s is
suitable for bind() */
memset(&req, 0, sizeof(req));
req.ai_flags = AI_PASSIVE;
req.ai_family = PF_UNSPEC; /* IPv6+IPv4: PF_UNSPEC, IPv4:
PF_INET */
req.ai_socktype = SOCK_STREAM;
req.ai_protocol = IPPROTO_TCP;
#define SLNP "3025"
if ((code = getaddrinfo(NULL, SLNP, &req, &ans)) != 0) {
fprintf(stderr, "SLNP (%s): getaddrinfo failed code %d: %s\n",
SLNP, code, gai_strerror(code));
exit(1);
}
/* 'ans' must contain at least one addrinfo and we use the first. */
/* it seems(!) that 1st one is the IPv6 when we use PF_UNSPEC */
if( (sockFd1 = socket(ans->ai_family, ans->ai_socktype,
ans->ai_protocol)) < 0) {
perror("socket");
exit(-1);
}
if (bind(sockFd1, ans->ai_addr, ans->ai_addrlen) < 0) {
perror("bind");
close(sockFd1);
exit(-1);
}
/* create the 1st LISTEN */
printf("1st (IPv6) LISTEN...\n");
listen(sockFd1, 5);
/* if there is a 2nd addrinfo provided by getaddrinfo(3C) and we will
create 2nd socket... */
ans2 = NULL;
if( ans->ai_next != NULL )
ans2 = ans->ai_next;
sockFd2 = -1; /* set to -1 to be used as this in poll, see below
*/
if( ans2 != NULL ) {
if( (sockFd2 = socket(ans2->ai_family, ans2->ai_socktype,
ans2->ai_protocol)) < 0) {
perror("socket");
exit(-1);
}
if (bind(sockFd2, ans2->ai_addr, ans2->ai_addrlen) < 0) {
perror("bind");
close(sockFd2);
exit(-1);
}
printf("2nd (IPv4) LISTEN...\n");
listen(sockFd2,
Re: IPv6 && getaddrinfo(3C)
> From: Doug Hardie
> Date: Thu, 12 Jul 2012 14:21:38 -0700
> Subject: Re: IPv6 && getaddrinfo(3C)
>
> On 12 July 2012, at 07:24, Matthias Apitz wrote:
>
> > Hello,
> >
> > I'm playing around with IPv6 code on a FreeBSD 9 system and can't get
> > getaddrinfo(3C) to do what it should do as stated in its man page:
> > accept an IPv6 and IPv4 IP addr, it only works with the IPv6 form:
> >
> > $ ./a.out ::1
> > host: ::1 read: SSH-2.0-OpenSSH_5.6p1 FreeBSD-2010
> > $ ./a.out 127.0.0.1
> > host: 127.0.0.1 ssh: getaddrinfo failed code 8: hostname nor servname
> > provided, or not known
> > $ telnet 127.0.0.1 22
> > Trying 127.0.0.1... Connected to localhost. Escape character is '^]'.
> > SSH-2.0-OpenSSH_5.6p1 FreeBSD-2010
> >
> > the used C-code is attached below; what I'm doing wrong in the code?
> >
> > Thanks
> >
> > matthias
> >
> > /* IPv6 client code using getaddrinfo */
> >
> > #include
> > #include
> > #include
> > #include
> > #include
> > #include
> > #include
> >
> >
> > main(argc, argv)/* client side */
> > intargc; char *argv[];
> > {
> >
> > struct addrinforeq, *ans; int code, s, n; char buf[1024];
> >
> > memset(&req, 0, sizeof(req));
> > req.ai_flags = AI_ADDRCONFIG|AI_NUMERICHOST;
> > req.ai_family = AF_INET6; /* Same as AF_INET6. */
Isn't the setting of 'req.ai_family', above, going to guarantee that
something that "looks like" an IPv4 address will not be considered valid?
After all, what *POSSIBLE* _IPv6_info_ is there about an IPv4 address?
Per the manpage example, try PF_UNSPEC.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 && getaddrinfo(3C)
On 12 July 2012, at 07:24, Matthias Apitz wrote:
>
> Hello,
>
> I'm playing around with IPv6 code on a FreeBSD 9 system and can't get
> getaddrinfo(3C) to do what it should do as stated in its man page:
> accept an IPv6 and IPv4 IP addr, it only works with the IPv6 form:
>
> $ ./a.out ::1
> host: ::1
> read: SSH-2.0-OpenSSH_5.6p1 FreeBSD-2010
> $ ./a.out 127.0.0.1
> host: 127.0.0.1
> ssh: getaddrinfo failed code 8: hostname nor servname provided, or not known
> $ telnet 127.0.0.1 22
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> SSH-2.0-OpenSSH_5.6p1 FreeBSD-2010
>
> the used C-code is attached below; what I'm doing wrong in the code?
>
> Thanks
>
> matthias
>
> /* IPv6 client code using getaddrinfo */
>
> #include
> #include
> #include
> #include
> #include
> #include
> #include
>
>
> main(argc, argv) /* client side */
> int argc;
> char *argv[];
> {
>
> struct addrinfo req, *ans;
> int code, s, n;
> char buf[1024];
>
> memset(&req, 0, sizeof(req));
> req.ai_flags = AI_ADDRCONFIG|AI_NUMERICHOST;
> req.ai_family = AF_INET6; /* Same as AF_INET6. */
> req.ai_socktype = SOCK_STREAM;
>
> /* */
> /* Use default protocol (in this case tcp) */
> /* */
>
> req.ai_protocol = 0;
>
> printf("host: %s\n", argv[1]);
> if ((code = getaddrinfo(argv[1], "ssh", &req, &ans)) != 0) {
> fprintf(stderr, "ssh: getaddrinfo failed code %d: %s\n", code,
> gai_strerror(code));
> exit(1);
> }
>
>
> /* */
> /* ans must contain at least one addrinfo, use */
> /* the first. */
> /* */
>
> s = socket(ans->ai_family, ans->ai_socktype, ans->ai_protocol);
> if (s < 0) {
> perror("ssh: socket");
> exit(3);
> }
>
> /* Connect does the bind for us */
>
> if (connect(s, ans->ai_addr, ans->ai_addrlen) < 0) {
> perror("ssh: connect");
> exit(5);
> }
>
> n = read(s, buf, 1024);
> printf ("read: %s", buf);
>
> /* */
> /* Free answers after use */
> /* */
> freeaddrinfo(ans);
>
> exit(0);
> }
>
>
I won't claim to be an expert on this, but I have used getaddrinfo successfully
in servers. The only thing I see that might be an issue is the use of zero for
ai_protocol. The comment in the man page implies that value is for servers and
not clients. I suspect you have to set the specific protocol you want. You
haven't included AI_PASSIVE so I suspect its expecting you to use the address
to contact a server.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 && getaddrinfo(3C)
Hello,
I'm playing around with IPv6 code on a FreeBSD 9 system and can't get
getaddrinfo(3C) to do what it should do as stated in its man page:
accept an IPv6 and IPv4 IP addr, it only works with the IPv6 form:
$ ./a.out ::1
host: ::1
read: SSH-2.0-OpenSSH_5.6p1 FreeBSD-2010
$ ./a.out 127.0.0.1
host: 127.0.0.1
ssh: getaddrinfo failed code 8: hostname nor servname provided, or not known
$ telnet 127.0.0.1 22
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.6p1 FreeBSD-2010
the used C-code is attached below; what I'm doing wrong in the code?
Thanks
matthias
/* IPv6 client code using getaddrinfo */
#include
#include
#include
#include
#include
#include
#include
main(argc, argv)/* client side */
int argc;
char *argv[];
{
struct addrinfo req, *ans;
int code, s, n;
char buf[1024];
memset(&req, 0, sizeof(req));
req.ai_flags = AI_ADDRCONFIG|AI_NUMERICHOST;
req.ai_family = AF_INET6; /* Same as AF_INET6. */
req.ai_socktype = SOCK_STREAM;
/* */
/* Use default protocol (in this case tcp) */
/* */
req.ai_protocol = 0;
printf("host: %s\n", argv[1]);
if ((code = getaddrinfo(argv[1], "ssh", &req, &ans)) != 0) {
fprintf(stderr, "ssh: getaddrinfo failed code %d: %s\n", code,
gai_strerror(code));
exit(1);
}
/* */
/* ans must contain at least one addrinfo, use */
/* the first. */
/* */
s = socket(ans->ai_family, ans->ai_socktype, ans->ai_protocol);
if (s < 0) {
perror("ssh: socket");
exit(3);
}
/* Connect does the bind for us */
if (connect(s, ans->ai_addr, ans->ai_addrlen) < 0) {
perror("ssh: connect");
exit(5);
}
n = read(s, buf, 1024);
printf ("read: %s", buf);
/* */
/* Free answers after use */
/* */
freeaddrinfo(ans);
exit(0);
}
--
Matthias Apitz
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
rc.conf ifconfig ipv6 address fails at boot
Hello questions, I can't figure out what I'm doing wrong here. Trying to get a static IPv6 on a server at boot time from rc.conf, and that fails. Notice I haven't set ipv6_network_interfaces , so it defaults to "auto". = ipv6_enable="YES" ipv6_defaultrouter="2a01:e35:2f1b:e2a0::1" # VLAN 99 = WAN / CISCO INTERCONNECTION ifconfig_vlan99="vlan 99 vlandev re0 up" ipv4_addrs_vlan99="192.168.99.3/24" ipv6_addrs_vlan99="2a01:e35:2f1b:e2a0::dead:beef/64" = I resorted to adding the IPv6 and default gateway via a @reboot line in /etc/crontab , but this is really not right... The machine is running 8.3-PRERELEASE from february. Should I instead try the following ? ifconfig_vlan99="inet 192.168.99.3/24 vlan 99 vlandev re0 up" ipv6_ifconfig_vlan99="2a01:e35:2f1b:e2a0::dead:beef/64" I'm not really at liberty to reboot the server to test during work time ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Configuration problem with IPv6 router ("cannot forward src")
On 08/06/2012 06:59, Matthew Seaman wrote: Probably. The good news is that once you've got it running the IPv6 support in FreeBSD is rock solid and works like a charm. It turns out that PF was being too helpful and trying to NAT for both IPv4 and IPv6 - adding 'inet' to the "nat on $ext_if..." line fixed it. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Configuration problem with IPv6 router ("cannot forward src")
On 07/06/2012 23:56, Robert Bonomi wrote: Please provide the output from these two commands: ifconfig -a netstat -nr on both the router and on an 'inside' machine. (identifying which is which:) There is also a question of 'where' the /48 comes from -- and how traffic to those addresses is being routed from the outside world. The /48 came from my ISP, so it should be getting routed correctly. ifconfig -a (with ral0/lo0 removed): em0: flags=8843 metric 0 mtu 1500 options=4219b ether [em0_MAC] inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::[em0_MAC]%em0 prefixlen 64 scopeid 0x1 inet6 [prefix]:a::b prefixlen 64 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active em1: flags=8843 metric 0 mtu 1500 options=4219b ether [em1_MAC] inet6 fe80::[em1_MAC]%em1 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active tun0: flags=8051 metric 0 mtu 1492 options=8 inet6 fe80::[em0_MAC]%tun0 prefixlen 64 scopeid 0xf inet [MYADDR] --> [HISADDR] netmask 0xff00 inet6 [prefix]:c::b prefixlen 64 nd6 options=21 Opened by PID 1092 Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default[HISADDR] UGS 0 2476 tun0 [MYADDR] link#15UHS 00lo0 [HISADDR] link#15UH 00 tun0 127.0.0.1 link#14UH 00lo0 192.168.2.0/24 link#1 U 0 3985em0 192.168.2.1link#1 UHS 00lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSlo0 => default fe80::[em0_MAC]%tun0 UGS tun0 ::1 link#14 UH lo0 :::0.0.0.0/96 ::1 UGRSlo0 [prefix]:c::/64 link#15 U tun0 [prefix]:c::1 link#15 UHS lo0 [prefix]:a::/64 link#1 U em0 [prefix]:a::1 link#1 UHS lo0 fe80::/10 ::1 UGRSlo0 fe80::%em0/64 link#1 U em0 fe80::[em0_MAC]%em0 link#1UHS lo0 fe80::%em1/64 link#2 U em1 fe80::[em1_MAC]%em1 link#2UHS lo0 fe80::%lo0/64 link#14 U lo0 fe80::1%lo0 link#14 UHS lo0 fe80::%tun0/64link#15 US tun0 fe80::[em0_MAC]%tun0 link#15 UHS lo0 ff01::%em0/32 fe80::[em0_MAC]%em0 U em0 ff01::%em1/32 fe80::[em1_MAC]%em1 U em1 ff01::%lo0/32 ::1 U lo0 ff01::%tun0/32fe80::[em0_MAC]%tun0 US tun0 ff02::/16 ::1 UGRSlo0 ff02::%em0/32 fe80::[em0_MAC]%em0 U em0 ff02::%em1/32 fe80::[em1_MAC]%em1 U em1 ff02::%lo0/32 ::1 U lo0 ff02::%tun0/32fe80::[em0_MAC]%tun0 UGS tun0 rtadvd.conf contains: em0:\ :addrs#1:addr="[prefix]:a::":prefixlen#64;tc=ether:raflags="o": rc.conf contains: ifconfig_em0=" inet 192.168.2.1 netmask 255.255.255.0" ifconfig_em0_ipv6=" inet6 [prefix]:a::b" ifconfig_em1="up" pf_enable="YES" gateway_enable="YES" ppp_enable="YES" ppp_nat="NO" ppp_goscomb_mode="ddial" ppp_goscomb_nat="NO" ppp_profile="isp" ipv6_gateway_enable="YES" ipv6_network_interfaces="em0 em1 tun0" dhcpd_enable="YES" dhcpd6_enable="NO" dhcpd_flags="-q" dhcpd6_flags="-q" dhcpd_conf="/usr/local/etc/dhcpd.conf" dhcpd6_conf="/usr/local/etc/dhcpd6.conf" dhcpd_ifaces="em0" dhcpd6_ifaces="em0" dhcpd_withumask="022" dhcpd6_withumask="022" dhcpd_chuser_enable="YES" dhcpd6_chuser_enable="YES" dhcpd_withuser="dhcpd" dhcpd6_withuser="dhcpd" dhcpd_withgroup="dhcpd" dhcpd6_withgroup="dhcpd" dhcpd_chroot_enable="YES" dhcpd6_chroot_enable="YES" dhcpd_devfs_enable="YES" dhcpd6_devfs_enable="YES" dhcpd_rootdir="/var/db/dhcpd" dhcpd6_rootdir="/var/db/dhcpd6" rtadvd_enable="NO" rtadvd_interfaces="em0" I've tried configuring a machine with a static configuration, bypassing any issues with rtadvd/dhcpd6 so I'm fairly sure the problem is on the router. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Configuration problem with IPv6 router ("cannot forward src")
Make sure you are only advertising a /64 addr prefixlen in rtadvd.conf, and not the entire /48. On 6/7/2012 4:36 PM, Bruce Cran wrote: I'm trying to set up a IPv6 router (running -current) on my home network. My ISP gives me a /128 via PPP and I have a /48 allocation, which I use to give em0 and tun0 public addresses in different subnets (tun0 is assigned the address via ppp.linkup). I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites from the router. The problem is that rtadvd continues advertising the default gateway as tun0's link-local address - and pinging from a machine on the network results in "cannot forward src" messages on the router (strangely, despite hisaddr being fe80::205:... in ppp.log, the kernel logs the address as fe80:f::205:...). Is there some extra configuration I've likely missed that's needed when using IPv6 via PPP? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Configuration problem with IPv6 router ("cannot forward src")
On 07/06/2012 23:36, Bruce Cran wrote: > I'm trying to set up a IPv6 router (running -current) on my home > network. My ISP gives me a /128 via PPP and I have a /48 allocation, > which I use to give em0 and tun0 public addresses in different subnets > (tun0 is assigned the address via ppp.linkup). > I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, > ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites > from the router. rtadvd can be limited to operate on a specific interface. Try setting rtadvd_interfaces="em0" in /etc/rc.conf > The problem is that rtadvd continues advertising the default gateway as > tun0's link-local address - and pinging from a machine on the network > results in "cannot forward src" messages on the router (strangely, > despite hisaddr being fe80::205:... in ppp.log, the kernel logs the > address as fe80:f::205:...). Try setting: ipv6_default_interface="tun0" and possibly also ipv6_defaultrouter="-interface tun0" I use a gif tunnel (IPv6 over IPv4) for my IPv6 connectivity -- no native support for IPv6 in my ADSL router -- so not exactly equivalent but pretty similar in many ways. > Is there some extra configuration I've likely missed that's needed when > using IPv6 via PPP? Probably. The good news is that once you've got it running the IPv6 support in FreeBSD is rock solid and works like a charm. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Configuration problem with IPv6 router ("cannot forward src")
> From: Bruce Cran > > I'm trying to set up a IPv6 router (running -current) on my home > network. My ISP gives me a /128 via PPP and I have a /48 allocation, > which I use to give em0 and tun0 public addresses in different subnets > (tun0 is assigned the address via ppp.linkup). > I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, > ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites > from the router. > > The problem is that rtadvd continues advertising the default gateway as > tun0's link-local address - and pinging from a machine on the network > results in "cannot forward src" messages on the router (strangely, > despite hisaddr being fe80::205:... in ppp.log, the kernel logs the > address as fe80:f::205:...). > > Is there some extra configuration I've likely missed that's needed when > using IPv6 via PPP? Please provide the output from these two commands: ifconfig -a netstat -nr on both the router and on an 'inside' machine. (identifying which is which :) There is also a question of 'where' the /48 comes from -- and how traffic to those addresses is being routed from the outside world. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Configuration problem with IPv6 router ("cannot forward src")
I'm trying to set up a IPv6 router (running -current) on my home network. My ISP gives me a /128 via PPP and I have a /48 allocation, which I use to give em0 and tun0 public addresses in different subnets (tun0 is assigned the address via ppp.linkup). I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites from the router. The problem is that rtadvd continues advertising the default gateway as tun0's link-local address - and pinging from a machine on the network results in "cannot forward src" messages on the router (strangely, despite hisaddr being fe80::205:... in ppp.log, the kernel logs the address as fe80:f::205:...). Is there some extra configuration I've likely missed that's needed when using IPv6 via PPP? -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
implementing ipv6 into my ipfw ruleset...
I have a fairly simple ipfw ruleset, which looks like: 100 allow tcp from any to any established 110 allow icmp from any to any icmptypes 0,3,8,11 120 deny icmp from any to any 130 allow ip from any to any via lo0 200 allow udp from me to any 53 210 allow udp from any 53 to me 220 allow udp from any to me 33433-33499 230 allow tcp from any to 82.197.184.219 22,80,443 setup 65000 deny log ip from any to me 65001 deny log ip from any to me6 What I am wondering is, am I blocking all ipv6 traffic by not explicitly allowing ipv6 in (for the established rule 100, icmp rule 110, and the entire block of 200-230) ? Or, since that is all tcp/udp/icmp, it doesn't matter, and I am properly allowing in ipv6 traffic, but ONLY for the tcp/udp ports I specify, and then blocking the rest ? Basically: how is my ruleset treating ipv6 traffic (other than the fact that, at the end of the set, I deny all ipv6 that has gotten to that point) thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
On 23. May 2012, at 08:22 , Venkat Duvvuru wrote: > Folks, > Can somebody please explain me why "tcp checsum" calculation is mandated in > the freebsd network stack (tcp_input--->in6_cksum) albeit the card supports > it? > > Probably Steve is the right person who can answer this. Just for public reference; we talked offline. The code simply was never done and let's see how much of it I can get into the tree the next 48 hours. /bz -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
Folks, Can somebody please explain me why "tcp checsum" calculation is mandated in the freebsd network stack (tcp_input--->in6_cksum) albeit the card supports it? Probably Steve is the right person who can answer this. /Venkat On Wed, May 23, 2012 at 11:27 AM, Venkat Duvvuru wrote: > Ok. I found the reason for the throughput drop in case of IPv6. > Reason is that the "tcp check sum" calculation is mandated in case of IPv6 > irrespective of whether the card is doing it or not (checksum offload). Is > there a reason why freebsd is doing it that way? > > /Venkat > > On Tue, May 22, 2012 at 11:16 PM, Jack Vogel wrote: > >> LRO is a huge win for 10G (as is TSO on the TX side), so odds are good >> its behind the drop, >> in any case you'll be able to test that soon :) >> >> Jack >> >> >> >> On Tue, May 22, 2012 at 10:35 AM, Venkat Duvvuru < >> venkatduvvuru...@gmail.com> wrote: >> >>> Thanks for the response. >>> >>> I observed that there is a significant performance drop in case of IPv6 >>> on the "rx" side. >>> While I'm able to hit line rate ~9.5 Gbps on a 10gb NIC for IPv4..I >>> could only get ~6 Gbps on the "rx" front for IPv6...However "tx" for IPv6 >>> is on par with IPv4 hitting almost line rates. >>> >>> Could this be because of lack of LRO6?? >>> >>> Note: hwpmc profiling shows that most of the time is spent in the IPv6 >>> stack code >>> >>> /Venkat >>> On Tue, May 22, 2012 at 10:37 PM, Bjoern A. Zeeb wrote: >>> >>>> >>>> On 22. May 2012, at 17:04 , Jack Vogel wrote: >>>> >>>> > Oh, that's right, distracted with other projects and I forgot, now we >>>> just need >>>> > to have an LRO that works with forwarding eh :) >>>> >>>> That's a 6 line bainaid commit afterwards, basically returning form the >>>> LRO queuing >>>> function in case forwarding is turned on for that address family; a >>>> proper solution >>>> for long term can than be done whenever we feel like it. The above we >>>> should have done >>>> years ago;) >>>> >>>> >>>> > You ROCK bz :) >>>> > >>>> > Jack >>>> > >>>> > >>>> > On Tue, May 22, 2012 at 10:01 AM, Bjoern A. Zeeb >>>> wrote: >>>> > >>>> > On 22. May 2012, at 16:50 , Jack Vogel wrote: >>>> > >>>> > > The LRO code as it stands right now is IPV4 specific, it would be >>>> nice to >>>> > > extend it, one of >>>> > > many improvements that may get done at some point. >>>> > >>>> > I am about to commit it to HEAD. Bear another few days with me; I >>>> know >>>> > I am running late but committing new code had less prio than some >>>> other >>>> > real life things currently. >>>> > >>>> > I'll also bring TSO6, etc... >>>> >>>> -- >>>> Bjoern A. Zeeb You have to have visions! >>>> It does not matter how good you are. It matters what good you do! >>>> >>>> >>> >> > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
Ok. I found the reason for the throughput drop in case of IPv6. Reason is that the "tcp check sum" calculation is mandated in case of IPv6 irrespective of whether the card is doing it or not (checksum offload). Is there a reason why freebsd is doing it that way? /Venkat On Tue, May 22, 2012 at 11:16 PM, Jack Vogel wrote: > LRO is a huge win for 10G (as is TSO on the TX side), so odds are good its > behind the drop, > in any case you'll be able to test that soon :) > > Jack > > > > On Tue, May 22, 2012 at 10:35 AM, Venkat Duvvuru < > venkatduvvuru...@gmail.com> wrote: > >> Thanks for the response. >> >> I observed that there is a significant performance drop in case of IPv6 >> on the "rx" side. >> While I'm able to hit line rate ~9.5 Gbps on a 10gb NIC for IPv4..I could >> only get ~6 Gbps on the "rx" front for IPv6...However "tx" for IPv6 is on >> par with IPv4 hitting almost line rates. >> >> Could this be because of lack of LRO6?? >> >> Note: hwpmc profiling shows that most of the time is spent in the IPv6 >> stack code >> >> /Venkat >> On Tue, May 22, 2012 at 10:37 PM, Bjoern A. Zeeb wrote: >> >>> >>> On 22. May 2012, at 17:04 , Jack Vogel wrote: >>> >>> > Oh, that's right, distracted with other projects and I forgot, now we >>> just need >>> > to have an LRO that works with forwarding eh :) >>> >>> That's a 6 line bainaid commit afterwards, basically returning form the >>> LRO queuing >>> function in case forwarding is turned on for that address family; a >>> proper solution >>> for long term can than be done whenever we feel like it. The above we >>> should have done >>> years ago;) >>> >>> >>> > You ROCK bz :) >>> > >>> > Jack >>> > >>> > >>> > On Tue, May 22, 2012 at 10:01 AM, Bjoern A. Zeeb >>> wrote: >>> > >>> > On 22. May 2012, at 16:50 , Jack Vogel wrote: >>> > >>> > > The LRO code as it stands right now is IPV4 specific, it would be >>> nice to >>> > > extend it, one of >>> > > many improvements that may get done at some point. >>> > >>> > I am about to commit it to HEAD. Bear another few days with me; I know >>> > I am running late but committing new code had less prio than some other >>> > real life things currently. >>> > >>> > I'll also bring TSO6, etc... >>> >>> -- >>> Bjoern A. Zeeb You have to have visions! >>> It does not matter how good you are. It matters what good you do! >>> >>> >> > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
LRO is a huge win for 10G (as is TSO on the TX side), so odds are good its behind the drop, in any case you'll be able to test that soon :) Jack On Tue, May 22, 2012 at 10:35 AM, Venkat Duvvuru wrote: > Thanks for the response. > > I observed that there is a significant performance drop in case of IPv6 on > the "rx" side. > While I'm able to hit line rate ~9.5 Gbps on a 10gb NIC for IPv4..I could > only get ~6 Gbps on the "rx" front for IPv6...However "tx" for IPv6 is on > par with IPv4 hitting almost line rates. > > Could this be because of lack of LRO6?? > > Note: hwpmc profiling shows that most of the time is spent in the IPv6 > stack code > > /Venkat > On Tue, May 22, 2012 at 10:37 PM, Bjoern A. Zeeb wrote: > >> >> On 22. May 2012, at 17:04 , Jack Vogel wrote: >> >> > Oh, that's right, distracted with other projects and I forgot, now we >> just need >> > to have an LRO that works with forwarding eh :) >> >> That's a 6 line bainaid commit afterwards, basically returning form the >> LRO queuing >> function in case forwarding is turned on for that address family; a >> proper solution >> for long term can than be done whenever we feel like it. The above we >> should have done >> years ago;) >> >> >> > You ROCK bz :) >> > >> > Jack >> > >> > >> > On Tue, May 22, 2012 at 10:01 AM, Bjoern A. Zeeb >> wrote: >> > >> > On 22. May 2012, at 16:50 , Jack Vogel wrote: >> > >> > > The LRO code as it stands right now is IPV4 specific, it would be >> nice to >> > > extend it, one of >> > > many improvements that may get done at some point. >> > >> > I am about to commit it to HEAD. Bear another few days with me; I know >> > I am running late but committing new code had less prio than some other >> > real life things currently. >> > >> > I'll also bring TSO6, etc... >> >> -- >> Bjoern A. Zeeb You have to have visions! >> It does not matter how good you are. It matters what good you do! >> >> > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
Thanks for the response. I observed that there is a significant performance drop in case of IPv6 on the "rx" side. While I'm able to hit line rate ~9.5 Gbps on a 10gb NIC for IPv4..I could only get ~6 Gbps on the "rx" front for IPv6...However "tx" for IPv6 is on par with IPv4 hitting almost line rates. Could this be because of lack of LRO6?? Note: hwpmc profiling shows that most of the time is spent in the IPv6 stack code /Venkat On Tue, May 22, 2012 at 10:37 PM, Bjoern A. Zeeb wrote: > > On 22. May 2012, at 17:04 , Jack Vogel wrote: > > > Oh, that's right, distracted with other projects and I forgot, now we > just need > > to have an LRO that works with forwarding eh :) > > That's a 6 line bainaid commit afterwards, basically returning form the > LRO queuing > function in case forwarding is turned on for that address family; a > proper solution > for long term can than be done whenever we feel like it. The above we > should have done > years ago;) > > > > You ROCK bz :) > > > > Jack > > > > > > On Tue, May 22, 2012 at 10:01 AM, Bjoern A. Zeeb wrote: > > > > On 22. May 2012, at 16:50 , Jack Vogel wrote: > > > > > The LRO code as it stands right now is IPV4 specific, it would be nice > to > > > extend it, one of > > > many improvements that may get done at some point. > > > > I am about to commit it to HEAD. Bear another few days with me; I know > > I am running late but committing new code had less prio than some other > > real life things currently. > > > > I'll also bring TSO6, etc... > > -- > Bjoern A. Zeeb You have to have visions! > It does not matter how good you are. It matters what good you do! > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
On 22. May 2012, at 17:04 , Jack Vogel wrote: > Oh, that's right, distracted with other projects and I forgot, now we just > need > to have an LRO that works with forwarding eh :) That's a 6 line bainaid commit afterwards, basically returning form the LRO queuing function in case forwarding is turned on for that address family; a proper solution for long term can than be done whenever we feel like it. The above we should have done years ago;) > You ROCK bz :) > > Jack > > > On Tue, May 22, 2012 at 10:01 AM, Bjoern A. Zeeb wrote: > > On 22. May 2012, at 16:50 , Jack Vogel wrote: > > > The LRO code as it stands right now is IPV4 specific, it would be nice to > > extend it, one of > > many improvements that may get done at some point. > > I am about to commit it to HEAD. Bear another few days with me; I know > I am running late but committing new code had less prio than some other > real life things currently. > > I'll also bring TSO6, etc... -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
Oh, that's right, distracted with other projects and I forgot, now we just need to have an LRO that works with forwarding eh :) You ROCK bz :) Jack On Tue, May 22, 2012 at 10:01 AM, Bjoern A. Zeeb wrote: > > On 22. May 2012, at 16:50 , Jack Vogel wrote: > > > The LRO code as it stands right now is IPV4 specific, it would be nice to > > extend it, one of > > many improvements that may get done at some point. > > I am about to commit it to HEAD. Bear another few days with me; I know > I am running late but committing new code had less prio than some other > real life things currently. > > I'll also bring TSO6, etc... > > /bz > > -- > Bjoern A. Zeeb You have to have visions! > It does not matter how good you are. It matters what good you do! > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
On 22. May 2012, at 16:50 , Jack Vogel wrote: > The LRO code as it stands right now is IPV4 specific, it would be nice to > extend it, one of > many improvements that may get done at some point. I am about to commit it to HEAD. Bear another few days with me; I know I am running late but committing new code had less prio than some other real life things currently. I'll also bring TSO6, etc... /bz -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: LRO support for IPv6
The LRO code as it stands right now is IPV4 specific, it would be nice to extend it, one of many improvements that may get done at some point. Jack On Tue, May 22, 2012 at 1:43 AM, Venkat Duvvuru wrote: > Folks, > Could somebody please tell about the base Freebsd version which has LRO > support for IPv6? > I'm using 9.0-RELEASE and I see that tcp_lro_rx is failing. > > Please confirm. > > /Venkat > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
LRO support for IPv6
Folks, Could somebody please tell about the base Freebsd version which has LRO support for IPv6? I'm using 9.0-RELEASE and I see that tcp_lro_rx is failing. Please confirm. /Venkat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 flow id hash calculation
Folks, This question is related to the hash calculation done as part of selecting the transmit queue for IPv6 traffic. I observed that no matter how many queues you use in the driver, the tx traffic is always coming on queue 0. Did anybody else observed this behaviour? and is that how it is in freebsd? Note: IPv4 traffic is coming on all the tx queues. Please clarify. /Venkat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 default-route - gone
On 03/04/2012 18:40, Ewald Jenisch wrote: > Hi, > > After installing a new machine under FreeBSD9 I discovered that the > IPv6-configuration I had in place with FreeBSD8 does no longer work. > > Here's what I've got in /etc/rc.conf: > ipv6_enable="YES" > ipv6_ifconfig_em0="2001:76c:2218:2009::11/64" > ipv6_defaultrouter="2001:76c:2218:2009::1" > > The interface address correctly shows up under "ifconfig" however the > default route doesn't seem to be installed, so I'm basically cut off > the Internet in terms of IPv6. > > Please note that the above config has worked unser FreeBSD8 - in fact > I've got a couple of boxes under FreeBSD8 with this exact same config. > > Has the IPv6-related config changed from FBSD 8 -> FBSD 9? > > Thanks much in advance for any help, > -ewald Hi, Yeah it's changed in 9. Here's what I have, for autoconfig use with a tunnel: ipv6_network_interfaces="re0" ifconfig_re0_ipv6="inet6 accept_rtadv" ip6addrctl_policy="ipv6_prefer" ...and it works For static I'd have: #ipv6_network_interfaces="re0" #ifconfig_re0_ipv6="my_end_of_tunnel_ipv6_ip prefixlen 64" #ipv6_defaultrouter="their_end_of_tunnel_ipv6_ip" #ip6addrctl_policy="ipv6_prefer" but I've not tried it static yet. -- freebsd at growveg dot net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 default-route - gone
Hi, After installing a new machine under FreeBSD9 I discovered that the IPv6-configuration I had in place with FreeBSD8 does no longer work. Here's what I've got in /etc/rc.conf: ipv6_enable="YES" ipv6_ifconfig_em0="2001:76c:2218:2009::11/64" ipv6_defaultrouter="2001:76c:2218:2009::1" The interface address correctly shows up under "ifconfig" however the default route doesn't seem to be installed, so I'm basically cut off the Internet in terms of IPv6. Please note that the above config has worked unser FreeBSD8 - in fact I've got a couple of boxes under FreeBSD8 with this exact same config. Has the IPv6-related config changed from FBSD 8 -> FBSD 9? Thanks much in advance for any help, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 VM
Oh also if you would like to relay smtp mail give me a shout right now it's restricted to the IPv6 64 blog that the machine manages - heck if you want an IPv6 address I could give you one and it SHOULD work anywhere you are connected as long as your IP can deal with IPv6 RB On Jan 27, 2012, at 10:45 AM, Steve Bertrand wrote: > On 2012.01.26 23:12, Robert Boyer wrote: >> just an FYI - that VM that you logged into tonight now has verified access >> via IPv6 from anywhere, is serving up the /64 block to my local devices vi >> route adverts, has route6d running and appears to work locally (resolves >> IPv6 name servers from other local machines via dig) nginx is now listing >> and serving pages via IPv6, and "should" also work have a working IPv6 email >> server (not tested yet). Shouldn't be a big deal bringing up named and dhcp6 >> if you want to do that. > > Thanks Robert! > > Is there any chance that I could get some sudo access to be able to install > things globally, and if necessary, make certain global config changes? > > I'll be happy to set you up a v6 email server if you wish. Nice to see others > interested and knowlegeable about v6. I have about five years experience. I > was the 17th entity in Canada to have a v6 prefix advertised into the global > IPv6 routing table, and the 1132nd globally :) > > Steve
Re: IPv6 VM
IPv6 fully operational - named/bind9 resolving all dns and works fine for IPv6 only hosts…. ipcloud.ws is IPv6 only to the external internet and works fine via www, ssh, smtp mail, etc as long as you are on another IPv6 capable host. Pretty nice. I am glad you brought this up. If you need a database I will stick one on there for you or choose your own. Now moving on to local dhcp serving up IPv6 only stuff - I like how you can delegate dhcp services amongst various dhcpd's in v6 very cool. RB Ps. anyone else that wants to mess around is welcome to grab a shell account just hit me via email or this list… On Jan 26, 2012, at 4:03 PM, Robert Boyer wrote: > I can probably arrange for a tunneled v6 address - should be the same thing > at the end of the day…. how much time/mem you need? > > RB > > On Jan 26, 2012, at 2:10 PM, Steve Bertrand wrote: > >> Hi all! >> >> I've been away for some time, but I'm now getting back into the full swing >> of things. >> >> I'm wondering if there is anyone out there who can let me temporarily borrow >> a CLI-only clean install FBSD virtual machine with a publicly facing IPv4 >> and native IPv6 address. It will be extremely low bandwidth (almost none at >> all) for testing some v6 DNS software and other v6 statistical programs I'm >> writing. >> >> Please contact off list. >> >> Thanks! >> >> Steve >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >
Re: IPv6 VM
On 2012.01.26 16:03, Robert Boyer wrote: I can probably arrange for a tunneled v6 address - should be the same thing at the end of the day…. how much time/mem you need? Thanks Robert, As far as time/mem, I'm not all too sure as it has been some time since I've run anything virtualized, so anything deemed standard, even minimum requirements is perfect. Regarding a v6 tunnel, I have a couple tunnel accounts (both end-user and BGP peering) over at he.net. One of the individual ones could be easily redirected. Cheers, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 VM
I can probably arrange for a tunneled v6 address - should be the same thing at the end of the day…. how much time/mem you need? RB On Jan 26, 2012, at 2:10 PM, Steve Bertrand wrote: > Hi all! > > I've been away for some time, but I'm now getting back into the full swing of > things. > > I'm wondering if there is anyone out there who can let me temporarily borrow > a CLI-only clean install FBSD virtual machine with a publicly facing IPv4 and > native IPv6 address. It will be extremely low bandwidth (almost none at all) > for testing some v6 DNS software and other v6 statistical programs I'm > writing. > > Please contact off list. > > Thanks! > > Steve > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 VM
Hi all! I've been away for some time, but I'm now getting back into the full swing of things. I'm wondering if there is anyone out there who can let me temporarily borrow a CLI-only clean install FBSD virtual machine with a publicly facing IPv4 and native IPv6 address. It will be extremely low bandwidth (almost none at all) for testing some v6 DNS software and other v6 statistical programs I'm writing. Please contact off list. Thanks! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 in FreeBSD 9
On Sun, 15 Jan 2012, the wise Erik Nørgaard wrote: Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable I replaced it with the new lines because according to the manpage ipv6_enable is deprecated. But why shouldn't I use ipv6? Sorry, meant to say, I don't use ipv6 so I can't do much debugging. Aaah, :-), perhaps I should have read better. Or, maybe there was an error with mergemaster? old scripts, new kernel variables? I ran mergemaster, but didn't get any error messages. Afaik all scripts in /etc are new. OK, in the error messages you posted it seems that some script checks or use these variables. Maybe try to run the different networking scripts manually and see where it fails. Thanks for the tip. I'll do some trial and error and dig deeper. -- Paul's Law: You can't fall off the floor.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 in FreeBSD 9
On 15/01/2012 21:41, Marco Beishuizen wrote: On Sun, 15 Jan 2012, the wise Erik Nørgaard wrote: Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable I replaced it with the new lines because according to the manpage ipv6_enable is deprecated. But why shouldn't I use ipv6? Sorry, meant to say, I don't use ipv6 so I can't do much debugging. Or, maybe there was an error with mergemaster? old scripts, new kernel variables? I ran mergemaster, but didn't get any error messages. Afaik all scripts in /etc are new. OK, in the error messages you posted it seems that some script checks or use these variables. Maybe try to run the different networking scripts manually and see where it fails. BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 in FreeBSD 9
On Sun, 15 Jan 2012, the wise Erik Nørgaard wrote: Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable I replaced it with the new lines because according to the manpage ipv6_enable is deprecated. But why shouldn't I use ipv6? Or, maybe there was an error with mergemaster? old scripts, new kernel variables? I ran mergemaster, but didn't get any error messages. Afaik all scripts in /etc are new. Regards, Marco -- Kin, n.: An affliction of the blood.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 in FreeBSD 9
On 14/01/2012 18:07, Marco Beishuizen wrote: Hi, In 8.2 ipv6 was enabled by adding ipv6_enable="YES" in rc.conf, and all worked fine. In FreeBSD 9 that changed to ipv6_activate_all_interfaces="YES". But now there are still some error messages at boot time, and ipv6 doesn't seem to work correctly: ... root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see rc.conf(5). root: /etc/rc: WARNING: $ipv6_enable is not set properly - see rc.conf(5). ... I do not use a static IP adress, but DHCP. Wat do I need to do more to enable ipv6? Don't use ipv6, but reading above: Did you replace ipv6_enable with ipv6_activate_all_interfaces? because the error seems to tell you that you must keep ipv6_enable Or, maybe there was an error with mergemaster? old scripts, new kernel variables? BR, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 in FreeBSD 9
On Sat, 14 Jan 2012, the wise Yuri Pankov wrote: In 8.2 ipv6 was enabled by adding ipv6_enable="YES" in rc.conf, and all worked fine. In FreeBSD 9 that changed to ipv6_activate_all_interfaces="YES". But now there are still some error messages at boot time, and ipv6 doesn't seem to work correctly: ... root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see rc.conf(5). root: /etc/rc: WARNING: $ipv6_enable is not set properly - see rc.conf(5). ... I do not use a static IP adress, but DHCP. Wat do I need to do more to enable ipv6? This works for me: ifconfig_em0_ipv6="inet6 accept_rtadv" ip6addrctl_policy="ipv6_prefer" No other IPv6-related settings done anywhere else. No didn't work. Still the same error messages. Marco -- Kamikazes do it once. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 in FreeBSD 9
On Sat, Jan 14, 2012 at 06:07:01PM +0100, Marco Beishuizen wrote: > Hi, > > In 8.2 ipv6 was enabled by adding ipv6_enable="YES" in rc.conf, and all > worked fine. In FreeBSD 9 that changed to > ipv6_activate_all_interfaces="YES". But now there are still some error > messages at boot time, and ipv6 doesn't seem to work correctly: > > ... > root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see > rc.conf(5). > root: /etc/rc: WARNING: $ipv6_enable is not set > properly - see rc.conf(5). > ... > > I do not use a static IP adress, but DHCP. Wat do I need to do more > to enable ipv6? This works for me: ifconfig_em0_ipv6="inet6 accept_rtadv" ip6addrctl_policy="ipv6_prefer" No other IPv6-related settings done anywhere else. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 in FreeBSD 9
Hi, In 8.2 ipv6 was enabled by adding ipv6_enable="YES" in rc.conf, and all worked fine. In FreeBSD 9 that changed to ipv6_activate_all_interfaces="YES". But now there are still some error messages at boot time, and ipv6 doesn't seem to work correctly: ... root: /etc/rc: WARNING: $ipv6_firewall_enable is not set properly - see rc.conf(5). root: /etc/rc: WARNING: $ipv6_enable is not set properly - see rc.conf(5). ... I do not use a static IP adress, but DHCP. Wat do I need to do more to enable ipv6? Thanks, Marco -- FORTUNE PRESENTS FAMOUS LAST WORDS: #4 Socrates: I DRANK WHAT!?!? Tarzan: Who greased the grape veee Al Capone: There's a violin in my violin case! Pilot, TWA Fl. #343:What's a mountain goat doing 'way up here? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
9.0RC2 IPV6 warnings from ntpd
After installing 9.0RC2 I'm getting the following warnings at boot time: Dec 9 10:31:09 curlew ntpd[1081]: bind() fd 23, family AF_INET6, port 123, scope 3, addr fe80::6ef0:49ff:fe9e:8897, mcast=0 flags=0x11 fails: Can't assign requested address Dec 9 10:31:09 curlew ntpd[1081]: unable to create socket on nfe0 (3) for fe80: :6ef0:49ff:fe9e:8897#123 I'm puzzled by this because I've only configured the system for IPV4 and yet my network interface has been configured for both: nfe0: flags=8843 metric 0 mtu 1500 options=82008 ether 6c:f0:49:9e:88:97 inet 192.168.1.13 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::6ef0:49ff:fe9e:8897%nfe0 prefixlen 64 scopeid 0x3 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active /etc/rc.conf: hostname="curlew.lan" ifconfig_nfe0="inet 192.168.1.13 netmask 255.255.255.0" defaultrouter="192.168.1.138" zfs_enable="YES" moused_enable="YES" keymap="uk.iso" ntpd_enable="YES" ntpd_sync_on_start="YES" sshd_enable="YES" inetd_enable="YES" powerd_enable="YES" /etc/ntp.conf contains just a single line: server ntp.plus.net maxpoll 9 The boot messages appear to be just warnings because ntpd is working fine over IPV4 but I feel that I should try to fix this in case it leads to problems later. I certainly don't need IPV6, neither my router nor my ISP provide the facility but I haven't managed to find any way of disabling it. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 enabled and panic in 7.4-RELEASE
Hello list, I enabled ipv6 in a server running 7.4-RELEASE with amd64 generic kernel, and bge. I issued a static ipv6 address with prefix lenght 120 (according to my network administrator) and ipv6 default route in rc.conf, and issued '/etc/rc.d/network_ipv6 start'. ifconfig bge0: bge0: flags=8843 metric 0 mtu 1500 options=9b ether 00:f5:0b:3d:3b:e4 inet6 fe80::217:a4ff:fe8d:33e8%bge0 prefixlen 64 scopeid 0x1 (ipv4 stuff) inet6 2a02:1823:1002:b1 prefixlen 120 (this is the static address) media: Ethernet autoselect (100baseTX ) status: active I enabled inet6 rules and in /etc/pf.conf like this: pass in on $ext_if inet6 proto tcp from any to $ext_if port http pass out on $ext_if inet6 proto tcp all pass out on $ext_if inet6 proto icmp6 all icmp6-type echoreq keep state pass in on $ext_if inet6 proto icmp6 all icmp6-type echoreq Locally, ipv6 seemed to work OK as I could ping6 localhost and hostname. However, ipv6 connections from outside were still being blocked by pf, so I was trying to solve that issue. At one point, I did a 'ping6 ipv6.google.com', after which the machine dropped the ssh connection. I connected to the console using ILO, only to see it rebooting. It was writing vmcore.0 at that point, which I interrupted using ctr-c, since I was not sure how long it would take. Now I have those files in /var/crash: bounds info.0 minfree vmcore.0 info.0 contains: Dump header from device /dev/da0s1b Architecture: amd64 Architecture Version: 2 Dump Length: 1812742144B (1728 MB) Blocksize: 512 Dumptime: Wed Jun 8 12:56:40 2011 Hostname: server Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.4-RELEASE #0: Fri Feb 18 01:55:22 UTC 2011 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Panic String: page fault Dump Parity: 2017522204 Bounds: 0 Dump Status: good The size of vmcore.0 is 767M. It is probably incomplete. In /var/log/messages I have: Jun 8 12:59:31 server savecore: reboot after panic: page fault Jun 8 12:59:31 server savecore: writing core to vmcore.0 I have not built a kernel locally, so will I be able to read the vmcore.0 using kgdb without local sources? Not sure if I can submit a PR for this either, thus I would like to learn more about this issue at first. I searched the freebsd bugs database, but found nothing really similar. Any help about how to handle this issue would be much appreciated. nick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 spam
On Sat, May 21, 2011 at 9:28 AM, Robert Simmons wrote: I have begun receiving ipv6 spam from this mailing list, and I was > wondering how to determine who the owner of a particular ipv6 address > is. A whois may tell you who the block has been given too (ISP wise) ... that may start you in the right direction For example: I have a valid IPv6 address from my hosting provider (they gets used for IRC on occasion ..) NetRange: 2610:1E8:: - 2610:1E8:::::: CIDR: 2610:1E8::/32 OriginAS: AS14595 NetName:NET-THINKTEL6-1 NetHandle: NET6-2610-1E8-1 Parent: NET6-2610-1 NetType:Direct Allocation RegDate:2007-05-04 Updated:2007-05-04 Ref:http://whois.arin.net/rest/net/NET6-2610-1E8-1 As you can see, a whois of that ip reveals the block provided to my hosts provider, from there you could start asking questions. Spam sent to the list, I tend to ignore, spam sent to me, I investigate and make go away. I'v also run a tracert(6) to find a general geographic region of the spam, if it's origin was reasonably local then I fire e-mails off to those locations as best I can. An interesting story here ... I actually knew one of my spammers, personally, a pseudofriend who always tried to show off to me, he had money and was always buying gadgets that he had no use for or how to use. When I figured it out I almost laughed meself stupid. I then took all my proof to his Mom and it all stopped, all his gadgets mysteriously disappeared from his house and he stopped calling ... coincidentally, all of that mysteriously disappeared junk, magically appeared in my bedroom :D Anywho there are ways, just takes patience and persistence... -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 spam
I have begun receiving ipv6 spam from this mailing list, and I was wondering how to determine who the owner of a particular ipv6 address is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 problem
On 3.2.2011 17:53, Thomas Sandford wrote: On 01/02/2011 07:29, pepe wrote: I have 2001:14b8:10:402::/64 ipv6 from my isp and I cant get it working. Ifconfig should be ok: backup# ifconfig rl0 inet6 rl0: flags=8843 metric 0 mtu 1500 options=8 inet6 2001:14b8:10:402:2::1 prefixlen 64 Looks a bit odd - I would expect to see a link-local address too - eg %ifconfig bge0 inet6 bge0: flags=8843 metric 0 mtu 1500 options=8009b inet6 fe80::20b:cdff:fef2:9a57%bge0 prefixlen 64 scopeid 0x1 inet6 2001:8b0:cae3:1:20b:cdff:fef2:9a57 prefixlen 64 autoconf default gateway is set to 2001:14b8:10:402:1::1. That sounds a slightly odd comment, since in general IPv6 routing is done with auto-discovery. Especially given the fact that the default route quoted lies within the same subnet (2001:14b8:10:402:: prefixlen 64) as the host in question. When I try to traceroute irc server for example I get this: traceroute6: Warning: irc.cc.tut.fi has multiple addresses; using 2001:708:310:4952:4320:5365:7276:6572 I get this message too - because the host irc.cc.tut.fi DOES have multiple addresses: %dig irc.cc.tut.fi ; <<>> DiG 9.6.2-P2 <<>> irc.cc.tut.fi ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24710 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 0 ;; QUESTION SECTION: ;irc.cc.tut.fi. IN ;; ANSWER SECTION: irc.cc.tut.fi. 3134 IN 2001:708:310:4952:4320:5365:7276:6572 irc.cc.tut.fi. 3134 IN 2001:708:310:4952:4320:436c:6965:6e74 ;; AUTHORITY SECTION: cc.tut.fi. 172334 IN NS ns-secondary.funet.fi. cc.tut.fi. 172334 IN NS kaustinen.cc.tut.fi. cc.tut.fi. 172334 IN NS ressu.cc.tut.fi. ;; Query time: 0 msec ;; SERVER: 81.187.228.6#53(81.187.228.6) ;; WHEN: Thu Feb 3 15:34:06 2011 ;; MSG SIZE rcvd: 164 traceroute6 to irc.cc.tut.fi (2001:708:310:4952:4320:5365:7276:6572) from 2001:14b8:10:402:2::1, 64 hops max, 12 byte packets 1 2001:14b8:10:402:2::1 2026.908 ms !A 2999.587 ms !A 3000.423 ms !A From the traceroute6 manpage !A Destination Unreachable - Address Unreachable. It also appears that your first hop address is the same as your source address, which does suggest that routing is more than a little bit screwy. On my system I get: %traceroute6 -n irc.cc.tut.fi traceroute6: Warning: irc.cc.tut.fi has multiple addresses; using 2001:708:310:4952:4320:436c:6965:6e74 traceroute6 to irc.cc.tut.fi (2001:708:310:4952:4320:436c:6965:6e74) from 2001:8b0:cae3:1:20b:cdff:fef2:9a57, 64 hops max, 12 byte packets 1 2001:8b0:cae3:1:21a:a2ff:fe34:e50b 1.349 ms 0.969 ms 1.011 ms 2 2001:8b0:0:53:203:97ff:fe05:8000 129.118 ms 143.449 ms 119.622 ms 3 2001:7f8:4::50e8:1 132.075 ms 119.009 ms 117.983 ms 4 2001:7f8:4::1b1b:1 123.832 ms 114.424 ms 119.675 ms 5 2001:7f8:4::a2b:1 114.905 ms 119.009 ms 118.030 ms 6 2001:948:1:8::3 134.205 ms 143.579 ms 130.875 ms 7 2001:948:1:2::3 145.068 ms 145.049 ms 156.321 ms 8 2001:948:3:2::3 165.258 ms 171.228 ms 156.591 ms 9 2001:708:0:f000:0:60:3060:2 233.114 ms 163.319 ms 158.668 ms 10 2001:708:310::2 67.252 ms 58.513 ms 59.656 ms 11 2001:708:310:4952:4320:436c:6965:6e74 58.906 ms 58.310 ms 58.045 ms (I ran it with -n as I think in this case the raw IPv6 addresses are more informative than the rDNS lookups). So. Could this be problem in my configs or is this because of something wrong at the isp side? It does look as though there is something a little odd with your configs. It's difficult to be more specific because you've given very little information. If things at the router (whether yours or at the isp) are set up correctly then the single line in /etc/rc.conf ipv6_enable="YES" should be sufficient to autoconfigure BOTH ipv6 address and routing using Router Discovery. This is all that I had to do on the machine I generated the above config dumps & traces from. In my case my ISP (AAISP in the UK) have allocated me a /48 2001:8b0:cae3:: Traffic comes to me over a 6to4 tunnel from the ISP terminated on a Cisco router (though I tested it on a FreeBSD host before I got the 6to4 tunnel set up on the router). The LAN side interface of the router has Router Advertisements enabled which means that the above rc.conf line is all that is required for everything to "just work". This one got solved at freebsd-net already with more information about my configs and system... It is problem at isp side instead of my configs... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 problem
On 01/02/2011 07:29, pepe wrote: I have 2001:14b8:10:402::/64 ipv6 from my isp and I cant get it working. Ifconfig should be ok: backup# ifconfig rl0 inet6 rl0: flags=8843 metric 0 mtu 1500 options=8 inet6 2001:14b8:10:402:2::1 prefixlen 64 Looks a bit odd - I would expect to see a link-local address too - eg %ifconfig bge0 inet6 bge0: flags=8843 metric 0 mtu 1500 options=8009b inet6 fe80::20b:cdff:fef2:9a57%bge0 prefixlen 64 scopeid 0x1 inet6 2001:8b0:cae3:1:20b:cdff:fef2:9a57 prefixlen 64 autoconf default gateway is set to 2001:14b8:10:402:1::1. That sounds a slightly odd comment, since in general IPv6 routing is done with auto-discovery. Especially given the fact that the default route quoted lies within the same subnet (2001:14b8:10:402:: prefixlen 64) as the host in question. When I try to traceroute irc server for example I get this: traceroute6: Warning: irc.cc.tut.fi has multiple addresses; using 2001:708:310:4952:4320:5365:7276:6572 I get this message too - because the host irc.cc.tut.fi DOES have multiple addresses: %dig irc.cc.tut.fi ; <<>> DiG 9.6.2-P2 <<>> irc.cc.tut.fi ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24710 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 0 ;; QUESTION SECTION: ;irc.cc.tut.fi. IN ;; ANSWER SECTION: irc.cc.tut.fi. 3134IN 2001:708:310:4952:4320:5365:7276:6572 irc.cc.tut.fi. 3134IN 2001:708:310:4952:4320:436c:6965:6e74 ;; AUTHORITY SECTION: cc.tut.fi. 172334 IN NS ns-secondary.funet.fi. cc.tut.fi. 172334 IN NS kaustinen.cc.tut.fi. cc.tut.fi. 172334 IN NS ressu.cc.tut.fi. ;; Query time: 0 msec ;; SERVER: 81.187.228.6#53(81.187.228.6) ;; WHEN: Thu Feb 3 15:34:06 2011 ;; MSG SIZE rcvd: 164 traceroute6 to irc.cc.tut.fi (2001:708:310:4952:4320:5365:7276:6572) from 2001:14b8:10:402:2::1, 64 hops max, 12 byte packets 1 2001:14b8:10:402:2::1 2026.908 ms !A 2999.587 ms !A 3000.423 ms !A From the traceroute6 manpage !A Destination Unreachable - Address Unreachable. It also appears that your first hop address is the same as your source address, which does suggest that routing is more than a little bit screwy. On my system I get: %traceroute6 -n irc.cc.tut.fi traceroute6: Warning: irc.cc.tut.fi has multiple addresses; using 2001:708:310:4952:4320:436c:6965:6e74 traceroute6 to irc.cc.tut.fi (2001:708:310:4952:4320:436c:6965:6e74) from 2001:8b0:cae3:1:20b:cdff:fef2:9a57, 64 hops max, 12 byte packets 1 2001:8b0:cae3:1:21a:a2ff:fe34:e50b 1.349 ms 0.969 ms 1.011 ms 2 2001:8b0:0:53:203:97ff:fe05:8000 129.118 ms 143.449 ms 119.622 ms 3 2001:7f8:4::50e8:1 132.075 ms 119.009 ms 117.983 ms 4 2001:7f8:4::1b1b:1 123.832 ms 114.424 ms 119.675 ms 5 2001:7f8:4::a2b:1 114.905 ms 119.009 ms 118.030 ms 6 2001:948:1:8::3 134.205 ms 143.579 ms 130.875 ms 7 2001:948:1:2::3 145.068 ms 145.049 ms 156.321 ms 8 2001:948:3:2::3 165.258 ms 171.228 ms 156.591 ms 9 2001:708:0:f000:0:60:3060:2 233.114 ms 163.319 ms 158.668 ms 10 2001:708:310::2 67.252 ms 58.513 ms 59.656 ms 11 2001:708:310:4952:4320:436c:6965:6e74 58.906 ms 58.310 ms 58.045 ms (I ran it with -n as I think in this case the raw IPv6 addresses are more informative than the rDNS lookups). So. Could this be problem in my configs or is this because of something wrong at the isp side? It does look as though there is something a little odd with your configs. It's difficult to be more specific because you've given very little information. If things at the router (whether yours or at the isp) are set up correctly then the single line in /etc/rc.conf ipv6_enable="YES" should be sufficient to autoconfigure BOTH ipv6 address and routing using Router Discovery. This is all that I had to do on the machine I generated the above config dumps & traces from. In my case my ISP (AAISP in the UK) have allocated me a /48 2001:8b0:cae3:: Traffic comes to me over a 6to4 tunnel from the ISP terminated on a Cisco router (though I tested it on a FreeBSD host before I got the 6to4 tunnel set up on the router). The LAN side interface of the router has Router Advertisements enabled which means that the above rc.conf line is all that is required for everything to "just work". -- Thomas Sandford ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 problem
I have 2001:14b8:10:402::/64 ipv6 from my isp and I cant get it working. Ifconfig should be ok: backup# ifconfig rl0 inet6 rl0: flags=8843 metric 0 mtu 1500 options=8 inet6 2001:14b8:10:402:2::1 prefixlen 64 default gateway is set to 2001:14b8:10:402:1::1. When I try to traceroute irc server for example I get this: traceroute6: Warning: irc.cc.tut.fi has multiple addresses; using 2001:708:310:4952:4320:5365:7276:6572 traceroute6 to irc.cc.tut.fi (2001:708:310:4952:4320:5365:7276:6572) from 2001:14b8:10:402:2::1, 64 hops max, 12 byte packets 1 2001:14b8:10:402:2::1 2026.908 ms !A 2999.587 ms !A 3000.423 ms !A So. Could this be problem in my configs or is this because of something wrong at the isp side? -- pepe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 Unkown header extension
L.S., every once in a while I see the following messages filling the logs on my FreeBSD installations: IPFW2: IPV6 - Unknown Extension Header(128), ext_hd=0 I am somewhat curious why this message occurs. Did I configure something wrong, Is there an implementation defect in an existing ipv6 stack that these packets try to abuse or is this part of an OS fingerprinting technique or something? Kind regards, Paul Koene___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 rtadv on FreeBSD 8.1?
Not specifically related but I just worked around an issue with a Dell laptop with the xl0 interface which has problems with 8.1. I was experimenting with a IPv6 setup and used an old PC (big and noisy) with the smallest install of 8.1. It worked fine as the tunnel server and ipv6 gateway (using rtadvd). I have an old laptop which is quieter and smaller and again installed the minimum 8.1 and used the same config (with rl0 changed to xl0). It worked fine for its own ipv6 traffic but another test box failed to get packets routed. After much head scratching I gave up on 8.1 and installed 7.3 ( I have all the FreeBSD Mall subscriptions going back years) and no more problems with xl0. Something changed with 8.1 which xl0 does not like while rl0 or re0 interfaces are happy it seems (on the other box). I haven't tried any debugging, sorry. Just thought I would mention it in case someone else has issues :-) Thanks Neil On 30 Jul 2010, at 18:48, Carl Johnson wrote: I have running versions of 7.3 and 8.0, so I tried experimenting with 8.1 in VirtualBox, but I ran into a couple of problems. I have an 8.0 system that is running a IPv6 tunnel to sixxs.net, and it is running rtadvd to act as the gatway for my network. On the 8.1 system I enabled IPv6 in rc.conf, but it is not picking up the advertised address. I can add it manually, and have put it in rc.local for now, but it seems it should work automatically as my others do. I noticed that the ifconfig output shows a new line that is not in 8.0: nd6 options=3 Is there something that has changed in 8.1 that I have to enable, or is there a problem with 8.1? IPv6 is working to the extent that it did assign a link-local address, and I can use that address as long as I specify the interface. My configuration is the same, and I didn't have to enable anything on the others to get the global address assigned automatically. Thanks for any advice. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org " -- Neil Long, Team Cymru http://www.cymru.com | +1 630 230 5422 | n...@cymru.com
Re: Gnus issue in FreeBSD (was: Re: IPv6 rtadv on FreeBSD 8.1?)
ash...@freebsd.org (Ashish SHUKLA) writes: > Carl Johnson writes: > > [...] > > >> Now if I could just figure out why gnus doesn't work right under emacs >> I could finish migrating from Linux to FreeBSD. > > I use same .gnus in both GNU/Linux and FreeBSD and keep the mailboxen on the > $HOME of both boxen sync-ed with each other, and works great for me. I posted that in another thread and replied later when I discovered the problem. It appears that I had somehow put gnus-agent in offline mode, so it worked once I realized that and put it back online. How do you sync the mailboxes together? That sounds like something that could be useful for my configuration. Actually I am trying to move my old mail from Linux to FreeBSD, but syncing might be an easier way to handle moving it. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Gnus issue in FreeBSD (was: Re: IPv6 rtadv on FreeBSD 8.1?)
Carl Johnson writes: [...] > Now if I could just figure out why gnus doesn't work right under emacs > I could finish migrating from Linux to FreeBSD. I use same .gnus in both GNU/Linux and FreeBSD and keep the mailboxen on the $HOME of both boxen sync-ed with each other, and works great for me. -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ “If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.” (Weinberg's Second Law) pgp4sLdZSMtuM.pgp Description: PGP signature
Re: IPv6 rtadv on FreeBSD 8.1?
Carl Johnson writes: > I have running versions of 7.3 and 8.0, so I tried experimenting with > 8.1 in VirtualBox, but I ran into a couple of problems. I have an 8.0 > system that is running a IPv6 tunnel to sixxs.net, and it is running > rtadvd to act as the gatway for my network. On the 8.1 system I > enabled IPv6 in rc.conf, but it is not picking up the advertised > address. I can add it manually, and have put it in rc.local for now, > but it seems it should work automatically as my others do. I noticed > that the ifconfig output shows a new line that is not in 8.0: > nd6 options=3 > > Is there something that has changed in 8.1 that I have to enable, or > is there a problem with 8.1? IPv6 is working to the extent that it > did assign a link-local address, and I can use that address as long as > I specify the interface. My configuration is the same, and I didn't > have to enable anything on the others to get the global address > assigned automatically. This is a followup to note that it does work when I run it on native hardware instead of under VirtualBox. My version of VirtualBox is an old one (2.1.4) running under Linux, so maybe it has some bugs. I had installed FreeBSD under VirtualBox, but installed to a primary partition specifically so that I could later boot directly into it. The odd thing is that I have a similar FreeBSD 7.3 installation which does work properly under VirtualBox. Now if I could just figure out why gnus doesn't work right under emacs I could finish migrating from Linux to FreeBSD. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 rtadv on FreeBSD 8.1?
Vincent Hoffman writes: > On 30/07/2010 18:48, Carl Johnson wrote: >> I have running versions of 7.3 and 8.0, so I tried experimenting with >> 8.1 in VirtualBox, but I ran into a couple of problems. I have an 8.0 >> system that is running a IPv6 tunnel to sixxs.net, and it is running >> rtadvd to act as the gatway for my network. On the 8.1 system I >> enabled IPv6 in rc.conf, but it is not picking up the advertised >> address. I can add it manually, and have put it in rc.local for now, >> but it seems it should work automatically as my others do. I noticed >> that the ifconfig output shows a new line that is not in 8.0: >> nd6 options=3 >> >> Is there something that has changed in 8.1 that I have to enable, or >> is there a problem with 8.1? IPv6 is working to the extent that it >> did assign a link-local address, and I can use that address as long as >> I specify the interface. My configuration is the same, and I didn't >> have to enable anything on the others to get the global address >> assigned automatically. >> >> Thanks for any advice. >> > I dont knw if its expected or not but try running > sysctl net.inet6.ip6.accept_rtadv=1 > > (to make it persistent echo "net.inet6.ip6.accept_rtadv=1" >> > /etc/sysctl.conf ) I had already checked that and it is enabled by default, but thanks for the suggestion anyways. It also turns out that I was wrong about it working with manual configuration. I forgot that the automatic configuration sets up the external routing, and I haven't figured out how to do that manually. So it works for my internal network, but nowhere else. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 rtadv on FreeBSD 8.1?
On 30/07/2010 18:48, Carl Johnson wrote: > I have running versions of 7.3 and 8.0, so I tried experimenting with > 8.1 in VirtualBox, but I ran into a couple of problems. I have an 8.0 > system that is running a IPv6 tunnel to sixxs.net, and it is running > rtadvd to act as the gatway for my network. On the 8.1 system I > enabled IPv6 in rc.conf, but it is not picking up the advertised > address. I can add it manually, and have put it in rc.local for now, > but it seems it should work automatically as my others do. I noticed > that the ifconfig output shows a new line that is not in 8.0: > nd6 options=3 > > Is there something that has changed in 8.1 that I have to enable, or > is there a problem with 8.1? IPv6 is working to the extent that it > did assign a link-local address, and I can use that address as long as > I specify the interface. My configuration is the same, and I didn't > have to enable anything on the others to get the global address > assigned automatically. > > Thanks for any advice. > I dont knw if its expected or not but try running sysctl net.inet6.ip6.accept_rtadv=1 (to make it persistent echo "net.inet6.ip6.accept_rtadv=1" >> /etc/sysctl.conf ) Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 rtadv on FreeBSD 8.1?
I have running versions of 7.3 and 8.0, so I tried experimenting with 8.1 in VirtualBox, but I ran into a couple of problems. I have an 8.0 system that is running a IPv6 tunnel to sixxs.net, and it is running rtadvd to act as the gatway for my network. On the 8.1 system I enabled IPv6 in rc.conf, but it is not picking up the advertised address. I can add it manually, and have put it in rc.local for now, but it seems it should work automatically as my others do. I noticed that the ifconfig output shows a new line that is not in 8.0: nd6 options=3 Is there something that has changed in 8.1 that I have to enable, or is there a problem with 8.1? IPv6 is working to the extent that it did assign a link-local address, and I can use that address as long as I specify the interface. My configuration is the same, and I didn't have to enable anything on the others to get the global address assigned automatically. Thanks for any advice. -- Carl Johnsonca...@peak.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 network traffic monitoring -- searching a working probe software
Hi, currently I'm monitoring the network traffic with ng_netflow and nfdump/nfsen is used to collect, display and analyze the network traffic. I'm reviewing the tools to monitor ipv6. ng_netflow doesn't support ipv6 (is there a schedule to implement the needed protocol version 9?). I tried it with softflowd, seeing there is a constant offset of 4294959.134 in the duration and the nfsen filtering (in/out if x) doesn't work at all. YAF flows aren't recognized by nfsen. Any suggestions how to monitor ipv6 traffic? Thanks Reinhard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 changes in src/UPDATING
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/03/2010 09:17:30, Robert Huff wrote: > > I am updating a system: > > FreeBSD 9.0-CURRENT #3: Tue Sep 15 18:49:58 EDT 2009 amd64 > > and failing to understand the (practical) consequences of > UPDATING entries 20090926 and 20091202. The system runs ipv6, but > external connectivity is though a v6-over-v4 tunnel (net/gateway6). > rc.conf currently has: > > huff@>>grep v6 /etc/rc.conf > ipv6_gateway_enable="YES" # Set to YES if this host will be a gateway. > ipv6_firewall_enable="YES" # Set to YES to enable IPv6 firewall > ipv6_firewall_type="UNKNOWN"# see /etc/rc.firewall6 > ipv6_firewall_script="/etc/ipfw.v6.set" # Which script to run to set up the > IPv6 firewall > ipv6_firewall_flags="" # see /etc/rc.firewall6 > gateway6_enable="YES" > >Um ... er ... ah ... what needs to change? None of the above, probably. As you're using a custom firewall initialisation script, you don't need to worry about the variables for controlling the various pre-canned scripts. The text in UPDATING seems fairly clear to me: for the 20090926 update, various rc.conf variables prefixed by ipv6 are deprecated in favour of similar variables *suffixed* by ipv6 -- this is a simple matter of editing to sort out. There is also a new overall control knob for turning on or off IPv6 capability entirely. The new thing here is that it allows you to make that change per-interface rather than for the whole machine. Given you want IPv6 capability on all interfaces, just use ipv6_prefer="YES" You need to look at the ifconfig_ifX* or ipv6_addrs_ifX variables. Given that you've said your machine is a router for ipv6, you can't use rtsol(8), so you should be manually configuring addresses on your interfaces. You may not need to make any changes there: even so, shouldn't be too hard to debug. For the 20091202 update, again it is pretty much a replacement of variables with an ipv6 prefix, to ones with an ipv6 suffix. All the variables mentioned just detail the local IP addresses and networks, and let you select which firewall script you want to use. As it says, the ipv6 configuration exactly parallels the ipv4 configuration now. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkurNroACgkQ8Mjk52CukIwfGwCfWJ6ZGlerqj3yMNrNaqY/SOyp LIoAn0+dT9Bp3YKnrP6dz9kGV2FZKXUg =kAQt -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 changes in src/UPDATING
I am updating a system: FreeBSD 9.0-CURRENT #3: Tue Sep 15 18:49:58 EDT 2009 amd64 and failing to understand the (practical) consequences of UPDATING entries 20090926 and 20091202. The system runs ipv6, but external connectivity is though a v6-over-v4 tunnel (net/gateway6). rc.conf currently has: huff@>>grep v6 /etc/rc.conf ipv6_gateway_enable="YES" # Set to YES if this host will be a gateway. ipv6_firewall_enable="YES" # Set to YES to enable IPv6 firewall ipv6_firewall_type="UNKNOWN"# see /etc/rc.firewall6 ipv6_firewall_script="/etc/ipfw.v6.set" # Which script to run to set up the IPv6 firewall ipv6_firewall_flags="" # see /etc/rc.firewall6 gateway6_enable="YES" Um ... er ... ah ... what needs to change? Respectfully, Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6: rtsol must be run a second time after boot to pick up default route
On Wed, 3 Feb 2010, Brian Conway wrote: I recently set up an HE.net tunnel using the following guides: http://www.freebsd.org/doc/handbook/network-ipv6.html http://www.freebsddiary.org/ipv6.php FreeBSD 7.2-p5 is used for the router and the host, and it works beautifully, except that the host will only pick up the IPv6 prefix on boot and set its IP accordingly (local network functions), but will NOT set the default route unless I wait up to 10 minutes for the advertisement, or manually run rtsol. The same problem happens with OS X 10.6.2, but not with Win7 (and Linux 2.6 remains untested at this time). The host has no firewall running currently, and there's no firewalling between the router and the host. Running rtsol with debugging doesn't show anything out of the ordinary, either during boot or after. Rtadvd is running on the router and my setup is identical to the guides other than device name: $ cat /etc/rtadvd.conf vr1:\ :addrs#1:addr="2001:470::::":prefixlen#64:tc=ether: Any suggestions? I've tried a few variations of rtadvd.conf without any changes in behavior. I'm inclined to think it's router-related, given the issue on multiple OSes, but I suppose it could go either way. I'd much prefer not to add in extra calls of rtsol in /etc/rc.local. Thanks. Brian Conway A few more (unusual) details as follow-up: - The missing route doesn't happen on Win7 or Linux 2.6 (Debian 5.0/Lenny) - The missing route still happens on both OS X 10.6.2 and FreeBSD 7.2-p5 - This ONLY happens after a warm reboot. Neither FreeBSD nor OS X have the issue with a cold boot. The boot-up's rtsol picks up the default route immediately. Weird. Brian Conway ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6: rtsol must be run a second time after boot to pick up default route
I recently set up an HE.net tunnel using the following guides: http://www.freebsd.org/doc/handbook/network-ipv6.html http://www.freebsddiary.org/ipv6.php FreeBSD 7.2-p5 is used for the router and the host, and it works beautifully, except that the host will only pick up the IPv6 prefix on boot and set its IP accordingly (local network functions), but will NOT set the default route unless I wait up to 10 minutes for the advertisement, or manually run rtsol. The same problem happens with OS X 10.6.2, but not with Win7 (and Linux 2.6 remains untested at this time). The host has no firewall running currently, and there's no firewalling between the router and the host. Running rtsol with debugging doesn't show anything out of the ordinary, either during boot or after. Rtadvd is running on the router and my setup is identical to the guides other than device name: $ cat /etc/rtadvd.conf vr1:\ :addrs#1:addr="2001:470::::":prefixlen#64:tc=ether: Any suggestions? I've tried a few variations of rtadvd.conf without any changes in behavior. I'm inclined to think it's router-related, given the issue on multiple OSes, but I suppose it could go either way. I'd much prefer not to add in extra calls of rtsol in /etc/rc.local. Thanks. Brian Conway ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 static route.
On Jan 25, 2010, at 6:59 PM, Brian A. Seklecki (CFI NOC) wrote: > On 1/25/2010 12:15 PM, Peter Ankerstål wrote: >> How do I set a static ipv6 route in rc.conf? >> >> This command works: route add -inet6 -net 2003:16c8:dc1e:2:: -prefixlen 64 >> 2003:16c8:dc1e::2 >> >> and I use this in rc.conf: >> ipv6_static_routes="2003:16c8:dc1e:2:: -prefixlen 64 2003:16c8:dc1e::2" >> > > Do it like IPv4 static routes with an itemized/serialized list: > > ipv6_static_routes="pitbpa0_0 pitbpa0_1 faith_0 faith_1" > ipv6_route_pitbpa0_0="2607:f000:0010:0100::/56 2607:f000:10::4000" > ipv6_route_pitbpa0_1="2607:f000:0010:0200::/56 2607:f000:10::4000" > ipv6_route_faith_0="2607:f000:10:0::: -prefixlen 96 ::1" > ipv6_route_faith_1="2607:f000:10:0::: -prefixlen 96 -ifp faith0" > > Keep the faith, yea? > > ~BAS > Thanks, I just figured it out too! -- Peter Ankerstål pe...@pean.org http://www.pean.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ipv6 static route.
On 1/25/2010 12:15 PM, Peter Ankerstål wrote: How do I set a static ipv6 route in rc.conf? This command works: route add -inet6 -net 2003:16c8:dc1e:2:: -prefixlen 64 2003:16c8:dc1e::2 and I use this in rc.conf: ipv6_static_routes="2003:16c8:dc1e:2:: -prefixlen 64 2003:16c8:dc1e::2" Do it like IPv4 static routes with an itemized/serialized list: ipv6_static_routes="pitbpa0_0 pitbpa0_1 faith_0 faith_1" ipv6_route_pitbpa0_0="2607:f000:0010:0100::/56 2607:f000:10::4000" ipv6_route_pitbpa0_1="2607:f000:0010:0200::/56 2607:f000:10::4000" ipv6_route_faith_0="2607:f000:10:0::: -prefixlen 96 ::1" ipv6_route_faith_1="2607:f000:10:0::: -prefixlen 96 -ifp faith0" Keep the faith, yea? ~BAS but it does not set the correct routes. -- Peter Ankerstål pe...@pean.org http://www.pean.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ipv6 static route.
How do I set a static ipv6 route in rc.conf? This command works: route add -inet6 -net 2003:16c8:dc1e:2:: -prefixlen 64 2003:16c8:dc1e::2 and I use this in rc.conf: ipv6_static_routes="2003:16c8:dc1e:2:: -prefixlen 64 2003:16c8:dc1e::2" but it does not set the correct routes. -- Peter Ankerstål pe...@pean.org http://www.pean.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
On Sat, Jan 09, 2010 at 10:56:31AM +, Matthew Seaman wrote:
> Gary Kline wrote:
>
>
> >This caught my interest this morning so I set up a commented-out trial in
> >/etc/rc.d for my ipv6 entry; the one I had in my database /etc/namedb/*
> >files
> >blew my connection sky-high recently.
> >
> >Does this seem plausible:
> >
> >
> >#
> >## ipv6 config
> >#
> >
> ># ipv6_enable="YES"
> ># ipv6_defaultrouter="2002:d1b4:d5d2::"
> ># ipv6_default_interface="em0"
> ># ipv6_gateway_enable="YES"
> >
> >given that my Adress record is 209.180.213.210 ?
> >
> >tia, gents,
>
> So you're using 6to4 tunnelling as described in stf(4)? That's a quite
> different setup to what has been discussed previously in this thread.
> I think 6to4 is, if not deprecated, certainly not the normal way of getting
> IPv6 connectivity nowadays. Generally you'ld get an address space
> allocation
> from your ISP, or failing that, a tunnel broker like Hurricane Electric[*].
>
> Anyhow, as stf(4) says, you need to encode your IPv4 address as hex in the
> 6to4 address -- that looks correct:
>
> % perl -e 'map { printf "%x\n", $_ } split( /\./, shift );' 209.180.213.210
> d1
> b4
> d5
> d2
>
> However 2002:d1b4:d5d2:: is *your* network address, and having it as the
> default router sounds wrong to me. You need to assign addresses from that
> range to your hosts -- which you can do automatically by enabling rtadvd(8)
> on your gateway machine and rtsold(8) on your clients. Also, to use 6to4
> you need to create a 'stf0' interface and make that the
> ipv6_default_interface.
Errp! Matthew, you lost me entirely. I *do* want to use IPv6
eventually. I have it sent up, latenly, in my mail and DNS files.
I do understand the need to go to v6 in a few years, but it is
probably going to take me that long to get mi mind around the
workings of the whole set of issues. [[I'm learning new+exciting
things about pfSEnse and networking-in-detail while getting X11
running on my new server]] Are there any IPv6-for-Dummies
around? The man pages are things you read for reference; or at
least that's been my experience!
>
> This is all independent of setting up IPv6 related items in your DNS. Get
> the IPv6 connectivity working first -- use ping6 and traceroute6 with IPv6
> numbers to confirm connectivity, and then worry about DNS settings.
>
I'll google around for some insights of things-v6; but you may know
what's best.
thanks,
gary
> Cheers,
>
> Matthew
>
> [*] Which is pretty crazy given that the prediction is IPv4 space is
> going to run out around 2012[+]. All of the major ISPs and NSPs really
> should be providing IPv6 natively by now.
>
> [+] Potential for another IT-feeding-frenzy-panic scenario like the run
> up to Y2K. Make sure IPv6 is on your CV...
>
> --
> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
> Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
> Kent, CT11 9PW
>
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
> I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my > FreeBSD 7.2-RELEASE-p6 > It`s a particular issue on the ipv6_defaultrouter config, it jost does not > work... > Upon network and routing restart ipv6 is enabled the gif interface are given > ip's and everything but the defaultrouter does not. > Researching a bit i found some say that gif1 sould work and tried both > ipv6_defaultrouter="-interface gif1" > and > ipv6_defaultrouter="2001:0470:1f0a:d40::1" > > but no joy... > here is the basic comand line config from tunnelbroker.net > http://pastebin.ca/1736599 > > > here's the rc.conf > defaultrouter="86.122.121.129" > gateway_enable="YES" > hostname="pgn.ro" > ifconfig_nfe0="inet ." > [...] > ipv6_enable="YES" > ipv6_network_interfaces="lo0 gif1" > ipv6_gateway_enable="YES" > gif_interfaces="gif1" > gifconfig_gif1="86.122.121.171 216.66.80.30" > ipv6_ifconfig_gif1="2001:0470:1f0a:d40::2/64" > ipv6_defaultrouter="-interface gif1" > [...] > > > after that i do a quick network restart > http://pastebin.ca/1736601 > > as ipv6 does not work i use route to add the gateaway : > http://pastebin.ca/1736604 Hi Bogdan, This is what I use on FreeBSD 7.2 i386 with HE tunnel: rc.conf: # # IPv6 # ipv6_enable="YES" ipv6_gateway_enable="YES" cloned_interfaces="gif0" ipv6_network_interfaces="auto" ipv6_ifconfig_rl1="2001:470:f8a3:25a::1 prefixlen 64" ipv6_ifconfig_rl2="2001:470:19:25a:3::1 prefixlen 64" ipv6_defaultrouter="2001:470:18:25a::1" ifconfig_gif0="tunnel 219.95.208.53 216.218.221.6 up" ipv6_ifconfig_gif0="2001:470:18:25a::2 2001:470:18:25a::1 prefixlen 128" rtadvd_enable="YES" rtadvd_interfaces="rl1 rl2" -Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Gary Kline wrote:
This caught my interest this morning so I set up a commented-out trial in
/etc/rc.d for my ipv6 entry; the one I had in my database /etc/namedb/* files
blew my connection sky-high recently.
Does this seem plausible:
#
## ipv6 config
#
# ipv6_enable="YES"
# ipv6_defaultrouter="2002:d1b4:d5d2::"
# ipv6_default_interface="em0"
# ipv6_gateway_enable="YES"
given that my Adress record is 209.180.213.210 ?
tia, gents,
So you're using 6to4 tunnelling as described in stf(4)? That's a quite
different setup to what has been discussed previously in this thread.
I think 6to4 is, if not deprecated, certainly not the normal way of getting
IPv6 connectivity nowadays. Generally you'ld get an address space allocation
from your ISP, or failing that, a tunnel broker like Hurricane Electric[*].
Anyhow, as stf(4) says, you need to encode your IPv4 address as hex in the
6to4 address -- that looks correct:
% perl -e 'map { printf "%x\n", $_ } split( /\./, shift );' 209.180.213.210
d1
b4
d5
d2
However 2002:d1b4:d5d2:: is *your* network address, and having it as the
default router sounds wrong to me. You need to assign addresses from that
range to your hosts -- which you can do automatically by enabling rtadvd(8)
on your gateway machine and rtsold(8) on your clients. Also, to use 6to4
you need to create a 'stf0' interface and make that the ipv6_default_interface.
This is all independent of setting up IPv6 related items in your DNS. Get
the IPv6 connectivity working first -- use ping6 and traceroute6 with IPv6
numbers to confirm connectivity, and then worry about DNS settings.
Cheers,
Matthew
[*] Which is pretty crazy given that the prediction is IPv4 space is
going to run out around 2012[+]. All of the major ISPs and NSPs really
should be providing IPv6 natively by now.
[+] Potential for another IT-feeding-frenzy-panic scenario like the run
up to Y2K. Make sure IPv6 is on your CV...
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: FreeBSD ipv6 rc.conf settings issue
On Thu, Jan 07, 2010 at 12:07:18PM -0500, Steve Bertrand wrote: > Matthew Seaman wrote: > > Steve Bertrand wrote: > > > >> Hmmm. This config does not work: > >> > >> ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" > >> ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" > >> ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" > >> ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" > > > > Yep. Try it like this: > > > > ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" > > ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" > > ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" > > ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" > > The above works. > > > or, even better, like this: > > > > ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" > > ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" > > Unfortunately, that one does not. I do not get any IPv6 addresses > configured. > > I didn't re-try my original configuration, but I will at another time. > > Both of your recommendations failed until I entered ipv6_enable="YES" in > /etc/rc.conf. I did not have this line prior, yet the addresses were > successfully applied, just no default gateway. > > Either way, thanks much :) > > I will try out your second recommendation again in the future. For now, > problem resolved. > > Cheers! > > Steve This caught my interest this morning so I set up a commented-out trial in /etc/rc.d for my ipv6 entry; the one I had in my database /etc/namedb/* files blew my connection sky-high recently. Does this seem plausible: # ## ipv6 config # # ipv6_enable="YES" # ipv6_defaultrouter="2002:d1b4:d5d2::" # ipv6_default_interface="em0" # ipv6_gateway_enable="YES" given that my Adress record is 209.180.213.210 ? tia, gents, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.79a release of Jottings: http://jottings.thought.org/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Some point out rc.local as a fix, i find it ok to but it has some ups'n'downs indeed in a reboot situation rc.local having the route add command would be ok but in a short network restart it wouldn't count (as i particularly value my uptime)... the ipv6 defaultroute it's not a big issue for me, as i do not depend on it so much, but i find it somewhat important to FreeBSD ... dunno i like to know that a distro is stable in any case (not that i'm complaining FreeBSD) reference: http://www.tunnelbroker.net/forums/index.php?topic=734.0 2010/1/7 Steve Bertrand > Bogdan Webb wrote: > > I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my > > FreeBSD 7.2-RELEASE-p6 > > It`s a particular issue on the ipv6_defaultrouter config, it jost does > not > > work... > > Upon network and routing restart ipv6 is enabled the gif interface are > given > > ip's and everything but the defaultrouter does not. > > Researching a bit i found some say that gif1 sould work and tried both > > ipv6_defaultrouter="-interface gif1" > > and > > ipv6_defaultrouter="2001:0470:1f0a:d40::1" > > This issue is not limited to gif interfaces... > > I've had this exact same problem on ALL of my FreeBSD hosts for, well, > since ever. > > No matter what I've tried, if a box reboots, I must manually enter in > the default IPv6 router. > > Even on IPv6-only hosts, the default gateway does not take upon reboot. > > I'm up for figuring this issue out today, if nobody else has a solution > for you. > > Let me know. If you're interested, I'll fire up a couple of hosts that > we can use and just continuously reboot if necessary :) > > Steve > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Matthew Seaman wrote: > Steve Bertrand wrote: > >> Hmmm. This config does not work: >> >> ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" >> ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" >> ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" >> ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" > > Yep. Try it like this: > > ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" > ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" > ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" > ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" The above works. > or, even better, like this: > > ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" > ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" Unfortunately, that one does not. I do not get any IPv6 addresses configured. I didn't re-try my original configuration, but I will at another time. Both of your recommendations failed until I entered ipv6_enable="YES" in /etc/rc.conf. I did not have this line prior, yet the addresses were successfully applied, just no default gateway. Either way, thanks much :) I will try out your second recommendation again in the future. For now, problem resolved. Cheers! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Matthew Seaman wrote: > Steve Bertrand wrote: > >> Hmmm. This config does not work: >> >> ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" >> ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" >> ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" >> ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" > > Yep. Try it like this: > > ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" > ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" > ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" > ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" > > or, even better, like this: > > ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" > ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" > > You can make the 2nd address in each case a /32 or /128 if you want, > but the requirement for having 2nd and subsequent addresses from a > netblock have a different netmask than the initial address on that NIC > has gone away. I thought I read that some time ago... This particular box is my MTA that I use for all of my personal email, so I'll get on the console, input the new settings reboot and let you know how it wor... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Steve Bertrand wrote: Hmmm. This config does not work: ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" Yep. Try it like this: ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" ipv6_ifconfig_re0="2607:f118::b6 prefixlen 64" ipv6_ifconfig_re0_alias0="2607:f118::b7 prefixlen 64" or, even better, like this: ipv4_addrs_re0="208.70.104.210/26 208.70.104.211/26" ipv6_addrs_re0="2607:f118::b6/64 2607:f118::b7/64" You can make the 2nd address in each case a /32 or /128 if you want, but the requirement for having 2nd and subsequent addresses from a netblock have a different netmask than the initial address on that NIC has gone away. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD ipv6 rc.conf settings issue
Matthew Seaman wrote: > Steve Bertrand wrote: > Funny. My IPv6 config works like a charm, on both 7.2-STABLE and > 8.0-STABLE. Related config settings look like this: > > gif_interfaces="gif0" > gifconfig_gif0="81.187.76.162 81.187.81.6" > > ipv6_ifconfig_gif0="2001:08b0:0151:0001::1/64" > ipv6_prefix_de0="2001:08b0:0151:0001" > > ipv6_enable="YES" > ipv6_defaultrouter="-interface gif0" > ipv6_default_interface="gif0" > ipv6_gateway_enable="YES" > > rtadvd_enable="YES" > rtadvd_interfaces="de0" > > This causes my machine to autoconfigure an IPv6 address on the ethernet > i/f, plus provide rtadvd service to anything else wanting IPv6 connectivity > on my home LAN. IPv6 traffic from the home LAN is routed via the tunnel to > the IPv6 tunnel handler provided by my ISP, but the only reason I need > to do > that is because IPv6 aware consumer broadband routers are kind of hard to > obtain. Hmmm. This config does not work: ifconfig_re0="inet 208.70.104.210 netmask 255.255.255.192" ifconfig_re0_alias0="inet 208.70.104.211 netmask 255.255.255.255" ifconfig_re0_alias1="inet6 2607:f118::b6 prefixlen 64" ifconfig_re0_alias2="inet6 2607:f118::b7 prefixlen 64" defaultrouter="208.70.104.193" ipv6_defaultrouter="2607:f118::1" I've got native v6. The above particular box is one of only a couple that have more than a single IP per protocol. The rest are generic, one v4 and one v6 address. Admittedly, I haven't spent much time at all on the issue, as my solution is simply to not let the boxes go down :) % uptime 10:52AM up 727 days, 3:11, 6 users, load averages: 0.19, 0.19, 0.24 %uptime 10:54AM up 549 days, 8:38, 1 user, load averages: 0.12, 0.16, 0.26 ...seriously, all of my other FreeBSD boxes receive proper updates etc, and the only time they are rebooted is when someone is at the console (or right nearby) and can manually enter in the default route. My FreeBSD routers running Quagga don't have this issue, presumably because they're in the DFZ, and acquire all routing info dynamically. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD ipv6 rc.conf settings issue
Steve Bertrand wrote: Bogdan Webb wrote: I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my FreeBSD 7.2-RELEASE-p6 It`s a particular issue on the ipv6_defaultrouter config, it jost does not work... Upon network and routing restart ipv6 is enabled the gif interface are given ip's and everything but the defaultrouter does not. Researching a bit i found some say that gif1 sould work and tried both ipv6_defaultrouter="-interface gif1" and ipv6_defaultrouter="2001:0470:1f0a:d40::1" This issue is not limited to gif interfaces... I've had this exact same problem on ALL of my FreeBSD hosts for, well, since ever. No matter what I've tried, if a box reboots, I must manually enter in the default IPv6 router. Even on IPv6-only hosts, the default gateway does not take upon reboot. I'm up for figuring this issue out today, if nobody else has a solution for you. Let me know. If you're interested, I'll fire up a couple of hosts that we can use and just continuously reboot if necessary :) Funny. My IPv6 config works like a charm, on both 7.2-STABLE and 8.0-STABLE. Related config settings look like this: gif_interfaces="gif0" gifconfig_gif0="81.187.76.162 81.187.81.6" ipv6_ifconfig_gif0="2001:08b0:0151:0001::1/64" ipv6_prefix_de0="2001:08b0:0151:0001" ipv6_enable="YES" ipv6_defaultrouter="-interface gif0" ipv6_default_interface="gif0" ipv6_gateway_enable="YES" rtadvd_enable="YES" rtadvd_interfaces="de0" This causes my machine to autoconfigure an IPv6 address on the ethernet i/f, plus provide rtadvd service to anything else wanting IPv6 connectivity on my home LAN. IPv6 traffic from the home LAN is routed via the tunnel to the IPv6 tunnel handler provided by my ISP, but the only reason I need to do that is because IPv6 aware consumer broadband routers are kind of hard to obtain. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: FreeBSD ipv6 rc.conf settings issue
Bogdan Webb wrote: > I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my > FreeBSD 7.2-RELEASE-p6 > It`s a particular issue on the ipv6_defaultrouter config, it jost does not > work... > Upon network and routing restart ipv6 is enabled the gif interface are given > ip's and everything but the defaultrouter does not. > Researching a bit i found some say that gif1 sould work and tried both > ipv6_defaultrouter="-interface gif1" > and > ipv6_defaultrouter="2001:0470:1f0a:d40::1" This issue is not limited to gif interfaces... I've had this exact same problem on ALL of my FreeBSD hosts for, well, since ever. No matter what I've tried, if a box reboots, I must manually enter in the default IPv6 router. Even on IPv6-only hosts, the default gateway does not take upon reboot. I'm up for figuring this issue out today, if nobody else has a solution for you. Let me know. If you're interested, I'll fire up a couple of hosts that we can use and just continuously reboot if necessary :) Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD ipv6 rc.conf settings issue
I'm having problems with the /etc/rc.conf setup of a ipv6 tunnel on my FreeBSD 7.2-RELEASE-p6 It`s a particular issue on the ipv6_defaultrouter config, it jost does not work... Upon network and routing restart ipv6 is enabled the gif interface are given ip's and everything but the defaultrouter does not. Researching a bit i found some say that gif1 sould work and tried both ipv6_defaultrouter="-interface gif1" and ipv6_defaultrouter="2001:0470:1f0a:d40::1" but no joy... here is the basic comand line config from tunnelbroker.net http://pastebin.ca/1736599 here's the rc.conf defaultrouter="86.122.121.129" gateway_enable="YES" hostname="pgn.ro" ifconfig_nfe0="inet ." [...] ipv6_enable="YES" ipv6_network_interfaces="lo0 gif1" ipv6_gateway_enable="YES" gif_interfaces="gif1" gifconfig_gif1="86.122.121.171 216.66.80.30" ipv6_ifconfig_gif1="2001:0470:1f0a:d40::2/64" ipv6_defaultrouter="-interface gif1" [...] after that i do a quick network restart http://pastebin.ca/1736601 as ipv6 does not work i use route to add the gateaway : http://pastebin.ca/1736604 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
bridge "filters" ipv6
Hi all, I have 7.2-RELEASE and a bridge between ath0 and sis0 everything works fine except ipv6 including router advertisements. There is no filtering, just a L2 bridge without any address. rtadv comes from lan/sis. What could be missing? bridge0: flags=8843 metric 0 mtu 1500 ether 0a:03:b2:xx:fe:xx id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: sis0 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 20 member: ath0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 370370 ath0: flags=8943 metric 0 mtu 1500 ether 00:80:48:xx:cd:xx inet6 fe80::280:48xx:fexx:%ath0 prefixlen 64 scopeid 0x1 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated ssid x channel 11 (2462 Mhz 11g) bssid 00:80:48:xx:cd:xx authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 2 TKIP 2:128-bit txpower 22 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 pureg protmode RTSCTS wme burst dtimperiod 1 sis0: flags=8943 metric 0 mtu 1500 options=8 ether 00:0d:b9:xx:52:xx inet6 fe80::20d:b9ff:fe03:52fc%sis0 prefixlen 64 scopeid 0x2 inet 172.23.0.1 netmask 0xff00 broadcast 172.20.0.255 media: Ethernet autoselect (100baseTX ) status: active ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6-only host and portupgrade
$witch writes: > have done a "best effort" to avoid useless question, am posting after > various faq-research and tests. > > having an IPv6-ONLY (FreeBSD 7.0) host that needs to perform a "portsnap > fetch" there is NO LIST of portsnap-IPv6-capable servers. > > maybe they don't exists or i am "too blind" to find them; is there anybody > that can post hostnames or links to souch kind of servers? > > obviously i can "workaround" using an IPv4-&-IPv6 intermediate-host, > but the goal is a "pure" IPv6 FreeBSD farm. You could ask Colin Percival... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6-only host and portupgrade
Hi, have done a "best effort" to avoid useless question, am posting after various faq-research and tests. having an IPv6-ONLY (FreeBSD 7.0) host that needs to perform a "portsnap fetch" there is NO LIST of portsnap-IPv6-capable servers. maybe they don't exists or i am "too blind" to find them; is there anybody that can post hostnames or links to souch kind of servers? obviously i can "workaround" using an IPv4-&-IPv6 intermediate-host, but the goal is a "pure" IPv6 FreeBSD farm. regards Alessandro ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Possible bug with IPv6 ICMPv6 handling
On 21 August 2009, at 11:33, David Horn wrote: On Fri, Aug 21, 2009 at 1:55 AM, Doug Hardie wrote: I have found what to me seems like a bug with ICMPv6 handling in IPv6. However, before submitting a PR I wanted to check to be sure that its not a misunderstanding on my part. The network setup. A host (A) connected to a router (B) connected to another host (C) on a separate network. When all are up and running, A can ping6 to C and gets a response. If you power off C and then do the ping again, tpcdump on A shows an ICMPv6 destination unreachable datagram received from B. However ping6 does not report that back to the user. A ktrace of ping6 shows that it does not receive the ICMPv6 response. Its my understanding that it should and the ping6 code seems to imply that also. Is this a bug? ___ What version of FreeBSD are you using ? 7.2 and 7.0. Did you try the -v parameter to ping6 to display non-echo responses ? (man ping6) No - didn't notice that in either the ping or ping6 man pages before. In a similar test I ran, I was able to get the icmp6 host unreachable message from ping6 -v on my FreeBSD 7.2 box. (I pinged a non-existent address/machine off an upstream router) uname -a FreeBSD dhorn-bsd 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 dh...@dhorn-bsd:~> ping6 -v 2001:470:7:584::3 PING6(56=40+8+8 bytes) 2001:470:8:584:20e:cff:: --> 2001:470:7:584::3 64 bytes from 2001:470:7:584::1: Destination Host Unreachable Vr TC Flow Plen Nxt Hlim 6 00 0 0010 3a 3e 2001:470:8:584:20e:cff::->2001:470:7:584::3 ICMP6: type = 128, code = 0 The other thing to potentially look at would be firewall rules, but that is unlikely if you can see the icmp6 response in tcpdump. No firewall involved. Good Luck. It would appear that this is an error, but in ping and not ping6. Both of their man pages have exactly the same comment for -v. However, ping does show things like Host down etc without the -v argument. Ping6 works per the man page and does not. I don't think that this is worth a PR though. Thanks for the help. --Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Possible bug with IPv6 ICMPv6 handling
On Fri, Aug 21, 2009 at 1:55 AM, Doug Hardie wrote: > I have found what to me seems like a bug with ICMPv6 handling in IPv6. > However, before submitting a PR I wanted to check to be sure that its not a > misunderstanding on my part. > > The network setup. A host (A) connected to a router (B) connected to > another host (C) on a separate network. When all are up and running, A can > ping6 to C and gets a response. If you power off C and then do the ping > again, tpcdump on A shows an ICMPv6 destination unreachable datagram > received from B. However ping6 does not report that back to the user. A > ktrace of ping6 shows that it does not receive the ICMPv6 response. Its my > understanding that it should and the ping6 code seems to imply that also. Is > this a bug? > ___ What version of FreeBSD are you using ? Did you try the -v parameter to ping6 to display non-echo responses ? (man ping6) In a similar test I ran, I was able to get the icmp6 host unreachable message from ping6 -v on my FreeBSD 7.2 box. (I pinged a non-existent address/machine off an upstream router) uname -a FreeBSD dhorn-bsd 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 dh...@dhorn-bsd:~> ping6 -v 2001:470:7:584::3 PING6(56=40+8+8 bytes) 2001:470:8:584:20e:cff:: --> 2001:470:7:584::3 64 bytes from 2001:470:7:584::1: Destination Host Unreachable Vr TC Flow Plen Nxt Hlim 6 00 0 0010 3a 3e 2001:470:8:584:20e:cff::->2001:470:7:584::3 ICMP6: type = 128, code = 0 The other thing to potentially look at would be firewall rules, but that is unlikely if you can see the icmp6 response in tcpdump. Good Luck. --Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Possible bug with IPv6 ICMPv6 handling
I have found what to me seems like a bug with ICMPv6 handling in IPv6. However, before submitting a PR I wanted to check to be sure that its not a misunderstanding on my part. The network setup. A host (A) connected to a router (B) connected to another host (C) on a separate network. When all are up and running, A can ping6 to C and gets a response. If you power off C and then do the ping again, tpcdump on A shows an ICMPv6 destination unreachable datagram received from B. However ping6 does not report that back to the user. A ktrace of ping6 shows that it does not receive the ICMPv6 response. Its my understanding that it should and the ping6 code seems to imply that also. Is this a bug? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ng_netflow and ipv6
Reinhard Haller wrote: I'm missing ipv6 traffic (all ssh-traffic is going over ipv6) in the filtered netflow output. I've checked the netflow data with tcpdump/wireshark, there is no ipv6 netflow monitored. ng_netflow implements netflow version 5, which doesn't support IPv6. Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ng_netflow and ipv6
Hi,
I'm monitoring the network traffic with ng_netflow and
collecting/displaying it with nfsen.
I'm missing ipv6 traffic (all ssh-traffic is going over ipv6) in the
filtered netflow output.
I've checked the netflow data with tcpdump/wireshark, there is no ipv6
netflow monitored.
My config:
FreeBSD 7.2 with netgraph included in kernel configuration
ngctl -f /usr/local/etc/netflow.conf is started after boot with the
following config:
mkpeer em0: netflow lower iface0
name em0:lower netflow
connect em0: netflow: upper out0
mkpeer netflow: ksocket export inet/dgram/udp
msg netflow:export connect inet/192.168.0.31:9996
connect em1: netflow: lower iface1
connect em1: netflow: upper out1
connect nfe0: netflow: lower iface2
connect nfe0: netflow: upper out2
msg netflow: setconfig {iface=0 conf=7}
msg netflow: setconfig {iface=1 conf=7}
msg netflow: setconfig {iface=2 conf=7}
Any suggestions?
Thanks
Reinhard Haller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPv6 FreeBSD servers
On Sun, 2009-07-19 at 17:56 +1000, Brett Wiggins wrote: > Hi, > > I am looking to rent a FreeBSD server that has access to an IPv6 > address. I have previously rented a FreeBSD server from theplanet.com > but they only offer IPv4 and I would like my server to be on the IPv6 > network. Does anyone have any knowledge of companies that offer this? > > thanks, > > Brett. > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Hi Brett What about using a ipv4 - ipv6 tunnel broker like sixxs, should just be a case of setting up an account then running the aiccu connectivity client on your server. Regards Craig B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPv6 FreeBSD servers
Hi, I am looking to rent a FreeBSD server that has access to an IPv6 address. I have previously rented a FreeBSD server from theplanet.com but they only offer IPv4 and I would like my server to be on the IPv6 network. Does anyone have any knowledge of companies that offer this? thanks, Brett. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Problems with IPv6 CARP Interface in PF
Michael K. Smith - Adhost wrote:
Hello:
I'm having reachability problems with a CARP interface set up on two 7.1
boxes with an uplink to Cisco routers. However, the inside CARP address
on the same set of PF boxes are reachable with no trouble. Here's the
config.
Cisco Cisco
HSRP Gateway
|
CARP Interface 1
PF Box PF Box
CARP Interface 2
|
Server
When I try to ping CARP Interface 1 above from the Internet, I get no
response. When I ping the CARP Interface 2, which has a route set from
the Cisco's to CARP Interface 1, it works. Here's what I see in my
logs.
00:38:45.763975 IP6 fe80::203:6cff:fef9:2c00 > ff02::1:ff00:7: ICMP6,
neighbor solicitation, who has 2001:4970:::7, length 32
... with no response.
Here is the ifconfig from one box.
carp0: flags=49 metric 0 mtu 1500
inet6 2001:4970:::6 prefixlen 64
inet6 2001:4970:::7 prefixlen 64
carp: MASTER vhid 1 advbase 1 advskew 100
carp1: flags=49 metric 0 mtu 1500
inet6 2001:4970::::1 prefixlen 64
carp: MASTER vhid 2 advbase 1 advskew 100
and the other shows appropriately as "BACKUP". There is no change if I
run with just one PF box.
Any help would be greatly appreciated.
* Do you have PF rulesets written to take account of the CARP interfaces
and IPs correctly? You can say things like:
pass in on carp0 proto icmp6 from any to { carp0 carp1 } keep state
You may not need carp specific rules if the carp IP is from the same
network as the IPs on the front interfaces of those PF boxes, and your
rules are written to filter traffic crossing those interfaces by network
(say) rather than by specific IP numbers.
A good debugging trick is to make sure that all pf rules that block
packets have a log clause, and then tcpdump pflog0 while doing your
connectivity tests. Immediately tells you if its PF blocking things
rather than some other problem.
* I'm sure this is far too obvious, but in case you've tripped over this
one accidentally:
pass ... proto inet
only allows IPv4. Either drop the proto clause altogether, or add explicit
'proto inet6' rules.
* Have you tried tcpdump on the various physical and carp interfaces on those
machines while trying to ping? Probably the most interesting data to be
gleaned
from that is if there are ping responses being sent, and what IP they originate
from.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Problems with IPv6 CARP Interface in PF
Hello: I'm having reachability problems with a CARP interface set up on two 7.1 boxes with an uplink to Cisco routers. However, the inside CARP address on the same set of PF boxes are reachable with no trouble. Here's the config. Cisco Cisco HSRP Gateway | CARP Interface 1 PF Box PF Box CARP Interface 2 | Server When I try to ping CARP Interface 1 above from the Internet, I get no response. When I ping the CARP Interface 2, which has a route set from the Cisco's to CARP Interface 1, it works. Here's what I see in my logs. 00:38:45.763975 IP6 fe80::203:6cff:fef9:2c00 > ff02::1:ff00:7: ICMP6, neighbor solicitation, who has 2001:4970:::7, length 32 ... with no response. Here is the ifconfig from one box. carp0: flags=49 metric 0 mtu 1500 inet6 2001:4970:::6 prefixlen 64 inet6 2001:4970:::7 prefixlen 64 carp: MASTER vhid 1 advbase 1 advskew 100 carp1: flags=49 metric 0 mtu 1500 inet6 2001:4970::::1 prefixlen 64 carp: MASTER vhid 2 advbase 1 advskew 100 and the other shows appropriately as "BACKUP". There is no change if I run with just one PF box. Any help would be greatly appreciated. Regards, Mike -- Michael K. Smith - CISSP, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1 (206) 404-9050 PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: net-snmp and IPv6 MIB
Aurélien Ansel wrote:
> Hi all,
>
> sorry in advance for my bad english.
>
> I think i have a problem with the MIB of IPv6.
>
> I have installed the last port of net-snmp.
>
> Can someone give the result of this request, it must be send to a
> computer with a smp daemon and at least one interface with an IPv6 address.
>snmpwalk -v 2c -c
> .1.3.6.1.2.1.4.34
>
> On my FreeBSD 7.1, this command give me : "IP-MIB::ipAddressTable = No
> Such Object available on this agent at this OID"
> But if I execute this command on a Ubuntu with IPv6 addresses and
> net-snmpd running that return a lot of results, in particulary the list
> of IPv6 addresses linked to the machine ( it's what i'm looking for ).
>
> So i don't know if the problem come from my computer or from the port.
It looks like it may be the port. None of my SNMP enabled boxes display
the IPv6 addresses of the interface either (I've never noticed, as I
don't use SNMP for that ;)
However, in the Makefile, I noticed this:
@${ECHO_MSG} "WITH_INETADDRESS_HACK=yes builds with the inetaddress hack"
Which I read somewhere by searching Google that it has something to do
with 'fixing' the IPv6 address issue. Put:
WITH_INETADDRESS_HACK=yes
in your /etc/make.conf file, and try rebuilding the port.
Let us know if that fixes it.
Steve
smime.p7s
Description: S/MIME Cryptographic Signature
