Rob Benwell recommends this site
Your friend Rob Benwell(instantprof...@yahoo.com) has recommended this site to you, and sends you the following message: Hello Friend, GUARANTEED!: Get your $778.83 instantprofit Commissions Now!!! Underground Automated Method Allows 19 Years Old Kid Blogger To Raid The Market For $23.6 Million And Takes Complete Newbie To $37,730 In Just 30 Days It Doesn\'t Matter If You\'ve Never Even Earned A Single Cent Online Before... If A Total Beginner Can Make $37,730 In His First Month Then Anyone Can Do This... Imagine waking up at 10 in the morning.. doing your short workout routine.. opening your computer..and finding out you made $100 up to $200 - while you were a sleep! It\'s Easy To Make Money Everyday Even If You\'re Starting From Scratch With Zero Knowledge, Experience Or Budget!I\'ll Show You Exactly How. We\'ve Start putting New 39 Members in YOUR TEAM for the January 1th-20th 2011 commission cycle... and GROWING everyday earn by $100 up to $200 or more. IMPORTANT: January 20, 2011 is the Cut-Off day to lock in your position then faster you act the higher commission you will earn!!! Go Here To Secure not less than $778.83 commission Now and it still growing as many people joining under you. if you secure your position right away: The $778.83 commission will Arrive Through your Paypal or Credit Card on February 20/2011 next month. Hurry\'this limited time, only 8 days remaining Positions are available Now. You will access your money in any ATM when you join early & follow the instructions you receive. Click below!! https://www.plimus.com/jsp/redirect.jsp?contractId=2896494&referrer=lanielami TYPE DATE & TIME --- NEW MEMBERS --- COUNTRY P -- JAN.3 @ 2:38 AM-Dianna Rosebilt- United States P -- JAN.3 @ 2:53 AM-JOan-- Jacckson United Kingdom P -- JAN.3 @ 2:56 AM-Mandene -- Jecob Germany M -- JAN.3 @ 4:19 AM-Cristy Chan- Hungary P -- JAN.3 @ 4:28 AM-Carlo- Wonder--- Italy M -- JAN.2 @ 6:01 AM-lalaine--- ferguson- Australia P -- JAN.2 @ 7:11 AM-Rebecca--- Underwood Canada P -- JAN.2 @ 7:39 AM-Jericho--- Morales-- Mexico P -- JAN.2 @ 9:42 AM-Thomas Silva --- California M -- JAN.2 @ 9:58 PM-Grace- Taylor--- Singapore P -- JAN.2 @ 10:21 PM-Gina-- Henry New Zealand P -- JAN.1 @ 11:24 PM-Mohammed-- Ahmen --- Oman M -- JAN.1 @ 11:33 PM-Tracia Furlong-- Puerto Rico P -- JAN.1 @ 11:41 PM-Jane-- Mckay Russia P -- JAN.1 @ 9:42 AM-Steve- Scott --- Netherlands M -- JAN.1 @ 9:58 PM-Greg-- Stanley-- Denmark P -- JAN.1 @ 10:21 PM-Jack-- Perkins-- Amsterdam P -- JAN.1 @ 11:24 PM-Arlene Tan - China M -- JAN.1 @ 11:33 PM-Andy-- Hopekins- New York P -- JAN.1 @ 11:41 PM-Jhon-- Robinson- United States M -- JAN.1 @ 2:34 AM --- Kevin- Hunt Sweden P -- JAN.1 @ 12:34 AM --- Delia- Lane New York P -- JAN.1 @ 6:45 AM --- Mohamed--- Suhail--- Saudi Arabia M -- JAN.1 @ 5:34 AM --- Aleks- Gjuroski Japan P -- JAN.1 @ 12:34 PM --- Andrew Karim --- England P -- JAN.1 @ 8:23 AM --- Carla- Pereira - South Korea P -- JAN.1 @ 2:34 PM --- Carl-- Krause -- India M -- JAN.1 @ 9:14 AM --- David- Cook Denmark P - JAN.1 @ 7:46 AM --- Paul-- Amid Taiwan P -- JAN.1 @ 1:54 AM --- Dennis Wilkins - Findland P -- JAN.1 @ 12:34 AM --- Jonathan-- Wangyu -- Thailand P -- JAN.1 @ 6:45 AM --- Mackie Anhui Indonesia M -- JAN.1 @ 5:34 AM --- Alexis Mathew -- Jerosalim P -- JAN.1 @ 8:23 AM --- Cheryl Moran --- Philippines P -- JAN.1 @ 2:34 PM --- Vergie Petter -- Ingland M -- JAN.1 @ 9:14 AM --- Tito-- Warren -- Bangladish P - JAN.1 @ 7:46 AM --- Raul-- Strogher United States Therefore, you have a GUARANTEED $778.83 CommissionS every month from now on!. Earn $19.97 Per Process!Each $19.97 x 39 = $778.83 Commission will be yours...! Be Sure to Copy the link below & Paste into your browser and press enter: To Secure your $778.83 commission! You will access your money in any ATM when you follow the instructions you receive. https://www.plimus.com/jsp/redirect.jsp?contractId=2896494&referrer=lanielami Big Chance to you ,Becuase $19.97 membership only automatic back to you,Guaranteed you can recieve lifetime commissions every 20th of the month. Today its $778.83 For the start of the month of January if goes up daily until the end of the month. You must UPGRADE right away or before others do Caring for Your Success, Rob Benwell https://kap7waterpolo.com/proddetail.php?prod=kap103Junior ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "
Re: kern/126742: [panic] kernel panic when sending file via ng_ubt(4)
The following reply was made to PR kern/126742; it has been noted by GNATS. From: Alex <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: kern/126742: [panic] kernel panic when sending file via ng_ubt(4) Date: Fri, 22 Aug 2008 22:27:39 GMT >Submitter-Id: current-users >Originator: Alex >Organization: >Confidential: no >Synopsis: Re: kern/126742: [panic] kernel panic when sending file via >ng_ubt(4) >Severity: serious >Priority: medium >Category: kern >Class:sw-bug >Release: 7-STABLE >Environment: FreeBSD moshnroll 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Aug 19 >21:20:04 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARUNDEL i386 >Description: ok. one last try. i'll simply attach the dmesg output as a file. >How-To-Repeat: >Fix: Patch attached with submission follows: Copyright (c) 1992-2008 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 7.0-STABLE #0: Tue Aug 19 21:20:04 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARUNDEL WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz (2997.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fd Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x2010 AMD Features2=0x1 Cores per package: 2 real memory = 2146304000 (2046 MB) avail memory = 2086535168 (1989 MB) ACPI APIC Table: ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7fde (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc07f mem 0xf600-0xf6ff,0xe000-0xefff,0xf400-0xf5ff irq 16 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] uhci0: port 0xe200-0xe21f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe000-0xe01f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe100-0xe11f irq 18 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xf8205000-0xf82053ff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered pcm0: mem 0xf820-0xf8203fff irq 22 at device 27.0 on pci0 pcm0: [ITHREAD] pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 atapci0: port 0xd000-0xd007,0xd100-0xd103,0xd200-0xd207,0xd300-0xd303,0xd400-0xd40f mem 0xf800-0xf8001fff irq 19 at device 0.0 on pci3 atapci0: [ITHREAD] atapci0: AHCI called from vendor specific driver atapci0: AHCI Version 01.00 controller with 2 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] pcib4: irq 16 at device 28.4 on pci0 pci4: on pcib4 uhci3: port 0xe300-0xe31f irq 23 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xe400-0xe41f irq 19 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered uhci5: port 0xe500-0xe51f irq 18 at device 29.2 on pci0 uhci5: [GIANT-LOCKED] uhci5: [ITHREAD] usb6: on uhci5 usb6: USB revision 1.0 uhub6: on usb6 uhub6: 2 ports with 2 removable, self powered ehci1: mem 0xf8204000-0xf82043ff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb7: EHCI version 1.0 usb7: companion controllers, 2 ports each: usb4 usb5 usb6 usb7: on ehci1 usb
Re: kern/126742: [panic] kernel panic when sending file via ng_ubt(4)
The following reply was made to PR kern/126742; it has been noted by GNATS.
From: Alex <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/126742: [panic] kernel panic when sending file via ng_ubt(4)
Date: Sat, 23 Aug 2008 02:13:27 GMT
>Submitter-Id: current-users
>Originator: Alex
>Organization:
>Confidential: no
>Synopsis: Re: kern/126742: [panic] kernel panic when sending file via
>ng_ubt(4)
>Severity: serious
>Priority: medium
>Category: kern
>Class:sw-bug
>Release: 7-STABLE
>Environment: FreeBSD moshnroll 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Aug 19
>21:20:04 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARUNDEL i386
>Description:
is there a reason that the problem report database ignores any text if there's
a line with a single dot (".") and nothing else in it?
i know that in 'mail' that's the way to end your text, but as you can see it's
not very useful in the case of this problem report.
cheers.
>How-To-Repeat:
>Fix:
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/126742: [panic] kernel panic when sending file via ng_ubt(4)
The following reply was made to PR kern/126742; it has been noted by GNATS.
From: Alex <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc:
Subject: Re: kern/126742: [panic] kernel panic when sending file via ng_ubt(4)
Date: Sat, 23 Aug 2008 08:21:45 GMT
>Submitter-Id: current-users
>Originator: Alex
>Organization:
>Confidential: no
>Synopsis: Re: kern/126742: [panic] kernel panic when sending file via
>ng_ubt(4)
>Severity: serious
>Priority: medium
>Category: kern
>Class:sw-bug
>Release: 7-STABLE
>Environment: FreeBSD moshnroll 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Aug 19
>21:20:04 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARUNDEL i386
>Description:
this should work. i simply replaced the lines with a single dot (".") in it
with "DOT".
--- dmesg begins here ---
Copyright (c) 1992-2008 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 7.0-STABLE #0: Tue Aug 19 21:20:04 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARUNDEL
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz (2997.02-MHz 686-class
CPU)
Origin = "GenuineIntel" Id = 0x6fd Stepping = 13
Features=0xbfebfbff
Features2=0xe39d
AMD Features=0x2010
AMD Features2=0x1
Cores per package: 2
real memory = 2146304000 (2046 MB)
avail memory = 2086535168 (1989 MB)
ACPI APIC Table:
ioapic0: Changing APIC ID to 2
ioapic0 irqs 0-23 on motherboard
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 7fde (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
pcib1: irq 16 at device 1.0 on pci0
pci1: on pcib1
vgapci0: port 0xc000-0xc07f mem
0xf600-0xf6ff,0xe000-0xefff,0xf400-0xf5ff irq 16 at
device 0.0 on pci1
nvidia0: on vgapci0
vgapci0: child nvidia0 requested pci_enable_busmaster
vgapci0: child nvidia0 requested pci_enable_io
nvidia0: [GIANT-LOCKED]
nvidia0: [ITHREAD]
uhci0: port 0xe200-0xe21f irq 16 at device
26.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: on uhci0
usb0: USB revision 1.0
uhub0: on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: port 0xe000-0xe01f irq 21 at device
26.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: on uhci1
usb1: USB revision 1.0
uhub1: on usb1
uhub1: 2 ports with 2 removable, self powered
uhci2: port 0xe100-0xe11f irq 18 at device
26.2 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: on uhci2
usb2: USB revision 1.0
uhub2: on usb2
uhub2: 2 ports with 2 removable, self powered
ehci0: mem 0xf8205000-0xf82053ff irq 18 at
device 26.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: on ehci0
usb3: USB revision 2.0
uhub3: on usb3
uhub3: 6 ports with 6 removable, self powered
pcm0: mem
0xf820-0xf8203fff irq 22 at device 27.0 on pci0
pcm0: [ITHREAD]
pcib2: irq 16 at device 28.0 on pci0
pci2: on pcib2
pcib3: irq 19 at device 28.3 on pci0
pci3: on pcib3
atapci0: port
0xd000-0xd007,0xd100-0xd103,0xd200-0xd207,0xd300-0xd303,0xd400-0xd40f mem
0xf800-0xf8001fff irq 19 at device 0.0 on pci3
atapci0: [ITHREAD]
atapci0: AHCI called from vendor specific driver
atapci0: AHCI Version 01.00 controller with 2 ports detected
ata2: on atapci0
ata2: [ITHREAD]
ata3: on atapci0
ata3: [ITHREAD]
ata4: on atapci0
ata4: [ITHREAD]
pcib4: irq 16 at device 28.4 on pci0
pci4: on pcib4
uhci3: port 0xe300-0xe31f irq 23 at device
29.0 on pci0
uhci3: [GIANT-LOCKED]
uhci3: [ITHREAD]
usb4: on uhci3
usb4: USB revision 1.0
uhub4: on usb4
uhub4: 2 ports with 2 removable, self powered
uhci4: port 0xe400-0xe41f irq 19 at device
29.1 on pci0
uhci4: [GIANT-LOCKED]
uhci4: [ITHREAD]
usb5: on uhci4
usb5: USB revision 1.0
uhub5: on usb5
uhub5: 2 ports with 2 removable, self powered
uhci5: port 0xe500-0xe51f irq 18 at device
29.2 on pci0
uhci5: [GIANT-LOCKED]
uhci5: [ITHREAD]
usb6: on uhci5
usb6: USB revision 1.0
uhub6: on usb6
uhub6: 2 ports with 2 removable, self powered
ehci1: mem 0xf8204000-0xf82043ff irq 23 at
device 29.7 on pci0
ehci1: [GIANT-LOCKED]
ehci1: [ITHREAD]
usb7: EHCI version 1.0
usb7: companion controllers, 2 ports each: usb4 usb5 usb6
usb7: on ehci1
usb7: USB revi
Re: kern/129022: [ath] ath cannot connect using WEP
The following reply was made to PR kern/129022; it has been noted by GNATS. From: Alex <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Subject: Re: kern/129022: [ath] ath cannot connect using WEP Date: Fri, 28 Nov 2008 12:26:59 GMT >Submitter-Id: current-users >Originator: Alex >Organization: >Confidential: no >Synopsis: Re: kern/129022: [ath] ath cannot connect using WEP >Severity: serious >Priority: high >Category: kern >Class:sw-bug >Release: 8-CURRENT >Environment: FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #8 r185353M: >Thu Nov 27 01:48:42 CET 2008 [EMAIL >PROTECTED]:/usr/obj/usr/src/sys/ARUNDEL i386 >Description: could somebody please have a look at this? just tell me if you need more debug output and i'll provide it. right now i have to connect to my router using no encryption at all which obviously is far from save. thanks in advance. >How-To-Repeat: >Fix: ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gif(4) and bpf(4)
Hello, Since we see ESP traffic directly on the ep0 interface, packets are not going through gif0 as stated in the routing table. IPsec SPD is overriding the routing table, can you check (provide us) with setkey -DP and setkey -D if no SPD is present from your net to 192.168.4.0/24 ? Regards, Alex. Yes they are (network on the other side of the tunnel is 192.168.4.0/24) : %%% yoda:tools# netstat -rnf inet Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire defaultUGSc 24 17513460ep0 [...] 192.168.4 192.168.4.13 UGSc0 691911 gif0 192.168.4.13 192.168.1.1UH 3 6949 gif0 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NDP Proxying Issue
Hi, I am running FreeBSD 12.1-RELEASE on DigitalOcean, where my Droplet is assigned 16 IPv6 addresses (2604::0 --> 2604::f). I would like it to respond to neighbor solicitation requests from DO, even though the IP being solicited is not bound to any interface on the machine. Based on my research, this is exactly what NDP proxying is for, which is configured by the "ndp" tool. I already have one IPv6 address fully operational, and I see it listed in the output of "ndp -a" (IPs redacted): 2604::1 12:34:56:78:90:ff vtnet0 permanent R "12:34:56:78:90:ff" is the MAC address of vtnet0, the main public-facing interface of the machine. I have executed the following command: ndp -s 2604::2 12:34:56:78:90:ff proxy leading to the following output from "ndp -a": 2604::2 12:34:56:78:90:ff vtnet0 permanent R p This indicates to me that NDP proxying for this IP has been set up properly. When running tcpdump on vtnet0, and after attempting to connect to 2604::2 from a remote machine, I see the following: 02:25:04.068528 IP6 fe80::1 > ff02::2: ICMP6, neighbor solicitation, who has 2604::2, length 32 The ISP is properly asking if my machine has that address, however I never see a neighbor advertisement in response. Based on the fact that the "ndp -s" command succeeded and the entry is listed, why would this be? I have pf disabled. I am not aware of any sysctl variables that might prevent this from working. Regards, Alex ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
no free() after malloc() in arp (src/usr.sbin/arp/arp.c)
hi there, i don't see a security issue in this, just want to ask if this is ok (or maybe unwanted?): in src/usr.sbin/arp/arp.c in function search() (starts line ~429) i see this (line ~447): if ((buf = malloc(needed)) == NULL) got from: http://www.FreeBSD.org/cgi/cvsweb.cgi/src/usr.sbin/arp/arp.c?rev=1.29&conte nt-type=text/x-cvsweb-markup which should be latest version(?) this allocated memory isn't free'd later in this function. so if arp uses this function over and over again, memory fills up (not much, but it does). i just came to this, because i used this search() function while playing around with ip -> mac translation and my test programm suddenly had ~60MB memory usage :) alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: natd, 2 NIC's, 2 Hubs, Something I'm missing?
hi, i have a fbsd 4.3 box with natd acting as a router too. unfortunately i did all the natd and ipfw stuff in my own rc.firewall script. but here my suggestions: - kernel options seems to be ok for natd - in rc.conf remove the 'natd_flags="-f /etc/natd.conf"' line in NATD section (or do you have anything special in this file..?). remove the whole 'router_*' section (you probably don't need routing when doing nat). - as you have the 'gateway_enable=YES' in your rc.conf, net.inet.ip.forwarding should already be enabled (done by rc.network if gateway_enable=yes) and anything should be fine, well i hope so :) i'm just worried about your ifconfig output for dc0, hat it really hw_addr of ff:ff:ff:ff:ff:ff ? unusual i think..?? greetings, alex --On Samstag, 26. Mai 2001 21:32 -0500 Brandt <[EMAIL PROTECTED]> wrote: > Hello all, this has got me stumped. > > FreeBSD 4.3 > vr0: ip= 65.3.111.111 subnet 255.255.255.0 > dc0: ip= 192.168.1.1 subnet 255.255.255.0 > > Kernel has been recompiled with IPDIVERT and IPFIREWALL options, > and every thing WORKS fine as long as I have both NIC's pluged into the > SAME hub. > > But shouldn't this also work when the vr0 interface is moved to a > seperate hub? So that the internet interface and the LAN interface > (dc0) are on seperate networks? > > The strange thing is that as soon as I unplug the 65.3.*.* interface from > the hub, the other 192.168.1.* boxes can't ping the dc0, 192.168.1.1 > interface even though they are still connected to the same hub. At the > same time, the dc0 interface can still ping the other LAN boxen on the > 192.168 network. > > Any ideas as to what is going on? > > - Brandt > ## My Kernel ## > options IPDIVERT > optionsIPFIREWALL > > ## /etc/rc.conf ## > sendmail_enable="YES" > sshd_enable="YES" > inetd_enable="YES" > gateway_enable="YES" > network_interfaces="vr0 lo0 dc0" > ifconfig_vr0="inet 65.3.111.111 netmask 255.255.255.0" > defaultrouter="65.3.111.1" > ifconfig_dc0="inet 192.168.1.1 netmask 255.255.255.0" > hostname="myhostname.mydomain.com" > > #NATD > natd_enable="YES" > natd_interface="vr0" > natd_flags="-f /etc/natd.conf" > > #FIREWALL > firewall_enable="YES" > firewall_script="/etc/rc.firewall" > firewall_type="open" > firewall_quiet="NO" > firewall_logging="YES" > firewall_flags="" > > #ATTEMPT TO CORRECT ROUTING TABLE > router_enable="YES" > router="routed" > router_flags="-s" > > ## ifconfig ## > dc0: flags=8843 mtu 1500 > inet 192.168.1.1 netmask 0x broadcast 192.168.255.255 > inet6 fe80::280:c8ff:fee8:58fe%dc0 prefixlen 64 scopeid 0x1 > ether ff:ff:ff:ff:ff:ff > media: autoselect (100baseTX ) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP none vr0: > flags=8843 mtu 1500 inet > 65.3.111.111 netmask 0xff00 broadcast 65.3.111.255 inet6 > fe80::280:c8ff:fee8:58fe%vr0 prefixlen 64 scopeid 0x2 ether > 00:80:c8:e8:58:fe > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 100baseTX 100baseTX > 10baseT/UTP 10baseT/UTP none > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Apache/TCP stack issues
On Wed, 13 Mar 2002, Dmitry Koltsov wrote: > I have some issues with TCP stack and/or Apache. Issue: I'm getting > "Connection refused" error when trying to connect to Apache over > Internet when packet loss is 1-2%. Not all connection attempts fail but > about 3% of attempts. When I'm trying to connect over local network(from > another machine and localhost) in the same time, all is ok. In order to > get this statistics, I've made 2 attempts from each place in the > same time. Some thoughts for you: > 00:55:24.794637 195.252.103.127.4389 > 216.65.107.31.80: S 15459564:15459564(0) win >8192 (DF) > 00:55:24.794720 216.65.107.31.80 > 195.252.103.127.4389: S 2478638582:2478638582(0) >ack 15459565 win 33232 (DF) > 00:55:26.521535 216.65.107.31.80 > 195.252.103.127.4389: R 1:1(0) ack 1 win 33232 >(DF) A major note that the source port (4389) is the same for many queries. This is not normal. Local port should not be reused until X time has passed. (X being at least time for TCP connection to go from TIME_WAIT to closed). I'm not sure what FreeBSD's policy on outgoing port reuse is, but this is definitely a problem. Why is it a problem: Since the tuple that identifies the connection is (sourceIP, sourcePort, destIP, destPort), which would be same for many of your TCP connections, server will consider this to be a syn-spoofing attack. Here's the logic: First connection (everything is good, seq1 and seq2 are sequence numbers) client.4389->server.80 SYN (seq1) server.80 ->client.4389 SYN ACK (seq2) ...some time passes... server.80 ->client.4389 RST client.4389->server.80 RST Now, assume that the RST from client got lost, following exchange: client.4389->server.80 SYN (seq3) server.80 ->client.4389 SYN ACK (seq4) ...some time passes... server.80 ->client.4389 RST client.4389->server.80 RST (LOST!) Now, on the server, the connection is still in TIME_WAIT state. On client, connection is gone, and the client immediately reuses the local port. Now, next connection: client.4389->server.80 SYN (seq5) Now, server is thinking "WTF? the sequence number doesn't match up for an _existing_ connection", and sends you back an RST, which is exactly what you are seeing. So, a question: Are you doing anything funky to cause local port reuse? I don't know what freebsd does, and haven't looked at RFC whether there's a requirement NOT to reuse port until at least TCP_FIN_TIMEOUT (or whatever's freebsd equivalent sysctl is) time passes, but it appears that it would be the right thing to do. -alex > 00:55:27.813385 195.252.103.127.4389 > 216.65.107.31.80: S 15459564:15459564(0) win >8192 (DF) > 00:55:27.813485 216.65.107.31.80 > 195.252.103.127.4389: S 2939404798:2939404798(0) >ack 15459565 win 33232 (DF) > 00:55:27.994115 195.252.103.127.4389 > 216.65.107.31.80: . ack 3834201081 win 8576 >(DF) > 00:55:27.994156 216.65.107.31.80 > 195.252.103.127.4389: R 2478638583:2478638583(0) >win 0 > 00:55:28.042403 195.252.103.127.4389 > 216.65.107.31.80: P 1:309(308) ack 3834201081 >win 8576 (DF) > 00:55:28.042466 216.65.107.31.80 > 195.252.103.127.4389: R 2478638583:2478638583(0) >win 0 > 00:55:28.217906 195.252.103.127.4389 > 216.65.107.31.80: R 15459565:15459565(0) win 0 > > > 00:55:26.893251 151.27.40.210.1560 > 216.65.107.31.80: S 37780527:37780527(0) win >8192 (DF) > 00:55:26.893329 216.65.107.31.80 > 151.27.40.210.1560: S 2578149080:2578149080(0) >ack 37780528 win 33232 (DF) > 00:55:27.300599 216.65.107.31.80 > 151.27.40.210.1560: R 1:1(0) ack 1 win 33232(DF) > 00:55:27.316952 151.27.40.210.1560 > 216.65.107.31.80: . ack 1 win 8576 (DF) > 00:55:27.317038 216.65.107.31.80 > 151.27.40.210.1560: R 2578149081:2578149081(0) >win 0 > 00:55:27.467521 151.27.40.210.1560 > 216.65.107.31.80: P 1:369(368) ack 1 win 8576 >(DF) > 00:55:27.467567 216.65.107.31.80 > 151.27.40.210.1560: R 2578149081:2578149081(0) >win 0 > > > 00:38:52.468064 194.85.102.167.46350 > 216.65.107.31.80: S 1156823521:1156823521 (0) >win 16384 (DF) > 00:38:52.468137 216.65.107.31.80 > 194.85.102.167.46350: S 4104358926:4104358926 (0) >ack 1156823522 win 33580 (DF) > 00:38:55.462633 216.65.107.31.80 > 194.85.102.167.46350: S 4104358926:4104358926 (0) >ack 1156823522 win 33580 (DF) > 00:38:57.544738 216.65.107.31.80 > 194.85.102.167.46350: R 1:1(0) ack 1 win 33580 >(DF) > > > Best regards, > Dmitry Koltsov > Host On Fly S.A. > tel: + 7 812 9404403 > tel: + 41 78 8286002 > fax: + 1 775 2426205 > ICQ: 44656213 > mailto:[EMAIL PROTECTED] > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Diagnose co-location networking problem
On Tue, 26 Dec 2006, Stephan Wehner wrote: > Most of the times I find the server responds nicely. But periodically it > doesn't respond properly when accessing its webpages: Type URL in > browser, hit return, no page appears. Try again and again and after a > few times it appears. DNS. try tcpdump -n -alex ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Diagnose co-location networking problem
On Tue, 26 Dec 2006, Stephan Wehner wrote: > Ok, thanks, I now ran tcpdump with -n. > > Here I am testing with a little script that continuously accesses one of > the pages. Right at the beginning it doesn't get very far: first > response after 90 seconds. > > What kind of DNS problem did you have in mind? Sorry, this doesn't seem to be DNS.. It may be something related to link/autonegotiation, or it could be something beyond your control, on the Internet between the two hosts in question. Are you able to do a traceroute when your connections fail? Where does the trace stop? -alex ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
X710 stalled TX Queue and loss of networking
Hello, DATA We are running FreeBSD 13.2-RELEASE-p9 #25 on top of several Dell R650 (Example Service Tag: 8FKQRY3). The system is running bhyve for other FreeBSD Virtual Machines. All these servers have X710-DA4 Fiber Network cards (4 port of SFP+). dev.ixl.0.%desc: Intel(R) Ethernet Controller X710 for 10GbE SFP+ - 2.3.3-k dev.ixl.0.fw_version: fw 9.840.76614 api 1.15 nvm 9.40 etid 8000e9b5 oem 225632.7 Some servers have an additional X710-DA2 (same card but with 2 ports) for extra fiber ports. ISSUE Periodically, the networking will stop working on individual interfaces. During packet capture we can see that the networking card is receiving traffic, but no traffic is being set out. During further investigation we found that ixl interface TX queue is getting into STALLED mode. [user@server ~]$ sysctl dev.ixl | grep ring_state dev.ixl.5.iflib.txq0.ring_state: pidx_head: 0751 pidx_tail: 0751 cidx: 0751 state: IDLE dev.ixl.4.iflib.txq0.ring_state: pidx_head: 1254 pidx_tail: 1254 cidx: 1254 state: IDLE dev.ixl.3.iflib.txq0.ring_state: pidx_head: 1193 pidx_tail: 1193 cidx: 1195 state: STALLED dev.ixl.2.iflib.txq0.ring_state: pidx_head: pidx_tail: cidx: state: IDLE dev.ixl.1.iflib.txq0.ring_state: pidx_head: 1393 pidx_tail: 1393 cidx: 1395 state: STALLED dev.ixl.0.iflib.txq0.ring_state: pidx_head: 0181 pidx_tail: 0181 cidx: 0183 state: STALLE RESOLUTIONS TRIED * Factory resetting the system (not a permanent fix, issue comes back) * Recreating Netowrking interfaces invluding VLANs (not a permanent fix, issue comes back) * Updating the driver with Dell iDRAC to the latest official QUESTION Is there anything else we can try to get this permanently resolved? Best Regards, Alex
Wallclock vs monotonic time in v6 expiry times?
Hi, I've been looking around in the IPv6 code recently and I noticed that time_second seems to be the clock of choice for calculating expiry times for prefixes, routers and addresses. Is there any specific reason it uses wall clock time and not time_uptime as this makes more sense to me? I'm referring to the kernel's internal representation of these expiry times, rather than what's exposed via sysctls. As an example, dr0.expire = time_second + dr0.rtlifetime; taken from sys/netinet6/nd6_rtr.c from nd6_ra_input. AlexY ___ 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: Wallclock vs monotonic time in v6 expiry times?
Thanks Chuck for the quick response, On 19 February 2013 18:51, Chuck Swiger wrote: > > Sequence #s, retry timers, etc do better if based off of wall clock time > than if based off of uptime because realtime persists in moving forward but > uptime gets reset if the host crashes/reboots. > > RFC-793 discusses "Quiet Time" concept for TCP, but it applies elsewhere. > > I take your point that it doesn't hurt to use wall clock time always assuming sensible clock stability on your system, as with Quiet Time optimizations and DHCP leases (to pick two examples) anything else wouldn't make sense. However is there any specific reason in the case of v6 prefixes and default routers to do this? As as far as I can tell the kernel does not store these expiry times in non-volatile storage, and neither does rtsold. I don't think it matters if it's monotonic time or not here, as long as you do the appropriate conversion when passing these values up to userland. If you wanted to persist prefixes/default routers across a crash/boot you could do all of this in userland with a modified rtsold or similar, much like with DHCP leases. Or am I missing something? AlexY ___ 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"
Create pkey on FreeBSD 9.1
Hello. I have FreeBSD 9.1 installed. There is mellanox adapter inside. OFED support is already installed. I try to add pkeys on ib0 port. Usually in Linux I did: echo 0x800c > /sys/class/net/ib0/create_child ifconfig -a To Make sure you see a new interface: ib0.800c How can I do it on FreeBSD? There is no "/sys/class/net/ib0/create_child" directory. Regards, Alex Liptsin ___ 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"
How to switch Datgram/Connected mtu modes?
Hello. I work with FreeBSD 9.1 and Mellanox devices. How can I configure MTU in connected mode on FreeBSD 9.1? In Linux to enable connected mode for interface ib0, I enter: echo connected > /sys/class/net/ib0/mode Switching between CM and UD mode can be done in run time: echo datagram > /sys/class/net/ib0/mode sets the mode of ib0 to UD echo connected > /sys/class/net/ib0/mode sets the mode ib0 to CM There is no such directories at FreeBSD. Wat shall I do? Datagram vs Connected modes The IPoIB driver supports two modes of operation: datagram and connected. The mode is set and read through an interface's /sys/class/net//mode file. In datagram mode, the IB UD (Unreliable Datagram) transport is used and so the interface MTU has is equal to the IB L2 MTU minus the IPoIB encapsulation header (4 bytes). For example, in a typical IB fabric with a 2K MTU, the IPoIB MTU will be 2048 - 4 = 2044 bytes. In connected mode, the IB RC (Reliable Connected) transport is used. Connected mode takes advantage of the connected nature of the IB transport and allows an MTU up to the maximal IP packet size of 64K, which reduces the number of IP packets needed for handling large UDP datagrams, TCP segments, etc and increases the performance for large messages. In connected mode, the interface's UD QP is still used for multicast and communication with peers that don't support connected mode. In this case, RX emulation of ICMP PMTU packets is used to cause the networking stack to use the smaller UD MTU for these neighbours. Thanks a lot Regards, Alex Liptsin Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> ___ 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"
Create bond on Infiniband ports
Hi. I use FreeBSD 9.1 with OFED compiled on it. There is a Mellanox adapter: [root@qa-h-vrt-030-006 ~]# pciconf -lv |grep mlx4 -A 3 mlx4_core0@pci0:0:5:0: class=0x028000 card=0x005015b3 chip=0x100315b3 rev=0x00 hdr=0x00 vendor = 'Mellanox Technologies' device = 'MT27500 Family [ConnectX-3]' class = network I want to create Bond on the two ports (ib0 and ib1) of this device: [root@qa-h-vrt-030-006 ~]# ifconfig em0: flags=8843 metric 0 mtu 1500 options=209b ether 00:50:56:23:1e:06 inet6 fe80::250:56ff:fe23:1e06%em0 prefixlen 64 scopeid 0x2 inet 10.195.30.6 netmask 0x broadcast 10.195.255.255 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 nd6 options=23 ib0: flags=8043 metric 0 mtu 65520 options=80018 lladdr 80.0.0.48.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.51 inet 11.195.30.1 netmask 0x broadcast 11.195.255.255 inet6 fe80::250:56ff:fe23:1e06%ib0 prefixlen 64 scopeid 0x4 nd6 options=23 ib1: flags=8043 metric 0 mtu 65520 options=80018 lladdr 80.0.0.49.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.52 inet 12.195.30.1 netmask 0x broadcast 12.195.255.255 inet6 fe80::250:56ff:fe23:1e06%ib1 prefixlen 64 scopeid 0x5 nd6 options=23 1. Is there "bond" in FreeBSD or its "Lagg"? 2. I tried to create this way, but failed: [root@qa-h-vrt-030-006 ~]# ifconfig lagg0 create root@qa-h-vrt-031-005 conf]# ifconfig lagg0 laggproto failover laggport ib0 laggport ib1 ifconfig: SIOCSLAGGPORT: Protocol not supported Any ideas? Is it supported on Infiniband ports? Regards, Alex Liptsin ___ 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: Create pkey on FreeBSD 9.1
Hi John. I did it, but there is no ping between the vlans. Ping without VLANs on that ports pass. Host1: [root@qa-h-vrt-030-006 ~]# ifconfig ib0.100 create [root@qa-h-vrt-030-006 ~]# ifconfig ib0.100 11.195.30.1/16 up [root@qa-h-vrt-030-006 ~]# ifconfig em0: flags=8843 metric 0 mtu 1500 options=209b ether 00:50:56:23:1e:06 inet6 fe80::250:56ff:fe23:1e06%em0 prefixlen 64 scopeid 0x2 inet 10.195.30.6 netmask 0x broadcast 10.195.255.255 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 nd6 options=23 ib0: flags=8043 metric 0 mtu 65520 options=80018 lladdr 80.0.0.48.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.51 inet6 fe80::250:56ff:fe23:1e06%ib0 prefixlen 64 scopeid 0x4 nd6 options=23 ib1: flags=8002 metric 0 mtu 65520 options=80018 lladdr 80.0.0.49.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.52 nd6 options=23 ib0.100: flags=8003 metric 0 mtu 65520 options=80018 lladdr 80.0.0.4a.fe.80.0.0.0.0.0.0.0.2.c9.0.1.0.d0.51 inet6 fe80::8200:4a:fe80:0%ib0.100 prefixlen 64 scopeid 0x6 inet 11.195.30.1 netmask 0x broadcast 11.195.255.255 nd6 options=23 vlan: 100 parent interface: ib0 Host2: [root@qa-h-vrt-031-005 ~]# ifconfig ib0.100 create [root@qa-h-vrt-031-005 ~]# ifconfig ib0.100 11.195.31.1/16 up [root@qa-h-vrt-031-005 ~]# ifconfig em0: flags=8843 metric 0 mtu 1500 options=209b ether 00:50:56:23:1f:05 inet6 fe80::250:56ff:fe23:1f05%em0 prefixlen 64 scopeid 0x2 inet 10.195.31.5 netmask 0x broadcast 10.195.255.255 nd6 options=23 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 nd6 options=23 ib0: flags=8043 metric 0 mtu 65520 options=80018 lladdr 80.0.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.a0.65.91 inet6 fe80::250:56ff:fe23:1f05%ib0 prefixlen 64 scopeid 0x4 nd6 options=23 ib1: flags=8002 metric 0 mtu 65520 options=80018 lladdr 80.0.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.a0.65.92 nd6 options=23 ib0.100: flags=8003 metric 0 mtu 65520 options=80018 lladdr 80.0.0.4a.fe.80.0.0.0.0.0.0.0.2.c9.3.0.a0.65.91 inet6 fe80::8200:4a:fe80:0%ib0.100 prefixlen 64 scopeid 0x6 inet 11.195.31.1 netmask 0x broadcast 11.195.255.255 nd6 options=23 vlan: 100 parent interface: ib0 [root@qa-h-vrt-031-005 ~]# ping 11.195.30.1 PING 11.195.30.1 (11.195.30.1): 56 data bytes ping: sendto: Network is down ping: sendto: Network is down ping: sendto: Network is down Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel -Original Message- From: John Baldwin [mailto:j...@freebsd.org] Sent: Wednesday, May 29, 2013 9:17 PM To: freebsd-net@freebsd.org Cc: Ryan Stone; Alex Liptsin Subject: Re: Create pkey on FreeBSD 9.1 On Thursday, May 23, 2013 2:36:25 pm Ryan Stone wrote: > On Thu, May 23, 2013 at 4:32 AM, Alex Liptsin wrote: > > > Hello. > > > > I have FreeBSD 9.1 installed. > > There is mellanox adapter inside. > > OFED support is already installed. > > > > I try to add pkeys on ib0 port. > > > > Usually in Linux I did: > > > > echo 0x800c > /sys/class/net/ib0/create_child > > > > ifconfig -a > > To Make sure you see a new interface: ib0.800c > > > > How can I do it on FreeBSD? There is no "/sys/class/net/ib0/create_child" > > directory. > > > > Regards, > > Alex Liptsin > > > > ___ > > 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" > > > > From reading the source it looks like this is done by attaching a vlan > interface to the interface. So try: > > ifconfig vlan create vlandev ib0 vlan 0xc > > This will create a new vlanX interface (ifconfig will its precise name > with its unit number to stdout). Simpler though is just 'ifconfig ib0.12 create' (and how most folks expect subinterfaces to be named). -- John Baldwin ___ 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"
How to compile ipoib module manually?
RealTek RTL8150 USB Ethernet device udav# Davicom DM9601E USB # USB Wireless device rum # Ralink Technology RT2501USB wireless NICs device run # Ralink Technology RT2700/RT2800/RT3000 NICs. device uath # Atheros AR5523 wireless NICs device upgt # Conexant/Intersil PrismGT wireless NICs. device ural # Ralink Technology RT2500USB wireless NICs device urtw # Realtek RTL8187B/L wireless NICs device zyd # ZyDAS zd1211/zd1211b wireless NICs # FireWire support device firewire # FireWire bus code # sbp(4) works for some systems but causes boot failure on others #devicesbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) device fwip # IP over FireWire (RFC 2734,3146) device dcons # Dumb console driver device dcons_crom# Configuration ROM for dcons # Sound support device sound # Generic sound driver (required) device snd_cmi # CMedia CMI8338/CMI8738 device snd_csa # Crystal Semiconductor CS461x/428x device snd_emu10kx # Creative SoundBlaster Live! and Audigy device snd_es137x # Ensoniq AudioPCI ES137x device snd_hda # Intel High Definition Audio device snd_ich# Intel, NVidia and other ICH AC'97 Audio device snd_uaudio # USB Audio device snd_via8233# VIA VT8233x Audio # Mellanox and IB support options OFED # Infiniband protocol options OFED_DEBUG_INIT options SDP # Sockets Direct Protocol for infiniband options SDP_DEBUG # options IPOIB_DEBUG # options IPOIB_CM # Use connect mode ipoib device mthca # Infinihost cards # device mlx4ib # ConnectX Infiniband support #device mlxen # ConnectX Ethernet support # device ipoib # IP over IB devices I commented on that lines, because I want to compile and load that modules manually. I had succeed to compile and load mlx4, mlx4ib and mlxen from /sys/modules: [root@h-qa-033 mlxen]# kldstat Id Refs AddressSize Name 1 14 0x8020 13acbd8 kernel 21 0x81612000 21e5 if_mos.ko 33 0x81615000 124ebmlx4.ko 41 0x81628000 e225 mlx4ib.ko 51 0x81637000 ec60 mlxen.ko The problem is that IPOIB module is missing in /sys/modules. 1. Where can I find it? 2. How can I compile ipoib support? Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel ___ 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: How to compile ipoib module manually?
Thanks a lot. Alex L. Sent from my iPhone On 5 ביונ 2013, at 18:13, "John Baldwin" mailto:j...@freebsd.org>> wrote: On Tuesday, June 04, 2013 5:18:46 am Alex Liptsin wrote: I commented on that lines, because I want to compile and load that modules manually. I had succeed to compile and load mlx4, mlx4ib and mlxen from /sys/modules: [root@h-qa-033 mlxen]# kldstat Id Refs AddressSize Name 1 14 0x8020 13acbd8 kernel 21 0x81612000 21e5 if_mos.ko 33 0x81615000 124ebmlx4.ko 41 0x81628000 e225 mlx4ib.ko 51 0x81637000 ec60 mlxen.ko The problem is that IPOIB module is missing in /sys/modules. 1. Where can I find it? 2. How can I compile ipoib support? You will have to create one. You should be able to use the existing module Makefiles as a guide. -- John Baldwin ___ 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"
Mellanox NIC names changed, each kldunload/kldload mlx4ib module
Hi. I work with FreeBSD9.1 and Mellanox devices. Every time I unload / load mlx4ib module, NIC names of mellanox devices (ibX) are renamed. Can I prevent it? [root@h-qa-032 mlx4]# ifconfig ib8: flags=8002 metric 0 mtu 65520 options=80018 lladdr 80.28.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31 nd6 options=29 ib9: flags=8002 metric 0 mtu 65520 options=80018 lladdr 80.28.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32 nd6 options=29 [root@h-qa-032 mlx4]# kldunload mlx4ib [root@h-qa-032 mlx4]# kldload -v mlx4ib Loaded mlx4ib, id=9 [root@h-qa-032 mlx4]# ifconfig ib10: flags=8002 metric 0 mtu 65520 options=80018 lladdr 80.30.0.48.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.31 nd6 options=29 ib11: flags=8002 metric 0 mtu 65520 options=80018 lladdr 80.30.0.49.fe.80.0.0.0.0.0.0.0.2.c9.3.0.2e.48.32 nd6 options=29 Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel ___ 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: How to switch Datgram/Connected mtu modes?
Hi. Yes. There is no such entry. The only way I found is to compile inside the kernel " options IPOIB_CM ". Can I do it manually without compiling the kernel each time I want to switch between the modes? Maybe add it somehow to sysctl or loader.conf? Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel -Original Message- From: John Baldwin [mailto:j...@freebsd.org] Sent: Wednesday, May 29, 2013 9:17 PM To: freebsd-net@freebsd.org Cc: Alex Liptsin; freebsd-questi...@freebsd.org Subject: Re: How to switch Datgram/Connected mtu modes? On Sunday, May 26, 2013 7:43:29 am Alex Liptsin wrote: > Hello. > > I work with FreeBSD 9.1 and Mellanox devices. > > How can I configure MTU in connected mode on FreeBSD 9.1? > In Linux to enable connected mode for interface ib0, I enter: > >echo connected > /sys/class/net/ib0/mode > > > > Switching between CM and UD mode can be done in run time: > >echo datagram > /sys/class/net/ib0/mode sets the mode of ib0 to UD > >echo connected > /sys/class/net/ib0/mode sets the mode ib0 to CM > > There is no such directories at FreeBSD. Wat shall I do? Have you tried looking for dev.ib.0 sysctls? It looks like the OFED bits in FreeBSD map Linux sysfs entries to sysctl nodes, but I don't have a box with IB handy to see what it looks like at runtime. -- John Baldwin ___ 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"
Failed to allocate receive buffer problem
Hi. I have a problem that when running a ping (or any other traffic) over IPoIB port, Traffic fails after some time. At destination server DMESG I see that errors: Jun 11 14:42:11 h-qa-033 kernel: ib1: failed to allocate receive buffer 253 Jun 11 14:42:12 h-qa-033 kernel: ib1: failed to allocate receive buffer 254 Jun 11 14:42:13 h-qa-033 kernel: ib1: failed to allocate receive buffer 255 Jun 11 14:42:14 h-qa-033 kernel: ib1: failed to allocate receive buffer 0 Jun 11 14:42:15 h-qa-033 kernel: ib1: failed to allocate receive buffer 1 Jun 11 14:42:16 h-qa-033 kernel: ib1: failed to allocate receive buffer 2 Jun 11 14:42:17 h-qa-033 kernel: ib1: failed to allocate receive buffer 3 Jun 11 14:42:18 h-qa-033 kernel: ib1: failed to allocate receive buffer 4 Jun 11 14:42:19 h-qa-033 kernel: ib1: failed to allocate receive buffer 5 Jun 11 14:42:20 h-qa-033 kernel: ib1: failed to allocate receive buffer 6 Jun 11 14:42:21 h-qa-033 kernel: ib1: failed to allocate receive buffer 7 I work with FreeBSD 9.1. Is it a bug or some configuration issues? Thanks. Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel ___ 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:: How to set VLAN priority?
Hello. I work with FreeBSD 9.1 RELEASE. I had configured VLANs on my server, but I can't find a way to configure VLAN priority. How can I do it? Thanks. Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel ___ 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"
How can I remove one interface from lagg, without destroying all lagg?
Hi. I have lagg interface created on my server: [root@h-qa-094 ~]$ ifconfig lagg0 lagg0: flags=8802 metric 0 mtu 1500 options=401bb ether 00:02:c9:19:82:80 nd6 options=21 media: Ethernet autoselect status: active laggproto failover lagghash l2,l3,l4 laggport: igb1 flags=0<> laggport: mlxen1 flags=0<> laggport: mlxen0 flags=5 Now, I want to removr igb1 interface from that lag. How can I do it? Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel ___ 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 9 as PPPoE BRAS(mpd 5.7) kernel panic
Hello. We have a problem with FreeBSD 9 stable (currently on r267070) as PPPoE BRAS by mpd 5.7. Server catches 1-3 kernel panics every month. Two last core.txt's: http://pkg.hostelnet.ru/pub/dump/core.txt.7.txt (r262224) and http://pkg.hostelnet.ru/pub/dump/core.txt.8.txt (r267070) Now trying to test hint with mpd-down script from similar trhread: http://lists.freebsd.org/pipermail/freebsd-net/2014-June/038952.html Hardware: HP DL360 with Intel 82571EB nic. Average load on server: 150-300 Mbit/s and around 150 users. FreeBSD configuration: running on GENERIC kernel IPFW with few rules (no dummynet, no nat) routing via OSPF (quagga) cat /boot/loader.conf net.isr.maxthreads=2 net.isr.numthreads=2 net.graph.maxdata=65536 net.graph.maxalloc=65536 net.isr.defaultqlimit=4096 net.link.ifqmaxlen=10240 cat /etc/sysctl.conf net.inet.ip.fastforwarding=1 net.inet.ip.redirect=0 kern.random.sys.harvest.ethernet=0 kern.random.sys.harvest.point_to_point=0 kern.random.sys.harvest.interrupt=0 net.inet.raw.maxdgram=16384 net.inet.raw.recvspace=16384 net.inet.ip.intr_queue_maxlen=10240 net.route.netisr_maxqlen=4096 Maybe someone can help to understand: it is a configuration error or a bug MPD/netgraph? ___ 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: FreeBSD 9 as PPPoE BRAS(mpd 5.7) kernel panic
Hi. So, hint with mpd-down script (with "sleep 1") does not help - panic after 7 days uptime (rev r267703). If somebody want to look into last core.txt and vmcore, they are here: http://pkg.hostelnet.ru/pub/dump/core.txt.9.txt ___ 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"
Filtering on IPSEC
Hi All, I've setup my first IPSEC VPN beetween FreeBSD 8.2 and CheckPoint VPN-1. I've used a gif interface for the tunnel, setkey for security policies and racoon for ikev1. All is working fine, but I get a strange behavior: outgoing packets go via enc0, while incoming packets arrive in gif0. To be precise, setting to '3' all the net.enc.* sysctls and sending a ping via vpn, I see the echo request, the encapsulated echo request, the encapsulated echo reply on enc0 and the echo reply on gif0. Is it correct? I expected to see all 4 packets on enc0, and perhaps the 2 clear packets also on gif0. The current behavior makes impossibile to use firewall stateful filtering. I have also another question (about NAT before IPSEC), but it's partially related to this first issue, so I'll wait for a clarification before exposing it. -- Alex Dupre ___ 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: Filtering on IPSEC
Bjoern A. Zeeb ha scritto: Need more input. A) why are using gif? B) are you using transport mode? I'm using gif, because the official FreeBSD documentation says so (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html). My configuration is very similar to what described in that page. If that's not the correct way, I'll fix the documentation after understanding the right procedure. I'm using tunnel mode for network to network vpn. NAT before IPSEC can be done with ipfw, not with pf, don't know about ipfilter. Can you elaborate a little more about the reason ipfw can and pf cannot? Is it because with ipfw/nat the packet is reinjected with the translated src IP and so matched by SPD? Currently, with my setup and pf, I faced exactly these two problems (SPD match before translation and i/o on different interfaces). I think it's not so uncommon that the two networks may collide, so assigning a "good" ip to one endpoint gateway and making NAT on it should be well documentated in our handbook. If you give me a hint on how this could be achieved with ipfw I'll update the docs accordingly. Thanks for your support. -- Alex Dupre ___ 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: Filtering on IPSEC
Bjoern A. Zeeb ha scritto: If you are using tunnel mode and gif you'll have trouble; just use tunnel mode without gif and you'll be happy. Done, it works and I see all packets on enc0 now, thanks. It's because (our) pf cannot NAT on incoming but only on outgoing interfaces. And you need to NAT on packet entry into the system... I found a setup that seems to work in my scenario with pf, but I'm not sure it's 100% correct. Basically I added nat on enc0 and then added a new policy including my internal lan. Scenario: - virtual ip (where nat takes place): 172.22.0.5 - internal lan: 192.168.2.0/24 - other lan: 172.28.0.0/16 In pf.conf I added: nat on enc0 from 192.168.2.0/24 to any -> 172.22.0.5 In setkey.conf I added: spdadd 192.168.2.0/24 172.28.0.0/16 any -P out ipsec esp/tunnel/MYEXTIP-OTHEREXTIP/require; in addition to the "standard": pdadd 172.28.0.0/16 172.22.0.5/32 any -P in ipsec esp/tunnel/OTHEREXTIP-MYEXTIP/require; spdadd 172.22.0.5/32 172.28.0.0/16 any -P out ipsec esp/tunnel/MYEXTIP-OTHEREXTIP/require; I'm searching for trouble or is it correct? -- Alex Dupre ___ 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"
Strong host model in IPv6?
(Originally posted on freebsd-hackers@ - sorry) Hi all, I've been playing around with IPv6 networking on FreeBSD release 8.2 and found that there seems to be no strong incoming host model as specified in RFC 1122. I've spotted that in IPv4 there is the sysctl "net.inet.ip.check_interface" which defaults to set, but I've been unable to find any guarantees that strong host model is enforced in v6 in the comments or internet. According to the IPv6 Core Protocols Implementation book (3.7 "Input processing: ip6_input() Function") the incoming network packet processing in ip6_input should use the routing table to look up whether packets are of relevance for an interface - but the code base has diverged significantly since then including vnets for jails which makes me wonder if this is a bug. However before going into the long grass and trying to fix it I thought I'd ask here to see if there's anything I could try first, if I'm making some horrific mistakes, or if somebody had come across this already (I had a quick look at svn but didn't see anything of concern). My recipe for reproducing is thus: One FreeBSD 8.2 machine (the box under test), with 2 network interfaces (interface 0 and interface 1). interface 0 is connected to a subnet with routes to the outside world on v4 and v6. Interface 1 is connected directly via ethernet cable to the interface of a testing machine, with v4 disabled and a static v6 address for an unroutable subnet via the other interface. A route is configured for this subnet out of interface 1 (to allow for communications with the testing machine). The testing machine (which happens to be running FreeBSD) has 2 network interfaces (interface A and B). Interface A is connected to the same subnet as interface 0 (this is for my administration prodding of the testing device), and interface B is directly connected to interface 1 on the machine under test. Interface B has a staticly configured IPv6 address that matches the subnet of interface 1. It has a route to allow traffic to flow this way, *and* a route configured to route traffic for the box under tests interface 0 IPv6 address via interface B. If I ping interface 0 from box 1, I get a response. To prove that the response isn't coming in via the other links I used tcpdump on that interface on the testing machine *and* the machine under test and showed packets entering and responses leaving those interfaces. My expectation here would be to see packets entering (as the bpf hook is below the IP layer) but see no response. I checked sysctl net.inet6.ip6.forwarding is set to 0 (on both machines). Many thanks for any help AlexY ___ 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: Strong host model in IPv6?
On 10 March 2012 00:03, Doug Barton wrote: > So I guess I'll re-ask the question here: According to > https://tools.ietf.org/html/rfc1122 that RFC has been updated quite a > bit over the last 23 years. Have you followed that chain upwards to make > sure that your concerns are still valid? > > > Doug > My question is perhaps not phrased brilliantly. I shouldn't have used the word "specified" when talking about the RFC and maybe re-written my question so apologies - it's late here. To sum up, is FreeBSD intended to support the strong host model for IPv6 as described in that RFC? As my tests don't seem to show it as not doing so, which seems contrary to what the KAME book suggests. However I can't find any specific wording on this on the internet or freebsd site. If this is so, is there any sysctl or other mechanism which I've missed which enables said strong host model - or am I stuck? As you have pointed out, RFC 1122 is 23 years old and covers a lot of the basics of what IP networking is and as a result has a significant number of updating RFCs. I simply point to it for the definition of strong ES model which is not redefined, and is referenced in the FreeBSD code base for at least IPv4 in ip_input.c. Next time I'll just say "strong host model". AlexY ___ 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: Strong host model in IPv6?
On 10 March 2012 18:27, JINMEI Tatuya / 神明達哉 wrote: > I've not closely followed the most recent version of FreeBSD IPv6 > code, but the use of the routing table in ip6_input in the original > KAME implementation had nothing to do with the strong host model. It > was just for faster determination of whether an incoming packet is > destined to *any* of host's IPv6 addresses (on any interface, which > may or may not be identical to the receiving interface). > > --- > JINMEI, Tatuya > Internet Systems Consortium, Inc. > Ah! That route lookup indeed doesn't ever actually compare the interface that route is configured for. For some reason I convinced myself rtalloc filters by interface - which is clearly wrong... Sorry for misquoting your text -- that's what I get for trying to be well prepared. My question still stands though, am I crazy in trying to have a strong model for v6 (does this for some reason not make sense?), does KAME already do this and I've just missed it, or (least likely) am I right in thinking it doesn't support it and this wouldn't be crazy? Many thanks for the help so far. AlexY ___ 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"
9-STABLE + Infiniband - incorrect interface counters
Hi, I'm playing with two FreeBSD 9-STABLE boxes connected via 10Gbps Infiniband (more details below) in Infiniband connected mode. I see incorrect interface statistics (e.g. in netstat output), output counters are 2x more than expected. EXAMPLE, ftp transfer of 1 GiB file: ftp> put file /dev/null local: file remote: /dev/null 229 Entering Extended Passive Mode (|||57978|) 150 Opening BINARY mode data connection for '/dev/null'. 100% |***| 953 MiB 390.43 MiB/s 00:00 ETA 226 Transfer complete. 10 bytes sent in 00:02 (390.13 MiB/s) Netstat on receiving side, counters are correct (for input): lexa@home-gw:/home/lexa# netstat -I ib1 5 input (ib1) output packets errs idrops bytespackets errs bytes colls 0 0 0 0 0 0 0 0 13955 0 0 222688126 9027 01192796 0 48921 0 0 780832960 32129 04240596 0 0 0 0 0 0 0 80 0 Sum of bytes (input) is 1003521086, as expected. Netstat on sending size, output is 2x more: lexa@new-gw:/home/lexa# netstat -I ib0 5 input (ib0) output packets errs idrops bytespackets errs bytes colls 1 0 0100 0 0 0 0 41162 0 02305210 62878 0 2008325984 0 1 0 0100 0 0 0 0 It looks like packet count is correct (13955+48921=62876, two packets missed somewhere), while byte count is exact 2x more. More details on my setup FreeBSD 9-STABLE, cvsuped today. One box is Core 2 Quad (Q9300), second one Core i7-920 1) Device MELLANOX MHEA28-XTC 10GBPS INFINIBAND HCA CARD (two port) Boot message: ib_mthca0: mem 0xfe90-0xfe9f,0xfd00-0xfd7f irq 16 at device 0.0 on pci1 ib_mthca: Mellanox InfiniBand HCA driver v1.0-ofed1.5.2 (August 4, 2010) Two cards connected via cable, no Infiniband switch 2) Kernel config: include GENERIC options OFED options SDP device ipoib options IPOIB_CM device mthca 3) Regardles of MTU settings (tried 16000, 32000, 48000), actual packed size in tcp flow is about 16000. Have not investigated it in details 4) There is no packet loss: lexa@new-gw:/home/lexa# ping -s 32000 -c 1 -f 10.1.1.1 PING 10.1.1.1 (10.1.1.1): 32000 data bytes . --- 10.1.1.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.157/0.225/1.758/0.156 ms -- Alex Tutubalin Web: http://blog.lexa.ru mailto:l...@lexa.ru ___ 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"
[patch] Strong ES model in IPv6
Hi all, I have some questions regarding accomplishing the strong model for ingress IPv6 traffic with FreeBSD, as implemented in ip6_input.c. Does it make sense to have a strong ES model in IPv6 *at all*? I’ve yet to find any wording in the RFC’s referring to this – although nothing explicitly disallowing it. Given that addresses that are globally scoped are “global” I could understand why a stack might make the choice to not do this, as the address may be considered attached to the “system” rather than the interface. However for separating networks at a basic level this isn’t appropriate. I realise that pF is an option in this case, but arguably it’s an option in ipv4 too – so why default ipv4 to strong model? Also of note, the KAME code in NetBSD reference’s a sysctl “net.inet6.ip6.sourcecheck” which is never used, but seems to indicate an intention to implement something like this. Was the intention to implement the strong model for ingress IPv6 traffic with this switch? This patch attempts to implement the strong model using the same sysctl as in NetBSD, note that multicast listeners already handle which interface they arrive at. There’s some thought that probably needs to go into using it in combination with ip_forwarding and other sysctls, but it wasn’t too difficult given the interface address list is already traversed upfront before the routeing table lookup. Does anybody know why this is, was something else intended here? I’ve hammered my code with isic6/tcpsic6/udpsic6 for a few hours with and without listening sockets and nothing caught fire. I haven’t tried using TAHI yet although given my rig it’s a bit more complicated to setup. Any guidance is greatly appreciated. -- This patch is on release 8.2, although if necessary I can port it up if this is unacceptably old now :). It implements the “net.inet6.ip6.sourcecheck” sysctl which when set to 1 will drop packets if they’re not for addresses configured on the interface on which they arrived. This is intended to implement RFC 1122’s “Strong end system model” for IPv6. -- diff -r 8b21c9a98cbd src/sys/netinet6/ip6_input.c --- a/src/sys/netinet6/ip6_input.c Mon Apr 02 14:15:19 2012 +0100 +++ b/src/sys/netinet6/ip6_input.c Tue May 01 14:32:30 2012 +0100 @@ -80,6 +80,7 @@ #include #include #include +#include #include #include @@ -125,6 +126,11 @@ .nh_policy = NETISR_POLICY_FLOW, }; +/* Take this variable name from NetBSD, but exposing it as a sysctl */ +static unsigned ip6_sourcecheck = 0; SYSCTL_DECL(_net_inet6); +SYSCTL_UINT(_net_inet6, OID_AUTO, sourcecheck, CTLFLAG_RW, +&ip6_sourcecheck, 0, "Check packets destination address is configured +on the incoming interface RFC1122"); + VNET_DECLARE(struct callout, in6_tmpaddrtimer_ch); #defineV_in6_tmpaddrtimer_ch VNET(in6_tmpaddrtimer_ch) @@ -599,6 +605,10 @@ if (lle != NULL) LLE_RUNLOCK(lle); + /*XXX AlexY if ip6_sourcecheck is set we immediately assume it's bad*/ + if (0 != ip6_sourcecheck) + goto bad; + dst = &rin6.ro_dst; dst->sin6_len = sizeof(struct sockaddr_in6); dst->sin6_family = AF_INET6; ___ 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"
Differences in network between 6.4 and 7.3
Hello! After a upgrade from 6.4 to 7.3 it seems that we have problems with the network. On the host are running several webserver and a squid, build with openpkg. I have installed the compat package to be sure that there are no problems with the libraries after the upgrade. Now we have network latency problems, with a wiki and bugzilla running on a DomU (seperate SLES 11 host). Also we get lots of open connection on another DomU where a webcontainer is running. In this case we have unreassembled packages and lots of dup ACK in the traffic. Any idea what to do and where to search for the problem? Thanks in advance Alex ___ 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"
Virtual Network Interface Card
Hi all, I just wonder that if there are virtual nic functionalities which provides MAC address? I need to run ISC DHCP Server on 4 different IP's within one sever, however I have only 2 NICs connected to the server. I need different MAC Address for those IPs in order to run it properly, so bxn0:l styled cards won't work. Solaris VNIC will just work for me, however I would like to use FreeBSD, Alex ___ 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"
jail source address selection doesn't work?
192.168.75.3 link#9 UH 00 carp1 192.168.75.4 link#4 UHS 02lo0 192.168.80.0/24link#1 U 6 618586 bce0 192.168.80.40 link#1 UHS 0 130620lo0 192.168.80.42 link#8 UH 095987 carp0 192.168.82.0/24link#5 U 2 2361 vlan82 192.168.82.2 link#5 UHS 00lo0 192.168.82.4 link#10UH 00 carp2 Seems reasonable, yes? Pinging from the box # ping 192.168.75.59 PING 192.168.75.59 (192.168.75.59): 56 data bytes 64 bytes from 192.168.75.59: icmp_seq=0 ttl=64 time=0.993 ms 64 bytes from 192.168.75.59: icmp_seq=1 ttl=64 time=0.986 ms 64 bytes from 192.168.75.59: icmp_seq=2 ttl=64 time=0.988 ms ^C --- 192.168.75.59 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.986/0.989/0.993/0.003 ms 10:45:31.425232 IP 192.168.75.4 > 192.168.75.59: ICMP echo request, id 12430, seq 0, length 64 10:45:31.426283 IP 192.168.75.59 > 192.168.75.4: ICMP echo reply, id 12430, seq 0, length 64 10:45:32.425415 IP 192.168.75.4 > 192.168.75.59: ICMP echo request, id 12430, seq 1, length 64 10:45:32.426404 IP 192.168.75.59 > 192.168.75.4: ICMP echo reply, id 12430, seq 1, length 64 Okay, yes? From jail: # ping 192.168.75.59 PING 192.168.75.59 (192.168.75.59): 56 data bytes ^C --- 192.168.75.59 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss 10:45:52.146600 IP 83.69.203.1 > 192.168.75.59: ICMP echo request, id 14222, seq 0, length 64 10:45:53.146702 IP 83.69.203.1 > 192.168.75.59: ICMP echo request, id 14222, seq 1, length 64 Setting ip.saddrsel to 1 or 0 did not change anything. Kernel is GENERIC+ALTQ What could I miss?... Alex. ___ 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"
VRRP on VLANs: does it work?
Hello! I've run into strange problem: in non-promisc mode, two freevrrpds does not seems to see each others multicasts. Is it a bug or a feature? Alex. ___ 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: jail source address selection doesn't work?
03.03.2011 0:48, Bjoern A. Zeeb пишет: On Mon, 7 Feb 2011, Alex Povolotsky wrote: Hello! On a multihomed FreeBSD 8.1-RELEASE, in a multihomed jail, source IP selection suddenly refused to work. ifconfig on a box: Seems reasonable, yes? Pinging from the box # ping 192.168.75.59 PING 192.168.75.59 (192.168.75.59): 56 data bytes 64 bytes from 192.168.75.59: icmp_seq=0 ttl=64 time=0.993 ms 64 bytes from 192.168.75.59: icmp_seq=1 ttl=64 time=0.986 ms 64 bytes from 192.168.75.59: icmp_seq=2 ttl=64 time=0.988 ms ^C --- 192.168.75.59 ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.986/0.989/0.993/0.003 ms 10:45:31.425232 IP 192.168.75.4 > 192.168.75.59: ICMP echo request, id 12430, seq 0, length 64 10:45:31.426283 IP 192.168.75.59 > 192.168.75.4: ICMP echo reply, id 12430, seq 0, length 64 10:45:32.425415 IP 192.168.75.4 > 192.168.75.59: ICMP echo request, id 12430, seq 1, length 64 10:45:32.426404 IP 192.168.75.59 > 192.168.75.4: ICMP echo reply, id 12430, seq 1, length 64 Okay, yes? From jail: # ping 192.168.75.59 PING 192.168.75.59 (192.168.75.59): 56 data bytes ^C --- 192.168.75.59 ping statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss 10:45:52.146600 IP 83.69.203.1 > 192.168.75.59: ICMP echo request, id 14222, seq 0, length 64 10:45:53.146702 IP 83.69.203.1 > 192.168.75.59: ICMP echo request, id 14222, seq 1, length 64 Setting ip.saddrsel to 1 or 0 did not change anything. Kernel is GENERIC+ALTQ What could I miss?... Don't use ping to test this. a) for ping inside the jail to work you need to enable raw sockets b) a) could give you a hint that ping does it's own thing. Telnet did all the same thing. Try a telnet to a random port to the destination and verify with tcpdump whether things are still not working correctly, of if you establish the connection with netstat. I used telnet to connect to specific ports. Ok, let's try again 104:tarkhil@box2.u.energodata.local:...local/etc/ezjail # jls JID IP Address Hostname Path 1 192.168.82.2 test /usr/jails/test 107:tarkhil@box2.u.energodata.local:...local/etc/ezjail # jls -j 1 ip4.saddrsel true 108:tarkhil@box2.u.energodata.local:...local/etc/ezjail # jls -j 1 ip4.addr 192.168.82.2,192.168.75.2 114:tarkhil@box2.u.energodata.local:...local/etc/ezjail # tcpdump -l -n -i bce0 host 192.168.82.2 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bce0, link-type EN10MB (Ethernet), capture size 96 bytes 09:27:54.492105 IP 192.168.82.2.50823 > 192.168.72.3.22: Flags [S], seq 3819433473, win 65535, options [mss 1460,nop,wscale 3,sackOK,TS val 1306232522 ecr 0], length 0 115:tarkhil@box2.u.energodata.local:...local/etc/ezjail # ifconfig bce0 bce0: flags=8843 metric 0 mtu 1500 options=c01bb ether 00:14:5e:1a:a6:27 inet 192.168.80.41 netmask 0xff00 broadcast 192.168.80.255 media: Ethernet autoselect (100baseTX ) status: active test# sysctl security.jail.jailed security.jail.jailed: 1 test# ifconfig bce0: flags=8843 metric 0 mtu 1500 options=c01bb ether 00:14:5e:1a:a6:27 media: Ethernet autoselect (100baseTX ) status: active bce1: flags=8843 metric 0 mtu 1500 options=c01bb ether 00:14:5e:1a:a6:29 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 vlan75: flags=8843 metric 0 mtu 1500 options=103 ether 00:14:5e:1a:a6:29 inet 192.168.75.2 netmask 0xff00 broadcast 192.168.75.255 media: Ethernet autoselect (100baseTX ) status: active vlan: 75 parent interface: bce1 vlan82: flags=8843 metric 0 mtu 1500 options=103 ether 00:14:5e:1a:a6:29 inet 192.168.82.2 netmask 0xff00 broadcast 192.168.82.255 media: Ethernet autoselect (100baseTX ) status: active vlan: 82 parent interface: bce1 In other words, source address is selected as primary IP, and packet runs out on 100% improper interface. No specific routing, no firewall. Alex. ___ 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: jail source address selection doesn't work?
On 03/03/11 15:03, Bjoern A. Zeeb wrote: Not sure what you expect. Your jail has an address out of 192.168.82.2/24 and 192.168.75.2/24 You are trying to connect to neither of those networks but 192.168.72.3. Now it was a typo. Either I've lost my mind or I can't reproduce a problem. Will check everything again. Alex. ___ 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/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable.
The following reply was made to PR kern/146517; it has been noted by GNATS. From: Alex Kozlov To: bug-follo...@freebsd.org, vi...@unsane.co.uk, rpa...@freebsd.org, s...@rm-rf.kiev.ua Cc: Subject: Re: kern/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable. Date: Mon, 31 May 2010 21:12:20 +0300 Hi I confirm this. Atheros 9280, work fine with 8.0R usb stick, timeout after few pings with 8.1-BETA1. I can try to find a particular commit, that causes this regression, if its help. -- Adios ___ 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/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable.
The following reply was made to PR kern/146517; it has been noted by GNATS. From: Alex Kozlov To: Rui Paulo , bug-follo...@freebsd.org, vi...@unsane.co.uk Cc: Subject: Re: kern/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable. Date: Mon, 21 Jun 2010 17:38:59 +0300 On Mon, May 31, 2010 at 07:30:04PM +, Rui Paulo wrote: > > I confirm this. Atheros 9280, work fine with 8.0R usb stick, > > timeout after few pings with 8.1-BETA1. > > I can try to find a particular commit, that causes this > > regression, if its help. > Yes, please. Sorry for the delay. I think that the culprit is r203959. -- Adios ___ 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/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable.
The following reply was made to PR kern/146517; it has been noted by GNATS. From: Alex Kozlov To: Rui Paulo , bug-follo...@freebsd.org, vi...@unsane.co.uk, s...@rm-rf.kiev.ua Cc: Subject: Re: kern/146517: [ath] [wlan] device timeouts for ath wlan device on recent stable. Date: Tue, 22 Jun 2010 16:35:59 +0300 On Mon, Jun 21, 2010 at 05:30:30PM +0100, Rui Paulo wrote: > On 21 Jun 2010, at 15:38, Alex Kozlov wrote: > > On Mon, May 31, 2010 at 07:30:04PM +, Rui Paulo wrote: > >>> I confirm this. Atheros 9280, work fine with 8.0R usb stick, > >>> timeout after few pings with 8.1-BETA1. > >>> I can try to find a particular commit, that causes this > >>> regression, if its help. > >> Yes, please. > > Sorry for the delay. I think that the culprit is r203959. > Please try this patch. Patch does not help, but if I change line in AR_SREV_MERLIN_20 from AH_PRIVATE((_ah))->ah_macRev == AR_XSREV_REVISION_MERLIN_20 to AH_PRIVATE((_ah))->ah_macRev >= AR_XSREV_REVISION_MERLIN_20 net works again. -- Adios ___ 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/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote:
> Regarding the 8.1 if_rum(4) panics... I got a similar one, extracted
> a dump and tried to gather some info for someone who knows the code:
>
> The zero divide fault was because (apparently) rate was unitialized,
> as is
>
> ((struct ieee80211_node *)
> m->M_dat.MH.MH_pkthdr.rcvif)->ni_vap->iv_txparms[0]
>
> i.e. struct ieee80211_txparam &vap->iv_txparms[0] in case it matters.
Yes, its seems that ratectl framework sometimes set ni->ni_txrate to 0
This can be mitigated by patch [1] or by setting ucastrate option in
ifconfig. Still real issue need to be solved.
--
Adios
Index: sys/dev/usb/wlan/if_rum.c
@@ -1153,9 +1153,11 @@
rate = params->ibp_rate0;
if (!ieee80211_isratevalid(ic->ic_rt, rate)) {
+ device_printf(sc->sc_dev, "invalid rate=%d\n", rate);
m_freem(m0);
return EINVAL;
}
+
flags = 0;
if ((params->ibp_flags & IEEE80211_BPF_NOACK) == 0)
flags |= RT2573_TX_NEED_ACK;
@@ -1217,6 +1219,13 @@
else
rate = ni->ni_txrate;
+ /* XXX ieee80211_ratectl sometimes set ni->ni_txrate to 0 */
+ if (!ieee80211_isratevalid(ic->ic_rt, rate)) {
+ device_printf(sc->sc_dev, "invalid rate=%d\n", rate);
+ m_freem(m0);
+ return EINVAL;
+ }
+
if (wh->i_fc[1] & IEEE80211_FC1_WEP) {
k = ieee80211_crypto_encap(ni, m0);
if (k == NULL) {
___
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/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
The following reply was made to PR kern/149185; it has been noted by GNATS.
From: Alex Kozlov
To: n...@freebsd.org, rpa...@freebsd.org, freebsd-net@FreeBSD.org,
bug-follo...@freebsd.org, s...@rm-rf.kiev.ua
Cc:
Subject: Re: kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
Date: Thu, 5 Aug 2010 09:52:16 +0300
--Q68bSM7Ycu6FN28Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote:
> Regarding the 8.1 if_rum(4) panics... I got a similar one, extracted
> a dump and tried to gather some info for someone who knows the code:
>
> The zero divide fault was because (apparently) rate was unitialized,
> as is
>
> ((struct ieee80211_node *)
> m->M_dat.MH.MH_pkthdr.rcvif)->ni_vap->iv_txparms[0]
>
> i.e. struct ieee80211_txparam &vap->iv_txparms[0] in case it matters.
Yes, its seems that ratectl framework sometimes set ni->ni_txrate to 0
This can be mitigated by patch [1] or by setting ucastrate option in
ifconfig. Still real issue need to be solved.
--
Adios
--Q68bSM7Ycu6FN28Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="patch.txt"
Index: sys/dev/usb/wlan/if_rum.c
@@ -1153,9 +1153,11 @@
rate = params->ibp_rate0;
if (!ieee80211_isratevalid(ic->ic_rt, rate)) {
+ device_printf(sc->sc_dev, "invalid rate=%d\n", rate);
m_freem(m0);
return EINVAL;
}
+
flags = 0;
if ((params->ibp_flags & IEEE80211_BPF_NOACK) == 0)
flags |= RT2573_TX_NEED_ACK;
@@ -1217,6 +1219,13 @@
else
rate = ni->ni_txrate;
+ /* XXX ieee80211_ratectl sometimes set ni->ni_txrate to 0 */
+ if (!ieee80211_isratevalid(ic->ic_rt, rate)) {
+ device_printf(sc->sc_dev, "invalid rate=%d\n", rate);
+ m_freem(m0);
+ return EINVAL;
+ }
+
if (wh->i_fc[1] & IEEE80211_FC1_WEP) {
k = ieee80211_crypto_encap(ni, m0);
if (k == NULL) {
--Q68bSM7Ycu6FN28Q--
___
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/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
The following reply was made to PR kern/149185; it has been noted by GNATS. From: Alex Kozlov To: Bernhard Schmidt , bug-follo...@freebsd.org, n...@freebsd.org, rpa...@freebsd.org, s...@rm-rf.kiev.ua Cc: Subject: Re: kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R Date: Thu, 5 Aug 2010 12:11:05 +0300 On Thu, Aug 05, 2010 at 10:05:39AM +0200, Bernhard Schmidt wrote: > On Thu, Aug 5, 2010 at 08:52, Alex Kozlov wrote: > > On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote: > >> Regarding the 8.1 if_rum(4) panics... I got a similar one, extracted > >> a dump and tried to gather some info for someone who knows the code: > >> > >> The zero divide fault was because (apparently) rate was unitialized, > >> as is > >> > >> ((struct ieee80211_node *) > >> m->M_dat.MH.MH_pkthdr.rcvif)->ni_vap->iv_txparms[0] > >> > >> i.e. struct ieee80211_txparam &vap->iv_txparms[0] in case it matters. > > Yes, its seems that ratectl framework sometimes set ni->ni_txrate to 0 > > This can be mitigated by patch [1] or by setting ucastrate option in > > ifconfig. Still real issue need to be solved. > > The real issue is that prior to an association (RUN state) > ieee80211_ratectl_node_init() is not called, therefore iv_bss is not > configured in any way. ieee80211_ratectl_node_init() called from iv_newstate when switching to IEEE80211_S_RUN state. Most drivers do the same. Is it wrong? Some call it from iv_newassoc, but this marked /* XXX move */ > I'll look into that if no one beats me. Thanks. -- Adios ___ 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/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
The following reply was made to PR kern/149185; it has been noted by GNATS. From: Alex Kozlov To: Bernhard Schmidt , bug-follo...@freebsd.org, s...@rm-rf.kiev.ua Cc: Subject: Re: kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R Date: Thu, 5 Aug 2010 21:14:41 +0300 On Thu, Aug 05, 2010 at 06:25:32PM +0200, Bernhard Schmidt wrote: > On Thu, Aug 5, 2010 at 11:11, Alex Kozlov wrote: > > On Thu, Aug 05, 2010 at 10:05:39AM +0200, Bernhard Schmidt wrote: > >> On Thu, Aug 5, 2010 at 08:52, Alex Kozlov wrote: > >> > On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote: > >> >> Regarding the 8.1 if_rum(4) panics... I got a similar one, extracted > >> >> a dump and tried to gather some info for someone who knows the code: > >> >> > >> >> The zero divide fault was because (apparently) rate was unitialized, > >> >> as is > >> >> > >> >> ((struct ieee80211_node *) > >> >> m->M_dat.MH.MH_pkthdr.rcvif)->ni_vap->iv_txparms[0] > >> >> > >> >> i.e. struct ieee80211_txparam &vap->iv_txparms[0] in case it matters. > >> > Yes, its seems that ratectl framework sometimes set ni->ni_txrate to 0 > >> > This can be mitigated by patch [1] or by setting ucastrate option in > >> > ifconfig. Still real issue need to be solved. > >> > >> The real issue is that prior to an association (RUN state) > >> ieee80211_ratectl_node_init() is not called, therefore iv_bss is not > >> configured in any way. > > ieee80211_ratectl_node_init() called from iv_newstate when switching to > > IEEE80211_S_RUN state. Most drivers do the same. Is it wrong? > > Some call it from iv_newassoc, but this marked /* XXX move */ > >> I'll look into that if no one beats me. > > Thanks. > Please give attached patch a try, it should fix the issue for rum and > all other drivers relying on the new ratectl stuff. Testing. Thanks again. -- Adios ___ 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/144755: [iwi] [panic] iwi panic when issuing /etc/rc.d/netif restart on 8-STABLE r205159
The following reply was made to PR kern/144755; it has been noted by GNATS.
From: Alex Kozlov
To: Bernhard Schmidt ,
Edwin Groothuis , bug-follo...@freebsd.org,
s...@rm-rf.kiev.ua
Cc:
Subject: Re: kern/144755: [iwi] [panic] iwi panic when issuing
/etc/rc.d/netif restart on 8-STABLE r205159
Date: Thu, 5 Aug 2010 23:55:43 +0300
--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Thu, Aug 05, 2010 at 08:10:08PM +, Bernhard Schmidt wrote:
> The following reply was made to PR kern/144755; it has been noted by GNATS.
>
> From: Bernhard Schmidt
> To: Edwin Groothuis
> Cc: bug-follo...@freebsd.org
> Subject: Re: kern/144755: [iwi] [panic] iwi panic when issuing
> /etc/rc.d/netif
> restart on 8-STABLE r205159
> Date: Thu, 5 Aug 2010 22:08:38 +0200
>
> --0015175cda7eab5eec048d191d67
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, Aug 5, 2010 at 00:31, Edwin Groothuis wrote:
> > [..]
> > Nice! Is there a workaround or patch available for testing?
>
> Please give the attached patch a try. It does not prevent
> wpa_supplicant from starting twice (for that you can define
> ctrl_interface= in wpa_supplicant.conf), but should no longer panic.
I can reproduce this panic for if_rum, similiar patch also helps.
wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x
fault code = supervisor read, page not present
instruction pointer= 0x20:0xc0900d42
stack pointer = 0x28:0xc4f05bac
frame pointer = 0x28:0xc4f05bb8
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process= 0 (rum0 taskq)
trap number= 12
panic: page fault
KDB: stack backtrace:
db_trace_self_wrapper(c0669547,c06cb000,c0660c6a,c4f05a5c,c4f05a5c,...) at
0xc0436706 = db_trace_self_wrapper+0x26
panic(c0660c6a,c0680c79,c4f05b6c,1,1,...) at 0xc04b898d = panic+0xed
trap_fatal(c06c9740,f000,1,0,c04c0ef6,...) at 0xc06474bd = trap_fatal+0x23d
trap_pfault(0,c066c5e8,2d7,0,c06c9220,...) at 0xc064787a = trap_pfault+0x27a
trap(c4f05b6c) at 0xc06481ab = trap+0x39b
calltrap() at 0xc062d4ac = calltrap+0x6
--- trap 0xc, eip = 0xc0900d42, esp = 0xc4f05bac, ebp = 0xc4f05bb8 ---
ieee80211_getcapinfo(c5caa000,,c08f415a,c5caa874,c5463d00,...) at
0xc0900d42 = ieee80211_getcapinfo+0x71
ieee80211_beacon_construct(c62a8000,18,676,c50f5c00,c54e3988,...) at
0xc090308d = ieee80211_beacon_construct+0x67
ieee80211_beacon_alloc(c62a8000,c5caa874,6,2c5,5,...) at 0xc09039a0 =
ieee80211_beacon_alloc+0x93
rum_newstate(c5caa000,5,,652,c5362014,...) at 0xc9a9b55f =
rum_newstate+0x259
ieee80211_newstate_cb(c5caa000,4,0,c0695c9c,0,...) at 0xc0906eb8 =
ieee80211_newstate_cb+0x7a
taskqueue_run(c537db00,c537db18,0,c0661905,0,...) at 0xc04ef61a =
taskqueue_run+0x8a
taskqueue_thread_loop(c5362074,c4f05d38,0,0,0,...) at 0xc04efd74 =
taskqueue_thread_loop+0x44
fork_exit(c04efd30,c5362074,c4f05d38) at 0xc048e868 = fork_exit+0x88
fork_trampoline() at 0xc062d524 = fork_trampoline+0x8
--
Adios
--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="patch.txt"
Index: sys/dev/usb/wlan/if_rum.c
@@ -719,7 +719,7 @@
break;
case IEEE80211_S_RUN:
- ni = vap->iv_bss;
+ ni = ieee80211_ref_node(vap->iv_bss);
if (vap->iv_opmode != IEEE80211_M_MONITOR) {
rum_update_slot(ic->ic_ifp);
@@ -743,6 +743,7 @@
tp = &vap->iv_txparms[ieee80211_chan2mode(ic->ic_curchan)];
if (tp->ucastrate == IEEE80211_FIXED_RATE_NONE)
rum_ratectl_start(sc, ni);
+ ieee80211_free_node(ni);
break;
default:
break;
@@ -2216,7 +2217,7 @@
struct ieee80211com *ic = vap->iv_ic;
struct ifnet *ifp = ic->ic_ifp;
struct rum_softc *sc = ifp->if_softc;
- struct ieee80211_node *ni = vap->iv_bss;
+ struct ieee80211_node *ni;
int ok, fail;
int sum, retrycnt;
@@ -2230,8 +2231,10 @@
sum = ok+fail;
retrycnt = (le32toh(sc->sta[5]) & 0x) + fail;
+ ni = ieee80211_ref_node(vap->iv_bss);
ieee80211_ratectl_tx_update(vap, ni, &sum, &ok, &retrycnt);
(void) ieee80211_ratectl_rate(ni, NULL, 0);
+ ieee80211_free_node(ni);
ifp->if_oerrors += fail;/* count TX retry-fail as Tx errors */
--mYCpIKhGyMATD0i+
Re: kern/144898: [wpi] [panic] wpi panics system
The following reply was made to PR kern/144898; it has been noted by GNATS.
From: Alex Kozlov
To: Dominic Fandrey , bug-follo...@freebsd.org,
s...@rm-rf.kiev.ua
Cc:
Subject: Re: kern/144898: [wpi] [panic] wpi panics system
Date: Fri, 6 Aug 2010 00:52:26 +0300
--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Hi, Dominic
It's seems to be common issue for many wireless if drivers.
Can You please try this patch? Thanks.
--
Adios
--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="patch.txt"
Index: sys/dev/wpi/if_wpi.c
@@ -2399,7 +2399,7 @@
wpi_auth(struct wpi_softc *sc, struct ieee80211vap *vap)
{
struct ieee80211com *ic = vap->iv_ic;
- struct ieee80211_node *ni = vap->iv_bss;
+ struct ieee80211_node *ni = ieee80211_ref_node(vap->iv_bss);
struct wpi_node_info node;
int error;
@@ -2449,6 +2449,7 @@
node.action = htole32(WPI_ACTION_SET_RATE);
node.antenna = WPI_ANTENNA_BOTH;
error = wpi_cmd(sc, WPI_CMD_ADD_NODE, &node, sizeof node, 1);
+ ieee80211_free_node(ni);
if (error != 0)
device_printf(sc->sc_dev, "could not add BSS node\n");
@@ -2459,7 +2460,7 @@
wpi_run(struct wpi_softc *sc, struct ieee80211vap *vap)
{
struct ieee80211com *ic = vap->iv_ic;
- struct ieee80211_node *ni = vap->iv_bss;
+ struct ieee80211_node *ni = ieee80211_ref_node(vap->iv_bss);
int error;
if (vap->iv_opmode == IEEE80211_M_MONITOR) {
@@ -2493,8 +2494,9 @@
}
error = wpi_set_txpower(sc, ni->ni_chan, 1);
+ ieee80211_free_node(ni);
if (error != 0) {
- device_printf(sc->sc_dev, "could set txpower\n");
+ device_printf(sc->sc_dev, "could not set txpower\n");
return error;
}
--7AUc2qLy4jB3hD7Z--
___
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/149185: [rum] [panic] panic in rum(4) driver on 8.1-R
The following reply was made to PR kern/149185; it has been noted by GNATS. From: Alex Kozlov To: Juergen Lock , Bernhard Schmidt , rpa...@freebsd.org, Kevin Lo , bug-follo...@freebsd.org, s...@rm-rf.kiev.ua Cc: Subject: Re: kern/149185: [rum] [panic] panic in rum(4) driver on 8.1-R Date: Mon, 9 Aug 2010 12:23:26 +0300 On Sun, Aug 08, 2010 at 05:14:46PM +0200, Juergen Lock wrote: > On Thu, Aug 05, 2010 at 06:25:32PM +0200, Bernhard Schmidt wrote: > > On Thu, Aug 5, 2010 at 11:11, Alex Kozlov wrote: > > > On Thu, Aug 05, 2010 at 10:05:39AM +0200, Bernhard Schmidt wrote: > > >> On Thu, Aug 5, 2010 at 08:52, Alex Kozlov wrote: > > >> > On Wed, Aug 04, 2010 at 10:02:35PM +0200, Juergen Lock wrote: > > >> >> Regarding the 8.1 if_rum(4) panics... I got a similar one, > > >> >> extracted > > >> >> a dump and tried to gather some info for someone who knows the code: > > >> >> > > >> >> The zero divide fault was because (apparently) rate was unitialized, > > >> >> as is > > >> >> > > >> >> ((struct ieee80211_node *) > > >> >> m->M_dat.MH.MH_pkthdr.rcvif)->ni_vap->iv_txparms[0] > > >> >> > > >> >> i.e. struct ieee80211_txparam &vap->iv_txparms[0] in case it matters. > > >> > Yes, its seems that ratectl framework sometimes set ni->ni_txrate to 0 > > >> > This can be mitigated by patch [1] or by setting ucastrate option in > > >> > ifconfig. Still real issue need to be solved. > > >> > > >> The real issue is that prior to an association (RUN state) > > >> ieee80211_ratectl_node_init() is not called, therefore iv_bss is not > > >> configured in any way. > > > ieee80211_ratectl_node_init() called from iv_newstate when switching to > > > IEEE80211_S_RUN state. Most drivers do the same. Is it wrong? > > > Some call it from iv_newassoc, but this marked /* XXX move */ > > > > > >> I'll look into that if no one beats me. > > > Thanks. > > > > > > Please give attached patch a try, it should fix the issue for rum and > > all other drivers relying on the new ratectl stuff. > That seems to stop the panics, but the wifi still only works partially > (at least with hostapd), like with my original hack of a patch. One That why I use ad-hoc. Yes, seems that this panic eliminated. -- Adios ___ 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/121257: [tcp] TSO + natd -> slow outgoing tcp traffic
The following reply was made to PR kern/121257; it has been noted by GNATS. From: Alex Samorukov <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: kern/121257: [tcp] TSO + natd -> slow outgoing tcp traffic Date: Fri, 27 Jun 2008 16:48:15 +0200 I can approve the problem. I found VERY slow outgoing speed on my new server with natd, and the problem was with TSO flag on public interface. Freebsd 7.0/i386, em network driver ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd IP Forwarding performance (question, and some info) [7-stable, current, em, smp]
0n Mon, Jun 30, 2008 at 03:44:48PM -0400, Mike Tancsa wrote: >OK, I setup 2 boxes on either end of a RELENG_7 box from about May >7th just now, to see with 2 boxes blasting across it how it would >work. *However*, this is with no firewall loaded and, I must enable >ip fast forwarding. Without that enabled, the box just falls over. What is "ip fast forwarding" ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd IP Forwarding performance (question, and some info) [7-stable, current, em, smp]
0n Tue, Jul 01, 2008 at 03:00:31AM +0200, Ingo Flaschberger wrote: >Dear Alex, > >>>OK, I setup 2 boxes on either end of a RELENG_7 box from about May >>>7th just now, to see with 2 boxes blasting across it how it would >>>work. *However*, this is with no firewall loaded and, I must enable >>>ip fast forwarding. Without that enabled, the box just falls over. >> >> What is "ip fast forwarding" ? > >instead of copying the while ip packet into system memory, only the ip >header is copyied and then in a "fast" path determined if it could be fast >forwarded. >if possible, a ned header is created at the other network-cards-buffer >and the ip-data is copied from network-card-buffer to network-card-buffer >directly. So how does one enable "ip fast forwarding" on FreeBSD ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd IP Forwarding performance (question, and some info) [7-stable, current, em, smp]
0n Mon, Jun 30, 2008 at 10:41:36PM -0400, Paul wrote: >All the NIC drivers in 7 pretty much use interrupt moderation so it can >never lock the machine anyway.. This effectively kills polling and it >really no longer has any use except to be able to have a fraction of the >cpu set aside for user space but you can do that anyway with SMP what is "interrupt moderation" ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TCP ECN patch to be committed
0n Wed, Jul 30, 2008 at 02:04:52AM +0100, Rui Paulo wrote: >After some chat with other TCP folks I'm going to commit the TCP ECN patch >I asked for review a couple months ago with some changes. Most notably is >the new padding fields added to the syncache struct. Um, what is "TCP ECN" ? Nutshell summary please ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Check out my photos on Facebook
Hi Freebsd-net, I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. Thanks, Alex To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=841695471&k=32DYP2TXT5XM5CEIXFY6X3&r freebsd-net@freebsd.org was invited to join Facebook by Alex Santiago. If you do not wish to receive this type of email from Facebook in the future, please click on the link below to unsubscribe. http://www.facebook.com/o.php?k=cbecc8&u=1119946398&mid=66e0fbG42c1069eG0G8 Facebook's offices are located at 156 University Ave., Palo Alto, CA 94301. ___ 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"
Is it possible to set VLAN-QOS/Priority?
Hi. Is it possible to configure VLAN priority on FreeBSD10-STABLE or FreeBSD11-CURRENT? Thanks. Alex Liptsin ___ 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"
VLAN priority
Hi. How can I configure VLAN priority on FreeBSD10-STABLE or FreeBSD11-CURRENT? Thanks, Alex. ___ 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"
redirecting pf example
Hello! I'm trying to set up a box as round-robin TCP proxy. Of course, I'm trying to do everything on kernel-level. This simple setup rdr on sk0 proto tcp from any to any port = smtp -> port 25 round-robin should work. At least, I thought so. However, attempt to connect to port 25 yielded unexpected result. pfctl -s state shows self tcp 89.108.94.212:25 <- 89.108.94.91:25 <- 89.108.94.211:56975 CLOSED:SYN_SENT connection never established, and no IP packet ever sends out to 89.108.94.212:25 I don't understand this thing. Maybe someone can point me to my error? (firewall rules a quite permissive, in fact, they are pass in quick and pass out quick for all interfaces. attempt to telnet to port 25 outside works ok) Alex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Please help with PF-based redirector
Hello! I'm trying to set up a box as round-robin TCP proxy. Of course, I'm trying to do everything on kernel-level. This simple setup rdr on sk0 proto tcp from any to any port = smtp -> port 25 round-robin should work. At least, I thought so. However, attempt to connect to port 25 yielded unexpected result. pfctl -s state shows self tcp 89.108.94.212:25 <- 89.108.94.91:25 <- 89.108.94.211:56975 CLOSED:SYN_SENT connection never established, and no IP packet ever sends out to 89.108.94.212:25 I don't understand this thing. Maybe someone can point me to my error? (firewall rules a quite permissive, in fact, they are pass in quick and pass out quick for all interfaces. attempt to telnet to port 25 outside works ok) Alex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please help with PF-based redirector
Max Laier wrote: On Sunday 15 April 2007 20:11, Alex Povolotsky wrote: Hello! I'm trying to set up a box as round-robin TCP proxy. Of course, I'm trying to do everything on kernel-level. This simple setup rdr on sk0 proto tcp from any to any port = smtp -> port 25 round-robin should work. At least, I thought so. However, attempt to connect to port 25 yielded unexpected result. pfctl -s state shows self tcp 89.108.94.212:25 <- 89.108.94.91:25 <- 89.108.94.211:56975 CLOSED:SYN_SENT Your test hosts seem to be on the same subnet. This does not work as you seems to think. In the same broadcast domain it is not possible for the pf box to forward the packet on behalf of the sending host (otherwise it would confuse the recipient or the switch). Instead it emits icmp redirects which are ignored in a normal setup. You have to separate the two networks in order for redirect to work the way you want it to. Okay, thanks a lot, I'll give a try Alex. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please help with PF-based redirector
Max Laier wrote: On Sunday 15 April 2007 20:11, Alex Povolotsky wrote: Hello! I'm trying to set up a box as round-robin TCP proxy. Of course, I'm trying to do everything on kernel-level. This simple setup rdr on sk0 proto tcp from any to any port = smtp -> port 25 round-robin should work. At least, I thought so. However, attempt to connect to port 25 yielded unexpected result. pfctl -s state shows self tcp 89.108.94.212:25 <- 89.108.94.91:25 <- 89.108.94.211:56975 CLOSED:SYN_SENT Your test hosts seem to be on the same subnet. This does not work as you seems to think. In the same broadcast domain it is not possible for the pf box to forward the packet on behalf of the sending host (otherwise it would confuse the recipient or the switch). Instead it emits icmp redirects which are ignored in a normal setup. You have to separate the two networks in order for redirect to work the way you want it to. I have separated them. #pfctl -s nat rdr on rl0 proto tcp from any to any port = smtp -> port 25 round-robin # pfctl -s state No ALTQ support in kernel ALTQ related functions disabled self tcp 89.108.94.212:25 <- 10.180.210.2:25 <- 10.180.210.1:61298 CLOSED:SYN_SENT tcpdump does not show any ICMP redirect unknown-1717# tcpdump -l -n -i rl0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on rl0, link-type EN10MB (Ethernet), capture size 96 bytes 20:53:14.907833 arp who-has 10.180.210.2 tell 10.180.210.1 20:53:14.907857 arp reply 10.180.210.2 is-at 00:0e:2e:98:7e:55 20:53:14.907924 IP 10.180.210.1.57528 > 10.180.210.2.25: S 3593018807:3593018807(0) win 65535 1,nop,nop,timestamp 285791868 0,sackOK,eol> 20:53:17.907599 IP 10.180.210.1.57528 > 10.180.210.2.25: S 3593018807:3593018807(0) win 65535 1,nop,nop,timestamp 285794868 0,sackOK,eol> 20:53:21.107441 IP 10.180.210.1.57528 > 10.180.210.2.25: S 3593018807:3593018807(0) win 65535 1,nop,nop,timestamp 285798068 0,sackOK,eol> 20:53:24.307283 IP 10.180.210.1.57528 > 10.180.210.2.25: S 3593018807:3593018807(0) win 65535 20:53:27.507126 IP 10.180.210.1.57528 > 10.180.210.2.25: S 3593018807:3593018807(0) win 65535 20:53:30.706974 IP 10.180.210.1.57528 > 10.180.210.2.25: S 3593018807:3593018807(0) win 65535 ^C 8 packets captured 8 packets received by filter 0 packets dropped by kernel What am I doing wrong? Or I can only redirect routable traffic? Nope, I've added alias to "external" interface, no changes Alex ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Please help with PF-based redirector
Max Laier wrote: On Sunday 15 April 2007 20:11, Alex Povolotsky wrote: Hello! I'm trying to set up a box as round-robin TCP proxy. Of course, I'm trying to do everything on kernel-level. This simple setup rdr on sk0 proto tcp from any to any port = smtp -> port 25 round-robin should work. At least, I thought so. However, attempt to connect to port 25 yielded unexpected result. pfctl -s state shows self tcp 89.108.94.212:25 <- 89.108.94.91:25 <- 89.108.94.211:56975 CLOSED:SYN_SENT Your test hosts seem to be on the same subnet. This does not work as you seems to think. In the same broadcast domain it is not possible for the pf box to forward the packet on behalf of the sending host (otherwise it would confuse the recipient or the switch). Instead it emits icmp redirects which are ignored in a normal setup. You have to separate the two networks in order for redirect to work the way you want it to. Sorry, things are not THAT simple. I've tried the setup: unknown-1717# ifconfig rl0: flags=8843 mtu 1500 options=8 inet 10.180.210.2 netmask 0xff00 broadcast 10.180.210.255 ether 00:0e:2e:98:7e:55 media: Ethernet autoselect (100baseTX ) status: active sk0: flags=8943 mtu 1500 options=b inet 89.108.94.91 netmask 0xf000 broadcast 89.108.95.255 inet 10.180.220.1 netmask 0xff00 broadcast 10.180.220.255 ether 00:18:f3:5c:de:6d media: Ethernet autoselect (100baseTX ) status: active plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 pfsync0: flags=0<> mtu 1348 syncpeer: 224.0.0.240 maxupd: 128 carp0: flags=49 mtu 1500 inet 89.108.94.92 netmask 0xf000 carp: MASTER vhid 21 advbase 1 advskew 0 unknown-1717# pfctl -s nat No ALTQ support in kernel ALTQ related functions disabled nat on sk0 inet from 10.180.210.0/24 to any -> (sk0) round-robin rdr on rl0 proto tcp from any to any port = smtp -> port 25 round-robin seems reasonable. yes? FIRST connect works ok Than - no success at all for some time. Than - works again unknown-1717# pfctl -s state No ALTQ support in kernel ALTQ related functions disabled self tcp 89.108.65.126:25 <- 10.180.210.2:25 <- 10.180.210.1:62736 CLOSED:SYN_SENT self tcp 89.108.65.126:25 <- 10.180.210.2:25 <- 10.180.210.1:58177 FIN_WAIT_2:FIN_WAIT_2 self tcp 89.108.94.212:25 <- 10.180.210.2:25 <- 10.180.210.1:57950 FIN_WAIT_2:FIN_WAIT_2 self tcp 89.108.94.212:25 <- 10.180.210.2:25 <- 10.180.210.1:58727 CLOSED:SYN_SENT self tcp 89.108.65.124:25 <- 10.180.210.2:25 <- 10.180.210.1:63480 CLOSED:SYN_SENT self tcp 10.180.210.1:63480 -> 89.108.94.91:54490 -> 89.108.65.124:25 SYN_SENT:CLOSED self tcp 10.180.210.1:62736 -> 10.180.220.1:52675 -> 89.108.65.126:25 SYN_SENT:CLOSED self tcp 10.180.210.1:58177 -> 89.108.94.91:51550 -> 89.108.65.126:25 FIN_WAIT_2:FIN_WAIT_2 self tcp 10.180.210.1:58727 -> 10.180.220.1:50704 -> 89.108.94.212:25 SYN_SENT:CLOSED self tcp 10.180.210.1:57950 -> 89.108.94.91:65245 -> 89.108.94.212:25 FIN_WAIT_2:FIN_WAIT_2 You can see that some connections works, and some fails. 110% problem is NOT on real SMTP servers' side. Alex. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firewall
0n Mon, Apr 30, 2007 at 10:58:18AM +0100, Robert Watson wrote: >One of the big selling points of IPFW is integration with DUMMYNET, which >offers bandwidth management facilities not present in the other systems. I >understand there may be efforts afoot to add DUMMYNET support to other >firewall packages, but don't have any details. I have to say that DUMMYNET >is the main selling point for ipfw on my servers -- being able to rate >limit arbitrary IP addresses, port numbers, etc, both in terms of inbound >and outbound traffic is invaluable. eh ? PF has ALTQ built in. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firewall
0n Tue, May 01, 2007 at 11:31:58AM +0800, Wilkinson, Alex wrote: >0n Mon, Apr 30, 2007 at 10:58:18AM +0100, Robert Watson wrote: > >>One of the big selling points of IPFW is integration with DUMMYNET, which >>offers bandwidth management facilities not present in the other systems. I >>understand there may be efforts afoot to add DUMMYNET support to other >>firewall packages, but don't have any details. I have to say that DUMMYNET >>is the main selling point for ipfw on my servers -- being able to rate >>limit arbitrary IP addresses, port numbers, etc, both in terms of inbound >>and outbound traffic is invaluable. > >eh ? PF has ALTQ built in. Read the next msg from Robert.Watson. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unix friendly network testbench for FreeBSD?
0n Wed, May 02, 2007 at 09:48:52AM -0700, [EMAIL PROTECTED] wrote: >Hi, > I'm looking for a network testbench / simulator to stimulate known > networking conditions to test out a component for a product at work. > I was wondering if there was a network simulator available (preferably > open source) that's FreeBSD / Linux compatible which I can simulate as > real of a network as possible on a virtual machine / network. I asked this same question a while back: [http://www.linuxsa.org.au/pipermail/linuxsa/2005-January/076909.html] -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Asus WL-167g not working
Hello! I'm trying to use ASUS WL-167g, with ural driver compiled into kernel, but system does not recognize it. from /var/log/messages May 12 23:47:15 tarkhil kernel: ugen1: Ralink 802.11 bg WLAN, rev 2.00/0.01, addr 2 from usbdevs -v port 5 addr 2: high speed, power 300 mA, config 1, 802.11 bg WLAN(0x1723), Ralink(0x0b05), rev 0.01 System is FreeBSD 6.2-RELEASEp3. Any help is appreciated. Alex. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Asus WL-167g not working
Volker wrote: On 05/12/07 21:55, Alex Povolotsky wrote: Hello! I'm trying to use ASUS WL-167g, with ural driver compiled into kernel, but system does not recognize it. from /var/log/messages May 12 23:47:15 tarkhil kernel: ugen1: Ralink 802.11 bg WLAN, rev 2.00/0.01, addr 2 from usbdevs -v port 5 addr 2: high speed, power 300 mA, config 1, 802.11 bg WLAN(0x1723), Ralink(0x0b05), rev 0.01 if_ural.c does not know about a usb ID 1723 (only Asus IDs 1706 and 1705 are known). You need to patch it. Partially helped. Now it can be detected, but cannot scan. May 13 01:37:03 tarkhil kernel: ural0: Ralink 802.11 bg WLAN, rev 2.00/0.01, addr 2 May 13 01:37:04 tarkhil kernel: ural0: MAC/BBP RT2570 (rev 0x00), RF unknown May 13 01:37:04 tarkhil kernel: ural0: Ethernet address: 00:18:f3:e5:b8:dd May 13 01:37:04 tarkhil kernel: ural0: if_start running deferred for Giant Here I do ifconfig ural0 up scan May 13 01:37:08 tarkhil kernel: ural0: timeout waiting for BBP/RF to wakeup And no scan result. Alex. HTH Volker ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: asymetric speeds over gigE link
0n Mon, May 21, 2007 at 07:39:06PM +0100, Tom Judge wrote: > I have also seen 700Mb/s sustained FreeBSD - FreeBSD using the openssh HPN > patch set and no extra tuning of the network stack. Which makes me > think that maybe the linux stack needs some tuning? What is the "HPN patch" ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: two public ip addresses on one interface
0n Fri, May 25, 2007 at 01:17:39PM -0700, Chuck Swiger wrote: > If your aliases are part of the same subnet as the "primary" or first configured IP, then you want to > use the all-1's netmask. In your case, however, the second IP is part of a completely different subnet, > and you can (and should) use a /24 netmask I have always wondered why we need to use the "all-1's" netmask. Why is this ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: two public ip addresses on one interface
0n Mon, May 28, 2007 at 11:43:21AM +0400, Eygene Ryabinkin wrote: >Alex, good day. > >Sun, May 27, 2007 at 07:07:41PM +0800, Wilkinson, Alex wrote: >> > If your aliases are part of the same subnet as the "primary" or first configured IP, then you want to >> > use the all-1's netmask. In your case, however, the second IP is part of a completely different subnet, >> > and you can (and should) use a /24 netmask >> >> I have always wondered why we need to use the "all-1's" netmask. Why is this ? > >Because if you're stuffing two addresses from the same subnet to >one interface it will not work: there can be only one route to the >specified network in the FreeBSD routing table. And adding IP to >the interface creates the entry in the routing table. So you should >specify the different mask and most probably 0x will be the >best choice, but your mileage may vary with your routing needs. mmm ... it looks like you can actually get around this on OpenBSD 4.1 with their new "multiple routing table" code. "Multiple routing tables. What does it mean for PF? Henning Brauer: The kernel used to have one routing table per address family--one for inet, one for inet6, one for IPsec, usually. Now it can have multiple tables. From within PF, you can select which routing table should be used for the route lookup later--you can implement policy routing with this. But much more could be done--this is really only the groundwork. It could be possible, in future, to have overlapping address ranges on interfaces and place interfaces into different routing tables, forming a kind of virtual routers. And of course, the routing daemons will learn to make more use of alternate tables." [http://www.onlamp.com/pub/a/bsd/2007/05/03/openbsd-41-puffy-strikes-again.html?page=2] -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: driver packet coalesce
0n Wed, May 30, 2007 at 04:45:05PM -0700, Jack Vogel wrote: > Does any driver do this now? And if a driver were to coalesce > packets and send something up the stack that violates mss > will it barf? erm, what is meant by "coalesce" ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New driver coming soon.
0n Thu, May 31, 2007 at 03:19:44PM -0700, Jack Vogel wrote: > FreeBSD customer base has been miniscule so not much has > been done to the code, maybe someday in my spare time :) "miniscule" ? That's scary to hear :( -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: netstat patch..
0n Tue, Jun 05, 2007 at 01:56:10PM -0400, Randall Stewart wrote: > Weongyo Jeong sent me a nice netstat patch that allows > netstat access to SCTP stuff :-D And for those that don't know much about SCTP, the benefit is ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network stack virtualization for FreeBSD 7.0
0n Tue, Jun 05, 2007 at 12:10:36PM -0700, Julian Elischer wrote: > I have two different versions of the talk on video. > The audio is a bit hard to hear but can still be understood. > When my RealWork(TM) lets up I will finish transcribing them to downloadable form. Can you please post to freebsd-announce@ when ready for consumption. Cheers! -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal double fault while copy to NFS filesystems
When I copy files to NFS on another host kernel crash: Fatal double fault: eip = 0xc07e9e29 esp = 0xe31a3000 ebp = 0xe31a3000 cpuid = 1; apic id = 01 panic: double fault cpuid = 1 === before this, I see on /var/log/messages nve0: device timeout === how repeat problem: ussr# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 72G6.1G 60G 9%/ devfs 1.0K1.0K 0B 100%/dev ussr# dd if=/dev/zero of=file_20mb bs=1m count=20 ussr# mount 192.168.254.254:/shares /mnt/ ussr# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 72G6.1G 60G 9%/ devfs 1.0K1.0K 0B 100%/dev 192.168.254.254:/shares271G179G 89G67%/mnt ussr# cp file_20mb /mnt/ then, after 3-5 second I see "device timeout", and later, after 5-7 seconds - system crash = another information - this problem appearance after I upgrade remote machine (6.2-RELEASE-p5), I change CPU from Celeron 466 to PIII 800. interface on remote machine - 3com509b if I slow copy to remote machine (~100kb/s - 10% interface usage) - all good. System not crash... if I copy from remote machine - all good - system not crash... on logs on remote machine - all clean. = 3 days ago I upgrade my system to 6.2-RELEASE-p5, but - problem exists... ussr# ifconfig fwe0: flags=108802 mtu 1500 options=8 ether 02:11:d8:ee:cc:8c ch 1 dma -1 nve0: flags=8843 mtu 1500 inet 192.168.254.193 netmask 0xff00 broadcast 192.168.254.255 ether 00:18:f3:97:3e:1b media: Ethernet autoselect (10baseT/UTP) status: active plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 ussr# === dmesg: Copyright (c) 1992-2007 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 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2004.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x40fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f,,CR8> Cores per package: 2 real memory = 1039007744 (990 MB) avail memory = 1007513600 (960 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: reservation of 3dee, 2 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02 irq 21 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff irq 22 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf400-0xf40f at device 13.0 on pci0 ata0: on atapci0 ata1: on atapci0 a
Re: Fatal double fault while copy to NFS filesystems
Kostik Belousov пишет: On Fri, Jul 06, 2007 at 07:07:00PM +0400, Alex Keda wrote: When I copy files to NFS on another host kernel crash: Fatal double fault: eip = 0xc07e9e29 esp = 0xe31a3000 ebp = 0xe31a3000 cpuid = 1; apic id = 01 panic: double fault cpuid = 1 === before this, I see on /var/log/messages nve0: device timeout === how repeat problem: ussr# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 72G6.1G 60G 9%/ devfs 1.0K1.0K 0B 100%/dev ussr# dd if=/dev/zero of=file_20mb bs=1m count=20 ussr# mount 192.168.254.254:/shares /mnt/ ussr# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 72G6.1G 60G 9%/ devfs 1.0K1.0K 0B 100%/dev 192.168.254.254:/shares271G179G 89G67%/mnt ussr# cp file_20mb /mnt/ then, after 3-5 second I see "device timeout", and later, after 5-7 seconds - system crash = another information - this problem appearance after I upgrade remote machine (6.2-RELEASE-p5), I change CPU from Celeron 466 to PIII 800. interface on remote machine - 3com509b if I slow copy to remote machine (~100kb/s - 10% interface usage) - all good. System not crash... if I copy from remote machine - all good - system not crash... on logs on remote machine - all clean. = 3 days ago I upgrade my system to 6.2-RELEASE-p5, but - problem exists... Double fault issue might be the problem that is fixed in CURRENT/RELENG_6. To confirm this, ddb backtrace after the panic will be helpful. You will need to compile DDB into the kernel, obtain DDB prompt after the panic and issue "bt" command. Fatal double fault: eip = 0xc07e8bd9 esp = 0xe3793000 ebp = 0xe3793020 cpuid = 0; apic id = 00 panic:double fault cpuid = 0 KDB: enter: panic [thread pid 25 tid 100019] Stopped at kdb_enter+0x2b:nop Tracing pid 25 tid 100019 td 0xc527b600 kdb_enter(c090f266) at kdb_enter+0x2b panic(c092d4c9,c092d671,0,0,0,...) at panic+0x127 dblfault_handler() at dblfault_handler+0x7a --- trap 0x17, eip = 0xc07e88bd9, esp = 0xe3793000, ebp = 0xe3793020 --- uma_zfree_arg(c1857960,c5718900,0) at uma_zfree_arg+0x21 m_freem(c5718900,e54ad000,e52ac65c,c543e810,1,...) at m_freem+0x2e nve_ospackettx(c543e800,e52ac65c,1,e54ad000,0,...) at nve_ospackettx+0x57 UpdateTransmitDescRingData() at UpdateTransmitDescRingData+0xd3 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal double fault while copy to NFS filesystems
Kostik Belousov пишет: On Fri, Jul 06, 2007 at 10:23:55PM +0400, Alex Keda wrote: Kostik Belousov пишет: On Fri, Jul 06, 2007 at 07:07:00PM +0400, Alex Keda wrote: When I copy files to NFS on another host kernel crash: Fatal double fault: eip = 0xc07e9e29 esp = 0xe31a3000 ebp = 0xe31a3000 cpuid = 1; apic id = 01 panic: double fault cpuid = 1 === before this, I see on /var/log/messages nve0: device timeout === how repeat problem: ussr# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 72G6.1G 60G 9%/ devfs 1.0K1.0K 0B 100%/dev ussr# dd if=/dev/zero of=file_20mb bs=1m count=20 ussr# mount 192.168.254.254:/shares /mnt/ ussr# df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a 72G6.1G 60G 9%/ devfs 1.0K1.0K 0B 100%/dev 192.168.254.254:/shares271G179G 89G67%/mnt ussr# cp file_20mb /mnt/ then, after 3-5 second I see "device timeout", and later, after 5-7 seconds - system crash = another information - this problem appearance after I upgrade remote machine (6.2-RELEASE-p5), I change CPU from Celeron 466 to PIII 800. interface on remote machine - 3com509b if I slow copy to remote machine (~100kb/s - 10% interface usage) - all good. System not crash... if I copy from remote machine - all good - system not crash... on logs on remote machine - all clean. = 3 days ago I upgrade my system to 6.2-RELEASE-p5, but - problem exists... Double fault issue might be the problem that is fixed in CURRENT/RELENG_6. To confirm this, ddb backtrace after the panic will be helpful. You will need to compile DDB into the kernel, obtain DDB prompt after the panic and issue "bt" command. Fatal double fault: eip = 0xc07e8bd9 esp = 0xe3793000 ebp = 0xe3793020 cpuid = 0; apic id = 00 panic:double fault cpuid = 0 KDB: enter: panic [thread pid 25 tid 100019] Stopped at kdb_enter+0x2b:nop Tracing pid 25 tid 100019 td 0xc527b600 kdb_enter(c090f266) at kdb_enter+0x2b panic(c092d4c9,c092d671,0,0,0,...) at panic+0x127 dblfault_handler() at dblfault_handler+0x7a --- trap 0x17, eip = 0xc07e88bd9, esp = 0xe3793000, ebp = 0xe3793020 --- uma_zfree_arg(c1857960,c5718900,0) at uma_zfree_arg+0x21 m_freem(c5718900,e54ad000,e52ac65c,c543e810,1,...) at m_freem+0x2e nve_ospackettx(c543e800,e52ac65c,1,e54ad000,0,...) at nve_ospackettx+0x57 UpdateTransmitDescRingData() at UpdateTransmitDescRingData+0xd3 Is this the full trace ? It seems to be unlikely that this is a problem I thought of. Yes. this - output 'bt' command: Tracing pid 25 tid 100019 td 0xc527b600 kdb_enter(c090f266) at kdb_enter+0x2b panic(c092d4c9,c092d671,0,0,0,...) at panic+0x127 dblfault_handler() at dblfault_handler+0x7a --- trap 0x17, eip = 0xc07e88bd9, esp = 0xe3793000, ebp = 0xe3793020 --- uma_zfree_arg(c1857960,c5718900,0) at uma_zfree_arg+0x21 m_freem(c5718900,e54ad000,e52ac65c,c543e810,1,...) at m_freem+0x2e nve_ospackettx(c543e800,e52ac65c,1,e54ad000,0,...) at nve_ospackettx+0x57 UpdateTransmitDescRingData() at UpdateTransmitDescRingData+0xd3 but there I see path to solution my problem (nve_ospackettx - i think - driver problem?) - tomorrow I insert fxp card and test again. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal double fault while copy to NFS filesystems
Pyun YongHyeon пишет: On Fri, Jul 06, 2007 at 07:07:00PM +0400, Alex Keda wrote: > When I copy files to NFS on another host kernel crash: > Fatal double fault: > eip = 0xc07e9e29 > esp = 0xe31a3000 > ebp = 0xe31a3000 > cpuid = 1; apic id = 01 > panic: double fault > cpuid = 1 > === > before this, I see on /var/log/messages > nve0: device timeout > === Try nfe(4) instead of nve(4). nve(4) is not reliable under high system load. nfe(4) is also default NVIDIA ethernet driver in CURRENT. For RELENG_6, try this one. http://www.f.csce.kyushu-u.ac.jp/~shigeaki//software/freebsd-nfe.html Thanks! It's work! :) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd6 utilities and proxy
0n Wed, Jul 18, 2007 at 11:01:11PM -0400, Dave wrote: >I've got a FreeBSD 6.2 machine now behind a squid nontransparent >authenticating proxy. The proxy use to be transparent and didn't require >authentication, those requirements now changed, so it now utilizes a >dedicated ip and basic authentication. This is fine for the machine it's on, >but for machines behind it this presents a problem. They run freshclam for >virus updating, csup or portsnap, fetch, and portupgrade and maybe others >not sure if i remembered them all. Is there a simple way i can configure >this box to deal with the new proxy? Environment variables: HTTP_PROXY= HTTP_PROXY_AUTH= FTP_PROXY= -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LAGG handbook entry
0n Mon, Aug 20, 2007 at 02:48:32PM +1200, Andrew Thompson wrote: >I have been putting together a chapter on 'Link Aggregation and >Failover', any feedback/corrections/additions would be appreciated. >http://nzfug.nz.freebsd.org/nzfug/HandbookUpdates/NetworkAggregation Awesome. Great stuff Andrew! Thanks! -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: Capability addition for IEEE 1588
0n Thu, Oct 04, 2007 at 02:47:37PM +0800, Wilkinson, Alex wrote: >0n Wed, Oct 03, 2007 at 10:52:43AM -0700, Jack Vogel wrote: > >>I am adding support into the em driver for PTP > >PTP ? Found http://ptpd.sourceforge.net/. Sorry for the noise. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: Capability addition for IEEE 1588
0n Wed, Oct 03, 2007 at 10:52:43AM -0700, Jack Vogel wrote: >I am adding support into the em driver for PTP PTP ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wireless recommendations ...
0n Thu, Oct 11, 2007 at 10:18:34PM -0300, Marc G. Fournier wrote: >... but, I haven't used wireless at all under FreeBSD ... what do we support >*well*? The machine(s) are going to be remote, so I'd like to go with >something that is generally felt to be 'consistently reliable' vs 'cheap' ... >or, at least, somewhere in the middle ground would be nice :) Atheros Chipsets are the way to go i.e. ath(4) driver. Netgate specialise in selling Atheros based chipset WiFi NICs [http://www.netgate.com/]. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
I/OAT ... Coming Soon ?
Hi all, Curious, is I/OAT [http://www.intel.com/go/ioat/] coming to FreeBSD soon ? Seems to be in the works for Linux [http://www.linux-foundation.org/en/Net:I/OAT] and OpenSolaris [http://blogs.sun.com/markusflierl/entry/what_s_going_on_in]. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named.root
0n Tue, Feb 05, 2008 at 06:45:13PM +0200, Petri Helenius wrote: >Any chance the recent root zone changes would make it to 7.0? Erm, curious, what where these changes in the first place ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Sangoma A301?
Hi Kurt, We support DS3 card but only clear channel. We don't have fractional DS3 support. Did u try to load this card? Does it recognize by kernel? If you have any questions, please feel free to contact me. Alex Sangoma Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kurt Buff Sent: March 17, 2008 5:17 PM To: freebsd-net@freebsd.org Subject: Sangoma A301? I've just received mine, and am trying to get FreeBSD 6.3 Release to recognize it. The application for this card is a fractional DS3 circuit that we're getting installed soon, and the box will eventually manage multiple links with BGP. I've been reading the docs from the Sangoma web site, and while they talk about FreeBSD installation/diagnostics/configuration/etc., they don't mention either the A301 or DS3 circuits. I've installed the wanpipe software (3.2.1), but am at this point lost in the thickets of the sparse documentation. Before I send off a message to their tech support, does anyone have words of wisdom for me? Thanks, Kurt ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: [networking-discuss] uperf - A network benchmark tool
FYI - Forwarded message from Neelakanth Nadgir <[EMAIL PROTECTED]> - Date: Tue, 06 May 2008 17:34:23 -0700 From: Neelakanth Nadgir <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: Neelakanth Nadgir <[EMAIL PROTECTED]> Subject: [networking-discuss] uperf - A network benchmark tool [apologies if you received duplicates] Folks, we just opensourced (under GPL v3) a network benchmarking tool called uperf at http://www.uperf.org. I encourage you to check it out. uperf (just like filebench) takes a description of the networking component of workloads and replays it. Using a "model" allows you to change different parameters (like scale, protocol, etc..) and analyze performance. I hope you find it useful. Uperf is work in progress and we are adding more functionality. If you would like to contribute, please feel free so; we can use all the help. thanks, -neel -- --- Neelakanth Nadgir http://blogs.sun.com/realneel ___ networking-discuss mailing list [EMAIL PROTECTED] - End forwarded message - IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to identify a PHY?
0n Mon, May 12, 2008 at 01:19:58PM +0200, Marius Strobl wrote: >If the system is running the simplest thing in order to identifiy >the PHYs is to check the oui= and model= output of `devinfo -v`. >Otherwise boot verbose and check the OUI and model output of >ukphy(4). Curious, once we have the hex codes for the oui and model e.g. brgphy0 pnpinfo oui=0x818 model=0x1a rev=0x2 at phyno=1 How do we then determine what 0x818 and 0x1a refer to ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: connect(): Operation not permitted
Hi Johan and List,
In my case a few months ago it was pahu. Don't give that fine fellow an
account on your precious system !
But seriously, I had a pf-firewalled jail being being used for DNS
testing, with large numbers of udp "connections" hanging around in pf
state. While the default udp timeout settings in PF are lower than those
of the tcp timeouts, it is was still too high for it to to remove the
states in time before hitting the default 10k state limit!
If this is the case with you - run 'pfctl -s state | wc -l' - when there
is traffic load you may see that hitting 10k states if you've not tuned
that variable.
What to do next - up the state limit or lower the state timeouts. I did
both, to be safe.
in /etc/pf.conf these must be at the very top of the file:
# options
# 10k is insanely low, lets raise it..
set limit { frags 16384, states 32768 }
# timeouts - see 'pfctl -s timeouts' for options - you will want to
# change the tcp ones rather than the udp ones for your smtp setup.
# but these are mine, I set them for the dns traffic.
set timeout { udp.first 15, udp.single 5, udp.multiple 30 }
don't forget to:
$ /etc/rc.d/pf check && /etc/rc.d/pf reload
HTH,
Alex
On Sat, 2008-05-17 at 16:33 +0200, Johan Ström wrote:
> Hello
>
> I got a FreeBSD 7 machine running mail services (among other things).
> This machine recently replaced a FreeBSD 6.2 machine doing the same
> tasks.
> Now and then I need to send alot of mail to customers (mailing list),
> and one thing i've noticed now after the change is that when I use a
> lot of connections subsequently (high connection rate, even if they
> are very shortlived) inside a jail (dunno if that has anything to do
> with it though), I start to get Operation not permitted in return to
> connect().
> I've seen this in the PHP app that sends mail, when it tried to
> connect to localhost, as well as from postfix when it have been trying
> to connect to amavisd on localhost, but also from postfix when it has
> tried to connect to remote SMTP servers.
>
> I do have PF for filtering, but there are no max-src-conn-rate limits
> enabled for any rules that is used for this. However, from one of the
> jail I do have a hfsc queue limiting the outgoing mail traffic from
> one jailed IP. But I'm not sure that this would be the problem, since
> I've also seen the problem when doing localhost connects in the jail,
> and also in other jails on an entierly different IP that is not
> affected.
>
> Does anyone have any clues about what I can look at and tune to fix
> this?
>
> Thanks!
>
> --
> Johan Ström
> Stromnet
> [EMAIL PROTECTED]
> http://www.stromnet.se/
>
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
signature.asc
Description: This is a digitally signed message part
Re: anyone tried the Multi routing table code yet?
0n Fri, May 23, 2008 at 05:39:17PM -0700, Julian Elischer wrote: >subject says it all really.. No, but I would like to ... if you could hold my hand :) -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mpd, nat, netflow: does not work for me
Hello! I'm trying to use mpd 5.1, on FreeBSD 6.2, and got some really strange problems. 1. NAT. [10:37] services-new:/<2>etc/mpd5 # grep nat /usr/local/etc/mpd5/mpd.conf set nat address 81.195.122.86 set iface enable nat in web interface, option for interface includes "nat enable" NO address translation at all. 2. Netflow set iface enable netflow-out set netflow peer PEER-IP-ADDR 8787 netflow-out, of course, is labeled as "enable" MPD even sends some netflow data (1464 bytes packet every 15-20 minutes, it is definitely insufficient to send required data), collector receives it and stores nothing. Maybe someone could help? Alex. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [RFC] ifconfig: match by link-level address
On Thu, May 20, 2004 at 10:18:38AM -0700, Brooks Davis wrote: >> This could be the first step towards teaching rc.conf about something like >> network_interfaces_rename="hw-00:03:0d:08:dc:a7 sis0int" > I don't really like the idea of adding magic values to the interface > namespace that only work with ifconfig. If you want ifconfig to match I agree, but there is another option: make such things not ifconfig-specific. I mean that it could be done though renaming the interface into the some lladdr-dependent name with fixed format. For example, ifconfig fxp0 llname will rename fxp0 into hw-00-90-27-35-ca-0c. As far as we know the format and MAC-address we could then do ifconfig hw-00-90-27-35-ca-0c name pppoeint This could be implemented easely right now and then automated though /etc/rc* Actually the discussing feature is long time expected one, so it would be nice to have it implemented finally :) Sincerely, Alex Semenyaka ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [RFC] ifconfig: match by link-level address
On Sun, May 23, 2004 at 07:37:37PM -0400, Louis A. Mamakos wrote: > >>> This could be the first step towards teaching rc.conf about something like > >>> network_interfaces_rename="hw-00:03:0d:08:dc:a7 sis0int" > >> I don't really like the idea of adding magic values to the interface > >> namespace that only work with ifconfig. If you want ifconfig to match >> I agree, but there is another option: make such things not ifconfig-specific. >> I mean that it could be done though renaming the interface into the some >> lladdr-dependent name with fixed format. For example, > This is all pretty interesting, though it seems like you'd only > need to cobble together a shell script to do what you're after. You've absolutely right and I wanted to propose it just on the base of currently existing functionality (independently of this thread). However if there will be automatic renaming things would be easier. Thus I decided to combine both approaches since it leads to simple solution. I would post my current changes (those giving the discussing functionality) to the startup scripts as PR and send here the number. I'll do it if anybody will express any interest in that. Actually those scripts could be changed in future if ``ifconfig'' will provide such possibility out-of-box, and changes will be seamless for users. -- Sincerely, Alex Semenyaka ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [RFC] ifconfig: match by link-level address
On Mon, May 24, 2004 at 09:51:47AM -0400, Louis A. Mamakos wrote: >> You've absolutely right and I wanted to propose it just on the base of >> currently existing functionality (independently of this thread). However if >> there will be automatic renaming things would be easier. Thus I decided to >> combine both approaches since it leads to simple solution. > This interface renaming operation is likely to only occur as the system > boots, and probably is an "automated" process rather than one that involves > human. Well, to some extend. I mean that the process should be automated but I want to be able to specify what to rename. > Keeping with the decades-long UNIX tradition of using combinations > of tools would lead you to writing a simple shell script, rather than going > to all the trouble to extend the existing tool. Exactly what I already DID :) Probably I did not express myself clear enough, sorry. I did it just as new script (/etc/rc.ifrename) which have simple config (/etc/ifrename.conf) like that: 00:01:02:03:04:05 int0 00:02:04:08:10:20 int1 Nothing but current /sbin/ifconfig and /bin/sh. And again, if it is interesting for somebody I'll publish patches... > Certainly there's no performance-related reason to do so. Sure. > I guess I don't see how you might choose to extend ifconfig to implement > some function that can't be done with some external tools. About the only Well actually you should discuss the necessity of the changes in ifconfig with the author of the original posting :) What I proposed was just middle way between what he proposed and what I did. I mean if somebody is changing ifconfig anyway that way would be easier to implement. However personally I did the job without any modification of ifconfig at all. > I'm not sure how much easier "automatic" renaming might be. You still > need some ability to specify policy on what interfaces are renamed > (e.g., only 100Base-T ethernet but not 802.11 wireless). What I am trying to solve is the situation when you have a box with (say) 4 etherexpresses and first on them is dead. Then old fxp1 becomes fxp0, old fxp2 becomes fxp1 and so on. And now you cannot remotely connect to that box abd find out what is going on, that's it. So I want automatic renaming during the boot, but I want it controlled: "this card will have the name intel0, that on - intel1", and it should leave untouched cards without explicit entry in the renaming config. It is the way I did it. Do you see any disadvanatges there? About the media type... well, I believe that if I will pick the MAC-address of the card and new name I know what that card is, right? I do ifconfig, choose cards I want to rename, and create renaming config. Why do I need to specify also media type? Is it possible that my wireless adaptor will have the same MAC-adress as my Inter Etherexpress? I believe not. -- Sincerely, Alex Semenyaka ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic in Freebsd 4.7 (m_copydata/tcp_output)
Hi,
I had a freebsd 4-7 stable system panic while i was running low on mbufs.
Can someone provide me with some background info so I can debug this some
more?
How would I get into the situation where the socket has no mbuf allocated to
it?
Where does this allocation usually take place?
How/why did send acknowledge count be greater then the send next count? Is
-1 a valid offset?
Saw a few similar postings where m_copy data ran in to the same args from
tcp_output
http://www.google.ca/search?q=cache:s7uT8Qeei-0J:www.geocrawler.com/mail/msg
.php3%3Fmsg_id%3D657553+freebsd+tcp_output+sb_mb&hl=en
and
an old bug
http://www.freebsd.org/cgi/query-pr.cgi?pr=1013
Any pointers to get me going on this would be appreciated. Thanks in
advance.
(kgdb) bt
#0 dumpsys ()
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/kern/kern_shutdown
.c:492
#1 0xc01c5978 in boot (howto=256)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/kern/kern_shutdown
.c:321
#2 0xc01c5ea1 in panic (fmt=0xc034945e "%s")
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/kern/kern_shutdown
.c:607
#3 0xc02ef324 in trap_fatal (frame=0xf2eca92c, eva=0)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/i386/i386/trap.c:9
92
#4 0xc02eef4d in trap_pfault (frame=0xf2eca92c, usermode=0, eva=12)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/i386/i386/trap.c:885
#5 0xc02ee9ef in trap (frame={tf_fs = -828506088, tf_es = -828506096,
tf_ds = 116129808, tf_edi = 1, tf_esi = 0, tf_ebp = -219371144,
tf_isp = -219371176, tf_ebx = -307373120, tf_edx = -1,
tf_ecx = -334664960, tf_eax = -1, tf_trapno = 12, tf_err = 0,
tf_eip = -1071748160, tf_cs = 8, tf_eflags = 66050, tf_esp =
-307373120,
tf_ss = 12})
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/i386/i386/trap.c:484
#6 0xc01e6bc0 in m_copydata (m=0x0, off=-1, len=1,
cp=0xc5b30a74 "~ñ\202,\200\205R\001òP\a÷;ªïIÅ+6«d\eh\17708.172.128.222
(http://www.footprint.net\";>Footprint
3.0/FPMCP)\n\n")
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/kern/uipc_mbuf.c:1002
#7 0xc022f0ce in tcp_output (tp=0xedaddbc0)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/netinet/tcp_output.c:
608
#8 0xc022e0bf in tcp_input (m=0xc5b30a00, off0=20, proto=6)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/netinet/tcp_input.c:2
252
#9 0xc02256bf in ip_input (m=0xc5b30a00)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/netinet/ip_input.c:88
1
#10 0xc0225747 in ipintr ()
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/netinet/ip_input.c:90
2
#11 0xc02dde61 in swi_net_next ()
#12 0xc0207100 in spec_write (ap=0x37)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/miscfs/specfs/spec
_vnops.c:283
#13 0xc0292d10 in ufsspec_write (ap=0xf2ecae70)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/ufs/ufs/ufs_vnops.
c:1873
#14 0xc0293465 in ufs_vnoperatespec (ap=0x0)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/ufs/ufs/ufs_vnops.
c:2440
#15 0xc0202996 in vn_write (fp=0xd7e676c0, uio=0xf2ecaedc, cred=0xd7a32880,
flags=0, p=0xf2c43ee0) at vnode_if.h:363
#16 0xc01d767e in dofilewrite (p=0xf2c43ee0, fp=0xd7e676c0, fd=0, buf=0x0,
nbyte=4075597532, offset=-942185962111238144, flags=0)
at /d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/sys/file.h:162
#17 0xc01d751b in write (p=0xf2c43ee0, uap=0xf2ecaf80)
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/kern/sys_generic.c
:329
#18 0xc02ef67d in syscall2 (frame={tf_fs = -1068957649, tf_es = 47,
tf_ds = 136314927, tf_edi = 1, tf_esi = 1747982016,
tf_ebp = -1079200356, tf_isp = -219369516, tf_ebx = 1748019148,
tf_edx = 136388608, tf_ecx = 1876638720, tf_eax = 4, tf_trapno = 22,
tf_err = 2, tf_eip = 1747725928, tf_cs = 31, tf_eflags = 646,
tf_esp = -1079200416, tf_ss = 47})
at
/d3/builds/swbuild_swbuild_plt_proton5_FREEBSD/src/sys/i386/i386/trap.c:1
193
#19 0xc02d9d6b in Xint0x80_syscall ()
#20 0x682b8981 in ?? ()
(kgdb) p *tp
$7 = {t_segq = {lh_first = 0x0}, t_dupacks = 0, unused = 0x0,
tt_rexmt = 0xedaddca4, tt_persist = 0xedaddcbc, tt_keep = 0xedaddcd4,
tt_2msl = 0xedaddcec, tt_delack = 0xedaddd04, t_inpcb = 0xedaddb00,
t_state = 4, t_flags = 33249, t_force = 0, snd_una = 1726825387,
snd_max = 1726825387, snd_nxt = 1726825386, snd_up = 1726825386,
snd_wl1 = 3607398008, snd_wl2 = 1726825387, iss = 1726825386,
irs = 3607398007, rcv_nxt = 3607398008, rcv_adv = 3607455928,
rcv_wnd = 57920, rcv_up = 3607398008, snd_wnd = 65535, snd_cwnd = 1448,
snd_bwnd = 1073725440, snd_ssthresh = 2904, snd_bandwidth = 0,
snd_recover = 1726825387, t_maxopd = 1460, t_rcvtime = 280063744,
t_starttime = 280063744, t_rtttime = 0, t_rtseq = 1726825386,
t_bw_rtttime = 280054231, t_bw_rtseq = 1726825386, t_rxtcur = 24464,
t_maxseg = 1448, t_srtt = 255616, t_rttvar = 63904, t_rxtshift = 0,
t_rttmin = 2500, t_
altq in current: where?
Hello! I'm trying to find out how to set up altq in 5.2.1-release and simply cannot understand where to start from. There is an rc.d script, and node for altq; but nothing more, no docs, no daemons. On altq page, the latest release is about stoneage time. Is it dead? Or I'm just cannot find the starting point for searching? -- Alex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
help needed with dummynet
Hello! I've read man ipfw several times but still did not catch the following thing: I want to make ssh traffic 'top priority', giving it all bandwidth it wants, without explicitly limiting other kinds of traffic. man ipfw is quite unclear on queue usage, can anyone give me a working example? -- Alex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
