FreeBSD 4.2 complicated diseases
	FreeBSD 4.2 complicated diseases Phenomenon : Without any network connection, the system will not respond. Failure of ping test, But 10 seconds in front of the other, such as SSH connection for a shorter time. This is a good few seconds of delay annoying to see the above website points out several times before. Who can give attending a consultation! Below is the relevant port application forms, and document translation Kernel Net port ------------------------------------------------------------- Tcp4 0 0 *.993 indicators shown as *.* LISTEN Tcp4 0 0 *.3128 indicators shown as *.* LISTEN Tcp4 0 0 *.995 indicators shown as *.* LISTEN Tcp4 0 0 *.25 indicators shown as *.* LISTEN Tcp4 0 0 *.22 indicators shown as *.* LISTEN Tcp4 0 0 *.21 indicators shown as *.* LISTEN Tcp4 0 0 *.80 indicators shown as *.* LISTEN Tcp4 0 0 *.443 indicators shown as *.* LISTEN Tcp4 0 0 *.3306 indicators shown as *.* LISTEN Tcp4 0 0 172.16.2.223.53 indicators shown as *.* LISTEN ------------------------------------------------------------- Kernel list ------------------------------------------------------------- Machine from beginning for the i386 Cpu I686_CPU Ident GENERIC Maxusers 128 Options INET #InterNETworking Options IPFILTER Options IPFILTER_LOG Fast Filesystem options FFS #Berkeley Options FFS_ROOT #FFS usable as root device [keep this!] FFS soft updates support options SOFTUPDATES #Enable Filesystem options MFS #Memory #MD Is a potential root device options MD_ROOT #ISO 9660 Filesystem options CD9660 Options CD9660_ROOT #CD-ROM usable as root, CD9660 required #Process Filesystem options PROCFS Options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #Allow Users to grab the console options UCONSOLE Options USERCONFIG #boot-c editor #visual Boot - c editor options VISUAL_USERCONFIG KTRACE #ktrace options (1) support #SYSV-style Shared memory options SYSVSHM Options SYSVMSG #SYSV-style message queues Options SYSVSEM #SYSV-style semaphores P1003_1B real-time extensions options P1003_1B #Posix Options _KPOSIX_PRIORITY_SCHEDULING #Rate Limit bad replies options ICMP_BANDLIM Options KBD_INSTALL_CDEV # install a CDEV entry in /dev Options SC_DISABLE_REBOOT Options SC_HISTORY_SIZE=999 Options MAXCONS=2 Device isa Pci device Device fdc0 at isa? port IO_FD1 irq 6 drq 2 Device fd0 at fdc0 drive 0 IO_WD1 irq 14 port device ata0 at isa? IO_WD2 irq 15 port device ata1 at isa? Device-Quds Device atadisk # ATA disk drives Atapicd # ATAPI device CDROM drives ATA_STATIC_ID #Static device numbering options DMA on ATAPI devices #Enable options ATA_ENABLE_ATAPI_DMA Isa? port device atkbdc0 at IO_KBD Irq 1 flags 0x1 device atkbd0 at atkbdc? Device vga0 at isa? Pseudo-device splash Sc0 at isa? flags 0x100 device IO_NPX irq 13 port device npx0 at nexus? Device sio0 at isa? port IO_COM1 flags 0x10 irq 4 Device sio1 at isa? port IO_COM2 irq 3 Intel EtherExpress PRO/100B device fxp0 # (82557, 82558) Intel EtherExpress PRO/100B fxp1 # device (82557, 82558) Miibus # MII bus support device Pseudo-device loop # Network loopback Pseudo-device ether # Ethernet support Pseudo-device pty # Pseudo-ttys (Telnet etc.) -------------------------------------------------------------
	I do not know if it was your NIC configuration, routing configuration, or what the problem is?
	I saw you two fxp allocated in the system, which is not a configuration problem? "Intel EtherExpress PRO/100B device fxp0 # (82557, 82558) "Intel EtherExpress PRO/100B device fxp1 # (82557, 82558) General are as follows : Device fxp You see Behold, I do not know if this is not the issue.
	Re : FreeBSD 4.2 complicated diseases
	Using dmesg, and ifconfig-a netstat -nr Tieshanglai your information.
	Re : no network adapter configuration, dual-NIC is?
	In a single NIC, it is the problem I have used a network adapter for the two, tried to solve the problem. Onboard NIC. Power Management to ban a long time ago Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" 935458134 Hz frequency CPU : Pentium III Xeon/Celeron III/Pentium (935.46-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff<FPU, VME, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR, PGE, MCA, CMOV, PAT, PSE36, MMX, FXSR, SSE> Real memory = 535691264 (523136K bytes) Avail memory = 518799360 (506640K bytes) Preloaded elf Kernel "Kernel" at 0xc0285000. MTRR support enabled Pentium Pro Npx0 : "math processor> on motherboard Npx0 : INT 16 interface Pcib0 : "Host to PCI bridge> on motherboard Pci0 : "PCI bus> on pcib0 Pci0 : "Intel model 1132 VGA-compatible display device> at 2.0 irq 11 Pcib1 : "PCI to PCI bridge (vendor=8086 device=244e)" at 30.0 on pci0 device Pci1 : "PCI bus> on pcib1 Fxp0 : "Intel Pro 10/100B/100+ Ethernet> 0xd800-0xd83f mem 0xff700000-0xff7fffff port. 0xff8fe000-0xff8fefff irq 11 at 4.0 on pci1 device Fxp0 : Ethernet address 00:30:48:41:0a:76 Fxp1 : "Intel PLC Ethernet> port 10/100 0xdf00-0xdf3f mem device 0xff8ff000-0xff8fffff irq 11 at 8.0 on pci1 Fxp1 : Ethernet address 00:30:48:41:0a:77 Isab0 : "PCI to ISA bridge (vendor=8086 device=2440)" at 31.0 on pci0 device Isa0 : "ISA bus> on isab0 Atapci0 : "Intel ICH2 ATA100 controller> port device 0xffa0-0xffaf at 31.1 on pci0 Ata0 : at 0x1f0 irq 14 on atapci0 Ata1 : at 0x170 irq 15 on atapci0 Pci0 : "USB UHCI controller> at 31.2 irq 3 Pci0 : "unknown card> (vendor=0x8086, dev=0x2443) at 31.3 irq 5 Pci0 : "USB UHCI controller> at 31.4 irq 10 Fdc0 : "NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 Fdc0 : FIFO enabled, 8 bytes threshold Fd0 : "1440-KB 3.5" drive> on fdc0 drive 0 Atkbdc0 : "Keyboard controller (i8042)" at the port 0x60,0x64 on isa0 Atkbd0 : "AT Keyboard> flags 0x1 irq 1 on atkbdc0 Kbd0 at atkbd0 Vga0 : "Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Sc0 : "System console> at flags 0x100 on isa0 Sc0 : VGA "two virtual consoles, flags=0x300> Sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Sio0 type 16550A : Sio1 : configured irq 3 not in bitmap of probed irqs 0 IP Filter : v3.4.23 initialized. Default = pass all, Logging = enabled : : Timeout waiting for WIPO ata_command ata0-slave Ata0-slave identify failed : Ad2 : 8223MB "ST38422A> [16708/16/63] at ata1-master UDMA66 Acd0 : CDROM "FX4830T> at ata0-master using UDMA33 Mounting root from ufs:/dev/ad2s1a Cd9660 : RockRidge Extension Fxp0 : flags=8802<BROADCAST, SIMPLE, MULTICAST> mtu 1500 Ether 00:30:48:41:0a:76 Autoselect status : no carrier media : Supported media : autoselect 100baseTX "full-duplex> 100baseTX 10baseT/UTP" full-duplex> 10baseT/UTP Fxp1 : flags=8843<UP, BROADCAST, RUNNING, SIMPLE, MULTICAST> mtu 1500 Inet 172.16.2.223 netmask 0xffff0000 broadcast 172.16.255.255 Ether 00:30:48:41:0a:77 Media : autoselect (100baseTX "full-duplex>) status : active Supported media : autoselect 100baseTX "full-duplex> 100baseTX 10baseT/UTP" full-duplex> 10baseT/UTP Lo0 : flags=8049<UP, LOOPBACK, RUNNING, MULTICAST> mtu 16384 Inet 127.0.0.1 netmask 0xff000000 Internet : Destination Gateway Flags Refs Use Netif Expire Default 0 85 fxp1 172.16.1.254 UGSc 127.0.0.1 127.0.0.1 UH 0 0 lo0 172.16 link#2 UC 0 0 fxp1> 172.16.1.4 0:d0:b7:b7:e1:5 fxp1 UHLW 0 66 1143 172.16.1.5 0:30:48:41:4:e6 fxp1 UHLW 1 81 1024 172.16.1.254 link#2 UHLW 1 3 fxp1> 172.16.2.222 0:10:88:2:c2:38 fxp1 UHLW 3 55220 1092
	Try ifconfig fxp0 down
	I know you have no problem with the routing table ah, you try to swap fxp0 down to the bar, I encountered such a problem before, it seems to be another piece down off enough.
	Re : no network adapter configuration, dual-NIC is?
	From the information point of view, no problem. Can two computer directly to the company, to see how the situation PING? If they do, look at the proposal installed 4.5, 4.1, 4.2 pre-installed version of the handbook in the search when they switched networks, it seems like a lock.
	Re : FreeBSD 4.2 complicated diseases
	The problem is in the DNS, you try to use or modify DNS resolv.conf documents.
	This seems to have nothing to do with DNS
	I feel that this seems to have nothing to do with DNS, because in the same network segment, if any, also may amend /etc/hosts documents, set up to solve the static analysis.
	Re : FreeBSD 4.2 complicated diseases
	"The problem is in the DNS, you try to use or modify DNS resolv.conf documents. Oh, one Much die 90% of the problem may really be out in the dns, ndc stop after you look at the link speed is a lot faster, or slow, which they take into resolv.conf the nameserver 127.0.0.1 (that is before you close the bind). If time is no problem in a summary of the net frame. Solution : First, pointed to an effective dns on resolv.conf Second, a non-forword the dns done, and will refer to this plane resolv.conf Third, this machine dns relations, and pointed to the plane resolv.com