Re: kern/140036: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock
Old Synopsis: lock order reversal with iwn0_com_lock and iwn0 softc lock New Synopsis: [iwn] [lor] lock order reversal with iwn0_com_lock and iwn0 softc lock Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Oct 28 08:20:57 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140036 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
LINKSYS WUSB600N, 802.11a/b/g
Does anyone know if this usb wifi adapter [LINKSYS WUSB600N, 802.11a/b/g] works with -CURRENT or 8.0-RC? Thanks Ivor ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/138130: [netinet] [patch] Resource leak in LibAliasRefreshModules() in file sys/netinet/libalias/alias.c
Synopsis: [netinet] [patch] Resource leak in LibAliasRefreshModules() in file sys/netinet/libalias/alias.c State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Wed Oct 28 13:10:37 CET 2009 State-Changed-Why: Committed, thanks! Responsible-Changed-From-To: freebsd-net->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Wed Oct 28 13:10:37 CET 2009 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=138130 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
snort on multiple interfaces
Some years ago, I checked to see whether I would be able to let a single snort process listen on more than one NIC. At the time it was only possible in Linux. Now, I searched a bit, but nothing new came up. Did anything improve since then? Do we still need multiple snort processes to listen on more than one interface? Can some netgraph node help with this? bye & Thanks av. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Hi. Regarding "automatic vlan creation"
Hi Now that FreeBSD has support for writing , cloned_interfaces="em0.100" instead of having to create for example a vlan0 and then specify vlandev etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? ifconfig_em0.100="" or ifconfig_em0_100="" does not work. Sincerely, Sebastian H ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: snort on multiple interfaces
On Wed, Oct 28, 2009 at 4:35 PM, Andrea Venturoli wrote: > Some years ago, I checked to see whether I would be able to let a single > snort process listen on more than one NIC. > At the time it was only possible in Linux. > In Linux the packet capture facility is implemented in a different (and very inefficient manner), via raw sockets (which means that, in order to reach userspace, a packet has to travel the whole IP stack - including firewall - until delivery to the user process). BSD has BPF, which basically delivers a copy of the packet to the userspace right before it enters the IP stack for kernel processing. Each network driver does this through the BPF_TAP() macro. > Now, I searched a bit, but nothing new came up. > > Did anything improve since then? Do we still need multiple snort processes > to listen on more than one interface? > Can some netgraph node help with this? You can try lagg(4) with the "loadbalance" option, ng_one2many(4), or ng_fec(4). > > bye & Thanks > av. > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: snort on multiple interfaces
Andrea Venturoli wrote:
Some years ago, I checked to see whether I would be able to let a
single snort process listen on more than one NIC.
At the time it was only possible in Linux.
Now, I searched a bit, but nothing new came up.
Did anything improve since then? Do we still need multiple snort
processes to listen on more than one interface?
Can some netgraph node help with this?
You can do this using if_bridge in monitor mode like so:
{/etc/rc.conf}
## DMZ Span Port
cloned_interfaces="bridge0"
ifconfig_fxp0="up promisc"
ifconfig_fxp1="up promisc"
ifconfig_bridge0="addm fxp0 addm fxp1 monitor up"
And then have you snort process run on bridge0.
Tom
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Hi. Regarding "automatic vlan creation"
2009/10/28 Sebastian Hyrwall : > Hi > > Now that FreeBSD has support for writing , cloned_interfaces="em0.100" > instead of having to create for example a vlan0 and then specify vlandev etc > in ifconfig. What is the correct ifconfig-line in rc.conf for this? > > ifconfig_em0.100="" or ifconfig_em0_100="" does not work. You probably forgot to put if_vlan_load="YES" in /boot/loader.conf ifconfig_em0_100="..." should work. -- Artis Caune Everything should be made as simple as possible, but not simpler. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Hi. Regarding "automatic vlan creation"
Hi. Ah ok. Well I did add that but maybe there was a typo somewhere else. Unfortuently I can't reach the server anymore (i wonder why heh ;) so I gave this email a try before going to the datacenter to fix it. Thanks for the input. Artis Caune skrev: 2009/10/28 Sebastian Hyrwall : Hi Now that FreeBSD has support for writing , cloned_interfaces="em0.100" instead of having to create for example a vlan0 and then specify vlandev etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? ifconfig_em0.100="" or ifconfig_em0_100="" does not work. You probably forgot to put if_vlan_load="YES" in /boot/loader.conf ifconfig_em0_100="..." should work. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
82575 NIC can't work with LAGG
In FreeBSD 8.0-RC1, igb can't work with lagg, however, em(82571) works. Is there something weird with igb driver? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
PF and DHCP
Hiya I have a server which acts as a gateway between the internet and my internal network. The external interface receives its IP address via DHCP. I set up pf.conf to allow DHCP packets via ports 67/68, but I notice that when the server boots, the DHCP exchange happens /before/ PF gets started. Does this mean that adding rules for DHCP isn't necessary (my firewall rules are block in/pass out, with a bit of NAT thrown in)? Does this mean that when my machine boots, there's a window between the interfaces coming up and the firewall being enabled? Thanks, --Jon ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: PF and DHCP
Jonathan Belson wrote: Hiya I have a server which acts as a gateway between the internet and my internal network. The external interface receives its IP address via DHCP. I set up pf.conf to allow DHCP packets via ports 67/68, but I notice that when the server boots, the DHCP exchange happens /before/ PF gets started. Does this mean that adding rules for DHCP isn't necessary (my firewall rules are block in/pass out, with a bit of NAT thrown in)? To address just this question, it is a good idea to leave the rules that allow DHCP in there, as the DHCP client will need to renew its lease later, while the firewall is running. -Boris Does this mean that when my machine boots, there's a window between the interfaces coming up and the firewall being enabled? Thanks, --Jon ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Hi. Regarding "automatic vlan creation"
On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote: > Hi > > Now that FreeBSD has support for writing , cloned_interfaces="em0.100" > instead of having to create for example a vlan0 and then specify vlandev > etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? > > ifconfig_em0.100="" or ifconfig_em0_100="" does not work. It should be ifconfig_em0_100. -- Brooks pgplfREukJbEH.pgp Description: PGP signature
Re: ZFS and 'traditional' nfs-export
On Tue, Oct 27, 2009 at 12:46:00AM +0100, Arno J. Klaassen wrote: > > Hello, > > I googled a bit on this question but could not find > a clear answer : > > is there any risk/inconvenience/advantage in exporting > a ZFS-fs by just putting it in /etc/exports the old > way and leaving the 'sharenfs' option on the filesystem off? > > I'd like to replace a UFS-based server serving mostly > linux-clients which work well now with a ZFS-fs, and somehow > am a bit waterfearing changing the nfsèoptions which worked > great till now. You can safely use /etc/exports without touching sharenfs property. -- Pawel Jakub Dawidek http://www.wheel.pl p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpX62VJDmMh1.pgp Description: PGP signature
Re: kern/140051: [bce] [arp] ARP not sent through Bridge Firewall with BCE network dirver
Old Synopsis: ARP not sent through Bridge Firewall with BCE network dirver New Synopsis: [bce] [arp] ARP not sent through Bridge Firewall with BCE network dirver Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Oct 28 18:37:36 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140051 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Hi. Regarding "automatic vlan creation"
2009/10/28 Brooks Davis : > On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote: >> Hi >> >> Now that FreeBSD has support for writing , cloned_interfaces="em0.100" >> instead of having to create for example a vlan0 and then specify vlandev >> etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? >> >> ifconfig_em0.100="" or ifconfig_em0_100="" does not work. > > It should be ifconfig_em0_100. btw, wouldn't it be nice not to bother with loader.conf when using . syntax? This patch will load if_vlan automatically in this case: --- sbin/ifconfig/ifconfig.c2009-10-26 14:11:16 + +++ sbin/ifconfig/ifconfig.c2009-10-28 21:43:07 + @@ -998,6 +998,10 @@ break; } + /* try to load vlan module if interface name is device.vlan_id */ + if (index(name, '.') != NULL) + strlcpy(ifname, "vlan", sizeof(ifname)); + /* turn interface and unit into module name */ strcpy(ifkind, "if_"); strlcpy(ifkind + MOD_PREFIX_LEN, ifname, -- Artis Caune Everything should be made as simple as possible, but not simpler. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: bce(4) BCM5907 CTX write errors on 7.2 driver
David Christensen wrote: Thanks for the rapid response. Dell have firmware 5.0.9 on their website here: http://tiny.cc/ex834 Will that work? Yes, that release does include a good version of BCM5709 bootcode (v5.06). I couldn't really tell until I downloaded the file and looked at the temporary files inside. Thanks for the link. After fighting with the update process for a bit and then learning about the live cycle manager I have managed to test the R610 with the 5.0.9 firmware. On the face of it, it seems that this resolves the issue. Tom ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: kern/139145: IPv6 blackhole / reject routes broken
The following reply was made to PR kern/139145; it has been noted by GNATS. From: Sten Spans To: freebsd-gnats-sub...@freebsd.org Cc: Subject: Re: kern/139145: IPv6 blackhole / reject routes broken Date: Thu, 29 Oct 2009 00:05:45 +0100 (CET) On Fri, 25 Sep 2009, freebsd-gnats-sub...@freebsd.org wrote: >> Category: kern >> Responsible:freebsd-bugs >> Synopsis: IPv6 blackhole / reject routes broken >> Arrival-Date: Fri Sep 25 22:50:01 UTC 2009 Not sure which commit fixed it but this issue seems to be fixed in 8.0-RC2: traceroute to 2a02:898:17:1234:: (2a02:898:17:1234::) from 2001:7b8:666::0:42ff:fe00:4, 30 hops max, 24 byte packets 1 gw.deepthought.blinkenlights.nl (2001:7b8:666:::1) 0.292 ms 0.227 ms 0.193 ms 2 hobby-gw.jun1.galilei.network.bit.nl (2001:7b8:3:47::2) 0.357 ms 0.402 ms 0.461 ms 3 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 2.603 ms 2.494 ms 2.234 ms 4 2001:6e0:8954:205b:1::2 (2001:6e0:8954:205b:1::2) 5.103 ms 5.144 ms 5.829 ms 5 ge-0-0-1-0.dcg-1.ipv6.coloclue.net (2a02:898:0:301::a) 5.238 ms 6.026 ms 6.345 ms 6 eddie.blinkenlights.nl (2a02:898::74:2) 3.18 ms 3.158 ms 4.044 ms 7 * * * -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Hi. Regarding "automatic vlan creation"
On Thu, Oct 29, 2009 at 12:31:49AM +0200, Artis Caune wrote: > 2009/10/28 Brooks Davis : > > On Wed, Oct 28, 2009 at 03:18:41PM +0100, Sebastian Hyrwall wrote: > >> Hi > >> > >> Now that FreeBSD has support for writing ??, cloned_interfaces="em0.100" > >> instead of having to create for example a vlan0 and then specify vlandev > >> etc in ifconfig. What is the correct ifconfig-line in rc.conf for this? > >> > >> ifconfig_em0.100="" or ifconfig_em0_100="" does not work. > > > > It should be ifconfig_em0_100. > > btw, wouldn't it be nice not to bother with loader.conf when using > . syntax? > This patch will load if_vlan automatically in this case: Sorry but my reation is: eww. There's no way I'd commit that. You'd be randomly loading the vlan code for any interface that had a dot in it. The real change we should make it to add device vlan to GENERIC. It's long past time for it to be in by default. -- Brooks > --- sbin/ifconfig/ifconfig.c 2009-10-26 14:11:16 + > +++ sbin/ifconfig/ifconfig.c 2009-10-28 21:43:07 + > @@ -998,6 +998,10 @@ > break; > } > > + /* try to load vlan module if interface name is device.vlan_id */ > + if (index(name, '.') != NULL) > + strlcpy(ifname, "vlan", sizeof(ifname)); > + > /* turn interface and unit into module name */ > strcpy(ifkind, "if_"); > strlcpy(ifkind + MOD_PREFIX_LEN, ifname, > > > > > > -- > Artis Caune > > Everything should be made as simple as possible, but not simpler. > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > pgp1baj7mew8X.pgp Description: PGP signature
Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering
The following reply was made to PR kern/124127; it has been noted by GNATS. From: Mark Atkinson To: freebsd prs Cc: Subject: Re: kern/124127: [msk] watchdog timeout (missed Tx interrupts) -- recovering Date: Wed, 28 Oct 2009 17:03:52 -0700 (PDT) =0A=0AOn the unpatched -current kernel, built=0A=0AFreeBSD hellfire.filamen= t.org 9.0-CURRENT FreeBSD 9.0-CURRENT #14: Mon Oct 19 09:12:03 PDT 2009 =0A= =0AI recieved the following panic today related to this:=0A=0AFatal trap 12= : page fault while in kernel mode=0Acpuid =3D 0; apic id =3D 00=0Afault vir= tual address =3D 0xdeadc10a=0Afault code =3D supervisor read= , page not present=0Ainstruction pointer =3D 0x20:0xc0987410=0Astack po= inter =3D 0x28:0xd533dac0=0Aframe pointer =3D 0x28:0xd5= 33dae8=0Acode segment=3D base 0x0, limit 0xf, type 0x1b=0A = =3D DPL 0, pres 1, def32 1, gran 1=0Aprocessor eflag= s=3D interrupt enabled, resume, IOPL =3D 0=0Acurrent process = =3D 0 (mskc0 taskq)=0APhysical memory: 495 MB=0ADumping 132 MB: 117 101 8= 5 69 53 37 21 5=0A=0AReading symbols from /boot/kernel/linux.ko...Reading s= ymbols from /boot/kernel/linux.ko.symbols...done.=0Adone.=0ALoaded symbols = for /boot/kernel/linux.ko=0A#0 0xc08907a9 in doadump () at /usr/src/sys/ke= rn/kern_shutdown.c:254=0A254 }=0A(kgdb) bt=0A#0 0xc08907a9 in doadump = () at /usr/src/sys/kern/kern_shutdown.c:254=0A#1 0xc04f7e37 in db_fncall (= dummy1=3D-1067299898, dummy2=3D0, dummy3=3D-718022488,=0Adummy4=3D0xd53= 3d898 "\200%t=C3") at /usr/src/sys/ddb/db_command.c:548=0A#2 0xc04f8214 in= db_command (last_cmdp=3D0xc0da059c, cmd_table=3D0x0, dopager=3D1)=0Aat= /usr/src/sys/ddb/db_command.c:445=0A#3 0xc04f8352 in db_command_loop () a= t /usr/src/sys/ddb/db_command.c:498=0A#4 0xc04fa05e in db_trap (type=3D12,= code=3D0) at /usr/src/sys/ddb/db_main.c:229=0A#5 0xc08bf2d2 in kdb_reente= r () at /usr/src/sys/kern/subr_kdb.c:398=0A#6 0xc0ba9b62 in trap_fatal (fr= ame=3D0x1, eva=3D3735929098)=0Aat /usr/src/sys/i386/i386/trap.c:938=0A#= 7 0xc0baa483 in trap (frame=3D0xd533da80) at /usr/src/sys/i386/i386/trap.c= :339=0A#8 0xc0b8e4ab in Xlcall_syscall () at /usr/src/sys/i386/i386/except= ion.s:241=0A#9 0xc0987410 in in_lltable_lookup (llt=3D0xc39e1000, flags=3D= Variable "flags" is not available.=0A)=0Aat /usr/src/sys/netinet/in.c:1= 380=0A#10 0xc0982470 in arpintr (m=3D0xc3baeb00) at /usr/src/sys/netinet/if= _ether.c:642=0A#11 0xc094227a in netisr_dispatch_src (proto=3D7, source=3D0= , m=3D0xc0de)=0Aat /usr/src/sys/net/netisr.c:932=0A#12 0xc09424dd in ne= tisr_unregister (nhp=3D0xc0de)=0Aat /usr/src/sys/net/netisr.c:583=0A#13= 0xc093ac69 in ether_demux (ifp=3D0x0, m=3D0xc3baeb00)=0Aat /usr/src/sy= s/net/if_ethersubr.c:911=0A#14 0xc093b1ce in ether_output (ifp=3D0xc36ad400= , m=3D0xc3baeb00, dst=3D0xc0c55c27,=0Aro=3D0x301010a) at /usr/src/sys/n= et/if_ethersubr.c:181=0A---Type to continue, or q to quit= ---=0A#15 0xc070b032 in msk_handle_events (sc=3D0xc3686c00)=0Aat /usr/s= rc/sys/dev/msk/if_msk.c:3048=0A#16 0xc070b828 in msk_int_task (arg=3D0xc368= 6c00, pending=3D1)=0Aat /usr/src/sys/dev/msk/if_msk.c:3625=0A#17 0xc08c= ac8c in taskqueue_run (queue=3D0xc36bf380)=0Aat /usr/src/sys/kern/subr_= taskqueue.c:72=0A#18 0xc08cadcc in taskqueue_thread_loop (arg=3D0xc3686c8c)= =0Aat /usr/src/sys/kern/subr_taskqueue.c:90=0A#19 0xc0869271 in fork_ex= it (callout=3D0xc08cad67 ,=0Aarg=3D0xc3686c8c= , frame=3D0xd533dd38) at /usr/src/sys/kern/kern_fork.c:854=0A#20 0xc0b8e520= in Xatpic_intr0 () at atpic_vector.s:62=0A#21 0x in ?? ()=0A=0A=0A= ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
RE: kern/139145: IPv6 blackhole / reject routes broken
I remember looking at this bug and tried to reproduce it ... If my memory serves me right, I believe this bug was fixed by svn r197364, committed on 9/20. RC1 was built on 9/17. Another symptom of this bug is the "route get" command issued on any lo0 addresses returns "destination: default" instead of "destination: lo0". -- Qing > -Original Message- > From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd- > n...@freebsd.org] On Behalf Of Sten Spans > Sent: Wednesday, October 28, 2009 4:10 PM > To: freebsd-net@freebsd.org > Subject: Re: kern/139145: IPv6 blackhole / reject routes broken > > The following reply was made to PR kern/139145; it has been noted by > GNATS. > > From: Sten Spans > To: freebsd-gnats-sub...@freebsd.org > Cc: > Subject: Re: kern/139145: IPv6 blackhole / reject routes broken > Date: Thu, 29 Oct 2009 00:05:45 +0100 (CET) > > On Fri, 25 Sep 2009, freebsd-gnats-sub...@freebsd.org wrote: > > >> Category: kern > >> Responsible:freebsd-bugs > >> Synopsis: IPv6 blackhole / reject routes broken > >> Arrival-Date: Fri Sep 25 22:50:01 UTC 2009 > > Not sure which commit fixed it but this issue seems to > be fixed in 8.0-RC2: > > traceroute to 2a02:898:17:1234:: (2a02:898:17:1234::) from > 2001:7b8:666::0:42ff:fe00:4, 30 hops max, 24 byte packets >1 gw.deepthought.blinkenlights.nl (2001:7b8:666:::1) 0.292 ms > 0.227 ms 0.193 ms >2 hobby-gw.jun1.galilei.network.bit.nl (2001:7b8:3:47::2) 0.357 ms > 0.402 ms 0.461 ms >3 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 2.603 > ms 2.494 ms 2.234 ms >4 2001:6e0:8954:205b:1::2 (2001:6e0:8954:205b:1::2) 5.103 ms > 5.144 ms 5.829 ms >5 ge-0-0-1-0.dcg-1.ipv6.coloclue.net (2a02:898:0:301::a) 5.238 ms > 6.026 ms 6.345 ms >6 eddie.blinkenlights.nl (2a02:898::74:2) 3.18 ms 3.158 ms 4.044 > ms >7 * * * > > -- > Sten Spans > > "There is a crack in everything, that's how the light gets in." > Leonard Cohen - Anthem > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
