Re: ezjails, systat -ifstat, and multiple network cards
On Thu, Feb 13, 2014 at 2:22 PM, Allan Jude free...@allanjude.com wrote: On 2014-02-13 13:59, Preston Hagar wrote: I have a server setup with FreeBSD-10.0-RELEASE. It has 3 Intel gigabit network cards in it, em0, em1, and em2. I have multiple ezjails setup that run various things. One jail, called db, runs a postgresql database. It was my intention to give it em0 all to itself. The other jails and host machine should be going through em2. em1 currently isn't being used. If I do an ifconfig, I see that em0 has the alias IP for my db jail and em2 has the alias IP for all other jails. All the jails respond to network traffic as expected and seemingly work fine. The weird thing is when I do a systat -ifstat from the host, it should essentially all traffic going through em0. Some of the jails that run off of em2 (as defined in their jail config files and seen in ifconfig) have large data transfers and/or are web servers with lots of photos. I have even tried to manually scp a large file out of a jail setup through em2 and the numbers don't seem to budge. If I do netstat -i -b -n -I and check em0 and em2, it seems to support the numbers shown by systat -ifstat. However, if I use trafshow or iftop (both of which require choosing one interface at a time), they both seem to indicate the traffic flowing through the interfaces as I would expect. So I was curious if anyone had seen something like this before or had any ideas of what is going on. I have net.fibs=2 set in /boot/loader.conf, but in all the jails I current have jail_name_fib= as I haven't got around to fullying setting up fibs. Is that perhaps the issue? Is there any way to determine with certainty which jail is using which interface short of physically pulling a network cable and seeing what stops working? Here are the relevant lines from my db (the one that should be on em0) config: export jail_db_hostname=db export jail_db_ip=em0|10.1.10.2 From another jail on em2 called www: export jail_www_hostname=www export jail_www_ip=em2|10.1.10.7 from ifconfig em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether 08:60:6e:13:94:06 inet 10.1.1.4 netmask 0x broadcast 10.1.255.255 inet6 fe80::a60:6eff:fe13:9406%em0 prefixlen 64 scopeid 0x1 inet 10.1.10.2 netmask 0x broadcast 10.1.10.2 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active em2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether 68:05:ca:13:74:2a inet 10.1.1.2 netmask 0x broadcast 10.1.255.255 inet6 fe80::6a05:caff:fe13:742a%em2 prefixlen 64 scopeid 0x3 inet 10.1.10.3 netmask 0x broadcast 10.1.10.3 inet 10.1.10.1 netmask 0x broadcast 10.1.10.1 inet 10.1.10.8 netmask 0x broadcast 10.1.10.8 inet 10.1.10.10 netmask 0x broadcast 10.1.10.10 inet 10.1.10.4 netmask 0x broadcast 10.1.10.4 inet 10.1.10.9 netmask 0x broadcast 10.1.10.9 inet 10.1.10.7 netmask 0x broadcast 10.1.10.7 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active Let me know if any more detail would be helpful or if you have any ideas of things to check. Thanks, Preston ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org All traffic going out from the jails will using the routing table from the host system. The routing table will use the network card that is in the same subnet as your default gateway to route the traffic to the internet. In your case, I would imagine this is 10.1.1.4/16 (and 10.1.1.2/16). 'netstat -rn' will tell the tale, but I imagine it is whichever was added first. If you want to have separate routing tables per jail, you'd have to either use FIBs, and set the jails to use the different FIBs, or use VNET jails and have a routing table in each jail. -- Allan Jude Makes sense, thank you. I'll setup the FIBs. Preston ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
ezjails, systat -ifstat, and multiple network cards
I have a server setup with FreeBSD-10.0-RELEASE. It has 3 Intel gigabit network cards in it, em0, em1, and em2. I have multiple ezjails setup that run various things. One jail, called db, runs a postgresql database. It was my intention to give it em0 all to itself. The other jails and host machine should be going through em2. em1 currently isn't being used. If I do an ifconfig, I see that em0 has the alias IP for my db jail and em2 has the alias IP for all other jails. All the jails respond to network traffic as expected and seemingly work fine. The weird thing is when I do a systat -ifstat from the host, it should essentially all traffic going through em0. Some of the jails that run off of em2 (as defined in their jail config files and seen in ifconfig) have large data transfers and/or are web servers with lots of photos. I have even tried to manually scp a large file out of a jail setup through em2 and the numbers don't seem to budge. If I do netstat -i -b -n -I and check em0 and em2, it seems to support the numbers shown by systat -ifstat. However, if I use trafshow or iftop (both of which require choosing one interface at a time), they both seem to indicate the traffic flowing through the interfaces as I would expect. So I was curious if anyone had seen something like this before or had any ideas of what is going on. I have net.fibs=2 set in /boot/loader.conf, but in all the jails I current have jail_name_fib= as I haven't got around to fullying setting up fibs. Is that perhaps the issue? Is there any way to determine with certainty which jail is using which interface short of physically pulling a network cable and seeing what stops working? Here are the relevant lines from my db (the one that should be on em0) config: export jail_db_hostname=db export jail_db_ip=em0|10.1.10.2 From another jail on em2 called www: export jail_www_hostname=www export jail_www_ip=em2|10.1.10.7 from ifconfig em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether 08:60:6e:13:94:06 inet 10.1.1.4 netmask 0x broadcast 10.1.255.255 inet6 fe80::a60:6eff:fe13:9406%em0 prefixlen 64 scopeid 0x1 inet 10.1.10.2 netmask 0x broadcast 10.1.10.2 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active em2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether 68:05:ca:13:74:2a inet 10.1.1.2 netmask 0x broadcast 10.1.255.255 inet6 fe80::6a05:caff:fe13:742a%em2 prefixlen 64 scopeid 0x3 inet 10.1.10.3 netmask 0x broadcast 10.1.10.3 inet 10.1.10.1 netmask 0x broadcast 10.1.10.1 inet 10.1.10.8 netmask 0x broadcast 10.1.10.8 inet 10.1.10.10 netmask 0x broadcast 10.1.10.10 inet 10.1.10.4 netmask 0x broadcast 10.1.10.4 inet 10.1.10.9 netmask 0x broadcast 10.1.10.9 inet 10.1.10.7 netmask 0x broadcast 10.1.10.7 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active Let me know if any more detail would be helpful or if you have any ideas of things to check. Thanks, Preston ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ezjails, systat -ifstat, and multiple network cards
On 2014-02-13 13:59, Preston Hagar wrote: I have a server setup with FreeBSD-10.0-RELEASE. It has 3 Intel gigabit network cards in it, em0, em1, and em2. I have multiple ezjails setup that run various things. One jail, called db, runs a postgresql database. It was my intention to give it em0 all to itself. The other jails and host machine should be going through em2. em1 currently isn't being used. If I do an ifconfig, I see that em0 has the alias IP for my db jail and em2 has the alias IP for all other jails. All the jails respond to network traffic as expected and seemingly work fine. The weird thing is when I do a systat -ifstat from the host, it should essentially all traffic going through em0. Some of the jails that run off of em2 (as defined in their jail config files and seen in ifconfig) have large data transfers and/or are web servers with lots of photos. I have even tried to manually scp a large file out of a jail setup through em2 and the numbers don't seem to budge. If I do netstat -i -b -n -I and check em0 and em2, it seems to support the numbers shown by systat -ifstat. However, if I use trafshow or iftop (both of which require choosing one interface at a time), they both seem to indicate the traffic flowing through the interfaces as I would expect. So I was curious if anyone had seen something like this before or had any ideas of what is going on. I have net.fibs=2 set in /boot/loader.conf, but in all the jails I current have jail_name_fib= as I haven't got around to fullying setting up fibs. Is that perhaps the issue? Is there any way to determine with certainty which jail is using which interface short of physically pulling a network cable and seeing what stops working? Here are the relevant lines from my db (the one that should be on em0) config: export jail_db_hostname=db export jail_db_ip=em0|10.1.10.2 From another jail on em2 called www: export jail_www_hostname=www export jail_www_ip=em2|10.1.10.7 from ifconfig em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether 08:60:6e:13:94:06 inet 10.1.1.4 netmask 0x broadcast 10.1.255.255 inet6 fe80::a60:6eff:fe13:9406%em0 prefixlen 64 scopeid 0x1 inet 10.1.10.2 netmask 0x broadcast 10.1.10.2 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active em2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=4219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO ether 68:05:ca:13:74:2a inet 10.1.1.2 netmask 0x broadcast 10.1.255.255 inet6 fe80::6a05:caff:fe13:742a%em2 prefixlen 64 scopeid 0x3 inet 10.1.10.3 netmask 0x broadcast 10.1.10.3 inet 10.1.10.1 netmask 0x broadcast 10.1.10.1 inet 10.1.10.8 netmask 0x broadcast 10.1.10.8 inet 10.1.10.10 netmask 0x broadcast 10.1.10.10 inet 10.1.10.4 netmask 0x broadcast 10.1.10.4 inet 10.1.10.9 netmask 0x broadcast 10.1.10.9 inet 10.1.10.7 netmask 0x broadcast 10.1.10.7 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active Let me know if any more detail would be helpful or if you have any ideas of things to check. Thanks, Preston ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org All traffic going out from the jails will using the routing table from the host system. The routing table will use the network card that is in the same subnet as your default gateway to route the traffic to the internet. In your case, I would imagine this is 10.1.1.4/16 (and 10.1.1.2/16). 'netstat -rn' will tell the tale, but I imagine it is whichever was added first. If you want to have separate routing tables per jail, you'd have to either use FIBs, and set the jails to use the different FIBs, or use VNET jails and have a routing table in each jail. -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: -current problem: Network cards doesn't run
On Sun, 17 Oct 1999, Andreas Klemm wrote: See ed0 When running a current kernel of some days ago, no problems. Were there perhaps changes in the last days that introduce this, that some NICs doesn't run ? Even the xl0 interface didn't run (DMZ). Ping to hosts in internet didn't succeed. I believe I've tracked this down. I'll commit a fix once I've verified it. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Oct 17 00:40:49 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 159383552 (155648K bytes) avail memory = 151044096 (147504K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc030c000. Pentium Pro MTRR support enabled ccd0-3: Concatenated disk drivers npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 chip1: Intel PIIX3 IDE controller at device 7.1 on pci0 vga-pci0: Matrox MGA 2064W graphics accelerator at device 10.0 on pci0 xl0: 3Com 3c900-COMBO Etherlink XL irq 19 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: selecting 10baseT transceiver, half duplex pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 18 pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 ahc0: Adaptec 2940 Ultra SCSI adapter irq 17 at device 13.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: Adaptec 2940 Ultra SCSI adapter irq 16 at device 14.0 on pci0 ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs fdc0: NEC 72065B or clone at port 0x3f0-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 port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 4 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default DUMMYNET initialized (990811) Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 sa0 at ahc1 bus 0 target 4 lun 0 sa0: TANDBERG TDC 4222 =07: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) Creating DISK cd0 Creating DISK cd1 changing root device to da0s2a cd1 at ahc1 bus 0 target 5 lun 0 cd1: TOSHIBA CD-ROM XM-5701TA 3136 Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: Attempt to query device size failed: NOT READY, Medium not present cd0 at ahc0 bus 0 target 6 lun 0 cd0: TEAC CD-R55S 1.0K Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da3 at ahc0 bus 0 target 3 lun 0 da3: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: IBM DORS-32160
-current problem: Network cards doesn't run
See ed0 When running a current kernel of some days ago, no problems. Were there perhaps changes in the last days that introduce this, that some NICs doesn't run ? Even the xl0 interface didn't run (DMZ). Ping to hosts in internet didn't succeed. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Oct 17 00:40:49 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 159383552 (155648K bytes) avail memory = 151044096 (147504K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc030c000. Pentium Pro MTRR support enabled ccd0-3: Concatenated disk drivers npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 chip1: Intel PIIX3 IDE controller at device 7.1 on pci0 vga-pci0: Matrox MGA 2064W graphics accelerator at device 10.0 on pci0 xl0: 3Com 3c900-COMBO Etherlink XL irq 19 at device 11.0 on pci0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: selecting 10baseT transceiver, half duplex pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 18 pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 ahc0: Adaptec 2940 Ultra SCSI adapter irq 17 at device 13.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: Adaptec 2940 Ultra SCSI adapter irq 16 at device 14.0 on pci0 ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs fdc0: NEC 72065B or clone at port 0x3f0-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 port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 4 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry by default DUMMYNET initialized (990811) Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 sa0 at ahc1 bus 0 target 4 lun 0 sa0: TANDBERG TDC 4222 =07: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) Creating DISK cd0 Creating DISK cd1 changing root device to da0s2a cd1 at ahc1 bus 0 target 5 lun 0 cd1: TOSHIBA CD-ROM XM-5701TA 3136 Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: Attempt to query device size failed: NOT READY, Medium not present cd0 at ahc0 bus 0 target 6 lun 0 cd0: TEAC CD-R55S 1.0K Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da3 at ahc0 bus 0 target 3 lun 0 da3: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc0 bus 0 target 2 lun 0 da2: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ed0: remote transmit DMA failed to complete
Re: Network Cards
On Thu, Feb 04, 1999 at 06:01:52AM -0500, Rod Taylor wrote: Suppose you have xl and vr in your computer. They are named eth0 and eth1, respectively. You then replace your vr by a ed. Mark But then if I added another say ed0, it wouldn't get eth2 :) But yeah, I understand where you're going... Not fully. I service fbsd routers with up to 12 ethernet cards. 8 isa cards + 4 pci on advantech prompc computer. And when a cableman add card to a router, (ctrl-alt-del, poweroff, screw card, power on) he install card corresponded to driver name, and set io/irq/mem corresponded to number. -- Igor Nikolaev To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
Rod Taylor wrote: I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... Suppose you have xl and vr in your computer. They are named eth0 and eth1, respectively. You then replace your vr by a ed. Mark with an X the correct option: ( ) the names for vr and ed will be eth0 and eth1, respectively. ( ) the names for vr and ed will be eth1 and eth0, respectively. ( ) none of the above Can you see what I'm getting at here? :-) The best solution would be hardwiring the names, but in that case it doesn't matter what are the default names. -- Daniel C. Sobral(8-DCS) d...@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
But then if I added another say ed0, it wouldn't get eth2 :) But yeah, I understand where you're going... However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... Suppose you have xl and vr in your computer. They are named eth0 and eth1, respectively. You then replace your vr by a ed. Mark with an X the correct option: ( ) the names for vr and ed will be eth0 and eth1, respectively. ( ) the names for vr and ed will be eth1 and eth0, respectively. ( ) none of the above Can you see what I'm getting at here? :-) The best solution would be hardwiring the names, but in that case it doesn't matter what are the default names. -- Daniel C. Sobral (8-DCS) d...@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Rod Taylor Proud Member of Team OS/2 User of FreeBSD KDE To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
On Thu, 4 Feb 1999, Daniel C. Sobral wrote: Rod Taylor wrote: I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc The best solution would be hardwiring the names, but in that case it doesn't matter what are the default names. Yes. Hardwiring is the only appropriate solution. It should be done as a part of the loader kernel configuration. Perhaps it should work somewhat like the SCSI disk partitions. Unspecified interfaces get the next available slot. However, and this is the important point, it is very useful to be able to assign an identifier to the logical interface and have that identifier appear in EVERY reference to the interface. I would like to hardwire 00:aa:bb:cc:dd:ee which uses the vr driver to eth23 and have ifconfig accept and report the device as 'eth23'. The actual driver is parenthetical. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
Rod Taylor wrote: I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... Suppose you have xl and vr in your computer. They are named eth0 and eth1, respectively. You then replace your vr by a ed. Mark with an X the correct option: ( ) the names for vr and ed will be eth0 and eth1, respectively. ( ) the names for vr and ed will be eth1 and eth0, respectively. ( ) none of the above Can you see what I'm getting at here? :-) The best solution would be hardwiring the names, but in that case it doesn't matter what are the default names. Actually, this is just a pathalogical case of: You have de0 and de1 in your computer. You replace one with another 'de' card/rearrange cards/whatever. Mark with an X the correct option ( ) de0 remains de0, de1 remains de1 ( ) de0 becomes de1, de1 becomes de0 ( ) you discover a new device, de-1 Having a single linear namespace for interfaces would, actually, make life somewhat easier for the administrator. You can simulate it buy only buying one type of ethernet card. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
On Thu, 4 Feb 1999, Daniel C. Sobral wrote: Rod Taylor wrote: I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc The best solution would be hardwiring the names, but in that case it doesn't matter what are the default names. Yes. Hardwiring is the only appropriate solution. Hardwiring is nonappropriate in a non-static environment. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Network Cards
I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... -- Rod Taylor Proud Member of Team OS/2 User of FreeBSD KDE To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network Cards
On Wed, 3 Feb 1999, Rod Taylor wrote: I've often wondered this, but why is it that every network card has a different 'name'. xl0, rl0, vr0, ed0, etc. etc. etc I tried simlinking them to a common name (I have xl0, rl0, and ed0 active in my current machine). linked to eth0, eth1, eth2 (didn't work). look at /etc/rc* , try to formulate something like rc.conf where you define internet interfaces like: eth0 = xl0 look at rc.firewall for better examples. However, it would be nice if they all had a common name to the end user.. Primarily, me.. Especially when you rip out one card, install another, then the name changes on you... ifconfig -a Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/4.0-current To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
