Re: Ethernet issue: works one way but not another
On Thu, 17 Mar 2005 22:43:15 -0500, John A. [EMAIL PROTECTED] wrote: No problem with the english, if you didn't mention it, I wouldn't have known. I can ping FBSD from M$, can't ping anything from FBSD. M$ box works when plugged into hub and directly into radio. All systems are on same subnet. If the other machines you are trying to ping have M$ firewall enabled, then you need to enable incoming echo request in the M$ firewall ICMP page. FBSD box worked when plugged into a 100mb hub, but doesn't work when plugged into 10mb hub or directly into radio. Both hubs are 3Com and are working with other systems plugged into them. Try to check the output of ifconfig on the FreeBSD box when you connect it to the 100m hub / 10m hub / radio. Also try route get M$ BOX IP on the FreeBSD box and check the output. Does it provide the correct interface/gateway? FBSD has no firwall configured. All I did was perform a standard installation loading all binaries and sources from ftp. I just tested another FBSD 5.3 box that I have and it does the same thing, works fine at 100mb, but appears to get lost at 10mb. Hope this answers some of your questions. John A. Am I the only one interested in this topic? Where is the rest of our lovely community? Come on guys let's scratch those gray cells and help John out. -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ethernet issue: works one way but not another
Abu Khaled wrote: ... Am I the only one interested in this topic? Where is the rest of our lovely community? Come on guys let's scratch those gray cells and help John out. Although progress is being made on getting detail, it's still insufficient (and, not entirely consistent? if the connection in question is *wired* then probably the fact that a wireless access point exists on the same subnet is not likely relevant). Anyway, I do not have a clear vision of what connects to what, how. The relevant portions of rc.conf, ifconfig output (and ipconfig output from the M$ box), the syntax of the tcpdump, the specs of the box, and other relevant details might spur more response. A simple ASCII representation of the network might help. FWIW, I've seen tcpdump behave poorly if the box or card just doesn't have the horsepower required to parse the volume of all the packets being seen on the network. re: can't ping M$ box... M$ firewall sounds like the most likely culprit. If you try to ping and get no response, does the M$ box nevertheless show up in FreeBSD's arp table (compare arp -an before and after the ping test)? If the MAC address shows up, you've got connectivity just fine, but something's dropping the ICMP packets. PS to Abu -- your written English is as good or better than many native speakers of the language, so don't apologize for it. =) -- Greg Barniskis, Computer Systems Integrator South Central Library System (SCLS) Library Interchange Network (LINK) gregb at scls.lib.wi.us, (608) 266-6348 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ethernet issue: works one way but not another
OK, lets see if this helps... dmesg: Copyright (c) 1992-2004 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 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 134152192 (127 MB) avail memory = 121622528 (115 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: XX AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU (3 Cx states) on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0x5000-0x500f,0x4000-0x4041,0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xd000-0xd3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 11 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 7.3 (no driver attached) ahc0: Adaptec 2940 Ultra SCSI adapter port 0xe400-0xe4ff mem 0xd700-0xd7000fff irq 10 at device 9.0 on pci0 ahc0: [GIANT-LOCKED] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xe800-0xe87f mem 0xd7001000-0xd700107f irq 5 at device 13.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:10:4b:7a:e4:ec fdc0: floppy drive controller port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 orm0: ISA Option ROMs at iomem 0xcc000-0xd07ff,0xc-0xcbfff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 451024000 Hz quality 800 Timecounters tick every 10.000 msec Waiting 15 seconds for SCSI devices to settle acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0% da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST34501W 0017 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4339MB (8887200 512 byte sectors: 255H 63S/T 553C) rc.conf: (names have been changed to protect the innocent/guilty) gateway_enable=NO hostname=myhost.domain.com nisdomainname=domain.com ifconfig_xl0=inet 192.168.79.254/24 defaultrouter=192.168.79.1 linux_enable=YES moused_enable=YES sshd_enable=YES usbd_enable=YES ifconfig: (This is when connected to internal network through 3Com 100mb hub) xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=9RXCSUM,VLAN_MTU inet6 fe80::210:4bff:fe7a:e4ec%xl0 prefixlen 64 scopeid 0x1 inet 192.168.79.254 netmask 0xff00 broadcast 192.168.79.255 ether 00:10:4b:7a:e4:ec media: Ethernet autoselect (100baseTX) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 netstat -rn: Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 127.0.0.1 127.0.0.1 UH 00lo0 192.168.79 link#1 UC 00xl0 192.168.79.1 00:30:48:41:dc:58 UHLW04xl0 1084 Internet6: Destination Gateway Flags Netif Expire ::1
Re: Ethernet issue: works one way but not another
The system uses a standard installation. I have only configured the ethernet card with the proper ip address for the wireless side of the network. The windoze box is running M$ firewall, but it works fine and allows me to ping my gateway and the FBSD box. What concerns me at this point is the fact that tcpdump takes so long to respond. If I let it run, it will display a packet about one every 2 min. They seem to be in time order with timestamps only ms apart. Let me know if any other information will help. John A. On Thu, 17 Mar 2005 04:16:51 +0200, abu khaled [EMAIL PROTECTED] wrote: Well I am sure some one well help you if you provide more information about your network configuration/firewall rules,etc... Do you have a firewall configured on the freebsd box/M$windoze? -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ethernet issue: works one way but not another
On Thu, 17 Mar 2005 11:21:44 -0500, John A. [EMAIL PROTECTED] wrote: The system uses a standard installation. I have only configured the ethernet card with the proper ip address for the wireless side of the network. The windoze box is running M$ firewall, but it works fine and allows me to ping my gateway and the FBSD box. What concerns me at this point is the fact that tcpdump takes so long to respond. If I let it run, it will display a packet about one every 2 min. They seem to be in time order with timestamps only ms apart. Let me know if any other information will help. John A. First, you have to excuse my English it is my third language and I do not have that much experience. This seems like a puzzle to me and I cannot figure out the topology of your network. * Can you ping the M$ box from FreeBSD? You need to enable incoming echo request in M$ firewall. * Are both systems on the same subnet? * Have you tried to plug the radio directly into FreeBSD box and test the connection like you did for M$ box? * Does your FreeBSD box have a firewall configured? You mentioned that the connection works if you plug the radio directly to M$ box. Does it also work when you plug both to the hub? If not then it might be a crossover cable problem. As you can see, many pices in this puzzle need sorting out. -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ethernet issue: works one way but not another
No problem with the english, if you didn't mention it, I wouldn't have known. I can ping FBSD from M$, can't ping anything from FBSD. M$ box works when plugged into hub and directly into radio. All systems are on same subnet. FBSD box worked when plugged into a 100mb hub, but doesn't work when plugged into 10mb hub or directly into radio. Both hubs are 3Com and are working with other systems plugged into them. FBSD has no firwall configured. All I did was perform a standard installation loading all binaries and sources from ftp. I just tested another FBSD 5.3 box that I have and it does the same thing, works fine at 100mb, but appears to get lost at 10mb. Hope this answers some of your questions. John A. On Fri, 18 Mar 2005 01:18:46 +0200, abu khaled [EMAIL PROTECTED] wrote: First, you have to excuse my English it is my third language and I do not have that much experience. This seems like a puzzle to me and I cannot figure out the topology of your network. * Can you ping the M$ box from FreeBSD? You need to enable incoming echo request in M$ firewall. * Are both systems on the same subnet? * Have you tried to plug the radio directly into FreeBSD box and test the connection like you did for M$ box? * Does your FreeBSD box have a firewall configured? You mentioned that the connection works if you plug the radio directly to M$ box. Does it also work when you plug both to the hub? If not then it might be a crossover cable problem. As you can see, many pices in this puzzle need sorting out. -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ethernet issue: works one way but not another
On Wed, 16 Mar 2005 21:06:32 -0500, John Allesee [EMAIL PROTECTED] wrote: This one has got me stumped. Been working on it for 3 days now with no resolution. Please help. I have a 686 system that I just installed 5.3 on through ftp. So I know that my network setup works. I have 2 networks that I am trying to access through. One network is connected to a 100mb 3com hub using private ips into a firewall. This one works with no problems. The problem comes when I connect the system to the other network. This network is connected through a Breezecom wireless radio at 10mb. I can see that the network is up, ip address is assigned, routes are set correctly. Pings time out. No traffic appears to cross from radio. Plug windoze box to radio, works fine. Plug radio into 10mb hub and plug FBSD server and windoze box to hub, same results on both. I can ping FBSD from windoze. FBSD still sees nothing. If I run tcpdump, wait 10 sec, hit ctl-C, nothing happens for 2.5 min. 1 packet is displayed and exit reports 1 packet captured, 6775 packets received by filter, 6094 packets dropped by kernel. I have tried 3 different network cards, each has the same results. Card 1: 3Com 3C905B, card 2: SMC 9432TX, card 3: Generic 10mb card by Realtec I know that the obvious answer is to connect the server through my firewalled connection, but I have a need to access another part of my company network from my desk and the wireless net is the easiest way to do this. Any and all help is greatly appreciated. TIA, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Well I am sure some one well help you if you provide more information about your network configuration/firewall rules,etc... Do you have a firewall configured on the freebsd box/M$windoze? -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
