Re: troubleshooting CVSUP failures
Hi, On Fri, 2003-02-14 at 22:56, Shane Hickey wrote: > Howdy, thanks for the response. No worries.., > > On Fri, 2003-02-14 at 15:39, Stacey Roberts wrote: > > What version of FreeBSD is this? > > 5.0-release. > > > Can you post the dmesg output for both (or more) of the nics on the > > system, please? > > What is the P'nP OS BIOS option set to on this box? > > Here's the dmesg: > ed1: at port 0x100-0x11f irq 11 function 0 IRQ 11 here.., > config 16 on pccard0 > ed1: address 00:e0:98:88:91:84, type Linksys (16 bit) > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > Product version: 5.0 > Product name: IBM | 10/100 EtherJet CardBus | IBMC-10/100 | 1.04 | > Manufacturer ID: a400130181 > Functions: Network Adaptor, Multi-Functioned > Function Extension: 04060006295290d8 > Function Extension: 0102 > Function Extension: 0280969800 > Function Extension: 0200e1f505 > Function Extension: 0301 > Function Extension: 0303 > Function Extension: 0501 > cardbus1: Invalid BAR number: 27(06) > CIS reading done > dc0: port 0x1000-0x107f mem > 0x88002400-0x880024ff,0x88002500-0x8800257f irq 11 at device 0.0 on IRQ 11 here as well :-( > cardbus1 Both ed1 & dc0 are sharing IRQ11, not always a good thing.., > dc0: Ethernet address: 06:00:06:29:52:90 > miibus1: on dc0 > tdkphy0: on miibus1 > tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > I don't see any mention of PNP in the BIOS and I didn't specifically > enable anything in the KERNEL. Let me know if you need more. Most MoBo's have an option in the SetUp menu (you know.., "press DEL for SETUP", during POST), where you tell the BIOS whether or not a P'nP OS is being installed - for FreeBSD, one usually selects "No" / "DISABLE" to this. > > Now, here's the weird thing. I reconfigured my ipnat.rules, ipf.rules > and rc.conf to switch the NICs. I rebooted and switched the cables and > now I haven't gotten an error on the new dc0 interface (which is now the > promiscuous snort interface). So, it might be that the ed1 interface is > conflicting with something and I only hear about it when I put it into > promiscuous mode. I'm going to try to do that next. Well., when putting an interface into promiscuous mode, you're then enabling the bpf (Berkley Packet Filter) device.., which might point to ed1 (on IRQ11) now having to contend with yet another device for IRQ resources.., Just a guess here. > > Thanks, > It'd be great to hear what results you get.., Hope to hear from you on this again soon. Regards, Stacey > shane > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: troubleshooting CVSUP failures
Howdy, thanks for the response. On Fri, 2003-02-14 at 15:39, Stacey Roberts wrote: > What version of FreeBSD is this? 5.0-release. > Can you post the dmesg output for both (or more) of the nics on the > system, please? > What is the P'nP OS BIOS option set to on this box? Here's the dmesg: ed1: at port 0x100-0x11f irq 11 function 0 config 16 on pccard0 ed1: address 00:e0:98:88:91:84, type Linksys (16 bit) ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Product version: 5.0 Product name: IBM | 10/100 EtherJet CardBus | IBMC-10/100 | 1.04 | Manufacturer ID: a400130181 Functions: Network Adaptor, Multi-Functioned Function Extension: 04060006295290d8 Function Extension: 0102 Function Extension: 0280969800 Function Extension: 0200e1f505 Function Extension: 0301 Function Extension: 0303 Function Extension: 0501 cardbus1: Invalid BAR number: 27(06) CIS reading done dc0: port 0x1000-0x107f mem 0x88002400-0x880024ff,0x88002500-0x8800257f irq 11 at device 0.0 on cardbus1 dc0: Ethernet address: 06:00:06:29:52:90 miibus1: on dc0 tdkphy0: on miibus1 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto I don't see any mention of PNP in the BIOS and I didn't specifically enable anything in the KERNEL. Let me know if you need more. Now, here's the weird thing. I reconfigured my ipnat.rules, ipf.rules and rc.conf to switch the NICs. I rebooted and switched the cables and now I haven't gotten an error on the new dc0 interface (which is now the promiscuous snort interface). So, it might be that the ed1 interface is conflicting with something and I only hear about it when I put it into promiscuous mode. I'm going to try to do that next. Thanks, shane To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: troubleshooting CVSUP failures
Hi, On Fri, 2003-02-14 at 22:12, Shane Hickey wrote: > On Fri, 2003-02-14 at 11:46, Shane Hickey wrote: > > Howdy all, > > My ISP just put in a packetshaper and I am now having problems getting > > CVSUP to work. I suppose it could be unrelated, but I wanted to see if > > anyone could suggest good troubleshooting steps. I've tried several > > cvsup servers (cvsup, cvsup2, cvsup7, cvsup8) and they all either fail > > immediately, or shortly thereafter with one of the following errors. > > > > TreeList failed: Network write failure: ChannelMux.ProtocolError > > > > Detailer failed: Network read failure: Input/output error: zlib data > > error > > I hadn't gotten any responses, but I just noticed something. I put my > firewall's outside interface into promiscuous mode for Snort and shortly > thereafter I started getting the following errors. > > Feb 14 15:00:37 elijah kernel: ed1: NIC memory corrupt - invalid packet > length 4 > Feb 14 15:00:48 elijah kernel: ed1: NIC memory corrupt - invalid packet > length 3 > Feb 14 15:00:52 elijah kernel: ed1: NIC memory corrupt - invalid packet > length 4 > Feb 14 15:00:53 elijah kernel: ed1: NIC memory corrupt - invalid packet > length 3 What version of FreeBSD is this? Can you post the dmesg output for both (or more) of the nics on the system, please? What is the P'nP OS BIOS option set to on this box? The reasoning behind my request for more information rests on the following:- 1] There is a possibility of an IRQ conflict with another adapter on the box 2] Duff ethernet cabling > > Now, my question all along has been whether my ISP munged something up > and packets are being corrupted. Might the errors that I'm seeing be > evidence of that or is it only pointing to the fact that my firewalls > ed1 interface might be screwy? > Not sure myself, come back to the list with that information, and hopefully others more informed than I would have memories jogged :-) Regards, Stacey > Thanks, > > Shane > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: troubleshooting CVSUP failures
On Fri, 2003-02-14 at 11:46, Shane Hickey wrote: > Howdy all, > My ISP just put in a packetshaper and I am now having problems getting > CVSUP to work. I suppose it could be unrelated, but I wanted to see if > anyone could suggest good troubleshooting steps. I've tried several > cvsup servers (cvsup, cvsup2, cvsup7, cvsup8) and they all either fail > immediately, or shortly thereafter with one of the following errors. > > TreeList failed: Network write failure: ChannelMux.ProtocolError > > Detailer failed: Network read failure: Input/output error: zlib data > error I hadn't gotten any responses, but I just noticed something. I put my firewall's outside interface into promiscuous mode for Snort and shortly thereafter I started getting the following errors. Feb 14 15:00:37 elijah kernel: ed1: NIC memory corrupt - invalid packet length 4 Feb 14 15:00:48 elijah kernel: ed1: NIC memory corrupt - invalid packet length 3 Feb 14 15:00:52 elijah kernel: ed1: NIC memory corrupt - invalid packet length 4 Feb 14 15:00:53 elijah kernel: ed1: NIC memory corrupt - invalid packet length 3 Now, my question all along has been whether my ISP munged something up and packets are being corrupted. Might the errors that I'm seeing be evidence of that or is it only pointing to the fact that my firewalls ed1 interface might be screwy? Thanks, Shane To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
