Re: Simple question, what is an inOctet ... ?
On Wed, Mar 24, 2004 at 12:01:39PM -0400, Marc G. Fournier wrote: > > Just setup net-snmp, and zabbix to monitor it ... what exactly is an > Octet? 1 byte? An octet is eight bits. A byte is also usually eight bits, but this is not universally true. 'Octet' is used in many standards-documents to have an unambigous term for a collection of eight bits, since 'byte' does not have a well-defined size. -- Erik Trulsson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unused argument in in_pcballoc() function.
Hi. I've found unused argument in in_pcballoc() function: http://people.freebsd.org/~pjd/patches/in_pcballoc.patch Is it possible to commit it, as it affect ipv6 code as well? -- Pawel Jakub Dawidek http://www.FreeBSD.org [EMAIL PROTECTED] http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! pgp0.pgp Description: PGP signature
Re: Fatal trap in rt_msg2
Also, my kernel is configured without INET6 and my netmask is /23
.. maybe I should try again with INET6 and /24 ??
Roberto Nunnari wrote:
Hello.
I'm posting here as I've been told in current it's a better place.
On March 18th I did an upgrade from 5.2-p1 to RELENG_5_2 which
gave me 5.2.1-p3. cvsup, build and install went well, but
when I rebooted I got Fatal trap 12 during network configuration,
late in the boot process..
I could boot and get a working system using the old kernel..
Anyways, i did a partial restore
/boot, /bin, /etc, /lib, /libexec, /sbin
that was enough to get the system back to multiuser mode
and running great as usual..
Yet.. I cannot seam to be able to upgrade the system any more..
Please help. Just ask and I'll be glad to give all relevant
information you may need in order to solve this problem.
I'm new to kernel debugging, but I'll do my best. I just
need some help and guidance. Thanks.
here is the 5.2-p1 kernel config and dmesg
http://www.dti.supsi.ch/~robi/WEB.20040323
http://www.dti.supsi.ch/~robi/dmesg.20040323
and this is the kernel config I used to save the dump.
http://www.dti.supsi.ch/~robi/WEB
it seams that sa in rt_msg2 (/usr/src/sys/net/rtsock.c:708)
is a bogus pointer..
Here is my gdb session:
web.dti.supsi.ch# gdb -k kernel.debug /usr/crash/vmcore.1
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xff70ff70
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0568949
stack pointer = 0x10:0xe40a1b04
frame pointer = 0x10:0xe40a1b28
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 = 303 (ifconfig)
trap number = 12
panic: page fault
cpuid = 0;
boot() called on cpu#0
syncing disks, buffers remaining... 218 218 216 216 215 215 215 215 215
215 215 215 215 215 215 215 215 215 215 215 215 215 215 215
giving up on 200 buffers
Uptime: 46s
Dumping 1023 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304
320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592
608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880
896 912 928 944 960 976 992 1008
---
Reading symbols from
/usr/obj/usr/src/sys/WEB/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/WEB/modules/usr/src/sys/modules/acpi/acpi.ko.debug
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) list *0xc0568949
0xc0568949 is in rt_msg2 (/usr/src/sys/net/rtsock.c:708).
703 register struct sockaddr *sa;
704
705 if ((sa = rtinfo->rti_info[i]) == 0)
706 continue;
707 rtinfo->rti_addrs |= (1 << i);
708 dlen = ROUNDUP(sa->sa_len);
709 if (cp) {
710 bcopy((caddr_t)sa, cp, (unsigned)dlen);
711 cp += dlen;
712 }
(kgdb) backtrace
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc04f1791 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc04f1b6e in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc062547c in trap_fatal (frame=0xe40a1ac4, eva=0) at
/usr/src/sys/i386/i386/trap.c:821
#4 0xc0625122 in trap_pfault (frame=0xe40a1ac4, usermode=0,
eva=4285595504) at /usr/src/sys/i386/i386/trap.c:735
#5 0xc0624d33 in trap (frame=
{tf_fs = 24, tf_es = -1066860528, tf_ds = 16, tf_edi = 0, tf_esi =
4, tf_ebp = -469099736, tf_isp = -469099792, tf_ebx = -964638720, tf_edx
= -9371792, tf_ecx = -469099704, tf_eax = 16, tf_trapno = 12, tf_err =
0, tf_eip = -1068070583, tf_cs = 8, tf_eflags = 66050, tf_esp =
-967258976, tf_ss = -964361888})
at /usr/src/sys/i386/i386/trap.c:420
#6 0xc0611f28 in calltrap () at {standard input}:94
#7 0xc0568fe6 in sysctl_iflist (af=0, w=0xe40a1b9c) at
/usr/src/sys/net/rtsock.c:981
#8 0xc056943e in sysctl_rtsock (oidp=0xc0694b00, arg1=0xe40a1cb4,
arg2=4, req=0xe40a1c10) at /usr/src/sys/net/rtsock.c:1132
#9 0xc04fb89a in sysctl_root (oidp=0x0, arg1=0x16, arg2=-469099504,
req=0xe40a1cb8) at /usr/src/sys/kern/kern_sysctl.c:1179
#10 0xc04fbb4d in userland_sysctl (td=0x0, name=0xe40a1cac, namelen=6,
old=0xe40a1c10, oldlenp=0xe40a1cb8, inkernel=0, new=0x16, newlen=0,
retval=0xe40a1ca8) at /usr/src/sys/kern/kern_sysctl.c:1286
Xircom REM56G10/100
Good morning, I spent last night digging through the archives trying to see if this card has been fixed in CURRENT. Does any one know the status of the fix? It is the 'CIS is to long -- truncating' error. I am about to try out the OLDCARD kernelconf and see if that takes care of the problem, but I just wanted to check before I started merging my conf with the OLDCARD one. Thanks, Brian Morgan. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Looking for switch recommendations ...
I'm looking at replacing my el'cheapo switch with something better that will allow me to fix my issues with the em/full-duplex problem ... I'm looking for ssomething managed, as well as SNMP aware so that I can tie it into Zabbix for monitoring ... something 8 or 12 port preferred. Cisco, of course, is always a big name ... but also expensive ... oen recommendation is the xl 1900, but I can't find any specs on her at cisco's site, so discontinued product? What about Netgear, which I have easy access to? Or Alcatel? models to stay away from? Thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
"Bits dont fail me now!" was what Marc G. Fournier muttered as he hastily typed this on Fri, Mar 26, 2004 at 12:05 : > I'm looking at replacing my el'cheapo switch with something > better that will allow me to fix my issues with the > em/full-duplex problem ... > I'm looking for ssomething managed, as well as SNMP aware so > that I can tie it into Zabbix for monitoring ... something 8 or > 12 port preferred. > Cisco, of course, is always a big name ... but also expensive ... oen > recommendation is the xl 1900, but I can't find any specs on her at > cisco's site, so discontinued product? Cisco is expensive - and the used market price stays up too. But the small ISP I work with needed something that did more than their Cisco 2948 [early model]. They got a Foundry Networks Netiron 24 port - used - from eBay. It is is a level 3 switch and it can be turned into router only or router/switch. $400. Not being a name-brand that small business equate like they do Cisco the used prices are just a fraction of the comparable Cisco product. I see similar one for $495 =buy-now= and they have been lower. Bill -- Bill Vermillion - bv @ wjv . com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
Hi, Don't know your budget, but HP Procurve 2650 (layer2/layer3 hybrid) works just fine. Full managed, snmp et al. respectfully /per [EMAIL PROTECTED] > > I'm looking at replacing my el'cheapo switch with something better > that will allow me to fix my issues with the em/full-duplex problem > ... > > I'm looking for ssomething managed, as well as SNMP aware so that I > can tie it into Zabbix for monitoring ... something 8 or 12 port > preferred. > > Cisco, of course, is always a big name ... but also expensive ... > oen recommendation is the xl 1900, but I can't find any specs on > her at cisco's site, so discontinued product? > > What about Netgear, which I have easy access to? Or Alcatel? > > models to stay away from? > > Thanks ... > > > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: > yscrappy ICQ: 7615664 > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
One thing I hate about comparison shopping for computers ... there are so many options :( What is the difference between Layer2 and Layer3, and what does that affect? I see the HP Procurve 2626 (I don't need 50 ports yet) for ~$600 on the web ... while I can pick up the Dell PowerConnect 3324 is ~$500 ... How do I compare the two? They seem to both use different terminologies for what I'd guess are the same thing: HP: Throughput: 2650 - 10.1 mpps (64-byte packets) 2626 - 6.6 mpps (64-byte packets) Switching capacity: 2650 - 13.6 Gbps 2626 - 9.6 Gbps Dell: Switch Fabric Capacity 8.8 Gb/s Forwarding Rate 6.5 Mpps So, in both cases, the HP is faster, but ... is that 6.6mpps "per port" (ie. the pp?) ... right now, I'm seeing max of around 3Mps going out a server, with average being well below 1 ... so I can't see hitting that high any time soon ... Based on the #s for throughput, I can't see a big advantage of HP over Dell to warrant the extra cost, but I see nothing on Dell about the Layer2/3 stuff ... but not sure what that gives either ... Price wise, both the HP and Dell versions look reasonable, and I think the Dell is easier for me to get in Panama (I know there is a local office for them there) ... I've had one + for Dell ... does anyone have any caveats against them? Or kudos too? On Fri, 26 Mar 2004, Per Engelbrecht wrote: > Hi, > Don't know your budget, but HP Procurve 2650 (layer2/layer3 hybrid) > works just fine. Full managed, snmp et al. > > respectfully > /per > [EMAIL PROTECTED] > > > > > > I'm looking at replacing my el'cheapo switch with something better > > that will allow me to fix my issues with the em/full-duplex problem > > ... > > > > I'm looking for ssomething managed, as well as SNMP aware so that I > > can tie it into Zabbix for monitoring ... something 8 or 12 port > > preferred. > > > > Cisco, of course, is always a big name ... but also expensive ... > > oen recommendation is the xl 1900, but I can't find any specs on > > her at cisco's site, so discontinued product? > > > > What about Netgear, which I have easy access to? Or Alcatel? > > > > models to stay away from? > > > > Thanks ... > > > > > > Marc G. Fournier Hub.Org Networking Services > > (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: > > yscrappy ICQ: 7615664 > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > > Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
Marc G. Fournier wrote: I'm looking for ssomething managed, as well as SNMP aware so that I can tie it into Zabbix for monitoring ... something 8 or 12 port preferred. The 3com SuperStack 2 line is being replaced by the SS3 (which have gigabit uplinks) so the older models are priced to clear out; you should be able to find a 12-port 3300XM for ~ $400 or so... -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
< said: > What is the difference between Layer2 and Layer3, and what does that > affect? "Layer 2 switch" is a fancy name for a bridge. "Layer 3 switch" is a fancy name for a router. -GAWollman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Looking for switch recommendations ...
From: Marc G. Fournier [mailto:[EMAIL PROTECTED] > One thing I hate about comparison shopping for computers ... there are > so many options :( > > What is the difference between Layer2 and Layer3, and what does that > affect? > > I see the HP Procurve 2626 (I don't need 50 ports yet) for > ~$600 on the > web ... while I can pick up the Dell PowerConnect 3324 is ~$500 ... > > How do I compare the two? They seem to both use different > terminologies > for what I'd guess are the same thing: > > HP: > Throughput: 2650 - 10.1 mpps (64-byte packets) 2626 - 6.6 > mpps (64-byte packets) > Switching capacity: 2650 - 13.6 Gbps 2626 - 9.6 Gbps > > Dell: > Switch Fabric Capacity 8.8 Gb/s > Forwarding Rate 6.5 Mpps > > So, in both cases, the HP is faster, but ... is that 6.6mpps > "per port" > (ie. the pp?) ... right now, I'm seeing max of around 3Mps going out a > server, with average being well below 1 ... so I can't see > hitting that > high any time soon ... > > Based on the #s for throughput, I can't see a big advantage of HP over > Dell to warrant the extra cost, but I see nothing on Dell about the > Layer2/3 stuff ... but not sure what that gives either ... > > Price wise, both the HP and Dell versions look reasonable, > and I think the > Dell is easier for me to get in Panama (I know there is a > local office for > them there) ... > > I've had one + for Dell ... does anyone have any caveats > against them? Or > kudos too? Gigabit ethernet has a maximum rate of ~1.5Mpps. This is millions of packets per second. Your server is likely 3Mbps, which if you figure the average packet size is ~400 bytes, is more like 1kpps. If you are not looking for layer 3 (routing), but just a switch, then look @ something like the dlink or linksys(cisco) layer 2 offers, compared vs e.g. a cisco cat2970. DGS-3224TG is what i use. Something like the linksys SR2024 is probably fine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
> What is the difference between Layer2 and Layer3, and what does that > affect? Layer3 == routing (based on IP destination address) Layer2 == switching (based on enet dest. address) Layer3 is probably not important for you. > HP: > Throughput: 2650 - 10.1 mpps (64-byte packets) 2626 - 6.6 mpps (64-byte packe > ts) > Switching capacity: 2650 - 13.6 Gbps 2626 - 9.6 Gbps > > Dell: > Switch Fabric Capacity 8.8 Gb/s > Forwarding Rate 6.5 Mpps > > So, in both cases, the HP is faster, but ... is that 6.6mpps "per port" > (ie. the pp?) ... right now, I'm seeing max of around 3Mps going out a > server, with average being well below 1 ... so I can't see hitting that > high any time soon ... For 100Mbps ports, the max packet rate in one direction is 10^8/672 == 148809 pps (packets per sec) per port. So for 24 port full duplex ports you get an aggregate maximum throughput of 148809*24*2 = 7738068 = 7.14Mpps (Million pps). For a 48 port switch it is 14.29Mpps. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
Hi again > > One thing I hate about comparison shopping for computers ... there > are so many options :( - what are your needs vs. $, kinda answers this. > > What is the difference between Layer2 and Layer3, and what does > that affect? All switching is done in layer2! Layer3 switch 'features' (functionality) is was the vendor put in the box. Depending on the amount of $ you're going to spent, you can have switches that can act as routers. > > I see the HP Procurve 2626 (I don't need 50 ports yet) for ~$600 on > the web ... while I can pick up the Dell PowerConnect 3324 is ~$500 > ... > > How do I compare the two? They seem to both use different > terminologies for what I'd guess are the same thing: > > HP: > Throughput: 2650 - 10.1 mpps (64-byte packets) 2626 - 6.6 mpps > (64-byte packets) Switching capacity: 2650 - 13.6 Gbps 2626 - 9.6 > Gbps > > Dell: > Switch Fabric Capacity 8.8 Gb/s > Forwarding Rate 6.5 Mpps > > So, in both cases, the HP is faster, but ... is that 6.6mpps "per > port" (ie. the pp?) ... right now, I'm seeing max of around 3Mps > going out a server, with average being well below 1 ... so I can't > see hitting that high any time soon ... The mpps is normally what the switch can do in total / back-plan back-bone or whatever the vendor want to call it. > > Based on the #s for throughput, I can't see a big advantage of HP > over Dell to warrant the extra cost, but I see nothing on Dell > about the Layer2/3 stuff ... but not sure what that gives either > ... If you're going to calculate a $ pr. port cost-benefit, then you have to make sure the rest of your setup is balanced accordingly (why spent time on $ pr. port if the nic in the rest of the setup is cheap) > > Price wise, both the HP and Dell versions look reasonable, and I > think the Dell is easier for me to get in Panama (I know there is a > local office for them there) ... There's a lot more to network boxes (router, bridge, switch et al.) than just price and capacity, e.g. management, (I)OS, firmware, support. best of luck. respectfully /per [EMAIL PROTECTED] > > I've had one + for Dell ... does anyone have any caveats against > them? Or kudos too? > > On Fri, 26 Mar 2004, Per Engelbrecht wrote: > >> Hi, >> Don't know your budget, but HP Procurve 2650 (layer2/layer3 >> hybrid) works just fine. Full managed, snmp et al. >> >> respectfully >> /per >> [EMAIL PROTECTED] >> >> >> > >> > I'm looking at replacing my el'cheapo switch with something >> > better that will allow me to fix my issues with the >> > em/full-duplex problem ... >> > >> > I'm looking for ssomething managed, as well as SNMP aware so >> > that I can tie it into Zabbix for monitoring ... something 8 or >> > 12 port preferred. >> > >> > Cisco, of course, is always a big name ... but also expensive >> > ... oen recommendation is the xl 1900, but I can't find any >> > specs on her at cisco's site, so discontinued product? >> > >> > What about Netgear, which I have easy access to? Or Alcatel? >> > >> > models to stay away from? >> > >> > Thanks ... >> > >> > >> > Marc G. Fournier Hub.Org Networking Services >> > (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: >> > yscrappy ICQ: 7615664 >> > ___ >> > [EMAIL PROTECTED] mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-net >> > To unsubscribe, send any mail to >> > "[EMAIL PROTECTED]" >> >> >> > > > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: > yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Fri, 26 Mar 2004, Bakul Shah wrote: > For 100Mbps ports, the max packet rate in one direction is 10^8/672 == > 148809 pps (packets per sec) per port. So for 24 port full duplex ports > you get an aggregate maximum throughput of 148809*24*2 = 7738068 = > 7.14Mpps (Million pps). For a 48 port switch it is 14.29Mpps. so, the closer the Mpps gets to that 7.1Mpps, the better the switch overall? I take it that has to do with the CPU driving the switch itself, or is there other factors that help drive that # up? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
> > For 100Mbps ports, the max packet rate in one direction is 10^8/672 == > > 148809 pps (packets per sec) per port. So for 24 port full duplex ports > > you get an aggregate maximum throughput of 148809*24*2 = 7738068 = > > 7.14Mpps (Million pps). For a 48 port switch it is 14.29Mpps. > > so, the closer the Mpps gets to that 7.1Mpps, the better the switch > overall? I take it that has to do with the CPU driving the switch itself, > or is there other factors that help drive that # up? Well, "better overall" involves a lot more than the max throughput -- you are very very unlikely to see nothing but 64 byte pkts in your network (typically 50% of pkts are acks, the other 50% are MTU size) so 6.6Mbps seems good enough to me. I would look at quality first, and then service, how this switch is to be used and whether there are other features that may be relevant (such as vlan, QoS etc). Also, I would choose a switch to ensure there is about 50% to 100% headroom for growth (in # of ports, etc). In terms of achieving max throughput it depends on how the switch is engineered. CPU driving the switch matters less than whether they have done a balanced design. You also need a backplane fabric that is capable of delivering full b/w no matter what the traffic pattern is (you may not achieve 7.14Mbps for a given pattern but for each pattern one can calculate a theoretical max which should be achievable). In any case, quality of the switch construction probably matters the most. If rj45 ports are flimsy nothing else matters! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Fri, Mar 26, 2004 at 04:25:55PM -0400, Marc G. Fournier wrote: > On Fri, 26 Mar 2004, Bakul Shah wrote: > > > For 100Mbps ports, the max packet rate in one direction is 10^8/672 == > > 148809 pps (packets per sec) per port. So for 24 port full duplex ports > > you get an aggregate maximum throughput of 148809*24*2 = 7738068 = > > 7.14Mpps (Million pps). For a 48 port switch it is 14.29Mpps. > > so, the closer the Mpps gets to that 7.1Mpps, the better the switch > overall? I take it that has to do with the CPU driving the switch itself, there is no 'cpu driving the switch', forwarding is done in hardware even in the cheapest units. E.g. see http://www.realtek.com.tw/products/products1-1.aspx?lineid=2 a switch (Edimax) based on the 8316 costs here 60 euro incl.VAT and does 16 ports full duplex at full wire speed on all ports. cheers luigi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
Luigi Rizzo wrote: a switch (Edimax) based on the 8316 costs here 60 euro incl.VAT and does 16 ports full duplex at full wire speed on all ports. But no counters and no management. Pete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Fri, Mar 26, 2004 at 11:05:05PM +0200, Petri Helenius wrote: > Luigi Rizzo wrote: > > > > >a switch (Edimax) based on the 8316 costs here 60 euro incl.VAT > >and does 16 ports full duplex at full wire speed on all ports. > > > > > > > > > But no counters and no management. for that you need to go to the RTL8326, yes. Still very cheap, I think managed units based on this one sell around $250. Anyways the point was, there is no CPU doing the forwarding or stats handling. cheers luigi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPsec: problems after upgrade 4.8 to 4.9
On Mon, Mar 22, 2004 at 08:21:35AM +0100, Helge Oldach wrote: > > (*) ERROR: ipsec_doi.c:440:print_ph1mismatched(): rejected dh_group: > >DB(prop#1:trns#1):Peer(prop#0:trns#0) = 1024-bit MODP group:1536-bit MODP > >group > >dh_group 2; > Try changing the last line to > >dh_group 5; Hi, wow, that works again! Thx alot! However, I still have two error lines in my logs: INFO: isakmp.c:899:isakmp_ph1begin_r(): begin Identity Prot ection mode. ERROR: ipsec_doi.c:1318:get_transform(): Only a single transform payload is allowed during phase 1 processing. INFO: isakmp.c:2412:log_ph1established(): ISAKMP-SA established 192.168.11.1[500]-192.168.11.10[500] spi:0d9434c7440e72ce:751d06200476bf1a INFO: isakmp.c:1049:isakmp_ph2begin_r(): respond new phase 2 negotiation: 192.168.11.1[0]<=>192.168.11.10[0] ERROR: proposal.c:496:cmpsatrns(): authtype mismatched: my: 2 peer:1 Can anyone tell me the cause of this? Thx in advance. /Holger -- ++ GnuPG Key -> http://www.t-online.de/~holger.eitzenberger ++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
Luigi Rizzo wrote: for that you need to go to the RTL8326, yes. Still very cheap, I think managed units based on this one sell around $250. Anyways the point was, there is no CPU doing the forwarding or stats handling. Do you know if this has a fan? I´ve been looking for managed L2 devices without noise but haven´t really located any. Pete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ifconfig causing fatal trap
I have a new thinkpad t40 with Intel PRO/1000 that I use as the em device and a cisco wireless that I use as the an device. typing /sbin/ifconfig causes a kernel panic (using GENERIC) and forces a reboot. I followed the directions in the manual and did: nm -n /kernel | grep c039cf (7e are also in the instruction pointer but returned no results) This shows the fault is caused by: cpystrflt cpystrflt_x copystr bcmp lgdt lidt lldt ltr ssdtosd Anyone have any idea what is causing this and how I can fix it? Thanks in advance! -Josh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Friday 26 March 2004 11:08 am, Bakul Shah wrote: > > What is the difference between Layer2 and Layer3, and what does that > > affect? > > Layer3 == routing (based on IP destination address) > Layer2 == switching (based on enet dest. address) > > Layer3 is probably not important for you. That depends. For a test network, a VLAN-capable Layer3 switch can be quite a nice tool, because you can partition the switch into 2 or 3 separate virtual networks without buying a bunch of boxes. I write this not because I think VLAN switches are a general necessity, but rather because I have an idea of the kinds of activities Marc gets involved in, and suspect his networking needs are often far beyond ordinary. I'm going to add a testimonial for the HP switches here. Given that I'm a former Xylan/Alcatel employee, this should carry some weight. The Alcatel architecture is fairly good, but it carries a lot of baggage from the Xylan "any to any" switching architecture which tends to drive their cost up a bit. The HP ProCurves perform well and are reliable and (relatively) cheap. -- "Where am I, and what am I doing in this handbasket?" Wes Peters [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Friday 26 March 2004 11:25 am, Per Engelbrecht wrote: > > What is the difference between Layer2 and Layer3, and what does > > that affect? > > All switching is done in layer2! Not true! > Layer3 switch 'features' (functionality) is was the vendor put in the > box. Depending on the amount of $ you're going to spent, you can have > switches that can act as routers. In the Xylan (now Alcatel) second-generation switches (The "X-Frame" backplane) the switching hardward was capable of switching on the MAC header *or* other predefined parts of the packet if no MAC header matches were found. This feature was used to implement hardware routing (the HRE-X module), allowing us to route packets between IP networks at a million packets per second. -- "Where am I, and what am I doing in this handbasket?" Wes Peters [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Fri, Mar 26, 2004 at 02:25:34PM -0800, Wes Peters wrote: ... > In the Xylan (now Alcatel) second-generation switches (The "X-Frame" > backplane) the switching hardward was capable of switching on the MAC > header *or* other predefined parts of the packet if no MAC header matches > were found. This feature was used to implement hardware routing (the HRE-X > module), allowing us to route packets between IP networks at a million > packets per second. i think you need to tell the full story, such as what was the limit on the routing table, and whether switching packets for which there wasn't a host-specific entry was slower. Finally, cost is not an inessential detail here... I pointed to an L2 switch which can switch around 2.5Mpps and costs Eur 60, retail... An L2 switch has two big advantages over an L3 switch: + only an exact match on the MAC address is necessary, as opposed to the longest prefix match which is required for a router. Surely you need more/different hw to do longest prefix match than the one needed for L2 exact match. Sure, you can install host-specific entries and then use an exact match on those, but the 'miss' case is more expensive, and if you want to do a worst-case rating, then you need to use that number; + in case of a miss, an L2 can flood all ports, a router can't (well, in principle even a router could do that, but i think the reviews wouldn't be so nice if a product did this). So an L2 thing is inherently cheaper as it can play tricks to cut costs down and still behave within the specs. cheers luigi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sendfile returning ENOTCONN under heavy load
I'm using thttpd on a server that pushes 300-400mbps of static content, using sendfile(2). Once the load reaches a certain point (around 800-1000 clients downloading, anywhere from 150-250mbps), sendfile() will start randomly returning ENOTCONN, and the client is disconnected. I've raised kern.ipc.nsfbufs pretty high and that hasn't made any difference. Is there any easy way to tell exactly why the sockets are being closed? I can't seem to find any obvious signs of memory exhaustion or anything. Thanks, Kevin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Looking for switch recommendations ...
On Fri, Mar 26, 2004 at 12:05:10PM -0400, Marc G. Fournier wrote: > > I'm looking at replacing my el'cheapo switch with something better that > will allow me to fix my issues with the em/full-duplex problem ... > > I'm looking for ssomething managed, as well as SNMP aware so that I can > tie it into Zabbix for monitoring ... something 8 or 12 port preferred. > > Cisco, of course, is always a big name ... but also expensive ... oen > recommendation is the xl 1900, but I can't find any specs on her at > cisco's site, so discontinued product? I've been happy with the Catalyst 2950T-24 (24-10/100 + 2-10/100/100). They make smaller versions in that series. > What about Netgear, which I have easy access to? Or Alcatel? > > models to stay away from? Stay away from the SMC TigerSwitch 8624T. It's got a hugh list of features an looks great on paper, but in practice, most of the features are pretty half-assed. It doesn't even boot reliably. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
Re: ifconfig causing fatal trap
At 26 Mar 2004 17:06:52 EST, Joshua Y. Stabiner wrote: > > I have a new thinkpad t40 with Intel PRO/1000 that I use as the em device and a > cisco wireless that I use as the an device. > > typing /sbin/ifconfig causes a kernel panic (using GENERIC) and forces a reboot. I > followed the directions in the manual and did: > > nm -n /kernel | grep c039cf (7e are also in the instruction pointer but > returned no results) > > This shows the fault is caused by: > cpystrflt > cpystrflt_x > copystr > bcmp > lgdt > lidt > lldt > ltr > ssdtosd > > Anyone have any idea what is causing this and how I can fix it? Thanks in advance! > Which version of FreeBSD are you using? Do you have a kernel dump? Later, George ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disabling VLAN_HWTAGGING
I did a little more debugging and placed some printf statements before and
after:
/*
* If we received a packet with a vlan tag, pass it
* to vlan_input() instead of ether_input().
*/
if (extsts & NGE_RXEXTSTS_VLANPKT) {
VLAN_INPUT_TAG(ifp, m,
extsts & NGE_RXEXTSTS_VTCI, continue);
}
What I found is that VLAN tagged frames sent to the interface never get to
this line at all. I figured the NIC must be droping it or something before
it even gets to the driver. So I commented out the following line:
/*
* Tell the chip to detect and strip VLAN tag info from
* received frames. The tag will be provided in the extsts
* field in the RX descriptors.
*/
NGE_SETBIT(sc, NGE_VLAN_IP_RXCTL,
NGE_VIPRXCTL_TAG_DETECT_ENB|NGE_VIPRXCTL_TAG_STRIP_ENB);
Now the driver gets the frame but the conditional about is false, presumable
because I comment out that line which says it will detect and set the extsts.
It does however get delivered to the ng lower hook and therefor the ng_vlan
gets it. The ng_eiface tied to vlan2 replies to the arp requests. Strangely
though when an ICMP ping request gets to ng_eiface it ignores it.
02:27:16.658526 0:90:27:f4:58:1d ff:ff:ff:ff:ff:ff 0806 56: arp who-has
10.2.0.1 tell 10.2.0.2
02:27:16.658633 11:22:33:44:55:66 0:90:27:f4:58:1d 0806 42: arp reply 10.2.0.1
is-at 11:22:33:44:55:66
02:27:16.659132 0:90:27:f4:58:1d 11:22:33:44:55:66 0800 98: 10.2.0.2 >
10.2.0.1: icmp: echo request
02:27:16.664321 0:90:27:f4:58:1d 11:22:33:44:55:66 0800 98: 10.2.0.2 >
10.2.0.1: icmp: echo request
Even more odd, I can ping from the ng_eiface interface and it makes it tagged
all the way out and back just fine. The ng_eiface gets the ICMP response just
fine.
Does any of this make sense to you? Is there possibly something wrong with
the logic in that detect and stip flag? Am I just a total tool and missing
someting completely obvious here, because it wouldn't be the first time.
Does anyone have a 1Gbit fiber NIC that they have tested in and out with VLAN
tagging that they could recommend.
--
Jacob S. Barrett
[EMAIL PROTECTED]
www.amduat.net
"I don't suffer from insanity, I enjoy every minute of it."
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disabling VLAN_HWTAGGING
On Fri, Mar 26, 2004 at 06:44:52PM -0800, Jacob S. Barrett wrote:
> I did a little more debugging and placed some printf statements before and
> after:
> /*
> * If we received a packet with a vlan tag, pass it
> * to vlan_input() instead of ether_input().
> */
> if (extsts & NGE_RXEXTSTS_VLANPKT) {
> VLAN_INPUT_TAG(ifp, m,
> extsts & NGE_RXEXTSTS_VTCI, continue);
> }
>
> What I found is that VLAN tagged frames sent to the interface never get to
> this line at all. I figured the NIC must be droping it or something before
> it even gets to the driver. So I commented out the following line:
> /*
> * Tell the chip to detect and strip VLAN tag info from
> * received frames. The tag will be provided in the extsts
> * field in the RX descriptors.
> */
> NGE_SETBIT(sc, NGE_VLAN_IP_RXCTL,
> NGE_VIPRXCTL_TAG_DETECT_ENB|NGE_VIPRXCTL_TAG_STRIP_ENB);
>
>
> Now the driver gets the frame but the conditional about is false, presumable
> because I comment out that line which says it will detect and set the extsts.
> It does however get delivered to the ng lower hook and therefor the ng_vlan
> gets it. The ng_eiface tied to vlan2 replies to the arp requests. Strangely
> though when an ICMP ping request gets to ng_eiface it ignores it.
>
> 02:27:16.658526 0:90:27:f4:58:1d ff:ff:ff:ff:ff:ff 0806 56: arp who-has
> 10.2.0.1 tell 10.2.0.2
> 02:27:16.658633 11:22:33:44:55:66 0:90:27:f4:58:1d 0806 42: arp reply 10.2.0.1
> is-at 11:22:33:44:55:66
> 02:27:16.659132 0:90:27:f4:58:1d 11:22:33:44:55:66 0800 98: 10.2.0.2 >
> 10.2.0.1: icmp: echo request
> 02:27:16.664321 0:90:27:f4:58:1d 11:22:33:44:55:66 0800 98: 10.2.0.2 >
> 10.2.0.1: icmp: echo request
>
> Even more odd, I can ping from the ng_eiface interface and it makes it tagged
> all the way out and back just fine. The ng_eiface gets the ICMP response just
> fine.
>
> Does any of this make sense to you? Is there possibly something wrong with
> the logic in that detect and stip flag? Am I just a total tool and missing
> someting completely obvious here, because it wouldn't be the first time.
>
I think so. 11:22:33:44:55:66 is the wrong MAC address -- the first octet
should be an odd number, otherwise it's treated as a broadcast/multicast.
> Does anyone have a 1Gbit fiber NIC that they have tested in and out with VLAN
> tagging that they could recommend.
>
I'm in the process of obtaining a NIC. Once I get it, I will look into the
issue. What's the ``pciconf -lv'' and dmesg(8) outputs corresponding to your
NIC? Also, is it plugged into the 64-bit PCI slot or not?
Cheers,
--
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer
pgp0.pgp
Description: PGP signature
