From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 07:06:58 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 802244BC for ; Mon, 24 Nov 2014 07:06:58 +0000 (UTC) Received: from umail.aei.mpg.de (umail.aei.mpg.de [194.94.224.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D47A8638 for ; Mon, 24 Nov 2014 07:06:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by umail.aei.mpg.de (Postfix) with ESMTP id 6C31C200BB4; Mon, 24 Nov 2014 08:06:48 +0100 (CET) X-Virus-Scanned: by amavisd-new-2.6.4 (20090625) (Debian) at aei.mpg.de Received: from umail.aei.mpg.de ([127.0.0.1]) by localhost (umail.aei.mpg.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wy5wcxkO9mN; Mon, 24 Nov 2014 08:06:48 +0100 (CET) Received: from mailgate.aei.mpg.de (mailgate.aei.mpg.de [194.94.224.5]) by umail.aei.mpg.de (Postfix) with ESMTP id 21F50200BB1; Mon, 24 Nov 2014 08:06:48 +0100 (CET) Received: from mailgate.aei.mpg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 11FAC405889; Mon, 24 Nov 2014 08:06:48 +0100 (CET) Received: from intranet.aei.uni-hannover.de (ahin1.aei.uni-hannover.de [130.75.117.40]) by mailgate.aei.mpg.de (Postfix) with ESMTP id AF59B406AF1; Mon, 24 Nov 2014 08:06:47 +0100 (CET) Received: from arc.aei.uni-hannover.de ([10.117.15.110]) by intranet.aei.uni-hannover.de (Lotus Domino Release 8.5.3FP6HF1016) with ESMTP id 2014112408063724-20217 ; Mon, 24 Nov 2014 08:06:37 +0100 Date: Mon, 24 Nov 2014 08:06:37 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Jack Vogel Subject: Re: igb Could not setup receive structures (again) Message-Id: <20141124080637.75dc6f55a499b88014a03a03@aei.mpg.de> In-Reply-To: References: <20141121114852.8b7d9a6c071c3e0799d5f30c@aei.mpg.de> <20141121183306.d057ff1743e2a1e04ae55f93@aei.mpg.de> Organization: Max Planck Gesellschaft X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on intranet/aei-hannover(Release 8.5.3FP6HF1016 | October 31, 2014) at 24.11.2014 08:06:37, Serialize by Router on intranet/aei-hannover(Release 8.5.3FP6HF1016 | October 31, 2014) at 24.11.2014 08:06:47, Serialize complete at 24.11.2014 08:06:47 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-PMX-Version: 6.0.2.2308539, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.11.24.65420 X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, MIME_LOWER_CASE 0.05, BODY_SIZE_10000_PLUS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __C230066_P5 0, __CP_MEDIA_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_BODY_WEBMAIL 0, __FRAUD_CONTACT_ADDY_B 0, __FRAUD_WEBMAIL 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __REFERENCES 0, __SANE_MSGID 0, __STOCK_PHRASE_24 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS ' Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 07:06:58 -0000 On Fri, 21 Nov 2014 13:01:23 -0800 Jack Vogel wrote about Re: igb Could not setup receive structures (again): JV> Yes, its strange, the mbuf resources look fine. JV> Can you show the dmesg record from a boot that JV> includes the failure please? Well, the machine is in production, I cannot boot it right now. However, here is the latest dmesg from /var/run: --- Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-STABLE #5 r261710: Mon Feb 10 16:55:29 CET 2014 root@mclane.rt.aei.uni-hannover.de:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Xeon(R) CPU E5-2609 v2 @ 2.50GHz (2500.05-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306e4 Family = 0x6 Model = 0x3e Stepping = 4 Features=0xbfebfbff Features2=0x7fbee3ff AMD Features=0x2c100800 AMD Features2=0x1 Standard Extended Features=0x281 TSC: P-state invariant, performance statistics real memory = 17196646400 (16400 MB) avail memory = 16523558912 (15758 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: < > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 random: initialized cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 26 at device 1.0 on pci0 pci1: on pcib1 pcib2: irq 26 at device 1.1 on pci0 pci2: on pcib2 igb0: port 0xe020-0xe03f mem 0xfbb20000-0xfbb3ffff,0xfbb44000-0xfbb47fff irq 27 at device 0.0 on pci2 igb0: Using MSIX interrupts with 5 vectors igb0: Ethernet address: 00:25:90:c5:db:56 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 igb1: port 0xe000-0xe01f mem 0xfbb00000-0xfbb1ffff,0xfbb40000-0xfbb43fff irq 30 at device 0.1 on pci2 igb1: Using MSIX interrupts with 5 vectors igb1: Ethernet address: 00:25:90:c5:db:57 igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb1: Bound queue 2 to cpu 2 igb1: Bound queue 3 to cpu 3 pcib3: irq 33 at device 2.0 on pci0 pci4: on pcib3 mps0: port 0xd000-0xd0ff mem 0xfba9c000-0xfba9ffff,0xfba40000-0xfba7ffff irq 32 at device 0.0 on pci4 mps0: Firmware: 17.00.01.00, Driver: 16.00.00.00-fbsd mps0: IOCCapabilities: 1285c pcib4: irq 33 at device 2.2 on pci0 pci5: on pcib4 pcib5: irq 41 at device 3.0 on pci0 pci6: on pcib5 pcib6: mem 0xfb700000-0xfb71ffff irq 40 at device 0.0 on pci6 pci7: on pcib6 pcib7: irq 44 at device 1.0 on pci7 pci8: on pcib7 igb2: port 0xb020-0xb03f mem 0xfb5a0000-0xfb5bffff,0xfb580000-0xfb59ffff,0xfb644000-0xfb647fff irq 44 at device 0.0 on pci8 igb2: Using MSIX interrupts with 5 vectors igb2: Ethernet address: 00:25:90:c8:3a:48 igb2: Bound queue 0 to cpu 0 igb2: Bound queue 1 to cpu 1 igb2: Bound queue 2 to cpu 2 igb2: Bound queue 3 to cpu 3 igb3: port 0xb000-0xb01f mem 0xfb540000-0xfb55ffff,0xfb520000-0xfb53ffff,0xfb640000-0xfb643fff irq 45 at device 0.1 on pci8 igb3: Using MSIX interrupts with 5 vectors igb3: Ethernet address: 00:25:90:c8:3a:49 igb3: Bound queue 0 to cpu 0 igb3: Bound queue 1 to cpu 1 igb3: Bound queue 2 to cpu 2 igb3: Bound queue 3 to cpu 3 pcib8: irq 45 at device 2.0 on pci7 pci10: on pcib8 igb4: port 0xa020-0xa03f mem 0xfb3a0000-0xfb3bffff,0xfb380000-0xfb39ffff,0xfb444000-0xfb447fff irq 45 at device 0.0 on pci10 igb4: Using MSIX interrupts with 5 vectors igb4: Ethernet address: 00:25:90:c8:3a:4a igb4: Bound queue 0 to cpu 0 igb4: Bound queue 1 to cpu 1 igb4: Bound queue 2 to cpu 2 igb4: Bound queue 3 to cpu 3 igb5: port 0xa000-0xa01f mem 0xfb340000-0xfb35ffff,0xfb320000-0xfb33ffff,0xfb440000-0xfb443fff irq 46 at device 0.1 on pci10 igb5: Using MSIX interrupts with 5 vectors igb5: Ethernet address: 00:25:90:c8:3a:4b igb5: Bound queue 0 to cpu 0 igb5: Bound queue 1 to cpu 1 igb5: Bound queue 2 to cpu 2 igb5: Bound queue 3 to cpu 3 pcib9: irq 41 at device 3.2 on pci0 pci12: on pcib9 pci0: at device 4.0 (no driver attached) pci0: at device 4.1 (no driver attached) pci0: at device 4.2 (no driver attached) pci0: at device 4.3 (no driver attached) pci0: at device 4.4 (no driver attached) pci0: at device 4.5 (no driver attached) pci0: at device 4.6 (no driver attached) pci0: at device 4.7 (no driver attached) pci0: at device 5.0 (no driver attached) pci0: at device 5.2 (no driver attached) pcib10: irq 16 at device 17.0 on pci0 pci13: on pcib10 isci0: port 0xc000-0xc0ff mem 0xfa47c000-0xfa47ffff,0xfa000000-0xfa3fffff irq 16 at device 0.0 on pci13 pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) ehci0: mem 0xfbc23000-0xfbc233ff irq 16 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 pcib11: irq 17 at device 28.0 on pci0 pci14: on pcib11 pcib12: irq 19 at device 28.7 on pci0 pci15: on pcib12 pcib13: at device 0.0 on pci15 pci16: on pcib13 pcib14: at device 0.0 on pci16 pci17: on pcib14 pcib15: at device 0.0 on pci17 pci18: on pcib15 vgapci0: mem 0xf9000000-0xf9ffffff,0xfb000000-0xfb003fff,0xfa800000-0xfaffffff irq 19 at device 0.0 on pci18 vgapci0: Boot video device pcib16: at device 1.0 on pci16 pci19: on pcib16 ehci1: mem 0xfbc22000-0xfbc223ff irq 23 at device 29.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci1 pcib17: at device 30.0 on pci0 pci20: on pcib17 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f mem 0xfbc21000-0xfbc217ff irq 18 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahciem0: on ahci0 pci0: at device 31.3 (no driver attached) pci0: at device 31.6 (no driver attached) pcib18: on acpi0 pci255: on pcib18 pci255: at device 8.0 (no driver attached) pci255: at device 9.0 (no driver attached) pci255: at device 10.0 (no driver attached) pci255: at device 10.1 (no driver attached) pci255: at device 10.2 (no driver attached) pci255: at device 10.3 (no driver attached) pci255: at device 11.0 (no driver attached) pci255: at device 11.3 (no driver attached) pci255: at device 12.0 (no driver attached) pci255: at device 12.1 (no driver attached) pci255: at device 13.0 (no driver attached) pci255: at device 13.1 (no driver attached) pci255: at device 14.0 (no driver attached) pci255: at device 14.1 (no driver attached) pci255: at device 15.0 (no driver attached) pci255: at device 15.1 (no driver attached) pci255: at device 15.2 (no driver attached) pci255: at device 15.3 (no driver attached) pci255: at device 15.4 (no driver attached) pci255: at device 15.5 (no driver attached) pci255: at device 16.0 (no driver attached) pci255: at device 16.1 (no driver attached) pci255: at device 16.2 (no driver attached) pci255: at device 16.3 (no driver attached) pci255: at device 16.4 (no driver attached) pci255: at device 16.5 (no driver attached) pci255: at device 16.6 (no driver attached) pci255: at device 16.7 (no driver attached) pci255: at device 19.0 (no driver attached) pci255: at device 19.1 (no driver attached) pci255: at device 19.4 (no driver attached) pci255: at device 19.5 (no driver attached) pci255: at device 22.0 (no driver attached) pci255: at device 22.1 (no driver attached) pci255: at device 22.2 (no driver attached) acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 est2: on cpu2 p4tcc2: on cpu2 est3: on cpu3 p4tcc3: on cpu3 Timecounters tick every 1.000 msec random: unblocking device. usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered ada0 at ahcich2 bus 0 scbus4 target 0 lun 0 ada0: ATA-7 SATA 2.x device ada0: Serial Number 99026130913030000295 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes) ada0: 7551MB (15465744 512 byte sectors: 16H 63S/T 15343C) ada0: Previously was known as ad8 ada1 at ahcich3 bus 0 scbus5 target 0 lun 0 ada1: ATA-7 SATA 2.x device ada1: Serial Number 99026130913030000296 ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 512bytes) ada1: 7551MB (15465744 512 byte sectors: 16H 63S/T 15343C) ada1: Previously was known as ad10 ses0 at ahciem0 bus 0 scbus8 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device cd0 at ahcich5 bus 0 scbus7 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: Serial Number KY4D4CN0946 cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da5 at mps0 bus 0 scbus0 target 5 lun 0 da5: Fixed Direct Access SCSI-6 device da5: Serial Number BTDA329102LM1802GN da5: 600.000MB/s transfers da5: Command Queueing enabled da5: 171705MB (351651888 512 byte sectors: 255H 63S/T 21889C) da5: quirks=0x8<4K> da6 at mps0 bus 0 scbus0 target 6 lun 0 da6: Fixed Direct Access SCSI-6 device da6: Serial Number BTDA328500BF1802GN da6: 600.000MB/s transfers da6: Command Queueing enabled da6: 171705MB (351651888 512 byte sectors: 255H 63S/T 21889C) da6: quirks=0x8<4K> da7 at mps0 bus 0 scbus0 target 7 lun 0 da7: Fixed Direct Access SCSI-6 device da7: Serial Number BTDA3285031U1802GN da7: 600.000MB/s transfers da7: Command Queueing enabled da7: 171705MB (351651888 512 byte sectors: 255H 63S/T 21889C) da7: quirks=0x8<4K> da3 at mps0 bus 0 scbus0 target 3 lun 0 da3: Fixed Direct Access SCSI-6 device da3: Serial Number CVKI336202CG080AGN da3: 600.000MB/s transfers da3: Command Queueing enabled da3: 76319MB (156301488 512 byte sectors: 255H 63S/T 9729C) da3: quirks=0x8<4K> da0 at mps0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-6 device da0: Serial Number BTDA328306M61802GN da0: 600.000MB/s transfers da0: Command Queueing enabled da0: 171705MB (351651888 512 byte sectors: 255H 63S/T 21889C) da0: quirks=0x8<4K> da1 at mps0 bus 0 scbus0 target 1 lun 0 da1: Fixed Direct Access SCSI-6 device da1: Serial Number BTDA3292018J1802GN da1: 600.000MB/s transfers da1: Command Queueing enabled da1: 171705MB (351651888 512 byte sectors: 255H 63S/T 21889C) da1: quirks=0x8<4K> da2 at mps0 bus 0 scbus0 target 2 lun 0 da2: Fixed Direct Access SCSI-6 device da2: Serial Number CVKI336202BT080AGN da2: 600.000MB/s transfers da2: Command Queueing enabled da2: 76319MB (156301488 512 byte sectors: 255H 63S/T 9729C) da2: quirks=0x8<4K> da4 at mps0 bus 0 scbus0 target 4 lun 0 da4: Fixed Direct Access SCSI-6 device da4: Serial Number BTDA328505JS1802GN da4: 600.000MB/s transfers da4: Command Queueing enabled da4: 171705MB (351651888 512 byte sectors: 255H 63S/T 21889C) da4: quirks=0x8<4K> Netvsc initializing... SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Timecounter "TSC-low" frequency 1250025326 Hz quality 1000 ugen0.2: at usbus0 uhub2: on usbus0 ugen1.2: at usbus1 uhub3: on usbus1 uhub2: 6 ports with 6 removable, self powered uhub3: 8 ports with 8 removable, self powered ugen0.3: at usbus0 ukbd0: on usbus0 kbd2 at ukbd0 ugen1.3: at usbus1 ukbd1: on usbus1 kbd3 at ukbd1 ugen1.4: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x4000 umass0:9:0:-1: Attached to scbus9 da8 at umass-sim0 bus 0 scbus9 target 0 lun 0 da8: Fixed Direct Access SCSI-0 device da8: Serial Number 9900210100751207 da8: 40.000MB/s transfers da8: 1960MB (4014080 512 byte sectors: 255H 63S/T 249C) da8: quirks=0x2 GEOM_STRIPE: Device swap created (id=350651771). GEOM_STRIPE: Disk da2p2 attached to swap. GEOM_MIRROR: Device mirror/boot launched (2/2). GEOM_STRIPE: Disk da3p2 attached to swap. GEOM_STRIPE: Device stripe/swap activated. GEOM_MIRROR: Device mirror/root launched (1/2). GEOM_MIRROR: Device root: rebuilding provider da3p3. GEOM_STRIPE: Cannot add disk gpt/swap1 to swap (error=17). GEOM_STRIPE: Cannot add disk gptid/b8d53ca0-67f2-11e3-93e3-002590c5db56 to swap (error=17). GEOM_STRIPE: Cannot add disk gpt/swap0 to swap (error=17). GEOM_STRIPE: Cannot add disk gptid/b521fb2f-67f2-11e3-93e3-002590c5db56 to swap (error=17). Trying to mount root from ufs:/dev/mirror/root [rw]... WARNING: / was not properly dismounted ZFS filesystem version: 5 ZFS storage pool version: features support (5000) ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 ums1: on usbus1 ums1: 5 buttons and [XYZ] coordinates ID=1 igb0: link state changed to UP arp: 10.117.0.1 moved from 00:1a:8c:f0:14:e1 to 00:1a:8c:f0:14:e0 on igb0 --- Only 4 cores (I think I said 6 before, my bad). Trying to set mtu 9000 yields these messages: --- Nov 21 11:16:42 mclane kernel: igb1: link state changed to UP Nov 21 11:16:42 mclane devd: Executing '/etc/rc.d/dhclient quietstart igb1' Nov 21 11:17:10 mclane kernel: igb1: link state changed to DOWN Nov 21 11:17:10 mclane kernel: igb1: Could not setup receive structures Nov 21 11:17:36 mclane kernel: igb1: Could not setup receive structures --- This was using rc.conf and rc.d scripts, but I get the same messages when doing that manually with just ifconfig. cu Gerrit From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 13:56:43 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 669A8F8E for ; Mon, 24 Nov 2014 13:56:43 +0000 (UTC) Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D6D0871 for ; Mon, 24 Nov 2014 13:56:43 +0000 (UTC) Received: by mail-qc0-f175.google.com with SMTP id b13so7624230qcw.34 for ; Mon, 24 Nov 2014 05:56:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BO7jNJPH106ZgzLWtrV5MKTpcUAM2l5CNMceEaCNsAU=; b=RaX+WuonDrkP0JW/cpBvr/qA+PJyDKXoI9bx2tTVV+a2G+efG8COFXe6rrGU2sR9M/ gVMsn7qBL47gZGCBHlVhouovL4XV9SkS8oecqDljFJr9G4nB8JwKKeGWnM2xm/U3clPg LlfdXX2feRRQHL4FMPLtdwf9EzVu022EIeHEN05PiT0bqUKU75sQvKhCabbAQvLCulNd x1U3LQQeFdx78xwhtigUkpW65iMQ/juoc6fcnjjyEiCDOAMVGfuMdEvSAjUguAbFAWxl k+DwIejyncX4PXLPKr2xs/YlJWbJLtom/iwXwDPTQPj6OoRcXuCKwxOkasNEieOTL7Xi XtwQ== MIME-Version: 1.0 X-Received: by 10.224.112.2 with SMTP id u2mr29033242qap.14.1416837402311; Mon, 24 Nov 2014 05:56:42 -0800 (PST) Received: by 10.140.92.98 with HTTP; Mon, 24 Nov 2014 05:56:42 -0800 (PST) In-Reply-To: <4833B5CE-33A7-40EA-862D-4E345083FABE@lakerest.net> References: <4833B5CE-33A7-40EA-862D-4E345083FABE@lakerest.net> Date: Mon, 24 Nov 2014 08:56:42 -0500 Message-ID: Subject: Re: Data Center Bridging? From: Juan Mojica To: Randall Stewart Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-net , "Eggert, Lars" , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 13:56:43 -0000 Was there any progress made on DCB? We need a way to classify specific flows from the application and mark them with a priority. Not only do we need a bit of work on the driver, but also a way to tag frames all the way down to the driver. I imagine this would entail a socket option to mark a given flow and a mbuf flag to carry the request for priority classification to the driver. -Juan On Wed, Feb 6, 2013 at 5:53 AM, Randall Stewart wrote: > Lars/Jack: > > I am pretty sure that my company would be interested in it as well.. and I > can > help out here too ;-) > > Jack: are there particular versions of Intel cards that this needs to > be on (we have both igb and ix cards in my office now).. thanks. > > R > > > On Jan 22, 2013, at 10:43 AM, Eggert, Lars wrote: > > > Hi, > > > > on Linux, various NICs (e.g., ixgbe) support Data Center Bridging. Is > this also available under FreeBSD? Do *any* NICs support DCB under FreeBSD? > > > > Thanks, > > Lars > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > > ------------------------------ > Randall Stewart > 803-317-4952 (cell) > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > -- Juan Mojica Email: jmojica@gmail.com From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 14:12:38 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 805FF9A3 for ; Mon, 24 Nov 2014 14:12:38 +0000 (UTC) Received: from tweddell.vserver-on.de (tweddell.de [84.38.66.62]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48134A78 for ; Mon, 24 Nov 2014 14:12:37 +0000 (UTC) Received: from bastian by tweddell.vserver-on.de with local (Exim 4.80) (envelope-from ) id 1XsuNW-0005I3-Ui for freebsd-net@freebsd.org; Mon, 24 Nov 2014 15:12:34 +0100 Date: Mon, 24 Nov 2014 15:12:34 +0100 From: Bastian To: freebsd-net@freebsd.org Subject: iwn fails to scan on E6330 Message-ID: <20141124141234.GG30752@tweddell.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 14:12:38 -0000 Hi all, I have to say, the BSD world is quite new to me. It peeked my interest long time ago, but a week a ago I was brave enough to give it a try on a real physical box. A Latitude E6330. In general the installation was straight forward. For now I just face troubles with GPT (another topic) and iwn. Here is what my machine has: ----- root@zam709:~ # pciconf -lv iwn0 iwn0@pci0:2:0:0: class=0x028000 card=0x13218086 chip=0x00828086 rev=0x34 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N 6205 [Taylor Peak]' class = network root@zam709 ~ 0 59 # kldstat -v | grep iwn 158 pci/iwn 17 1 0xffffffff820cc000 52db4 iwn1000fw.ko (/boot/kernel/iwn1000fw.ko) 509 iwn1000fw_fw 18 1 0xffffffff8211f000 ad28f iwn2030fw.ko (/boot/kernel/iwn2030fw.ko) 510 iwn2030fw_fw 19 1 0xffffffff821cd000 2e58a iwn4965fw.ko (/boot/kernel/iwn4965fw.ko) 511 iwn4965fw_fw 20 1 0xffffffff821fc000 53a21 iwn5000fw.ko (/boot/kernel/iwn5000fw.ko) 512 iwn5000fw_fw 21 1 0xffffffff82250000 52d42 iwn5150fw.ko (/boot/kernel/iwn5150fw.ko) 513 iwn5150fw_fw 22 1 0xffffffff822a3000 6f71e iwn6000fw.ko (/boot/kernel/iwn6000fw.ko) 514 iwn6000fw_fw 23 1 0xffffffff82313000 a5d05 iwn6000g2afw.ko (/boot/kernel/iwn6000g2afw.ko) 515 iwn6000g2afw_fw 24 1 0xffffffff823b9000 70fc2 iwn6000g2bfw.ko (/boot/kernel/iwn6000g2bfw.ko) 516 iwn6000g2bfw_fw 25 1 0xffffffff8242a000 73265 iwn6050fw.ko (/boot/kernel/iwn6050fw.ko) root@zam709:~ # ifconfig iwn0 iwn0: flags=8802 metric 0 mtu 2290 ether 6c:88:14:18:fb:d0 nd6 options=21 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier root@zam709:~ # time ifconfig iwn0 up scan ifconfig: unable to get scan results 0.007u 0.028s 0:00.03 66.6% 370+400k 2+0io 0pf+0w root@zam709:~ # uname -a FreeBSD zam709 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 ----- >From the logs above you can see that the kernel has a built in module for iwn and the firmwares are loaded. The kernel sees the interface and I can bring it up. But when trying to scan for available BSSs, the scan command return immediately without success (exit 1). Right now I suspect the firmware is somehow wrongly configured. But I cannot find any logs about firmwares in the logs. Q: What is the proper procedure to debug a startup of the iwn module? Coming from the linux administration, I failed to gain knowledge how the firmware is handeled. I tried to enable different sets of firmware which were to enable just single firmware and up to enable all availabel firmwares. I used kldload/unload for this. Q: When are the firmwares getting effectively used? Meaning, how does dynamically loading/unloading a firmware change the bahaviour of the module? or When does a module expect a firmware to be available and does it accepts a runtime cahnge of the firmware? Q: As the iwn module is compiled into the kernel, how can I restart this inorder it might read in the firmware again? Other questions I have: Q: Which is the poper firmware for my wireless device? Many thanks, -- Bastian From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 16:10:08 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D11E0D1E for ; Mon, 24 Nov 2014 16:10:08 +0000 (UTC) Received: from smtp31.i.mail.ru (smtp31.i.mail.ru [94.100.177.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45E74986 for ; Mon, 24 Nov 2014 16:10:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=ww8hhnvjeIDVwMa/I9s7EJObu3pLJl4/Cv9lSzdY6p0=; b=XxU99wN5q+kDREScLrMmuGaQL6TnuUmWz55dw0Tris2dCCyE8nHOEkFo5K5r+fou4C059bcem4CmPUYaf0Ke68oS7Bd8ZDjH3nSwow63/nqYZ1tLmOv0NmWrh/eQKhgE1/B6YDerRULK4bnZ2jskkkKCgbfqkj4AsLkL0Z3EL70=; Received: from [2001:67c:13e4:1000::37] (port=10736 helo=work.lehis.ru) by smtp31.i.mail.ru with esmtpa (envelope-from ) id 1XswD9-00082I-8m; Mon, 24 Nov 2014 19:09:59 +0300 Message-ID: <54735857.2010209@mail.ru> Date: Mon, 24 Nov 2014 19:09:59 +0300 From: "Alexey V. Panfilov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: IPMI stops respond if boot in single user mode References: <546F1A96.1060309@mail.ru> In-Reply-To: <546F1A96.1060309@mail.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Spam: Not detected X-Mras: Ok X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 16:10:08 -0000 21.11.2014 13:57, Alexey V. Panfilov wrote: > Hi, > > My IBM System x3250 M5 has IPMI. It shares onboard NIC Broadcom BCM5719. > I'm setup it and IPMI works perfectly. > But when server boots in single user mode IPMI's IP becomes unreachable. > It occures when bge0 init. > > Any hints? > > Thanks. > > > Details are: > > FreeBSD 10.1-STABLE (r274690) amd64 > > /boot/loader.conf > hw.bge.allow_asf=1 > > > bge0: 0x5719001> mem > 0x82a50000-0x82a5ffff,0x82a40000-0x82a4ffff,0x82a30000-0x82a3ffff irq 16 > at device 0.0 on pci6 > bge0: APE FW version: NCSI v1.2.33.0 > bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow > bge0: Using defaults for TSO: 65518/35/2048 > bge0: Ethernet address: 6c:ae:8b:5b:74:98 > > > bge0@pci0:6:0:0: class=0x020000 card=0x04911014 chip=0x165714e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'NetXtreme BCM5719 Gigabit Ethernet PCIe' > class = network > subclass = ethernet > bar [10] = type Prefetchable Memory, range 64, base 0x82a50000, > size 65536, enabled > bar [18] = type Prefetchable Memory, range 64, base 0x82a40000, > size 65536, enabled > bar [20] = type Prefetchable Memory, range 64, base 0x82a30000, > size 65536, enabled > cap 01[48] = powerspec 3 supports D0 D3 current D0 > cap 03[50] = VPD > cap 05[58] = MSI supports 8 messages, 64 bit enabled with 1 message > cap 11[a0] = MSI-X supports 17 messages > Table in map 0x20[0x0], PBA in map 0x20[0x1000] > cap 10[ac] = PCI-Express 2 endpoint max data 128(256) FLR link x2(x4) > speed 5.0(5.0) ASPM disabled(L0s/L1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 0003[13c] = Serial 1 00006cae8b5b7498 > ecap 0004[150] = Power Budgeting 1 > ecap 0002[160] = VC 1 max VC0 > > When it boots in single-user mode and manually run: #ifconfig bge0 up then ipmi become accessable. How it can be fixed automatically after system is boot in single-user mode? -- With best regards, Alexey V. Panfilov phone: (495)678-8007 ext 6000 mail: lehis@starnet.ru -- Best regards, Alexey V. Panfilov From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 16:16:01 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C5E51FA for ; Mon, 24 Nov 2014 16:16:01 +0000 (UTC) Received: from mx.mega-net.ru (www.mega-net.ru [91.217.137.33]) by mx1.freebsd.org (Postfix) with SMTP id CDE34A5E for ; Mon, 24 Nov 2014 16:15:59 +0000 (UTC) Received: (qmail 86913 invoked from network); 24 Nov 2014 19:09:17 +0300 X-Mail-Scanner: Scanned by qSheff-II-2.1-r3 (http://www.enderunix.org/qsheff/) Received: from unknown [172.16.10.37] (HELO work.lehis.ru) by mx.mega-net.ru with ESMTP; 24 Nov 2014 19:09:17 +0300 Message-ID: <5473582D.9060100@starnet.ru> Date: Mon, 24 Nov 2014 19:09:17 +0300 From: "Alexey V. Panfilov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: IPMI stops respond if boot in single user mode References: <546F1A96.1060309@mail.ru> In-Reply-To: <546F1A96.1060309@mail.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 16:16:01 -0000 21.11.2014 13:57, Alexey V. Panfilov wrote: > Hi, > > My IBM System x3250 M5 has IPMI. It shares onboard NIC Broadcom BCM5719. > I'm setup it and IPMI works perfectly. > But when server boots in single user mode IPMI's IP becomes unreachable. > It occures when bge0 init. > > Any hints? > > Thanks. > > > Details are: > > FreeBSD 10.1-STABLE (r274690) amd64 > > /boot/loader.conf > hw.bge.allow_asf=1 > > > bge0: 0x5719001> mem > 0x82a50000-0x82a5ffff,0x82a40000-0x82a4ffff,0x82a30000-0x82a3ffff irq 16 > at device 0.0 on pci6 > bge0: APE FW version: NCSI v1.2.33.0 > bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E > miibus0: on bge0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow > bge0: Using defaults for TSO: 65518/35/2048 > bge0: Ethernet address: 6c:ae:8b:5b:74:98 > > > bge0@pci0:6:0:0: class=0x020000 card=0x04911014 chip=0x165714e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'NetXtreme BCM5719 Gigabit Ethernet PCIe' > class = network > subclass = ethernet > bar [10] = type Prefetchable Memory, range 64, base 0x82a50000, > size 65536, enabled > bar [18] = type Prefetchable Memory, range 64, base 0x82a40000, > size 65536, enabled > bar [20] = type Prefetchable Memory, range 64, base 0x82a30000, > size 65536, enabled > cap 01[48] = powerspec 3 supports D0 D3 current D0 > cap 03[50] = VPD > cap 05[58] = MSI supports 8 messages, 64 bit enabled with 1 message > cap 11[a0] = MSI-X supports 17 messages > Table in map 0x20[0x0], PBA in map 0x20[0x1000] > cap 10[ac] = PCI-Express 2 endpoint max data 128(256) FLR link x2(x4) > speed 5.0(5.0) ASPM disabled(L0s/L1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > ecap 0003[13c] = Serial 1 00006cae8b5b7498 > ecap 0004[150] = Power Budgeting 1 > ecap 0002[160] = VC 1 max VC0 > > When it boots in single-user mode and manually run: #ifconfig bge0 up then ipmi become accessable. How it can be fixed automatically after system is boot in single-user mode? -- With best regards, Alexey V. Panfilov phone: (495)678-8007 ext 6000 mail: lehis@starnet.ru From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 16:20:13 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8541F2FE for ; Mon, 24 Nov 2014 16:20:13 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17FD6AA5 for ; Mon, 24 Nov 2014 16:20:13 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id r20so6361637wiv.14 for ; Mon, 24 Nov 2014 08:20:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d6ne4xCDvyvfZ2tSqSjK6u/MOnXjpv2+yoOv4JYWBCw=; b=GzhGpZlLmziwaaAyNa4V/mNVBZoiKMASVFzpeK5t8qf88b6hDtTxhNo24+BC+eKd/b Z5p4xBv/EwprKdW96mvmObUkB3CXmVPDjXSIRxzgaIdDOhsfRki4VaolkeEspIT6b8IT QCT99aEgQIjLssUCo/ln3aIOBBqmIbcWry8/OBASBR1nimcgRaiAWJRAOqTM3gIAVa4y 5WTKRDWoPCLvTHdFRS4Cac3pdja0oEQRy6EGTFOJ+TGCapBGOi+4tPVVvwIGONHirdIz 43kjdAocyBAowB0XAbJ6y4PlLxuRdOgBCR8tCURCZyHjlC00Whl9bsBEn4RTpt88LOfB x6Dg== MIME-Version: 1.0 X-Received: by 10.180.99.1 with SMTP id em1mr23403471wib.29.1416846011429; Mon, 24 Nov 2014 08:20:11 -0800 (PST) Received: by 10.194.76.34 with HTTP; Mon, 24 Nov 2014 08:20:11 -0800 (PST) In-Reply-To: References: <4833B5CE-33A7-40EA-862D-4E345083FABE@lakerest.net> Date: Mon, 24 Nov 2014 08:20:11 -0800 Message-ID: Subject: Re: Data Center Bridging? From: Jack Vogel To: Juan Mojica Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-net , "Eggert, Lars" , Randall Stewart X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 16:20:13 -0000 No, I'm sorry but I've been kept very busy in development of our 40G driver, however, now that its complete we have been taking on a variety of other tasks, so this is one that I can have the team look into. Jack On Mon, Nov 24, 2014 at 5:56 AM, Juan Mojica wrote: > Was there any progress made on DCB? > > We need a way to classify specific flows from the application and mark > them with a priority. Not only do we need a bit of work on the driver, but > also a way to tag frames all the way down to the driver. I imagine this > would entail a socket option to mark a given flow and a mbuf flag to carry > the request for priority classification to the driver. > > -Juan > > On Wed, Feb 6, 2013 at 5:53 AM, Randall Stewart wrote: > >> Lars/Jack: >> >> I am pretty sure that my company would be interested in it as well.. and >> I can >> help out here too ;-) >> >> Jack: are there particular versions of Intel cards that this needs to >> be on (we have both igb and ix cards in my office now).. thanks. >> >> R >> >> >> On Jan 22, 2013, at 10:43 AM, Eggert, Lars wrote: >> >> > Hi, >> > >> > on Linux, various NICs (e.g., ixgbe) support Data Center Bridging. Is >> this also available under FreeBSD? Do *any* NICs support DCB under FreeBSD? >> > >> > Thanks, >> > Lars >> > _______________________________________________ >> > freebsd-net@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >> > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > >> >> ------------------------------ >> Randall Stewart >> 803-317-4952 (cell) >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > > > > -- > Juan Mojica > Email: jmojica@gmail.com > From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 16:27:57 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F84D4FA for ; Mon, 24 Nov 2014 16:27:57 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5CE8B89 for ; Mon, 24 Nov 2014 16:27:56 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id r20so6415176wiv.8 for ; Mon, 24 Nov 2014 08:27:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=suAarfXYg+lklP3fy4qPxcy7r6KRiHYngei2AfNjbIs=; b=c9Oy5naB+wfBkDxxzp5q2RES3ErirC0KHXuOZM/AHQAG5B5MkBE0+JBXbFOIFaM9ZN EJrO77A3XbTGj0aSwrlFvRaM2aGfyQFMqn8Qq7ZRPzvtW9Qweenn8jO7Jzj1dp18ahCL eZ/wTUJlZdxMrkR93IHV+pQB4xADfWLWfck3DCcb+1C7CG1gEP3E2EJj9Khd5XGIyn9L hgHQEYAQGarfWzJTlS5IDI3hTKYcLH7z+3YpqfCSomN1qmfSbQL+ASd65Wfc2mkewcMj ZSSxM9GPZ9PBZDklVpvv1c2HsfObXxHxwRe5HEfuCmoLJyhLG9xSF9TaF0sglTuzxHjK XrWg== MIME-Version: 1.0 X-Received: by 10.194.24.103 with SMTP id t7mr15746287wjf.15.1416846475184; Mon, 24 Nov 2014 08:27:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Mon, 24 Nov 2014 08:27:55 -0800 (PST) In-Reply-To: <20141124141234.GG30752@tweddell.de> References: <20141124141234.GG30752@tweddell.de> Date: Mon, 24 Nov 2014 08:27:55 -0800 X-Google-Sender-Auth: m69zYsO5OYlArSxrfURGTMFBqSE Message-ID: Subject: Re: iwn fails to scan on E6330 From: Adrian Chadd To: Bastian Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 16:27:57 -0000 Hi! You need to create wlan0 first before you use it. # ifconfig wlan0 create wlandev iwn0 # ifconfig wlan0 up # ifconfig wlan0 list scan (bringing it 'up' will start scanning) -a On 24 November 2014 at 06:12, Bastian wrote: > Hi all, > > I have to say, the BSD world is quite new to me. It peeked my interest > long time ago, but a week a ago I was brave enough to give it a try on a > real physical box. A Latitude E6330. > > In general the installation was straight forward. For now I just face > troubles with GPT (another topic) and iwn. > > Here is what my machine has: > ----- > root@zam709:~ # pciconf -lv iwn0 > iwn0@pci0:2:0:0: class=0x028000 card=0x13218086 chip=0x00828086 rev=0x34 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Centrino Advanced-N 6205 [Taylor Peak]' > class = network > > root@zam709 ~ 0 > 59 # kldstat -v | grep iwn > 158 pci/iwn > 17 1 0xffffffff820cc000 52db4 iwn1000fw.ko (/boot/kernel/iwn1000fw.ko) > 509 iwn1000fw_fw > 18 1 0xffffffff8211f000 ad28f iwn2030fw.ko (/boot/kernel/iwn2030fw.ko) > 510 iwn2030fw_fw > 19 1 0xffffffff821cd000 2e58a iwn4965fw.ko (/boot/kernel/iwn4965fw.ko) > 511 iwn4965fw_fw > 20 1 0xffffffff821fc000 53a21 iwn5000fw.ko (/boot/kernel/iwn5000fw.ko) > 512 iwn5000fw_fw > 21 1 0xffffffff82250000 52d42 iwn5150fw.ko (/boot/kernel/iwn5150fw.ko) > 513 iwn5150fw_fw > 22 1 0xffffffff822a3000 6f71e iwn6000fw.ko (/boot/kernel/iwn6000fw.ko) > 514 iwn6000fw_fw > 23 1 0xffffffff82313000 a5d05 iwn6000g2afw.ko (/boot/kernel/iwn6000g2afw.ko) > 515 iwn6000g2afw_fw > 24 1 0xffffffff823b9000 70fc2 iwn6000g2bfw.ko (/boot/kernel/iwn6000g2bfw.ko) > 516 iwn6000g2bfw_fw > 25 1 0xffffffff8242a000 73265 iwn6050fw.ko (/boot/kernel/iwn6050fw.ko) > > > root@zam709:~ # ifconfig iwn0 > iwn0: flags=8802 metric 0 mtu 2290 > ether 6c:88:14:18:fb:d0 > nd6 options=21 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > > root@zam709:~ # time ifconfig iwn0 up scan > ifconfig: unable to get scan results > 0.007u 0.028s 0:00.03 66.6% 370+400k 2+0io 0pf+0w > > root@zam709:~ # uname -a > FreeBSD zam709 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 > root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > ----- > > From the logs above you can see that the kernel has a built in module > for iwn and the firmwares are loaded. The kernel sees the interface and > I can bring it up. But when trying to scan for available BSSs, the scan > command return immediately without success (exit 1). > > Right now I suspect the firmware is somehow wrongly configured. But I > cannot find any logs about firmwares in the logs. > > Q: What is the proper procedure to debug a startup of the iwn module? > > Coming from the linux administration, I failed to gain knowledge how the > firmware is handeled. I tried to enable different sets of firmware > which were to enable just single firmware and up to enable all availabel > firmwares. I used kldload/unload for this. > > Q: When are the firmwares getting effectively used? Meaning, how does > dynamically loading/unloading a firmware change the bahaviour of the > module? > or > When does a module expect a firmware to be available and does it > accepts a runtime cahnge of the firmware? > > Q: As the iwn module is compiled into the kernel, how can I restart > this inorder it might read in the firmware again? > > Other questions I have: > > Q: Which is the poper firmware for my wireless device? > > > > Many thanks, > -- > Bastian > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Mon Nov 24 17:03:57 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B17AB2B9; Mon, 24 Nov 2014 17:03:57 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 60DA4FD1; Mon, 24 Nov 2014 17:03:56 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id sAOH3i8Z014319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 24 Nov 2014 09:03:46 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <547364EB.7090505@freebsd.org> Date: Tue, 25 Nov 2014 01:03:39 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Bjoern A. Zeeb" , Craig Rodrigues Subject: Re: RFC: Enabling VIMAGE in GENERIC References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> <20141119195923.GS24601@funkthat.com> <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> In-Reply-To: <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: FreeBSD Net , Marko Zec , "freebsd-virtualization@freebsd.org" , freebsd-arch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 17:03:57 -0000 On 11/20/14, 8:33 AM, Bjoern A. Zeeb wrote: > On 19 Nov 2014, at 23:14 , Craig Rodrigues wrote: > >> On Wed, Nov 19, 2014 at 11:59 AM, John-Mark Gurney wrote: >> >>> Yes, we need a man page talking about this feature first, how to enable >>> it, compile it into the kernel, how to manage it, what subsystems it >>> interacts w/, what sysctl nodes it provides, etc. >>> >> Marko, >> >> Do you have any text which can be put into a vnet(9) man page? >> It doesn't have to be perfect, but just something that we can start from. >> >> I tried looking at some of the notes and presentations that you have done >> on VIMAGE: >> https://wiki.freebsd.org/?action=fullsearch&context=180&value=VIMAGE&titlesearch=Titles >> >> but didn’t see anything that could be readily turned into a man page. > > https://people.freebsd.org/~bz/20100530-02.vnet.9.html > > The man page should be in that perforce branch you converted to github. also look at the following: (a little dated) http://p4web.freebsd.org/@md=d&cd=//depot/projects/vimage/&cdf=//depot/projects/vimage/porting_to_vimage.txt&c=tO0@//depot/projects/vimage/porting_to_vimage.txt?ac=22 > > — > Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > > From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 00:42:31 2014 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CF8336D3 for ; Tue, 25 Nov 2014 00:42:31 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7BACCE3 for ; Tue, 25 Nov 2014 00:42:31 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAP0gVIR078328 for ; Tue, 25 Nov 2014 00:42:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0 Date: Tue, 25 Nov 2014 00:42:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jrm@ftfl.ca X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 00:42:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967 Joseph Mingrone changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrm@ftfl.ca --- Comment #16 from Joseph Mingrone --- I just upgraded our storage server from 9.3 to 10.1 and we're now seeing this problem as well. This is what we had in /etc/rc.conf: cloned_interfaces="lagg0" ifconfig_lagg0="laggproto lacp laggport em0 laggport em1 laggport em2 laggport em3 192.168.0.102/24" I'll also attach a screenshot of ifconfig -a. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 00:58:18 2014 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BCBCA18 for ; Tue, 25 Nov 2014 00:58:18 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 23FE5E17 for ; Tue, 25 Nov 2014 00:58:18 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAP0wIwe024831 for ; Tue, 25 Nov 2014 00:58:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0 Date: Tue, 25 Nov 2014 00:58:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jrm@ftfl.ca X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 00:58:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967 --- Comment #17 from Joseph Mingrone --- Screenshots: https://picasaweb.google.com/104346539473598376650/LaggProblems?authuser=0&authkey=Gv1sRgCKjvr5q29ouZLg&feat=directlink -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 01:17:48 2014 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1CD357E for ; Tue, 25 Nov 2014 01:17:48 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7141FEB for ; Tue, 25 Nov 2014 01:17:47 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id g10so8576142pdj.23 for ; Mon, 24 Nov 2014 17:17:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8NaqJhUIoXVRwACwQ80RnwpXwkoM4djemJWN9n748jw=; b=lmILo+n66MF+eQBwlxyDFO/ruFiHCSQeSx6n1ic6S9omRoRbW+w7jklKva9R3QzqB9 Pvf2eketdIoWdytFZAErE+XmczHLeDvlIUIMFl38Vv9Ms7HwTCYlWk03KTpCdGzPZ6Z1 Lg2VKSlV8hxuAAohZb0VtxL0whtNvpg9YhD+6BauRkQ4OCpaBRRibir5fpvofYqYdOeF PK87BL1rzPGxogdDxlLiRp+DT/K/1bvnj/YPS9Azzt/IzSh+669kxc9j2BmXsVTMMFZV ZM3zEnxxUVDhAUpA7BhsHeT5Haxif/pWAhOOhLOy11DKXxS0ga5F9WuBfWM5u8k4fQdP bP7Q== MIME-Version: 1.0 X-Received: by 10.68.65.16 with SMTP id t16mr37956211pbs.70.1416878267456; Mon, 24 Nov 2014 17:17:47 -0800 (PST) Received: by 10.70.42.198 with HTTP; Mon, 24 Nov 2014 17:17:47 -0800 (PST) In-Reply-To: References: <20141117193354.T31139@sola.nimnet.asn.au> Date: Tue, 25 Nov 2014 09:17:47 +0800 Message-ID: Subject: Re: dragonflybsd's ipfw From: bycn82 To: Sato Kentney Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Ian Smith , FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 01:17:48 -0000 *that ipfw2 means "ipfw too", because it is originally from FreeBSD and totally not new create things, IMHO* *BTW Sato, I think the in-kernel NAT is almost there, I tested the basic NAT and it works in my lab environment.* On Tue, Nov 18, 2014 at 9:38 AM, Sato Kentney wrote= : > i agree, > i am not good in english as networking administor from Tokyo. > but when i read the page, i see that the main idea is so call "modular > design" and there is a long way to catch up the freebsd's ipfw > > anyway, i dont think it can compare to freebsd's ipfw, as Smith said thei= r > ipfw is the version without in-kernel NAT and tables .all these important > features > > On Mon, Nov 17, 2014 at 5:07 PM, Ian Smith wrote: > > > On Mon, 17 Nov 2014 15:48:13 +0800, Sato Kentney wrote: > > > > > I saw a email in dragonflybsd email list, someone is doing this! > > > http://www.dragonflybsd.org/docs/ipfw2/ > > > > We've had 'ipfw2' for a very long while. I couldn't help wondering why > > DF wouldn't just import our many years of development and experience > > rather than using bycn82's 'rewrite'? .. but DF already has ipfw2: > > > > http://leaf.dragonflybsd.org/cgi/web-man?command=3Dipfw§ion=3DANY > > > > man page dated October 2008. Before tables, in-kernel NAT, later > > dummynet updates and no doubt more. So why not start from there? > > > > cheers, Ian > > > > > > -- > =E3=81=82=E3=82=8A=E3=81=8C=E3=81=A8=E3=81=86 > =E4=BD=90=E8=97=A4=E6=9F=AF=E5=BE=B7 > Sato K. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 08:57:13 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28AED124 for ; Tue, 25 Nov 2014 08:57:13 +0000 (UTC) Received: from smtp31.i.mail.ru (smtp31.i.mail.ru [94.100.177.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 906DE763 for ; Tue, 25 Nov 2014 08:57:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=kR+I5y3SJ3J3yonAhTicjCkJ9QgVG6J4oIy5GKmyb0Y=; b=CuKSlOuJ/H08RG5Q2tp8GBC/pEW6HKinfiNoZMzJsPFGemasAKcuZhyHQn0xW1JoDI80w5UgCh5V7TS3QBNFyZALcpRA2FpJhlnK/agLYil4OcnJ9h6eUgqUVS9sb/iG20ltUBVZ7HWP36reClAcLom22XeYVRpKLPdR2Nq1/Ao=; Received: from [2001:67c:13e4:1000::37] (port=17728 helo=work.lehis.ru) by smtp31.i.mail.ru with esmtpa (envelope-from ) id 1XtBvo-0004ob-LD; Tue, 25 Nov 2014 11:57:08 +0300 Message-ID: <54744463.3090102@mail.ru> Date: Tue, 25 Nov 2014 11:57:07 +0300 From: "Alexey V. Panfilov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: IPMI stops respond if boot in single user mode References: <546F1A96.1060309@mail.ru> <54735857.2010209@mail.ru> In-Reply-To: <54735857.2010209@mail.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Spam: Not detected X-Mras: Ok X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 08:57:13 -0000 24.11.2014 19:09, Alexey V. Panfilov wrote: > 21.11.2014 13:57, Alexey V. Panfilov wrote: >> Hi, >> >> My IBM System x3250 M5 has IPMI. It shares onboard NIC Broadcom BCM5719. >> I'm setup it and IPMI works perfectly. >> But when server boots in single user mode IPMI's IP becomes unreachable. >> It occures when bge0 init. >> >> Any hints? >> >> Thanks. >> >> >> Details are: >> >> FreeBSD 10.1-STABLE (r274690) amd64 >> >> /boot/loader.conf >> hw.bge.allow_asf=1 >> >> >> bge0: > 0x5719001> mem >> 0x82a50000-0x82a5ffff,0x82a40000-0x82a4ffff,0x82a30000-0x82a3ffff irq 16 >> at device 0.0 on pci6 >> bge0: APE FW version: NCSI v1.2.33.0 >> bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E >> miibus0: on bge0 >> brgphy0: PHY 1 on miibus0 >> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow >> bge0: Using defaults for TSO: 65518/35/2048 >> bge0: Ethernet address: 6c:ae:8b:5b:74:98 >> >> >> bge0@pci0:6:0:0: class=0x020000 card=0x04911014 chip=0x165714e4 >> rev=0x01 hdr=0x00 >> vendor = 'Broadcom Corporation' >> device = 'NetXtreme BCM5719 Gigabit Ethernet PCIe' >> class = network >> subclass = ethernet >> bar [10] = type Prefetchable Memory, range 64, base 0x82a50000, >> size 65536, enabled >> bar [18] = type Prefetchable Memory, range 64, base 0x82a40000, >> size 65536, enabled >> bar [20] = type Prefetchable Memory, range 64, base 0x82a30000, >> size 65536, enabled >> cap 01[48] = powerspec 3 supports D0 D3 current D0 >> cap 03[50] = VPD >> cap 05[58] = MSI supports 8 messages, 64 bit enabled with 1 message >> cap 11[a0] = MSI-X supports 17 messages >> Table in map 0x20[0x0], PBA in map 0x20[0x1000] >> cap 10[ac] = PCI-Express 2 endpoint max data 128(256) FLR link x2(x4) >> speed 5.0(5.0) ASPM disabled(L0s/L1) >> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected >> ecap 0003[13c] = Serial 1 00006cae8b5b7498 >> ecap 0004[150] = Power Budgeting 1 >> ecap 0002[160] = VC 1 max VC0 >> >> > > When it boots in single-user mode and manually run: > > #ifconfig bge0 up > > then ipmi become accessable. > > How it can be fixed automatically after system is boot in single-user mode? > > man 8 loader says that it can be done by add line to /boot/loader.conf: init_script="/boot/ifup.sh" #cat /boot/ifup.sh #!/bin/sh /sbin/ifconfig bge0 up It doesn't remove the root of trouble, but it's better than nothing. -- Best regards, Alexey V. Panfilov From owner-freebsd-net@FreeBSD.ORG Tue Nov 25 21:32:00 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 834BAD21; Tue, 25 Nov 2014 21:32:00 +0000 (UTC) Received: from tweddell.vserver-on.de (tweddell.de [84.38.66.62]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49414B15; Tue, 25 Nov 2014 21:31:59 +0000 (UTC) Received: from bastian by tweddell.vserver-on.de with local (Exim 4.80) (envelope-from ) id 1XtNiA-0007tp-OZ; Tue, 25 Nov 2014 22:31:50 +0100 Date: Tue, 25 Nov 2014 22:31:50 +0100 From: Bastian To: Adrian Chadd Subject: Re: iwn fails to scan on E6330 Message-ID: <20141125213150.GH30752@tweddell.de> References: <20141124141234.GG30752@tweddell.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2014 21:32:00 -0000 On 24Nov14 08:27 -0800, Adrian Chadd wrote: > You need to create wlan0 first before you use it. > > # ifconfig wlan0 create wlandev iwn0 > # ifconfig wlan0 up > # ifconfig wlan0 list scan (bringing it 'up' will start scanning) > Many thanks. I skiped that one while reading the manual. But now it works well. May I assume, that you can create multiple wlan\d devices on one and the sane iwn0 kernel device? Now, I have wpa_supplicant working, in a way that it is automatically searching for an available wifi network. This is triggered in the /etc/rc.conf file during boot. I may have some follow-up questions: Q: service netif stop, shuts everything down, but the wpa_supplicant process withstands from going down and starts to loop 100% cpu cyles :/ Q: How can I just shutdown a single network interface? Keeping others up and with the adjustment of the default routing. Many thanks in advance, -- Bastian From owner-freebsd-net@FreeBSD.ORG Wed Nov 26 01:10:17 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6446E960 for ; Wed, 26 Nov 2014 01:10:17 +0000 (UTC) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E91462FA for ; Wed, 26 Nov 2014 01:10:16 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id h11so10952762wiw.7 for ; Tue, 25 Nov 2014 17:10:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Kvj+Y3PiQiXMjna9N7Kg4I+7onSBDAjd/HFcECYgGqo=; b=CAZgMo17TEDvXWMxdAgIGrCTirIaaNUekCY9JsU/mx+XTjP+dcHco2F/180SXjhDWj g4n9eAnzmwlRWd5cypH4qulnCGjPtDg2uQs5ByI7Z8xTw/RBACbuNL3KbB4IamV28mmN KXpUS5Eum2pIbooy3gnPnPK6pciNllJ8NjggFz4ig2NOj/mXmjPXLxRlnFDacRJ4dR6h X67pZFOrfQeZLi/n7nOMlv6iL/fbSuoqVnWSkQxzToGaluh7YmLYf411oOjBl7UBrH6u fTt/N/URkr9SgvrGcq99x+flXCZy65vv7FCDOFH+I7OKKKL0hp0K3Z+zJjBFpryQ3Zfl vDUw== MIME-Version: 1.0 X-Received: by 10.194.24.103 with SMTP id t7mr23901730wjf.15.1416964215210; Tue, 25 Nov 2014 17:10:15 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.106.136 with HTTP; Tue, 25 Nov 2014 17:10:15 -0800 (PST) In-Reply-To: <20141125213150.GH30752@tweddell.de> References: <20141124141234.GG30752@tweddell.de> <20141125213150.GH30752@tweddell.de> Date: Tue, 25 Nov 2014 17:10:15 -0800 X-Google-Sender-Auth: M8a8s4yrrF7PkHoFVyR8bR4AYn8 Message-ID: Subject: Re: iwn fails to scan on E6330 From: Adrian Chadd To: Bastian Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2014 01:10:17 -0000 The framework exists so NICs that allow multiple virtual interfaces can. The iwn driver currently doesn't support this - it only supports one. I'm not sure about why wpa_supplicant is chewing so much CPU time and why it isn't shut down cleanly. You can use service to shut down a single interface - I don't recall why. Try service netif stop wlan0 ? -a On 25 November 2014 at 13:31, Bastian wrote: > On 24Nov14 08:27 -0800, Adrian Chadd wrote: >> You need to create wlan0 first before you use it. >> >> # ifconfig wlan0 create wlandev iwn0 >> # ifconfig wlan0 up >> # ifconfig wlan0 list scan (bringing it 'up' will start scanning) >> > > Many thanks. I skiped that one while reading the manual. But now it > works well. > > May I assume, that you can create multiple wlan\d devices on one and the > sane iwn0 kernel device? > > > Now, I have wpa_supplicant working, in a way that it is automatically > searching for an available wifi network. This is triggered in the > /etc/rc.conf file during boot. > > I may have some follow-up questions: > > Q: service netif stop, shuts everything down, but the wpa_supplicant > process withstands from going down and starts to loop 100% cpu cyles > :/ > > Q: How can I just shutdown a single network interface? Keeping others > up and with the adjustment of the default routing. > > > Many thanks in advance, > > -- > Bastian From owner-freebsd-net@FreeBSD.ORG Wed Nov 26 21:38:00 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BAD578EE for ; Wed, 26 Nov 2014 21:38:00 +0000 (UTC) Received: from kozubik.com (kozubik.com [216.218.240.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EB48792 for ; Wed, 26 Nov 2014 21:38:00 +0000 (UTC) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.14.3/8.14.3) with ESMTP id sAQLRgfT073450 for ; Wed, 26 Nov 2014 13:27:42 -0800 (PST) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.14.3/8.14.3/Submit) with ESMTP id sAQLRaVh073447 for ; Wed, 26 Nov 2014 13:27:36 -0800 (PST) (envelope-from john@kozubik.com) Date: Wed, 26 Nov 2014 13:27:36 -0800 (PST) From: John Kozubik To: freebsd-net@freebsd.org Subject: Does anyone want to work on sshuttle for FreeBSD ? (bounty or paid consulting) Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2014 21:38:00 -0000 Hello, I'm very interested in getting sshuttle[1] working on FreeBSD. Currently, however, it only sort of works. TCP works fine, but UDP does not work at all, which means that DNS requests cannot be sent through the tunnel. If anyone is interested in looking into this and fixing sshuttle so that UDP works properly with sshuttle on FreeBSD, I would be willing to pay you to do that work. Please do respond to me off-list if this interests you. Thanks, John Kozubik [1] https://github.com/apenwarr/sshuttle From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 18:15:48 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F9AD7E8 for ; Fri, 28 Nov 2014 18:15:48 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [67.212.89.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2D85FB6 for ; Fri, 28 Nov 2014 18:15:47 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 8A429139CB for ; Fri, 28 Nov 2014 16:06:00 -0200 (BRST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-transfer-encoding:content-type:content-type:subject :subject:to:mime-version:user-agent:from:from:date:date :message-id; s=dkim; t=1417197955; x=1418061956; bh=+ypuOtmec3zV SrjwC4ZnRo669p8Mlyhcvk04qVun2Xo=; b=kHEubnXp64oIGo2YL2tt9CCMRj1D eUXPOwi9OPUjogoyVmHTxGXRN0HFRiuVKy7A4vMH+ZdPs+QM7xDru4ZXGUuOQK6Q 86WGOCG0D8nNkoYNQyBFmE448YjjG6eVv8NWeDFuSCE//X6rR6uid5p/KBp55VFI QIbagvn68JjvwdU= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYqBNHg81h54 for ; Fri, 28 Nov 2014 16:05:55 -0200 (BRST) Received: from [192.168.88.15] (unknown [186.193.48.8]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id 8D414139CA for ; Fri, 28 Nov 2014 16:05:55 -0200 (BRST) Message-ID: <5478B971.8090705@bsdinfo.com.br> Date: Fri, 28 Nov 2014 16:05:37 -0200 From: Marcelo Gondim User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "freebsd-net >> FreeBSD Net" Subject: IPv6 - traceroute6 not working Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2014 18:15:48 -0000 Hi all, I have IPv6 deployed here in ISP and everything works normally. Today I was testing a traceroute and it did not work. Below an example: (root@rt01)[~]# ping6 ipv6.google.com PING6(56=40+8+8 bytes) 2001:xxxx:2001:1001::96 --> 2800:3f0:4001:813::1004 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=0 hlim=60 time=6.449 ms 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=1 hlim=60 time=6.266 ms 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=2 hlim=60 time=6.340 ms 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=3 hlim=60 time=6.410 ms ^C --- ipv6.l.google.com ping6 statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 6.266/6.366/6.449/0.070 ms (root@rt01)[~]# traceroute6 ipv6.google.com traceroute6 to ipv6.l.google.com (2800:3f0:4001:813::1004) from 2001:xxxx:2001:1001::96, 64 hops max, 12 byte packets (root@rt01)[~]# uname -a FreeBSD rt01.xxxxx.com.br 10.1-RELEASE FreeBSD 10.1-RELEASE #2 r274375: Tue Nov 11 10:24:44 BRST 2014 root@rt01.xxxxx.com.br:/usr/obj/usr/src/sys/GONDIM10 amd64 Must enable some sysctl or may be a bug? Best regards, Gondim From owner-freebsd-net@FreeBSD.ORG Fri Nov 28 18:57:10 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60B33138 for ; Fri, 28 Nov 2014 18:57:10 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [67.212.89.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 301A4627 for ; Fri, 28 Nov 2014 18:57:10 +0000 (UTC) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 99883139CB for ; Fri, 28 Nov 2014 16:57:21 -0200 (BRST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-transfer-encoding:content-type:content-type :in-reply-to:references:subject:subject:to:mime-version :user-agent:from:from:date:date:message-id; s=dkim; t= 1417201037; x=1418065038; bh=IEMEksalLZ2jh80pATMGLZJll88CV7NOIoW FqnetM4Q=; b=jxFZRXX/RXAEzbFRCUdIgVHTW02C3r5xJHal2q+2Nnn/DjSkgoq nhv3PY/rCvObw66eHWRf0aECP+aE2tU5jDkQsmKlEpkck9frQpubebSIG/V+NAdk FJjEvTxLnQ3kn420SsDUEG5fo7CaKvRgbHCJQxwuJyofjbleZ69zV6gM= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7LHajWHqW5f for ; Fri, 28 Nov 2014 16:57:17 -0200 (BRST) Received: from [192.168.88.15] (unknown [186.193.48.8]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id 74757139CA for ; Fri, 28 Nov 2014 16:57:16 -0200 (BRST) Message-ID: <5478C575.1090008@bsdinfo.com.br> Date: Fri, 28 Nov 2014 16:56:53 -0200 From: Marcelo Gondim User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: IPv6 - traceroute6 not working References: <5478B971.8090705@bsdinfo.com.br> In-Reply-To: <5478B971.8090705@bsdinfo.com.br> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2014 18:57:10 -0000 On 28/11/2014 16:05, Marcelo Gondim wrote: > Hi all, > > I have IPv6 deployed here in ISP and everything works normally. Today > I was testing a traceroute and it did not work. Below an example: > > (root@rt01)[~]# ping6 ipv6.google.com > PING6(56=40+8+8 bytes) 2001:xxxx:2001:1001::96 --> > 2800:3f0:4001:813::1004 > 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=0 hlim=60 time=6.449 ms > 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=1 hlim=60 time=6.266 ms > 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=2 hlim=60 time=6.340 ms > 16 bytes from 2800:3f0:4001:813::1004, icmp_seq=3 hlim=60 time=6.410 ms > ^C > --- ipv6.l.google.com ping6 statistics --- > 4 packets transmitted, 4 packets received, 0.0% packet loss > round-trip min/avg/max/std-dev = 6.266/6.366/6.449/0.070 ms > > (root@rt01)[~]# traceroute6 ipv6.google.com > traceroute6 to ipv6.l.google.com (2800:3f0:4001:813::1004) from > 2001:xxxx:2001:1001::96, 64 hops max, 12 byte packets > > (root@rt01)[~]# uname -a > FreeBSD rt01.xxxxx.com.br 10.1-RELEASE FreeBSD 10.1-RELEASE #2 > r274375: Tue Nov 11 10:24:44 BRST 2014 > root@rt01.xxxxx.com.br:/usr/obj/usr/src/sys/GONDIM10 amd64 > > Must enable some sysctl or may be a bug? Sorry my fault!!! The problem was firewall rules. (root@rt01)[~]# ipfw add 1 allow ipv6-icmp from any to any 00001 allow ipv6-icmp from any to any (root@rt01)[~]# traceroute6 ipv6.google.com traceroute6 to ipv6.l.google.com (2800:3f0:4001:812::100e) from 2001:xxxx:2001:1001::96, 64 hops max, 12 byte packets 1 2001:xxxx:2001:1001::95 0.588 ms 0.494 ms 0.447 ms 2 2001:4860:1:1:0:ddd:0:3e 6.648 ms 6.570 ms 6.767 ms 3 2001:4860::1:0:4f24 17.159 ms 18.648 ms 6.919 ms 4 2001:4860:0:1::7c3 7.257 ms 6.688 ms 7.041 ms 5 2800:3f0:4001:812::15 6.664 ms 6.568 ms 6.730 ms Cheers, From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 08:55:31 2014 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41E8D17D for ; Sat, 29 Nov 2014 08:55:31 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 29518C38 for ; Sat, 29 Nov 2014 08:55:31 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAT8tVnk095030 for ; Sat, 29 Nov 2014 08:55:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 191468] [vimage] options VIMAGE + Infiniband - kernel panic, crashes during system boot Date: Sat, 29 Nov 2014 08:55:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rodrigc@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2014 08:55:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191468 Craig Rodrigues changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[vimage] options VIMAGE - |[vimage] options VIMAGE + |kernel panic, crashes |Infiniband - kernel panic, |during system boot |crashes during system boot -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-net@FreeBSD.ORG Sat Nov 29 09:28:59 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 169D6AE4; Sat, 29 Nov 2014 09:28:59 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84E97EDD; Sat, 29 Nov 2014 09:28:58 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id gm9so6722193lab.12 for ; Sat, 29 Nov 2014 01:28:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nOk/8cDzD87G+NOCc1gE5lBPOJzp7QitMiSZ38qjqEM=; b=yygMI2Y6x6B1LeOnyGMIOJYBX/Mm6Yb5TRmVIpsHP0aXzhb/6m1B00Ka57TnbKk30m CVnHTgZ0CtW/0NAzIqeXRcyWNrvV3CjM6dv/3olqLHIgRFfm1Z2KA3jLzxJvZQFIZlxS l4XiZ0yORrlwWnXDQCa57HSgfFS+7nMxY5Wtu2RBeLhKphl8WxvH1jXzd4OtAUmbHH4q iBRAi4yrNfqnS4h20L/lklGcWnhs5Xxt1g6rmx9GvDAwVoAlGlYDqmciMdQKl2F9beAR aVHJyXH7H4gve469BgNErhiVH6dRD+wriX/oNzOp2h4AVdZaxXh4tTN02Awng7nMDXs5 ji1w== MIME-Version: 1.0 X-Received: by 10.152.88.44 with SMTP id bd12mr32125249lab.88.1417253335677; Sat, 29 Nov 2014 01:28:55 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sat, 29 Nov 2014 01:28:55 -0800 (PST) In-Reply-To: <547364EB.7090505@freebsd.org> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> <20141119195923.GS24601@funkthat.com> <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> <547364EB.7090505@freebsd.org> Date: Sat, 29 Nov 2014 01:28:55 -0800 X-Google-Sender-Auth: INz4Aba9egH0dYwnkJ6vYYSijMk Message-ID: Subject: Re: RFC: Enabling VIMAGE in GENERIC From: Craig Rodrigues To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2014 09:28:59 -0000 On Mon, Nov 24, 2014 at 9:03 AM, Julian Elischer wrote: > > > also look at the following: (a little dated) > > http://p4web.freebsd.org/@md=d&cd=//depot/projects/vimage/&cdf=//depot/projects/vimage/porting_to_vimage.txt&c=tO0@//depot/projects/vimage/porting_to_vimage.txt?ac=22 This is a useful document. I put it on the wiki: https://wiki.freebsd.org/VIMAGE/porting-to-vimage -- Craig