From owner-freebsd-net Sun Jul 15 1:28:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id 4AD2237B401; Sun, 15 Jul 2001 01:28:01 -0700 (PDT) (envelope-from bmah@employees.org) Received: from intruder.bmah.org ([24.176.204.87]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010715082800.WCD9548.femail4.sdc1.sfba.home.com@intruder.bmah.org>; Sun, 15 Jul 2001 01:28:00 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.4/8.11.3) id f6F8Rxh02585; Sun, 15 Jul 2001 01:27:59 -0700 (PDT) (envelope-from bmah) Message-Id: <200107150827.f6F8Rxh02585@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: bmah@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> Comments: In-reply-to JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= message dated "Fri, 13 Jul 2001 02:14:04 +0900." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_2096513372P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 15 Jul 2001 01:27:59 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_2096513372P Content-Type: multipart/mixed ; boundary="==_Exmh_20962154840" This is a multipart MIME message. --==_Exmh_20962154840 Content-Type: text/plain; charset=us-ascii If memory serves me right, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI= ?= wrote: OK, I got another crash, with symbols and all. This is a 4-STABLE machine from 7 July. > If possible, please let us know > - the kernel configuration file Attached. > - the result of > % ifconfig -a > % ndp -p > % ndp -r > before the crash (I know it is difficult, though.) I scripted this output shortly after the last reboot. I didn't bother santizing...my RFC 1918 IPv4 and site/link-local IPv6 addresses are probably not of use to anybody. :-) intruder:bmah% ndp -p fec0:0:0:1::/64 if=dc0 flags=A vltime=0, pltime=0, expired, ref=1 advertised by fe80::200:c0ff:fecb:bdf2%dc0 (reachable) fe80::%dc0/64 if=dc0 flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0 No advertising router fe80::%lo0/64 if=lo0 flags=LAO vltime=infinity, pltime=infinity, expire=Never, ref=0 No advertising router intruder:bmah% ndp -r fe80::200:c0ff:fecb:bdf2%dc0 if=dc0, flags=, pref=medium, expire=56m54s intruder:bmah% ifconfig -a dc0: flags=8843 mtu 1500 inet6 fe80::200:f8ff:fe10:7aa2%dc0 prefixlen 64 scopeid 0x1 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fec0::1:200:f8ff:fe10:7aa2 prefixlen 64 autoconf ether 00:00:f8:10:7a:a2 media: Ethernet autoselect (10baseT/UTP) status: active gif0: flags=8010 mtu 1280 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff000000 stf0: flags=0<> mtu 1280 > as well as the stack trace with debugging symbols. Also attached. Please let me know if there's any other information I can provide. Thanks! Bruce. --==_Exmh_20962154840 Content-Type: text/plain ; name="NIMITZ"; charset=us-ascii Content-Description: NIMITZ # # $Id: NIMITZ,v 1.19 2001/01/18 05:59:25 bmah Exp $ # # NIMITZ -- Bruce's semi-generic workstation configuration # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.25 2001/05/13 03:50:01 jlemon Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident NIMITZ maxusers 128 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols makeoptions KERNEL=kernel # # Certain applications can grow to be larger than the 128M limit # that FreeBSD initially imposes. Below are some options to # allow that limit to grow to 256MB, and can be increased further # with changing the parameters. MAXDSIZ is the maximum that the # limit can be set to, and the DFLDSIZ is the default value for # the limit. You might want to set the default lower than the # max, and explicitly set the maximum with a shell command for processes # that regularly exceed the limit like INND. # options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_DEBUG #debug for IP security options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options PNPBIOS # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 disable drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family device ahc0 # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #options SYM_SETUP_LP_PROBE_MAP=0x40 # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured #device adv0 at isa? #device adw #device bt0 at isa? device aha0 at isa? #device aic0 at isa? #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required) device scbus0 at ahc0 #device da # Direct Access (disks) device da0 at scbus0 target 0 device da1 at scbus0 target 1 device da2 at scbus0 target 2 device da3 at scbus0 target 3 device da4 at scbus0 target 4 device da5 at scbus0 target 5 device da6 at scbus0 target 6 device da8 at scbus0 target 8 device da9 at scbus0 target 9 device da10 at scbus0 target 10 device da11 at scbus0 target 11 device da12 at scbus0 target 12 device da13 at scbus0 target 13 device da14 at scbus0 target 14 device da15 at scbus0 target 15 device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache - See LINT for options! #device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers #device aac # Adaptec FSA RAID, Dell PERC2/PERC3 #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family #device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device tx # SMC 9432TX (83c170 ``EPIC'') device vx # 3Com 3c590, 3c595 (``Vortex'') device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcn # AMD Am79C79x PCI 10/100 NICs device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex device ep #device fe0 at isa? port 0x300 # Xircom Ethernet #device xe # PRISM I IEEE 802.11b wireless NIC. #device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. #device an # Xircom Ethernet #device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 1 # IPv6 and IPv4 tunneling #pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device stf 1 # 6to4 IPv6 over IPv4 encapsulation pseudo-device vn # Vnode driver (turns a file into a device) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet # Brooktree driver has been ported to the new I2C framework. Thus, # you'll need to have the following 3 lines in the kernel config. # device smbus # device iicbus # device iicbb # The iic and smb devices are only needed if you want to control other # I2C slaves connected to the external connector of some cards. # device bktr # # SMB bus # # System Management Bus support provided by the 'smbus' device. # # Supported devices: # smb standard io # # Supported interfaces: # iicsmb I2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # intpm Intel PIIX4 Power Management Unit # alpm Acer Aladdin-IV/V/Pro2 Power Management Unit # device smbus # Bus support, required for smb below. device intpm device alpm device smb # # I2C Bus # # Philips i2c bus support is provided by the `iicbus' device. # # Supported devices: # ic i2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. # # Supported interfaces: # pcf Philips PCF8584 ISA-bus controller # bktr brooktree848 I2C software interface # # Other: # iicbb generic I2C bit-banging code (needed by lpbb, bktr) # device iicbus # Bus support, required for ic/iic/iicsmb below. device iicbb device ic device iic device iicsmb # smb over i2c bridge #device pcf0 at isa? port 0x320 irq 5 # The newpcm driver (use INSTEAD of snd0 and all VOXWARE drivers!). # Note that motherboard sound devices may require options PNPBIOS. # # Supported cards include: # Creative SoundBlaster ISA PnP/non-PnP # Supports ESS and Avance ISA chips as well. # Gravis UltraSound ISA PnP/non-PnP # Crystal Semiconductor CS461x/428x PCI # Neomagic 256AV (ac97) # Most of the more common ISA/PnP sb/mss/ess compatable cards. # For non-pnp sound cards with no bridge drivers only: #device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 # # For PnP/PCI sound cards device pcm0 # The bridge drivers for sound cards. These can be seperately configured # for providing services to the likes of new-midi (not in the tree yet). # When used with 'device pcm' they also provide pcm sound services. # # sbc: Creative SoundBlaster ISA PnP/non-PnP # Supports ESS and Avance ISA chips as well. # gusc: Gravis UltraSound ISA PnP/non-PnP # csa: Crystal Semiconductor CS461x/428x PCI # For non-PnP cards: device sbc0 #device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 #device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 --==_Exmh_20962154840 Content-Type: text/plain ; name="typescript"; charset=us-ascii Content-Description: typescript Script started on Sun Jul 15 01:19:06 2001 intruder:bmah% cd /var/crash intruder:crash% sudo gdb -k /usr/obj/usr/src/sys/NIMITZ/kernel.debug vmcore.1 Password: GNU gdb 4.18 Copyright 1998 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"... IdlePTD 4808704 initial pcb at 3c6940 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3f fault code = supervisor read, page not present instruction pointer = 0x8:0xc01fc048 stack pointer = 0x10:0xce0faf60 frame pointer = 0x10:0xce0faf78 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 369 (setiathome) interrupt mask = trap number = 12 panic: page fault syncing disks... 3 1 done Uptime: 1d22h58m51s dumping to dev #da/0x30001, offset 786456 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:472 472 if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:472 #1 0xc017a6a3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:312 #2 0xc017aa20 in poweroff_wait (junk=0xc036940f, howto=-930851904) at /usr/src/sys/kern/kern_shutdown.c:559 #3 0xc03089c1 in trap_fatal (frame=0xce0faf20, eva=63) at /usr/src/sys/i386/i386/trap.c:951 #4 0xc0308699 in trap_pfault (frame=0xce0faf20, usermode=0, eva=63) at /usr/src/sys/i386/i386/trap.c:844 #5 0xc0308253 in trap (frame={tf_fs = -1052442608, tf_es = 16, tf_ds = 16, tf_edi = -1053982720, tf_esi = 3, tf_ebp = -837832840, tf_isp = -837832884, tf_ebx = -1051834112, tf_edx = 0, tf_ecx = 6422528, tf_eax = -1052087104, tf_trapno = 12, tf_err = 0, tf_eip = -1071660984, tf_cs = 8, tf_eflags = 66054, tf_esp = 0, tf_ss = -1071661068}) at /usr/src/sys/i386/i386/trap.c:443 #6 0xc01fc048 in nd6_timer (ignored_arg=0x0) at /usr/src/sys/netinet6/nd6.c:443 #7 0xc01802a9 in softclock () at /usr/src/sys/kern/kern_timeout.c:131 #8 0xc02fc1df in doreti_swi () #9 0x3263 in ?? () #10 0xef9b in ?? () #11 0x138fe in ?? () #12 0x13a25 in ?? () #13 0x2abb in ?? () #14 0x107e in ?? () (kgdb) up #1 0xc017a6a3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:312 312 dumpsys(); (kgdb) p The history is empty. (kgdb) up #2 0xc017aa20 in poweroff_wait (junk=0xc036940f, howto=-930851904) at /usr/src/sys/kern/kern_shutdown.c:559 559 boot(bootopt); (kgdb) up #3 0xc03089c1 in trap_fatal (frame=0xce0faf20, eva=63) at /usr/src/sys/i386/i386/trap.c:951 951 panic(trap_msg[type]); (kgdb) up #4 0xc0308699 in trap_pfault (frame=0xce0faf20, usermode=0, eva=63) at /usr/src/sys/i386/i386/trap.c:844 844 trap_fatal(frame, eva); (kgdb) up #5 0xc0308253 in trap (frame={tf_fs = -1052442608, tf_es = 16, tf_ds = 16, tf_edi = -1053982720, tf_esi = 3, tf_ebp = -837832840, tf_isp = -837832884, tf_ebx = -1051834112, tf_edx = 0, tf_ecx = 6422528, tf_eax = -1052087104, tf_trapno = 12, tf_err = 0, tf_eip = -1071660984, tf_cs = 8, tf_eflags = 66054, tf_esp = 0, tf_ss = -1071661068}) at /usr/src/sys/i386/i386/trap.c:443 443 (void) trap_pfault(&frame, FALSE, eva); (kgdb) up #6 0xc01fc048 in nd6_timer (ignored_arg=0x0) at /usr/src/sys/netinet6/nd6.c:443 443 continue; (kgdb) list 438 /* XXX: used for the DELAY case only: */ 439 struct nd_ifinfo *ndi = NULL; 440 441 if ((rt = ln->ln_rt) == NULL) { 442 ln = next; 443 continue; 444 } 445 if ((ifp = rt->rt_ifp) == NULL) { 446 ln = next; 447 continue; (kgdb) quit intruder:crash% exit exit Script done on Sun Jul 15 01:20:05 2001 --==_Exmh_20962154840-- --==_Exmh_2096513372P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7UVQP2MoxcVugUsMRAuQnAKDQL4tKjA9GyJ8s0p5Rii/VL8oC4gCfW59C dXcCNap3tl1t5NPGGa5Vnf4= =dD9o -----END PGP SIGNATURE----- --==_Exmh_2096513372P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 8:13:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id CA29337B405; Sun, 15 Jul 2001 08:13:21 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:/M4qi+yn9uZXApUdmq3hyph/y1X0dKpgjNqoGKKKaUVJ+S7Z4ex+2eFlSxc4C369@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.4/8.11.4/peace) with ESMTP/inet6 id f6FFDIo35936; Mon, 16 Jul 2001 00:13:18 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 16 Jul 2001 00:13:14 +0900 (JST) Message-Id: <20010716.001314.59549708.ume@mahoroba.org> To: net@FreeBSD.org, current@FreeBSD.org Subject: Use of M_WAITOK in if_addmulti(). From: Hajimu UMEMOTO In-Reply-To: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> References: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> X-Mailer: Mew version 1.95b119 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Current if_addmulti() calls MALLOC() with M_WAITOK. However, if_addmulti() can be called from in[6]_addmulti() with splnet(). It may lead kernel panic. So, I wish to change to use M_NOWAIT. Any comment? Index: sys/net/if.c diff -u sys/net/if.c.orig sys/net/if.c --- sys/net/if.c.orig Wed Jul 4 20:28:47 2001 +++ sys/net/if.c Sun Jul 15 23:47:15 2001 @@ -1412,8 +1412,8 @@ llsa = 0; } - MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_WAITOK); - MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_WAITOK); + MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_NOWAIT); + MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_NOWAIT); bcopy(sa, dupsa, sa->sa_len); ifma->ifma_addr = dupsa; @@ -1441,9 +1441,9 @@ ifma->ifma_refcount++; } else { MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, - M_IFMADDR, M_WAITOK); + M_IFMADDR, M_NOWAIT); MALLOC(dupsa, struct sockaddr *, llsa->sa_len, - M_IFMADDR, M_WAITOK); + M_IFMADDR, M_NOWAIT); bcopy(llsa, dupsa, llsa->sa_len); ifma->ifma_addr = dupsa; ifma->ifma_ifp = ifp; -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 9:19:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id E27ED37B403 for ; Sun, 15 Jul 2001 09:19:13 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Jul 2001 17:18:56 +0100 (BST) To: Bernd Walter Cc: Hajimu UMEMOTO , freebsd-net@FreeBSD.ORG Subject: Re: how to get AF_LOCAL from getaddrinfo() In-Reply-To: Your message of "Sat, 14 Jul 2001 18:44:27 +0200." <20010714184427.C23031@cicely20.cicely.de> Date: Sun, 15 Jul 2001 17:18:54 +0100 From: Ian Dowse Message-ID: <200107151718.aa17383@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <20010714184427.C23031@cicely20.cicely.de>, Bernd Walter writes: >> Our getaddrinfo(3) doesn't support AF_UNIX. > >Arg - I looked into src/contrib/bin/lib/irs/getaddrinfo.c >The one in libc is different... I'd very much like to see PF_LOCAL support added to our getaddrinfo() and getnameinfo(). I know that PF_LOCAL sockets have semantics that are quite different to other protocol families, so the goal of protocol-independent translation is not really met. However supporting this will still result in simpler code within many programs. Is there any standard that defines how getaddrinfo() should deal with PF_LOCAL addreses? I guess we could do something such as the following, but it would make sense to stick to the same semantics as any other implementations that might exist: getaddrinfo: nodename NULL (maybe allow "localhost" or just ignore?) servname NUL-terminated sun_path hints: ai_flags AI_PASSIVE, AI_NUMERICHOST ignored AI_CANONNAME must not be specified ai_family must be PF_LOCAL ai_socktype SOCK_STREAM or SOCK_DGRAM ai_protocol must be 0 ai_addrlen must be 0 ai_canonname must be NULL ai_addr must be NULL ai_next must be NULL getnameinfo: host, hostlen maybe require NULL, or store "localhost"? serv, servlen store NUL-terminated sun_path flags ignore NI_NOFQDN, NI_NUMERICHOST, NI_NAMEREQD, NI_NUMERICSERV, NI_DGRAM These look quite easy to implement, since the code can just check hints->ai_family (for getnameinfo, sa->sa_family) to determine if the request is for a PF_LOCAL address. Obviously, to create listening PF_LOCAL sockets, the caller still has to do the unlink (and umask if desired). Any comments or suggestions, or should I just try this and post proposed patches? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 9:24:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id D292E37B409; Sun, 15 Jul 2001 09:24:14 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA79651; Sun, 15 Jul 2001 11:18:48 -0700 (PDT) Message-ID: <3B51C28F.7A56D8D8@elischer.org> Date: Sun, 15 Jul 2001 09:19:27 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Hajimu UMEMOTO Cc: net@FreeBSD.org, current@FreeBSD.org Subject: Re: Use of M_WAITOK in if_addmulti(). References: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> <20010716.001314.59549708.ume@mahoroba.org> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hajimu UMEMOTO wrote: NOWAIT MAY return. you have not handled the case for when it returns with a NULL allocation so if it returns NULL you continue, and page-fault immediatly. > > Hi, > > Current if_addmulti() calls MALLOC() with M_WAITOK. However, > if_addmulti() can be called from in[6]_addmulti() with splnet(). It > may lead kernel panic. So, I wish to change to use M_NOWAIT. > Any comment? > > Index: sys/net/if.c > diff -u sys/net/if.c.orig sys/net/if.c > --- sys/net/if.c.orig Wed Jul 4 20:28:47 2001 > +++ sys/net/if.c Sun Jul 15 23:47:15 2001 > @@ -1412,8 +1412,8 @@ > llsa = 0; > } > > - MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_WAITOK); > - MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_WAITOK); > + MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_NOWAIT); > + MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_NOWAIT); > bcopy(sa, dupsa, sa->sa_len); > > ifma->ifma_addr = dupsa; > @@ -1441,9 +1441,9 @@ > ifma->ifma_refcount++; > } else { > MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, > - M_IFMADDR, M_WAITOK); > + M_IFMADDR, M_NOWAIT); > MALLOC(dupsa, struct sockaddr *, llsa->sa_len, > - M_IFMADDR, M_WAITOK); > + M_IFMADDR, M_NOWAIT); > bcopy(llsa, dupsa, llsa->sa_len); > ifma->ifma_addr = dupsa; > ifma->ifma_ifp = ifp; > > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org > http://www.imasy.org/~ume/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message WAIT____ -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 10:25:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 2974637B403; Sun, 15 Jul 2001 10:25:11 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.3+3.4W/8.11.3/light) with UUCP id f6FHP1216099; Mon, 16 Jul 2001 02:25:01 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:sxTc4RZcYEQYf5SvLGaGaTycVj/Aeo06n0y4OZO1NAxuUEKkgHGMLia8iE2DyX/X@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) (authenticated as ume with CRAM-MD5) by mail.mahoroba.org (8.11.4/8.11.4/chaos) with ESMTP/inet6 id f6FHOgL23057; Mon, 16 Jul 2001 02:24:43 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 16 Jul 2001 02:24:39 +0900 (JST) Message-Id: <20010716.022439.74683611.ume@mahoroba.org> To: julian@elischer.org Cc: net@FreeBSD.org, current@FreeBSD.org Subject: Re: Use of M_WAITOK in if_addmulti(). From: Hajimu UMEMOTO In-Reply-To: <3B51C28F.7A56D8D8@elischer.org> References: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> <20010716.001314.59549708.ume@mahoroba.org> <3B51C28F.7A56D8D8@elischer.org> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Sun, 15 Jul 2001 09:19:27 -0700 >>>>> Julian Elischer said: julian> NOWAIT MAY return. julian> you have not handled the case for when it returns with a NULL allocation julian> so if it returns NULL you continue, and page-fault immediatly. Oops, thank you. How about this? Index: sys/net/if.c diff -u sys/net/if.c.orig sys/net/if.c --- sys/net/if.c.orig Mon Jul 16 01:39:34 2001 +++ sys/net/if.c Mon Jul 16 01:51:49 2001 @@ -1412,8 +1412,14 @@ llsa = 0; } - MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_WAITOK); - MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_WAITOK); + MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_NOWAIT); + if (iama == NULL) + return (ENOBUFS); + MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_NOWAIT); + if (dupsa == NULL) { + FREE(ifma, M_IFMADDR); + return (ENOBUFS); + } bcopy(sa, dupsa, sa->sa_len); ifma->ifma_addr = dupsa; @@ -1441,9 +1447,15 @@ ifma->ifma_refcount++; } else { MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, - M_IFMADDR, M_WAITOK); + M_IFMADDR, M_NOWAIT); + if (iama == NULL) + return (ENOBUFS); MALLOC(dupsa, struct sockaddr *, llsa->sa_len, - M_IFMADDR, M_WAITOK); + M_IFMADDR, M_NOWAIT); + if (dupsa == NULL) { + FREE(ifma, M_IFMADDR); + return (ENOBUFS); + } bcopy(llsa, dupsa, llsa->sa_len); ifma->ifma_addr = dupsa; ifma->ifma_ifp = ifp; -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 10:31:12 2001 Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 3DEC437B401; Sun, 15 Jul 2001 10:31:04 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:KDGClK7a+52EuQvJR80VQaf99FNJoc1zyOjYd+cAUNj1xi/oQcCHgLI5f1K70omw@localhost [::1]) (authenticated as ume with CRAM-MD5) by peace.mahoroba.org (8.11.4/8.11.4/peace) with ESMTP/inet6 id f6FHUkJ60741; Mon, 16 Jul 2001 02:30:46 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 16 Jul 2001 02:30:43 +0900 (JST) Message-Id: <20010716.023043.130171162.ume@mahoroba.org> To: julian@elischer.org Cc: net@FreeBSD.org, current@FreeBSD.org Subject: Re: Use of M_WAITOK in if_addmulti(). From: Hajimu UMEMOTO In-Reply-To: <20010716.022439.74683611.ume@mahoroba.org> References: <20010716.001314.59549708.ume@mahoroba.org> <3B51C28F.7A56D8D8@elischer.org> <20010716.022439.74683611.ume@mahoroba.org> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org ume> Index: sys/net/if.c ume> diff -u sys/net/if.c.orig sys/net/if.c ume> --- sys/net/if.c.orig Mon Jul 16 01:39:34 2001 ume> +++ sys/net/if.c Mon Jul 16 01:51:49 2001 Oops, it was wrong version. Index: sys/net/if.c diff -u sys/net/if.c.orig sys/net/if.c --- sys/net/if.c.orig Mon Jul 16 01:39:34 2001 +++ sys/net/if.c Mon Jul 16 01:51:49 2001 @@ -1412,8 +1412,14 @@ llsa = 0; } - MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_WAITOK); - MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_WAITOK); + MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, M_IFMADDR, M_NOWAIT); + if (ifma == NULL) + return (ENOBUFS); + MALLOC(dupsa, struct sockaddr *, sa->sa_len, M_IFMADDR, M_NOWAIT); + if (dupsa == NULL) { + FREE(ifma, M_IFMADDR); + return (ENOBUFS); + } bcopy(sa, dupsa, sa->sa_len); ifma->ifma_addr = dupsa; @@ -1441,9 +1447,15 @@ ifma->ifma_refcount++; } else { MALLOC(ifma, struct ifmultiaddr *, sizeof *ifma, - M_IFMADDR, M_WAITOK); + M_IFMADDR, M_NOWAIT); + if (ifma == NULL) + return (ENOBUFS); MALLOC(dupsa, struct sockaddr *, llsa->sa_len, - M_IFMADDR, M_WAITOK); + M_IFMADDR, M_NOWAIT); + if (dupsa == NULL) { + FREE(ifma, M_IFMADDR); + return (ENOBUFS); + } bcopy(llsa, dupsa, llsa->sa_len); ifma->ifma_addr = dupsa; ifma->ifma_ifp = ifp; -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 12: 3:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id D3F9D37B401; Sun, 15 Jul 2001 12:03:16 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id 8B8355D010; Sun, 15 Jul 2001 14:03:05 -0500 (CDT) Date: Sun, 15 Jul 2001 14:03:05 -0500 From: Alfred Perlstein To: Hajimu UMEMOTO Cc: julian@elischer.org, net@FreeBSD.org, current@FreeBSD.org Subject: Re: Use of M_WAITOK in if_addmulti(). Message-ID: <20010715140305.H15299@sneakerz.org> References: <20010716.001314.59549708.ume@mahoroba.org> <3B51C28F.7A56D8D8@elischer.org> <20010716.022439.74683611.ume@mahoroba.org> <20010716.023043.130171162.ume@mahoroba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010716.023043.130171162.ume@mahoroba.org>; from ume@mahoroba.org on Mon, Jul 16, 2001 at 02:30:43AM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Hajimu UMEMOTO [010715 12:31] wrote: > > ume> Index: sys/net/if.c > ume> diff -u sys/net/if.c.orig sys/net/if.c > ume> --- sys/net/if.c.orig Mon Jul 16 01:39:34 2001 > ume> +++ sys/net/if.c Mon Jul 16 01:51:49 2001 > > Oops, it was wrong version. One trick is to pass a "waitok" parameter, the INET6 code would call it with it set to zero, however most other consumers would call it with it set to one meaning they can block. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 13:11:54 2001 Delivered-To: freebsd-net@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-181.dsl.lsan03.pacbell.net [64.165.226.181]) by hub.freebsd.org (Postfix) with ESMTP id E14A537B401 for ; Sun, 15 Jul 2001 13:11:50 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 66B2A66DF6; Sun, 15 Jul 2001 13:11:49 -0700 (PDT) Date: Sun, 15 Jul 2001 13:11:48 -0700 From: Kris Kennaway To: Jonathan Lemon Cc: gjohnson@srrc.ars.usda.gov, net@freebsd.org, provos@OpenBSD.org Subject: TCP ISN algorithm breaks TIME_WAIT (Re: select fails to return incoming connect on FreeBSD-4.3) Message-ID: <20010715131148.A10745@xor.obsecurity.org> References: <200106111937.f5BJb9o99898@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106111937.f5BJb9o99898@prism.flugsvamp.com>; from jlemon@flugsvamp.com on Mon, Jun 11, 2001 at 02:37:10PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 11, 2001 at 02:37:10PM -0500, Jonathan Lemon wrote: > In article you write: > >First off, I hope this is the right list. > > > >Could someone take a look at PR misc/27880? >=20 > This was broken by the initial sequence number patch to TCP. >=20 > When the server closes the socket, it puts the entry into the=20 > TIME_WAIT state. When a new SYN is received from the client while > the socket is in this state, the new connection is only accepted > if the new sequence number is > than the old one. >=20 > Unfortunately, with a randomized seqence #, the new connection ISN > may be less than the old sequence used, and the SYN will be ignored. >=20 > I've copied this over to kris, who (IIRC) brought in the new sequence > numbering. Sorry I've been ignoring this; I'm still getting caught up from my vacation. Niels, how has OpenBSD handled this? Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7UfkDWry0BWjoQKURAndRAJ9TNWKGlAulHyU0TwLYGMWjdXNquACfa75B CG2rN09GXm31z+TU3JBwzv0= =8RZE -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 13:45:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 190F037B405; Sun, 15 Jul 2001 13:45:21 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6FKjJK19528; Sun, 15 Jul 2001 13:45:19 -0700 Date: Sun, 15 Jul 2001 13:45:19 -0700 From: Brooks Davis To: net@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: review request: if_faith modernization Message-ID: <20010715134519.A19048@Odin.AC.HMC.Edu> References: <20010714144147.A27610@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010714144147.A27610@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Sat, Jul 14, 2001 at 02:41:47PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 14, 2001 at 02:41:47PM -0700, Brooks Davis wrote: > Please review the following patch. It makes the faith interface > loadable, unloadable, and clonable. It also converts it from a count > device to an option device. A copy is also available at: >=20 > http://people.freebsd.org/~brooks/patches/faith.diff I've updated the patch at the above URL. It no longer bogusly contains the (commited) style change to sys/modules/Makefile or an unrelated addition to sys/conf/files. -- Brooks --=20 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 --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7UgDeXY6L6fI4GtQRAiSpAKCb9PZOWedoNqaowob2lDjOogiDNgCgiTSq Tg4rga2oo3Pe6Ou17sGzZu0= =+LBm -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 13:51:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id F390E37B403; Sun, 15 Jul 2001 13:51:16 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f6FKoae21142; Sun, 15 Jul 2001 16:50:36 -0400 (EDT) (envelope-from wollman) Date: Sun, 15 Jul 2001 16:50:36 -0400 (EDT) From: Garrett Wollman Message-Id: <200107152050.f6FKoae21142@khavrinen.lcs.mit.edu> To: Hajimu UMEMOTO Cc: net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Use of M_WAITOK in if_addmulti(). In-Reply-To: <20010716.001314.59549708.ume@mahoroba.org> References: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> <20010716.001314.59549708.ume@mahoroba.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Current if_addmulti() calls MALLOC() with M_WAITOK. However, > if_addmulti() can be called from in[6]_addmulti() with splnet(). It > may lead kernel panic. This is not a problem (or should not be). It is permissible to sleep while some interrupts are blocked; it is just not (in 4-stable) permissible to sleep in interrupt context. The PR that I sent a few days ago was an example of one such circumstance. Is it really the case that in6_addmulti() can be invoked in interrupt context, and if so, why? -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Jul 15 18:43:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 49B1737B401; Sun, 15 Jul 2001 18:43:35 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:10c1:ed03:fbc7:d990:5678]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id KAA08771; Mon, 16 Jul 2001 10:45:23 +0900 (JST) Date: Mon, 16 Jul 2001 10:43:31 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Garrett Wollman Cc: net@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Use of M_WAITOK in if_addmulti(). In-Reply-To: <200107152050.f6FKoae21142@khavrinen.lcs.mit.edu> References: <20010715120317.A99869@fump.kawo2.rwth-aachen.de> <20010716.001314.59549708.ume@mahoroba.org> <200107152050.f6FKoae21142@khavrinen.lcs.mit.edu> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 29 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Sun, 15 Jul 2001 16:50:36 -0400 (EDT), >>>>> Garrett Wollman said: >> Current if_addmulti() calls MALLOC() with M_WAITOK. However, >> if_addmulti() can be called from in[6]_addmulti() with splnet(). It >> may lead kernel panic. > This is not a problem (or should not be). It is permissible to sleep > while some interrupts are blocked; it is just not (in 4-stable) > permissible to sleep in interrupt context. The PR that I sent a few > days ago was an example of one such circumstance. Is it really the > case that in6_addmulti() can be invoked in interrupt context, Yes, it is. in6_update_ifa() can be called under an interrupt context, as you pointed out, and it calls in6_joingroup(), which then calls in6_addmulti(). > and if > so, why? When a new unicast address is configured, the configuring node must be join the solicited-node multicast group corresponding to the unicast address. Since the autoconfiguration procedure runs under an interrupt context, the joining routine also runs under the context. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 0:18: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id 146C937B401 for ; Mon, 16 Jul 2001 00:18:03 -0700 (PDT) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust170.tnt22.rtm1.nl.uu.net [213.116.138.170] with SMTP for id JAA17057 (8.8.8/1.3); Mon, 16 Jul 2001 09:18:01 +0200 (MET DST) Reply-To: From: "Peter Blok" To: Subject: patch for if_wi.c Date: Mon, 16 Jul 2001 09:13:47 +0200 Message-ID: <000801c10dc6$db51c760$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I have bought two SMC wireless cards. One SMC2632 in my laptop, the other a SMC2602 (PCI to SMC2632) in my FreeBSD server. I am running FreeBSD-STABLE as of july 1. Initially it didn't work because the PCI to PCMCIA bridge picked an interrupt that was already in use. Since I couldn't force the SMC2602 or BIOS to use another interrupt, I started to wonder if it was really necessary to have a non-shared interrupt. I have patched the code to allow shared interrupts and everything works fine. The other devices on the same interrupt are working too. Can somebody please look at the patch and apply it if ok. I don't know if it going to break the code when you use the PCMCIA card in a FreeBSD ISA to PCMCIA bridge. *** if_wi.c.orig Sun Jul 15 12:06:12 2001 --- if_wi.c Sun Jul 15 11:57:02 2001 *************** *** 1906,1912 **** sc->irq_rid = 0; sc->irq = bus_alloc_resource(dev, SYS_RES_IRQ, &sc->irq_rid, ! 0, ~0, 1, RF_ACTIVE); if (!sc->irq) { wi_free(dev); device_printf(dev, "No irq?!\n"); --- 1906,1912 ---- sc->irq_rid = 0; sc->irq = bus_alloc_resource(dev, SYS_RES_IRQ, &sc->irq_rid, ! 0, ~0, 1, RF_SHAREABLE|RF_ACTIVE); if (!sc->irq) { wi_free(dev); device_printf(dev, "No irq?!\n"); Thx, Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 1: 2:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 7BC3D37B403 for ; Mon, 16 Jul 2001 01:02:22 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f6G804B04402; Mon, 16 Jul 2001 11:00:04 +0300 (EEST) (envelope-from ru) Date: Mon, 16 Jul 2001 11:00:04 +0300 From: Ruslan Ermilov To: Kris Kennaway Cc: Jonathan Lemon , gjohnson@srrc.ars.usda.gov, net@FreeBSD.ORG, provos@OpenBSD.org Subject: Re: TCP ISN algorithm breaks TIME_WAIT (Re: select fails to return incoming connect on FreeBSD-4.3) Message-ID: <20010716110004.C97729@sunbay.com> Mail-Followup-To: Kris Kennaway , Jonathan Lemon , gjohnson@srrc.ars.usda.gov, net@FreeBSD.ORG, provos@OpenBSD.org References: <200106111937.f5BJb9o99898@prism.flugsvamp.com> <20010715131148.A10745@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010715131148.A10745@xor.obsecurity.org>; from kris@obsecurity.org on Sun, Jul 15, 2001 at 01:11:48PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, Jul 15, 2001 at 01:11:48PM -0700, Kris Kennaway wrote: > On Mon, Jun 11, 2001 at 02:37:10PM -0500, Jonathan Lemon wrote: > > In article you write: > > >First off, I hope this is the right list. > > > > > >Could someone take a look at PR misc/27880? > > > > This was broken by the initial sequence number patch to TCP. > > > > When the server closes the socket, it puts the entry into the > > TIME_WAIT state. When a new SYN is received from the client while > > the socket is in this state, the new connection is only accepted > > if the new sequence number is > than the old one. > > > > Unfortunately, with a randomized seqence #, the new connection ISN > > may be less than the old sequence used, and the SYN will be ignored. > > > > I've copied this over to kris, who (IIRC) brought in the new sequence > > numbering. > > Sorry I've been ignoring this; I'm still getting caught up from my > vacation. Niels, how has OpenBSD handled this? > Recall my question on IRC about monotonicity right after you committed this? Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 1: 8: 6 2001 Delivered-To: freebsd-net@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-2.dsl.lsan03.pacbell.net [64.169.104.2]) by hub.freebsd.org (Postfix) with ESMTP id D58CD37B405 for ; Mon, 16 Jul 2001 01:08:03 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 77B6A67378; Mon, 16 Jul 2001 01:08:02 -0700 (PDT) Date: Mon, 16 Jul 2001 01:08:01 -0700 From: Kris Kennaway To: Kris Kennaway , Jonathan Lemon , gjohnson@srrc.ars.usda.gov, net@FreeBSD.ORG, provos@OpenBSD.org Subject: Re: TCP ISN algorithm breaks TIME_WAIT (Re: select fails to return incoming connect on FreeBSD-4.3) Message-ID: <20010716010800.C15001@xor.obsecurity.org> References: <200106111937.f5BJb9o99898@prism.flugsvamp.com> <20010715131148.A10745@xor.obsecurity.org> <20010716110004.C97729@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="/unnNtmY43mpUSKx" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010716110004.C97729@sunbay.com>; from ru@FreeBSD.ORG on Mon, Jul 16, 2001 at 11:00:04AM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --/unnNtmY43mpUSKx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 16, 2001 at 11:00:04AM +0300, Ruslan Ermilov wrote: > Recall my question on IRC about monotonicity right after you committed > this? Yes; recall my answer? :) Kris --/unnNtmY43mpUSKx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7UqDgWry0BWjoQKURAnzoAJ9/3B56Oi/MUR9zDHtRoiLs9kLnzACgoTRK 0+y2CVDSjsJEXg+EZ1m1QfQ= =xP8x -----END PGP SIGNATURE----- --/unnNtmY43mpUSKx-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 3:53: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 5203137B405 for ; Mon, 16 Jul 2001 03:53:03 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15M60Z-0001wl-00 for net@FreeBSD.org; Mon, 16 Jul 2001 12:53:47 +0200 From: Sheldon Hearn To: net@FreeBSD.org Subject: Contributing manpage patches back to KAME project Date: Mon, 16 Jul 2001 12:53:47 +0200 Message-ID: <7486.995280827@axl.seasidesoftware.co.za> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi folks, Where do I send changes to the KAME manual pages? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 4: 4:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from arpa.it.uc3m.es (arpa.it.uc3m.es [163.117.139.120]) by hub.freebsd.org (Postfix) with ESMTP id 7D6DC37B407 for ; Mon, 16 Jul 2001 04:04:01 -0700 (PDT) (envelope-from jrh@arpa.it.uc3m.es) Received: from localhost (jrh@localhost) by arpa.it.uc3m.es (8.9.3/8.9.3) with SMTP id NAA22752 for ; Mon, 16 Jul 2001 13:03:57 +0200 Date: Mon, 16 Jul 2001 13:03:57 +0200 (MET DST) From: Juan Francisco Rodriguez Hervella Reply-To: Juan Francisco Rodriguez Hervella To: freebsd-net@freebsd.org Subject: In which kernel version appears 6to4 tunnels? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi: I need to know in what version of FreeBSD you can use the 6to4 tunnels for IPv6. How long have 6to4 tunnels been implemented ? Also, if someone knows in which versions of FreeBSD appeared the automatic and configured tunnels for IPv6, or where I can search these information... Thanks!. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 4:25:32 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id DEB2437B406 for ; Mon, 16 Jul 2001 04:25:28 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:10c1:3067:80ad:62f9:3f4d]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id UAA13068; Mon, 16 Jul 2001 20:27:15 +0900 (JST) Date: Mon, 16 Jul 2001 20:25:23 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Sheldon Hearn Cc: net@FreeBSD.ORG Subject: Re: Contributing manpage patches back to KAME project In-Reply-To: <7486.995280827@axl.seasidesoftware.co.za> References: <7486.995280827@axl.seasidesoftware.co.za> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 17 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Mon, 16 Jul 2001 12:53:47 +0200, >>>>> Sheldon Hearn said: > Where do I send changes to the KAME manual pages? Thanks for the offer. The best place would be core@kame.net, which is the list for core developers of the KAME project. This list is closed to discuss delicate issues such as confidential ones, but I think the list is appropriate in this case because the changes would be minor details for most people. If you deal with them in a public place, please use snap-users@kame.net. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 5:22:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id 2F78637B409 for ; Mon, 16 Jul 2001 05:22:23 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 53029 invoked by uid 1000); 16 Jul 2001 12:26:38 -0000 Date: Mon, 16 Jul 2001 15:26:38 +0300 From: Peter Pentchev To: net@FreeBSD.org Subject: ICMP source quench - deprecated? Message-ID: <20010716152638.B52566@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I just had a friend ask me a weird question about ICMP source quench and its handling in various OS's. He proceeded to show me a part of some version of the Linux kernel source, which processed a source quench request properly, yet had a 'This is deprecated' comment at the top. I had a quick look at src/sys/netinet/tcp_subr.c, and on FreeBSD 4.x and -current, an ICMP source quench seems to provoke a proper downsizing of the connection window. Is there any reason for ICMP source quench to be deprecated? If so, what is it to be replaced with? Or are the TCP window scaling algorithms smart enough to downsize the window quick enough in case of a noticeable packet loss? (I guess they should be..) G'luck, Peter -- If I were you, who would be reading this sentence? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 6:47:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 3929937B401; Mon, 16 Jul 2001 06:47:08 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:10c1:bd79:bebf:2dfd:d3ef]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id WAA14465; Mon, 16 Jul 2001 22:49:00 +0900 (JST) Date: Mon, 16 Jul 2001 22:47:07 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: bmah@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: <200107150827.f6F8Rxh02585@intruder.bmah.org> References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 33 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Sun, 15 Jul 2001 01:27:59 -0700, >>>>> "Bruce A. Mah" said: > OK, I got another crash, with symbols and all. This is a 4-STABLE > machine from 7 July. Thanks for the info. (kgdb) list 438 /* XXX: used for the DELAY case only: */ 439 struct nd_ifinfo *ndi = NULL; 440 441 if ((rt = ln->ln_rt) == NULL) { 442 ln = next; 443 continue; 444 } 445 if ((ifp = rt->rt_ifp) == NULL) { 446 ln = next; 447 continue; Hmm, could you show us the contents of "rt" and "ln" at this point? If possible, it would be helpful to see if the chain of llinfo starting at llinfo_nd6, too. And I'd also like to know the result of % netstat -rn -M corefile -N kernel_binary Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 7:25:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4FFB637B401 for ; Mon, 16 Jul 2001 07:25:44 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Jul 2001 15:25:28 +0100 (BST) To: freebsd-net@FreeBSD.ORG Cc: Bernd Walter , Hajimu UMEMOTO Subject: Re: how to get AF_LOCAL from getaddrinfo() In-Reply-To: Your message of "Sun, 15 Jul 2001 17:18:54 BST." <200107151718.aa17383@salmon.maths.tcd.ie> Date: Mon, 16 Jul 2001 15:25:25 +0100 From: Ian Dowse Message-ID: <200107161525.aa15954@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <200107151718.aa17383@salmon.maths.tcd.ie>, Ian Dowse writes: > >I'd very much like to see PF_LOCAL support added to our getaddrinfo() >and getnameinfo(). I know that PF_LOCAL sockets have semantics that Here is quick and simple implementation - any comments welcome. It probably needs a few changes to match the conventions of other implementations, and a mention of these conventions on the manpage. Ian Index: getaddrinfo.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/lib/libc/net/getaddrinfo.c,v retrieving revision 1.21 diff -u -r1.21 getaddrinfo.c --- getaddrinfo.c 2001/06/10 20:25:23 1.21 +++ getaddrinfo.c 2001/07/16 14:20:42 @@ -87,6 +87,7 @@ #include #include #include +#include #include #include #include @@ -143,13 +144,19 @@ offsetof(struct sockaddr_in6, sin6_addr), in6_addrany, in6_loopback, 1}, #define N_INET 1 +#define N_LOCAL 2 #else #define N_INET 0 +#define N_LOCAL 1 #endif {PF_INET, sizeof(struct in_addr), sizeof(struct sockaddr_in), offsetof(struct sockaddr_in, sin_addr), in_addrany, in_loopback, 0}, + {PF_LOCAL, sizeof(((struct sockaddr_un *)0)->sun_path), + sizeof(struct sockaddr_un), + offsetof(struct sockaddr_un, sun_path), + NULL, NULL, 0}, {0, 0, 0, 0, NULL, NULL, 0}, }; @@ -165,9 +172,6 @@ }; static const struct explore explore[] = { -#if 0 - { PF_LOCAL, 0, ANY, ANY, NULL, 0x01 }, -#endif #ifdef INET6 { PF_INET6, SOCK_DGRAM, IPPROTO_UDP, "udp", 0x07 }, { PF_INET6, SOCK_STREAM, IPPROTO_TCP, "tcp", 0x07 }, @@ -223,6 +227,8 @@ const char *, struct addrinfo **)); static int explore_numeric_scope __P((const struct addrinfo *, const char *, const char *, struct addrinfo **)); +static int explore_local __P((const struct addrinfo *, const char *, + const char *, struct addrinfo **)); static int get_canonname __P((const struct addrinfo *, struct addrinfo *, const char *)); static struct addrinfo *get_ai __P((const struct addrinfo *, @@ -317,6 +323,8 @@ { if (ecode < 0 || ecode > EAI_MAX) ecode = EAI_MAX; + if (ecode == EAI_SYSTEM) + return strerror(errno); return ai_errlist[ecode]; } @@ -394,6 +402,10 @@ case PF_INET6: #endif break; + case PF_LOCAL: + if (hints->ai_protocol != 0) + ERR(EAI_BADHINTS); + break; default: ERR(EAI_FAMILY); } @@ -420,6 +432,17 @@ } /* + * PF_LOCAL addresses are handled specially. The protocol family + * must be set to PF_LOCAL in the hints. + */ + if (pai->ai_family == PF_LOCAL) { + error = explore_local(pai, hostname, servname, &cur->ai_next); + if (error) + goto free; + goto good; + } + + /* * post-2553: AI_ALL and AI_V4MAPPED are effective only against * AF_INET6 query. They needs to be ignored if specified in other * occassions. @@ -833,6 +856,56 @@ return error; #endif +} + +/* + * PF_LOCAL address + */ +static int +explore_local(pai, hostname, servname, res) + const struct addrinfo *pai; + const char *hostname; + const char *servname; + struct addrinfo **res; +{ + struct sockaddr_un sun; + const struct afd *afd; + struct addrinfo *ai; + int error; + + *res = NULL; + ai = NULL; + afd = &afdl[N_LOCAL]; + + if (pai->ai_flags & ~(AI_PASSIVE | AI_CANONNAME | AI_NUMERICHOST)) + ERR(EAI_BADFLAGS); + if (servname == NULL) + ERR(EAI_SERVICE); + if (strlen(servname) >= sizeof(sun.sun_path)) { + errno = ENAMETOOLONG; + ERR(EAI_SYSTEM); + } + memset(&sun, 0, sizeof(sun)); + strlcpy(sun.sun_path, servname, sizeof(sun.sun_path)); + GET_AI(ai, afd, sun.sun_path); + GET_CANONNAME(ai, "localhost"); + + /* + * XXX should we set ai->addrlen and sun_len to SUN_LEN(sun)? + * The kernel doesn't mind, but (broken) userland apps might + * either expect a NUL-terminated string when they bcopy + * ai->addrlen bytes from ai->addr, or else they might expect + * sun_len to be SUN_LEN(sun). + */ + + *res = ai; + return 0; + +free: +bad: + if (ai != NULL) + freeaddrinfo(ai); + return error; } static int Index: getnameinfo.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/lib/libc/net/getnameinfo.c,v retrieving revision 1.7 diff -u -r1.7 getnameinfo.c --- getnameinfo.c 2001/02/15 10:35:54 1.7 +++ getnameinfo.c 2001/07/16 00:50:38 @@ -44,6 +44,7 @@ #include #include +#include #include #include #include @@ -80,6 +81,8 @@ u_short si_port; }; +static int local_getnameinfo __P((const struct sockaddr *, + socklen_t, char *, size_t, char *, size_t, int)); #ifdef INET6 static int ip6_parsenumeric __P((const struct sockaddr *, const char *, char *, size_t, int)); @@ -119,6 +122,11 @@ if (sa == NULL) return ENI_NOSOCKET; + /* AF_LOCAL is treated differently to the rest. */ + if (sa->sa_family == AF_LOCAL) + return local_getnameinfo(sa, salen, host, hostlen, serv, + servlen, flags); + if (sa->sa_len != salen) return ENI_SALEN; @@ -282,6 +290,46 @@ } } } + return SUCCESS; +} + +static int +local_getnameinfo(sa, salen, host, hostlen, serv, servlen, flags) + const struct sockaddr *sa; + socklen_t salen; + char *host; + size_t hostlen; + char *serv; + size_t servlen; + int flags; +{ + struct sockaddr_un *sun; + char *p; + int pathlen; + + /* + * Allow the case of salen == sizeof(struct sockaddr_un) but + * sa->sa_len covering only to the end of the path. + */ + if (sa->sa_len <= offsetof(struct sockaddr_un, sun_path) || + salen < sa->sa_len || salen > sizeof(struct sockaddr_un)) + return ENI_SALEN; + sun = (struct sockaddr_un *)sa; + pathlen = sa->sa_len - offsetof(struct sockaddr_un, sun_path); + if ((p = memchr(sun->sun_path, '\0', pathlen)) != NULL) + pathlen = p - sun->sun_path; + + if (host != NULL) { + if (hostlen < strlen("localhost") + 1) + return ENI_MEMORY; + strlcpy(host, "localhost", hostlen); + } + if (serv != NULL) { + if (servlen < pathlen + 1) + return ENI_MEMORY; + snprintf(serv, servlen, "%.*s", pathlen, sun->sun_path); + } + return SUCCESS; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 8:20:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id C7D1237B407 for ; Mon, 16 Jul 2001 08:20:37 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id DC2D54B22; Tue, 17 Jul 2001 00:20:31 +0900 (JST) To: Ian Dowse Cc: freebsd-net@FreeBSD.ORG, Bernd Walter , Hajimu UMEMOTO In-reply-to: iedowse's message of Mon, 16 Jul 2001 15:25:25 +0100. <200107161525.aa15954@salmon.maths.tcd.ie> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: how to get AF_LOCAL from getaddrinfo() From: itojun@iijlab.net Date: Tue, 17 Jul 2001 00:20:31 +0900 Message-ID: <14350.995296831@itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>I'd very much like to see PF_LOCAL support added to our getaddrinfo() >>and getnameinfo(). I know that PF_LOCAL sockets have semantics that >Here is quick and simple implementation - any comments welcome. It >probably needs a few changes to match the conventions of other >implementations, and a mention of these conventions on the manpage. what is the main motive of your change? your change is correct in terms of address family independence, however, due to the impact of the change, i would really want you to be careful as hell. if i were you i won't go there. (i don't think i will bring the change back to kame tree, i don't want to affect other platforms) the change will break a lot of applications. specifically: - TCP-only clients, including ftp. (*) - daemons which usees AI_PASSIVE to open listeing sockets. they won't get broken, but they will have a AF_UNIX socket unwillingly opened for listening. (*) you can blame us (or whoever else) for not checking AF_INET/ AF_INET6 on getaddrinfo loop, but anyway, there are a lot of applications that does not. also, with AF_UNIX, {NI,AI}_NUMERIC{HOST,SERV} does not have proper interpretation. you will need to pick some interpretation (maybe you may want to follow what NRL did for linux glibc/NRL IPv6 stack) again, if i were you i won't go there. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 8:42:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 7C6F337B415 for ; Mon, 16 Jul 2001 08:42:08 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Jul 2001 16:41:44 +0100 (BST) To: itojun@iijlab.net Cc: freebsd-net@FreeBSD.ORG, Bernd Walter , Hajimu UMEMOTO Subject: Re: how to get AF_LOCAL from getaddrinfo() In-Reply-To: Your message of "Tue, 17 Jul 2001 00:20:31 +0900." <14350.995296831@itojun.org> Date: Mon, 16 Jul 2001 16:41:40 +0100 From: Ian Dowse Message-ID: <200107161641.aa27724@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <14350.995296831@itojun.org>, itojun@iijlab.net writes: > > the change will break a lot of applications. specifically: Thanks for your comments. I may not have explained this very well; the proposed change only takes effect when getaddrinfo() is given a `hints' structure with hints->ai_family set to PF_LOCAL. No existing applications have any reason to set hints->ai_family to PF_LOCAL, so they should not see any change in behaviour. I certainly do not intend to have any PF_LOCAL addresses returned by a wildcard match, nor even by something like getaddrinfo(NULL, "/tmp/sock", NULL, &ai) which might be considered "unambiguous". The semantics of PF_LOCAL addresses are just too different from INET/INET6, so I had purposefully arranged that PF_LOCAL addresses would only be returned when specifically asked for. Does that restriction make the proposal more reasonable? > also, with AF_UNIX, {NI,AI}_NUMERIC{HOST,SERV} does not have proper > interpretation. you will need to pick some interpretation (maybe > you may want to follow what NRL did for linux glibc/NRL IPv6 stack) The approach I took was to ignore these flags. There is no concept of numeric addresses for PF_LOCAL addresses, but applications setting *_NUMERIC* just wishing to avoid a DNS lookup shouldn't need to specifically avoid passing these flags in the PF_LOCAL case. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 8:45:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id B87AA37B406 for ; Mon, 16 Jul 2001 08:45:07 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f6GFj2h26014; Mon, 16 Jul 2001 11:45:02 -0400 (EDT) Message-ID: <00d201c10e0e$4720fdc0$0b2d2d0a@battleship> From: "Joseph Gleason" To: "Peter Pentchev" , References: <20010716152638.B52566@ringworld.oblivion.bg> Subject: Re: ICMP source quench - deprecated? Date: Mon, 16 Jul 2001 11:45:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Unless I am mistaken, ICMP source quench applies to any IP traffic, not just TCP. Also, ICMP source quench can be sent by intermediate routers. ----- Original Message ----- From: "Peter Pentchev" To: Sent: Monday, July 16, 2001 08:26 Subject: ICMP source quench - deprecated? > Hi, > > I just had a friend ask me a weird question about ICMP source quench > and its handling in various OS's. He proceeded to show me a part > of some version of the Linux kernel source, which processed a source > quench request properly, yet had a 'This is deprecated' comment > at the top. > > I had a quick look at src/sys/netinet/tcp_subr.c, and on FreeBSD 4.x > and -current, an ICMP source quench seems to provoke a proper downsizing > of the connection window. > > Is there any reason for ICMP source quench to be deprecated? > If so, what is it to be replaced with? Or are the TCP window scaling > algorithms smart enough to downsize the window quick enough in case of > a noticeable packet loss? (I guess they should be..) > > G'luck, > Peter > > -- > If I were you, who would be reading this sentence? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 8:52: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.39]) by hub.freebsd.org (Postfix) with SMTP id D497A37B409 for ; Mon, 16 Jul 2001 08:51:07 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 58036 invoked by uid 1000); 16 Jul 2001 15:55:16 -0000 Date: Mon, 16 Jul 2001 18:55:16 +0300 From: Peter Pentchev To: Joseph Gleason Cc: net@FreeBSD.ORG Subject: Re: ICMP source quench - deprecated? Message-ID: <20010716185516.F56285@ringworld.oblivion.bg> References: <20010716152638.B52566@ringworld.oblivion.bg> <00d201c10e0e$4720fdc0$0b2d2d0a@battleship> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00d201c10e0e$4720fdc0$0b2d2d0a@battleship>; from clash@tasam.com on Mon, Jul 16, 2001 at 11:45:02AM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I know; those were my reasons for lifting an eyebrow at the 'deprecated' comment in the Linux kernel source.. G'luck, Peter -- "yields falsehood, when appended to its quotation." yields falsehood, when appended to its quotation. On Mon, Jul 16, 2001 at 11:45:02AM -0400, Joseph Gleason wrote: > Unless I am mistaken, ICMP source quench applies to any IP traffic, not just > TCP. > > Also, ICMP source quench can be sent by intermediate routers. > > > > ----- Original Message ----- > From: "Peter Pentchev" > To: > Sent: Monday, July 16, 2001 08:26 > Subject: ICMP source quench - deprecated? > > > > Hi, > > > > I just had a friend ask me a weird question about ICMP source quench > > and its handling in various OS's. He proceeded to show me a part > > of some version of the Linux kernel source, which processed a source > > quench request properly, yet had a 'This is deprecated' comment > > at the top. > > > > I had a quick look at src/sys/netinet/tcp_subr.c, and on FreeBSD 4.x > > and -current, an ICMP source quench seems to provoke a proper downsizing > > of the connection window. > > > > Is there any reason for ICMP source quench to be deprecated? > > If so, what is it to be replaced with? Or are the TCP window scaling > > algorithms smart enough to downsize the window quick enough in case of > > a noticeable packet loss? (I guess they should be..) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 8:54:48 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id EDE0737B406 for ; Mon, 16 Jul 2001 08:54:36 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f6GFsRu34790; Mon, 16 Jul 2001 11:54:27 -0400 (EDT) (envelope-from wollman) Date: Mon, 16 Jul 2001 11:54:27 -0400 (EDT) From: Garrett Wollman Message-Id: <200107161554.f6GFsRu34790@khavrinen.lcs.mit.edu> To: Peter Pentchev Cc: net@FreeBSD.ORG Subject: ICMP source quench - deprecated? In-Reply-To: <20010716152638.B52566@ringworld.oblivion.bg> References: <20010716152638.B52566@ringworld.oblivion.bg> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > Is there any reason for ICMP source quench to be deprecated? There are a few problems with ICMP source quench: 1) If a sender-TCP actually pays attention to them, an attacker can substantially reduce TCP performance by forging them (a low-grade DoS attack). 2) Few if any routers legitimately generate the things (see #3). 3) The Internet community figured out a decade or more ago that the last thing one wants to do on an overloaded link is to generate even more traffic. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 8:57:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 1708237B40A for ; Mon, 16 Jul 2001 08:56:58 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 5F0544B21; Tue, 17 Jul 2001 00:56:55 +0900 (JST) To: Ian Dowse Cc: freebsd-net@FreeBSD.ORG, Bernd Walter , Hajimu UMEMOTO In-reply-to: iedowse's message of Mon, 16 Jul 2001 16:41:40 +0100. <200107161641.aa27724@salmon.maths.tcd.ie> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: how to get AF_LOCAL from getaddrinfo() From: itojun@iijlab.net Date: Tue, 17 Jul 2001 00:56:55 +0900 Message-ID: <14832.995299015@itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org i still am not getting your motive... do you have actual applications that use getaddrinfo/getnameinfo for AF_UNIX? >> the change will break a lot of applications. specifically: >Thanks for your comments. I may not have explained this very well; >the proposed change only takes effect when getaddrinfo() is given >a `hints' structure with hints->ai_family set to PF_LOCAL. No >existing applications have any reason to set hints->ai_family to >PF_LOCAL, so they should not see any change in behaviour. i'm sorry. i misread your patch about "explore" portion. but still - how many special case behavior do we want to put? there are a lot of other AFs... which item is included in AF_UNSPEC and which are not? if we want uniformity, we will break existing apps. if we don't want to break existing apps, we need to drop uniformity. it is a hard question to ask... itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 9: 9:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from nu.cuk.nu (nu.cuk.nu [212.30.95.50]) by hub.freebsd.org (Postfix) with ESMTP id 4316437B40B for ; Mon, 16 Jul 2001 09:09:22 -0700 (PDT) (envelope-from cuk@cuk.nu) Received: from localhost (localhost.nu.cuk.nu [127.0.0.1]) by nu.cuk.nu (Postfix) with ESMTP id C8FF91AB72 for ; Mon, 16 Jul 2001 18:09:31 +0200 (CEST) Received: from cuk.nu (iris.localnet [192.168.6.12]) by nu.cuk.nu (Postfix) with ESMTP id E63CE1AB71 for ; Mon, 16 Jul 2001 18:09:29 +0200 (CEST) Message-ID: <3B531168.8AE10F7@cuk.nu> Date: Mon, 16 Jul 2001 18:08:08 +0200 From: Marko Cuk X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Multi homed maschine Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello ! I have a few problems, because I'd like to merge two maschines because of small room and heating problems there. One maschine has its own link and other too. Now i'd like to merge them into one maschine with four ethernet cards. How can I do, that packets from one subnet/host will go through one outgoing link and packets from other subnet/host will go through NAT to the default gateway, wich will be the default gw for FreeBSD itself too? I am using ipfw and I have read lot of documentation and I still don't have enough idea, how to do it. With ipfw fwd, like at transparent proxy, or ? It is a kind of source routing, isn't it ? Please, help me. Many thanks to all. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 10:16:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id 16DED37B401; Mon, 16 Jul 2001 10:16:26 -0700 (PDT) (envelope-from bmah@employees.org) Received: from intruder.bmah.org ([24.176.204.87]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010716171624.SMFR17182.femail4.sdc1.sfba.home.com@intruder.bmah.org>; Mon, 16 Jul 2001 10:16:24 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.4/8.11.3) id f6GHGO207568; Mon, 16 Jul 2001 10:16:24 -0700 (PDT) (envelope-from bmah) Message-Id: <200107161716.f6GHGO207568@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: bmah@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> Comments: In-reply-to JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= message dated "Mon, 16 Jul 2001 22:47:07 +0900." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-1058769219P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 16 Jul 2001 10:16:23 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_-1058769219P Content-Type: text/plain; charset=us-ascii If memory serves me right, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI= ?= wrote: > Hmm, could you show us the contents of "rt" and "ln" at this point? (kgdb) print rt $1 = (struct rtentry *) 0x3 (kgdb) print ln $2 = (struct llinfo_nd6 *) 0x620000 > If possible, it would be helpful to see if the chain of llinfo > starting at llinfo_nd6, too. Typos filtered out...if this is supposed to be a circular linked list, I think I got it all. (kgdb) print llinfo_nd6 $3 = {ln_next = 0xc1422100, ln_prev = 0xc12d91e0, ln_rt = 0x0, ln_hold = 0x0, ln_asked = 0, ln_expire = 0, ln_state = 0, ln_router = 0, ln_byhint = 0} (kgdb) print *(llinfo_nd6.ln_next) $5 = {ln_next = 0xc1366900, ln_prev = 0xc0388ee0, ln_rt = 0xc15b0100, ln_hold = 0x0, ln_asked = 0, ln_expire = 995175630, ln_state = 2, ln_router = 1, ln_byhint = 0} (kgdb) print *(llinfo_nd6.ln_next)->ln_next $6 = {ln_next = 0xc1366b80, ln_prev = 0xc1422100, ln_rt = 0xc13a3c00, ln_hold = 0x0, ln_asked = 0, ln_expire = 0, ln_state = 1, ln_router = 0, ln_byhint = 0} (kgdb) print *(llinfo_nd6.ln_next)->ln_next->ln_next $7 = {ln_next = 0xc12d91e0, ln_prev = 0xc1366900, ln_rt = 0xc139d200, ln_hold = 0x0, ln_asked = 0, ln_expire = 0, ln_state = 1, ln_router = 0, ln_byhint = 0} (kgdb) print *(llinfo_nd6.ln_next)->ln_next->ln_next->ln_next $8 = {ln_next = 0xc0388ee0, ln_prev = 0xc1366b80, ln_rt = 0xc1308000, ln_hold = 0x0, ln_asked = 0, ln_expire = 0, ln_state = 1, ln_router = 0, ln_byhint = 0} (kgdb) print *(llinfo_nd6.ln_next)->ln_next->ln_next->ln_next->ln_next $9 = {ln_next = 0xc1422100, ln_prev = 0xc12d91e0, ln_rt = 0x0, ln_hold = 0x0, ln_asked = 0, ln_expire = 0, ln_state = 0, ln_router = 0, ln_byhint = 0} (kgdb) print *(llinfo_nd6.ln_next)->ln_next->ln_next->ln_next->ln_next->ln_next $10 = {ln_next = 0xc1366900, ln_prev = 0xc0388ee0, ln_rt = 0xc15b0100, ln_hold = 0x0, ln_asked = 0, ln_expire = 995175630, ln_state = 2, ln_router = 1, ln_byhint = 0} > And I'd also like to know the result of > % netstat -rn -M corefile -N kernel_binary intruder:bmah% sudo netstat -rn -M /var/crash/vmcore.1 -N /usr/obj/usr/src/sys/N IMITZ/kernel.debug Password: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.1.1 UGSc 2 0 dc0 127.0.0.1 127.0.0.1 UH 2 21435 lo0 192.168.1 link#1 UC 3 0 dc0 => 192.168.1.1 0:0:c0:cb:bd:f2 UHLW 5 17908 dc0 => 192.168.1.3 0:0:f8:10:7a:a2 UHLW 0 119004 lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSc lo0 => default fe80::200:c0ff:fecb:bdf2%dc0 UGc dc0 ::1 ::1 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRSc lo0 fe80::/10 ::1 UGRSc lo0 fe80::%dc0/64 link#1 UC dc0 fe80::200:f8ff:fe10:7aa2%dc0 0:0:f8:10:7a:a2 UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#3 UHL lo0 fec0::1:200:c0ff:fecb:bdf2 0:0:c0:cb:bd:f2 UHL dc0 fec0::1:200:f8ff:fe10:7aa2 0:0:f8:10:7a:a2 UHL lo0 ff01::/32 ::1 U lo0 ff02::/16 link#1 UCS dc0 ff02::%dc0/32 link#1 UC dc0 ff02::%lo0/32 ::1 UC lo0 Hope this helps...let me know if you need anything else. Thanks! Bruce. --==_Exmh_-1058769219P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7UyFn2MoxcVugUsMRAlqQAKDwh5Kz6+swyBMD3XjBBOukAeCi9gCgrJOW oOXPP7mcYNRXIyW38F9Fo44= =ct2M -----END PGP SIGNATURE----- --==_Exmh_-1058769219P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 10:43: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 1088737B406; Mon, 16 Jul 2001 10:42:57 -0700 (PDT) (envelope-from matt-l@pacbell.net) Received: from fire (1Cust227.tnt1.pasadena.ca.da.uu.net [63.28.226.227]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id KAA22920; Mon, 16 Jul 2001 10:42:55 -0700 (PDT) Message-ID: <001b01c10e1d$e1d4e1b0$6503c23f@XGforce.com> Reply-To: "matt" From: "matt" To: , Cc: "FreeBSD-ISP" Subject: router question Date: Mon, 16 Jul 2001 10:36:41 -0700 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Does anyone know if there's a inbound T1 line with RJ45 connector will work with my FreeBSD box without connecting to a CISCO router first? In another word, hook FreeBSD box directly to the T1's RJ45. Or i have to buy a CISCO router to have the T1 RJ45 connect to it, then from router to a switch, and then to FreeBSD? ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 10:45: 0 2001 Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 70A6537B403 for ; Mon, 16 Jul 2001 10:44:56 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Jul 2001 18:44:41 +0100 (BST) To: itojun@iijlab.net Cc: freebsd-net@FreeBSD.ORG, Bernd Walter , Hajimu UMEMOTO Subject: Re: how to get AF_LOCAL from getaddrinfo() In-Reply-To: Your message of "Tue, 17 Jul 2001 00:56:55 +0900." <14832.995299015@itojun.org> Date: Mon, 16 Jul 2001 18:44:39 +0100 From: Ian Dowse Message-ID: <200107161844.aa52089@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <14832.995299015@itojun.org>, itojun@iijlab.net writes: > i still am not getting your motive... do you have actual applications > that use getaddrinfo/getnameinfo for AF_UNIX? The main purpose is to allow code using AF_UNIX sockets to do so without having to deal with the internals of the sockaddr_un structure. This is particularly useful for programs such as telnet and rpcbind that already support multiple protocols, but they must deal with AF_UNIX sockets completely separately because getaddrinfo does not support it. They will still need to do the unlink() etc with getaddrinfo support, but at least the logic can still be based around storing sockaddrs in 'struct addrinfo' structures instead of having completely different data structures for the AF_UNIX case. For getnameinfo, the AF_UNIX case does not require any special handling by the application; the only question is what to return as the hostname. > but still - how many special case behavior do we want to put? > there are a lot of other AFs... which item is included in AF_UNSPEC > and which are not? if we want uniformity, we will break existing apps. > if we don't want to break existing apps, we need to drop uniformity. > it is a hard question to ask... I think only protocols where the resulting sockaddr can be passed directly to bind() or connect(), and that have an unambiguous way to specify the protocol via host/service, should be included in an AF_UNSPEC search. At the moment, that pretty much means just INET and INET6. This approach also appears in the protocols listed by /etc/netconfig which are used by TI-RPC; only udp4, udp6, tcp4, tcp6 are marked as "visable" protocols; the others are supported, but you have to explicitly ask for them. As to the other AF_* protocols, I don't think any of them are used as widely as AF_UNIX in FreeBSD. If support were to be added to getaddrinfo for some of the more obscure protocols, it could probably be #ifdef'd out by default. Another important reason to add this feature is for compatibility with other platforms' getaddrinfo() implementations. I just tried a random Linux box here, and it seems to have very similar behaviour to that implemented by my patch. There is also the general idea that the way to encourage people to use a "preferred" interface is to make it useful in as many situations as possible :-) Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 10:50:21 2001 Delivered-To: freebsd-net@freebsd.org Received: from zero.namba1.com (zero.namba1.com [64.75.169.20]) by hub.freebsd.org (Postfix) with ESMTP id 9811037B401; Mon, 16 Jul 2001 10:50:13 -0700 (PDT) (envelope-from aaron@namba1.com) Received: from [134.173.120.17] by zero.namba1.com (NTMail 5.02.0001/QC8568.34.ce8cdec7) with ESMTP id qiibaaaa for freebsd-hackers@freebsd.org; Mon, 16 Jul 2001 07:50:07 -1000 From: "Aaron Namba" To: "matt" , , Cc: "FreeBSD-ISP" Subject: RE: router question Date: Mon, 16 Jul 2001 10:49:44 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <001b01c10e1d$e1d4e1b0$6503c23f@XGforce.com> Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Depends of course on whether you need routing... -----Original Message----- From: owner-freebsd-isp@FreeBSD.ORG [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt Sent: Monday, July 16, 2001 10:37 AM To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org Cc: FreeBSD-ISP Subject: router question Does anyone know if there's a inbound T1 line with RJ45 connector will work with my FreeBSD box without connecting to a CISCO router first? In another word, hook FreeBSD box directly to the T1's RJ45. Or i have to buy a CISCO router to have the T1 RJ45 connect to it, then from router to a switch, and then to FreeBSD? ====================================== WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. ====================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 10:55:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 4DAA237B409 for ; Mon, 16 Jul 2001 10:55:18 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f6GHsph28697; Mon, 16 Jul 2001 13:55:03 -0400 (EDT) Message-ID: <000f01c10e20$713e86b0$0b2d2d0a@battleship> From: "Joseph Gleason" To: "matt" , References: <001b01c10e1d$e1d4e1b0$6503c23f@XGforce.com> Subject: Re: router question Date: Mon, 16 Jul 2001 13:54:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org It needs to goto something that can handle it like a Cisco router with approiate WAN options or a FreeBSD box with an appropriate card (search the mailing lists for info on those cards). ----- Original Message ----- From: "matt" To: ; Cc: "FreeBSD-ISP" Sent: Monday, July 16, 2001 13:36 Subject: router question > Does anyone know if there's a inbound T1 line with RJ45 > connector will work with my FreeBSD box without > connecting to a CISCO router first? In another word, > hook FreeBSD box directly to the T1's RJ45. > > Or i have to buy a CISCO router to have the T1 RJ45 > connect to it, then from router to a switch, and then to > FreeBSD? > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 10:56:24 2001 Delivered-To: freebsd-net@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 3A18237B401 for ; Mon, 16 Jul 2001 10:56:18 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f6GHuBh28732; Mon, 16 Jul 2001 13:56:12 -0400 (EDT) Message-ID: <001f01c10e20$99a16c80$0b2d2d0a@battleship> From: "Joseph Gleason" To: "Aaron Namba" , "matt" , References: Subject: Re: router question Date: Mon, 16 Jul 2001 13:56:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org With a Cisco or a FreeBSD box can do routing. ----- Original Message ----- From: "Aaron Namba" To: "matt" ; ; Cc: "FreeBSD-ISP" Sent: Monday, July 16, 2001 13:49 Subject: RE: router question > Depends of course on whether you need routing... > > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt > Sent: Monday, July 16, 2001 10:37 AM > To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org > Cc: FreeBSD-ISP > Subject: router question > > > Does anyone know if there's a inbound T1 line with RJ45 > connector will work with my FreeBSD box without > connecting to a CISCO router first? In another word, > hook FreeBSD box directly to the T1's RJ45. > > Or i have to buy a CISCO router to have the T1 RJ45 > connect to it, then from router to a switch, and then to > FreeBSD? > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 11: 1:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from skeezix.n0qds.org (skeezix.n0qds.org [204.246.69.106]) by hub.freebsd.org (Postfix) with ESMTP id 8F80837B406 for ; Mon, 16 Jul 2001 11:01:45 -0700 (PDT) (envelope-from gregp@n0qds.org) Received: by skeezix.n0qds.org (Postfix, from userid 501) id CA017C9; Mon, 16 Jul 2001 13:01:35 -0500 (CDT) Date: Mon, 16 Jul 2001 13:01:35 -0500 From: Greg Putrich To: matt Cc: freebsd-net@FreeBSD.ORG Subject: Re: router question Message-ID: <20010716130135.A3137@skeezix.n0qds.org> References: <001b01c10e1d$e1d4e1b0$6503c23f@XGforce.com> <000f01c10e20$713e86b0$0b2d2d0a@battleship> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000f01c10e20$713e86b0$0b2d2d0a@battleship>; from clash@tasam.com on Mon, Jul 16, 2001 at 01:54:50PM -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matt- You'll need to get a DSU/CSU for the FreeBSD box. Not sure what exists out there, if anything. I'd start with the FreeBSD supported hardware list and see if there's anything there. As far as routing goes, you'll have no problem there. Joseph Gleason said: > It needs to goto something that can handle it like a Cisco router with > approiate WAN options or a FreeBSD box with an appropriate card (search the > mailing lists for info on those cards). > > > > ----- Original Message ----- > From: "matt" > To: ; > Cc: "FreeBSD-ISP" > Sent: Monday, July 16, 2001 13:36 > Subject: router question > > > > Does anyone know if there's a inbound T1 line with RJ45 > > connector will work with my FreeBSD box without > > connecting to a CISCO router first? In another word, > > hook FreeBSD box directly to the T1's RJ45. > > > > Or i have to buy a CISCO router to have the T1 RJ45 > > connect to it, then from router to a switch, and then to > > FreeBSD? > > > > ====================================== > > WWW.XGFORCE.COM > > The Next Generation Load Balance and > > Fail Safe Server Clustering Software > > for the Internet. > > ====================================== > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- -------------------------------------------------------------------------- Greg Putrich - Internet: gregp@n0qds.org [sk] "I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered. My life is my own." - No. 6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 11:15:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail5.carolina.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id A60C037B403; Mon, 16 Jul 2001 11:15:24 -0700 (PDT) (envelope-from khayman@carolina.rr.com) Received: from carolina.rr.com ([168.215.135.201]) by mail5.carolina.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 16 Jul 2001 14:15:22 -0400 Message-ID: <3B532F3A.95B68A8E@carolina.rr.com> Date: Mon, 16 Jul 2001 14:15:22 -0400 From: khayman X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Aaron Namba Cc: matt , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, FreeBSD-ISP Subject: Re: router question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org also, just because it terminates in RJ45 (and are you sure it's rj45, or does the male connector just look like it) does not mean that it is ethernet. Our cisco 7200 series routers have cards in them with what looks like rj45 ports (female). They are actually rj48 (different pin-outs i think) and are integrated csu/dsu's that'll take that connector off a channelized t1. Its actually a serial interface. I would say in all likelihood, the answer to your question is "no". You need something that'll take the serial signal off the t1 and convert it to ethernet at layer2. Unless of course you have a csu/dsu in your fBSD box. hope this helps. Aaron Namba wrote: > > Depends of course on whether you need routing... > > -----Original Message----- > From: owner-freebsd-isp@FreeBSD.ORG > [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt > Sent: Monday, July 16, 2001 10:37 AM > To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org > Cc: FreeBSD-ISP > Subject: router question > > Does anyone know if there's a inbound T1 line with RJ45 > connector will work with my FreeBSD box without > connecting to a CISCO router first? In another word, > hook FreeBSD box directly to the T1's RJ45. > > Or i have to buy a CISCO router to have the T1 RJ45 > connect to it, then from router to a switch, and then to > FreeBSD? > > ====================================== > WWW.XGFORCE.COM > The Next Generation Load Balance and > Fail Safe Server Clustering Software > for the Internet. > ====================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 11:23:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-out1.apple.com (mail-out1.apple.com [17.254.0.52]) by hub.freebsd.org (Postfix) with ESMTP id 9525637B406; Mon, 16 Jul 2001 11:23:33 -0700 (PDT) (envelope-from rbraun@apple.com) Received: from apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id LAA11845; Mon, 16 Jul 2001 11:23:33 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by apple.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Mon, 16 Jul 2001 11:23:26 -0700 Received: from ibook (il0204a-dhcp65.apple.com [17.202.45.193]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id LAA01529; Mon, 16 Jul 2001 11:23:26 -0700 (PDT) Date: Mon, 16 Jul 2001 11:21:55 -0700 X-Mailer: Apple Mail (2.402) Mime-Version: 1.0 (Apple Message framework v402) Cc: Aaron Namba , matt , freebsd-hackers@freebsd.org, freebsd-net@freebsd.org, FreeBSD-ISP Message-Id: <7059E29D-7A17-11D5-B921-003065AD81C0@ibook.apple.com> Content-Transfer-Encoding: 7bit In-Reply-To: <3B532F3A.95B68A8E@carolina.rr.com> Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: router question From: Rob Braun To: khayman Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Several companies, one of which is LanMedia Corporation (LMC), sell PCI cards that handle T1s and include an integrated CSU/DSU. So, yes, you can terminate a T1 on your PC. Find one of these cards and you're all set. I believe FreeBSD already has a driver for the LMC cards. Rob On Monday, July 16, 2001, at 11:15 AM, khayman wrote: > also, just because it terminates in RJ45 (and are you sure it's rj45, or > does the male connector just look like it) does not mean that it is > ethernet. Our cisco 7200 series routers have cards in them with what > looks like rj45 ports (female). They are actually rj48 (different > pin-outs i think) and are integrated csu/dsu's that'll take that > connector off a channelized t1. Its actually a serial interface. > > I would say in all likelihood, the answer to your question is "no". You > need something that'll take the serial signal off the t1 and convert it > to ethernet at layer2. Unless of course you have a csu/dsu in your fBSD > box. > > hope this helps. > > Aaron Namba wrote: >> >> Depends of course on whether you need routing... >> >> -----Original Message----- >> From: owner-freebsd-isp@FreeBSD.ORG >> [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of matt >> Sent: Monday, July 16, 2001 10:37 AM >> To: freebsd-hackers@freebsd.org; freebsd-net@freebsd.org >> Cc: FreeBSD-ISP >> Subject: router question >> >> Does anyone know if there's a inbound T1 line with RJ45 >> connector will work with my FreeBSD box without >> connecting to a CISCO router first? In another word, >> hook FreeBSD box directly to the T1's RJ45. >> >> Or i have to buy a CISCO router to have the T1 RJ45 >> connect to it, then from router to a switch, and then to >> FreeBSD? >> >> ====================================== >> WWW.XGFORCE.COM >> The Next Generation Load Balance and >> Fail Safe Server Clustering Software >> for the Internet. >> ====================================== >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-isp" in the body of the message >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 11:27:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id CCB5C37B401 for ; Mon, 16 Jul 2001 11:27:24 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f6GIQwV95221; Mon, 16 Jul 2001 20:26:58 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f6GIRkM01339; Mon, 16 Jul 2001 20:27:46 +0200 (CEST) Date: Mon, 16 Jul 2001 20:27:46 +0200 From: Bernd Walter To: Ian Dowse Cc: itojun@iijlab.net, freebsd-net@FreeBSD.ORG, Bernd Walter , Hajimu UMEMOTO Subject: Re: how to get AF_LOCAL from getaddrinfo() Message-ID: <20010716202745.A1326@cicely20.cicely.de> References: <14832.995299015@itojun.org> <200107161844.aa52089@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107161844.aa52089@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Mon, Jul 16, 2001 at 06:44:39PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jul 16, 2001 at 06:44:39PM +0100, Ian Dowse wrote: > In message <14832.995299015@itojun.org>, itojun@iijlab.net writes: > Another important reason to add this feature is for compatibility > with other platforms' getaddrinfo() implementations. I just tried > a random Linux box here, and it seems to have very similar behaviour > to that implemented by my patch. There is also the general idea > that the way to encourage people to use a "preferred" interface is > to make it useful in as many situations as possible :-) The libbind shipped with bind does so. The getaddrinfo described by W. Richard Stevens in Unix Networkprogramming Vol1 describes it for Unix domain sockets In the later case its also for AF_UNSPEC if the host begins with '/' But on the other side I never saw getnameinfo with support for it. Solaris and NetBSD doesn't support it - so your Linux example seems to be very alone (maybe they are using plain bind implementation). I primarily asked for it because I found it in contrib/bind and asumed it to be implemented. Applications usualy have to deal with it thereself anyway especialy if they need to be portable and filling a sockaddr_un is by far the easiest kind of socket tasks to do. getaddrinfo is realy usefull if you have a FQDN or IPv4/6 ASCII address which which are difficult to differenciate and which may have multiple A and AAAA records to try. So I don't know if it's even usefull to have unix domain sockets in getaddrinfo. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 11:51:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from citi.umich.edu (citi.umich.edu [141.211.92.141]) by hub.freebsd.org (Postfix) with ESMTP id 4C4C737B401 for ; Mon, 16 Jul 2001 11:51:36 -0700 (PDT) (envelope-from provos@citi.umich.edu) Received: from citi.umich.edu (ssh-mapper.citi.umich.edu [141.211.92.147]) by citi.umich.edu (Postfix) with ESMTP id B314F207C1; Mon, 16 Jul 2001 14:51:35 -0400 (EDT) Subject: Re: TCP ISN algorithm breaks TIME_WAIT (Re: select fails to return incoming connect on FreeBSD-4.3) To: Kris Kennaway Cc: Jonathan Lemon , gjohnson@srrc.ars.usda.gov, net@freebsd.org From: Niels Provos In-Reply-To: Kris Kennaway, Sun, 15 Jul 2001 13:11:48 PDT Date: Mon, 16 Jul 2001 14:51:35 -0400 Message-Id: <20010716185135.B314F207C1@citi.umich.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In message <20010715131148.A10745@xor.obsecurity.org>, Kris Kennaway writes: >Sorry I've been ignoring this; I'm still getting caught up from my >vacation. Niels, how has OpenBSD handled this? Not. We have the same problem. I argue that the test is bogus. First of all, if we are getting a SYN for this 4-tuple, it is very likely that all segments from the old connection have left the network. The current code does not deal with wrap around either. On the other hand, there are already a number of operating systems that use randomized ISNs. Linux has been doing this for quite some time. As a result, we can not rely on monotonely increasing ISNs anyway. Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 12: 1:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from buug.homeip.net (we-66-27-250-19.we.mediaone.net [66.27.250.19]) by hub.freebsd.org (Postfix) with ESMTP id EAC0837B405; Mon, 16 Jul 2001 12:01:50 -0700 (PDT) (envelope-from bear@buug.homeip.net) Received: from localhost (localhost [127.0.0.1]) by buug.homeip.net (8.11.4/8.11.4) with ESMTP id f6GJ1n580437; Mon, 16 Jul 2001 12:01:49 -0700 (PDT) (envelope-from bear@buug.homeip.net) Date: Mon, 16 Jul 2001 12:01:49 -0700 (PDT) From: Joey Garcia X-X-Sender: To: , Subject: Help needed with setting up routing Message-ID: <20010716115150.H80369-100000@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello all! Okay, I'm still having a bit of problems setting up a FreeBSD router. I'm not sure if FreeBSD forwards the packets automatically or if I need to add routes to the routing table or what. Here's what I'm trying to do. I have 3 networks: 192.168.0.0/24, 192.168.10.0/24, and 192.168.20/29. I have one FreeBSD box with one interface having these addresses: 192.168.0.8, 192.168.10.100, and 192.168.20.1 (with corresponsing netmasks stated above). I also have clients on each of the networks. If I were to draw it out, I guess it would looke a bit like this: ---------- 192.168.0.8/24 | bsd | 192.168.10.100/24 ---------- 192.168.20.1/29 | | --------------------------------------- | | | | | | ----- ----- ----- |PC1| |PC2| |PC3| ----- ----- ----- 192.168.0.50/25 192.168.10.200/24 192.168.20.50/29 Granted, this is a very simple view. There are hubs thrown in there, and there also is another router that routes 192.168.0.0/24 to the internet. At this time I just wanted to get these 3 subnets talking then I'll experiment with getting them going out on the Internet. So basically, I'd like to get those machines talking to each other. So far, I can make PC1 ping all the IP addresses on the router, but I can't get it to ping PC2 or PC3 (and vice-versa). I have read through the Handbook, at it seems what I'm trying to do here is called a multi-homed host. Althouh, there wasn't much of an explanation how to accomplish on what I'd like to do. I have also read through the manpage for route and came across something concerning if the destination is directly reachable (I guess that means there are no hops in between), then I use the -interface modifier. I'm not quite sure on how to properly use the route add command with the -interface modifier. Some assistance would be appreciated. (Then again, that's probably not what I need to do in this case) I'm really inexperienced when it comes to routing. The only routes I've ever fiddled with was 'route add default ipaddress' when it came to setting up my Internet connectivity. I guess I should now provide the mandatory ifconfig and netstat -rn information for my machine. Here it is: ifconfig: tl0: flags=8843 mtu 1500 inet6 fe80::280:5fff:feb6:3731%tl0 prefixlen 64 scopeid 0x1 inet 192.168.0.8 netmask 0xffffff00 broadcast 192.168.0.255 inet 192.168.20.1 netmask 0xfffffff8 broadcast 192.168.20.7 inet 192.168.10.100 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:80:5f:b6:37:31 media: autoselect (10baseT/UTP) status: active netstat -rn: Internet: Destination Gateway Flags Refs Use Netif Expire 127.0.0.1 127.0.0.1 UH 0 94 lo0 192.168 link#1 UC 0 0 tl0 => 192.168.10 link#1 UC 0 0 tl0 => 192.168.20/29 link#1 UC 0 0 tl0 => Okay, not sure what other peices of information I can help out with but I have set net.inet.ip.forwarding to 1 and I'm not running routed (do I need to?). From reading the manual page I gathered that the routes are directly reachable because all 3 networks lie on the same interface. Therefore, I believe I need to use the -iface modifier. I have tried commands such as this with no luck: route add -net 192.168.10.0 -iface (and other combinations) I'd really appreciate any help. I guess I need some pointers on how to properly use the route command as well as how to properly route to 3 different networks on the same interace. TIA, Joey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 12: 6:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from fasterix.frmug.org (d211.dhcp212-198-74.noos.fr [212.198.74.211]) by hub.freebsd.org (Postfix) with ESMTP id B45DA37B403 for ; Mon, 16 Jul 2001 12:06:39 -0700 (PDT) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.11.3/8.9.3/pb-19990315) id f6GJ6bD18939; Mon, 16 Jul 2001 21:06:37 +0200 (CEST) Message-ID: <20010716210637.A18624@fasterix.frmug.org> Date: Mon, 16 Jul 2001 21:06:37 +0200 From: Pierre Beyssac To: freebsd-net@freebsd.org Cc: traceroute@ee.lbl.gov Subject: fix for traceroute (bin/29026) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.8i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Could anyone check this fix for PR bin/29026 (traceroute -s option)? It just reenables the bind(2) call checking for the source address correctness, and moves the IP_HDRINCL after that (once IP_HDRINCL is enabled on the socket, bind doesn't check this anymore). It seems to work on my (very outdated) current as well as -stable, but I'm not able to check it on a recent -current, and although I have tested it with and without -s I may have missed some side effects with weird options combinations. If someone can confirm that this works, I can commit it. Index: traceroute.c =================================================================== RCS file: /home/ncvs/src/contrib/traceroute/traceroute.c,v retrieving revision 1.18 diff -u -r1.18 traceroute.c --- traceroute.c 2001/06/06 16:12:59 1.18 +++ traceroute.c 2001/07/16 18:53:44 @@ -727,13 +727,6 @@ exit(1); } #endif -#ifdef IP_HDRINCL - if (setsockopt(sndsock, IPPROTO_IP, IP_HDRINCL, (char *)&on, - sizeof(on)) < 0) { - Fprintf(stderr, "%s: IP_HDRINCL: %s\n", prog, strerror(errno)); - exit(1); - } -#endif if (options & SO_DEBUG) (void)setsockopt(sndsock, SOL_SOCKET, SO_DEBUG, (char *)&on, sizeof(on)); @@ -744,14 +737,19 @@ if (source != NULL) { source = savestr(getsin(&from, source)); outip->ip_src = from.sin_addr; -#ifndef IP_HDRINCL if (bind(sndsock, (struct sockaddr *)&from, sizeof(from)) < 0) { Fprintf(stderr, "%s: bind: %s\n", prog, strerror(errno)); exit (1); } -#endif } +#ifdef IP_HDRINCL + if (setsockopt(sndsock, IPPROTO_IP, IP_HDRINCL, (char *)&on, + sizeof(on)) < 0) { + Fprintf(stderr, "%s: IP_HDRINCL: %s\n", prog, strerror(errno)); + exit(1); + } +#endif #if defined(IPSEC) && defined(IPSEC_POLICY_IPSEC) if (setpolicy(sndsock, "in bypass") < 0) -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org Why write portable code when you can write Linux code? Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 12:16:49 2001 Delivered-To: freebsd-net@freebsd.org Received: from web10602.mail.yahoo.com (web10602.mail.yahoo.com [216.136.130.166]) by hub.freebsd.org (Postfix) with SMTP id 328EC37B401 for ; Mon, 16 Jul 2001 12:16:46 -0700 (PDT) (envelope-from danny_j_mitzel@yahoo.com) Message-ID: <20010716191646.9105.qmail@web10602.mail.yahoo.com> Received: from [63.99.114.2] by web10602.mail.yahoo.com via HTTP; Mon, 16 Jul 2001 12:16:46 PDT Date: Mon, 16 Jul 2001 12:16:46 -0700 (PDT) From: danny mitzel Subject: Re: ICMP source quench - deprecated? To: Peter Pentchev , net@FreeBSD.ORG In-Reply-To: <20010716152638.B52566@ringworld.oblivion.bg> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org RFC1812 Requirements for IP Version 4 Routers 4.3.3.3 Source Quench A router SHOULD NOT originate ICMP Source Quench messages. As specified in Section [4.3.2], a router that does originate Source Quench messages MUST be able to limit the rate at which they are generated. DISCUSSION Research seems to suggest that Source Quench consumes network bandwidth but is an ineffective (and unfair) antidote to congestion. See, for example, [INTERNET:9] and [INTERNET:10]. Section [5.3.6] discusses the current thinking on how routers ought to deal with overload and network congestion. A router MAY ignore any ICMP Source Quench messages it receives. DISCUSSION A router itself may receive a Source Quench as the result of originating a packet sent to another router or host. Such datagrams might be, e.g., an EGP update sent to another router, or a telnet stream sent to a host. A mechanism has been proposed ([INTERNET:11], [INTERNET:12]) to make the IP layer respond directly to Source Quench by controlling the rate at which packets are sent, however, this proposal is currently experimental and not currently recommended. __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 13: 2:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from kawoserv.kawo2.rwth-aachen.de (kawoserv.kawo2.RWTH-Aachen.DE [134.130.180.1]) by hub.freebsd.org (Postfix) with ESMTP id BA43637B405 for ; Mon, 16 Jul 2001 13:02:19 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from zerogravity.kawo2.rwth-aachen.de (zerogravity.kawo2.rwth-aachen.de [134.130.181.28]) by kawoserv.kawo2.rwth-aachen.de (8.9.3/8.9.3) with ESMTP id WAA00976 for ; Mon, 16 Jul 2001 22:02:18 +0200 Received: by zerogravity.kawo2.rwth-aachen.de (Postfix, from userid 1001) id 27C3E14DAB; Mon, 16 Jul 2001 22:02:18 +0200 (CEST) Date: Mon, 16 Jul 2001 22:02:18 +0200 From: Alexander Langer To: freebsd-net@FreeBSD.org Subject: IP accounting/filtering for bigger setups Message-ID: <20010716220218.A7652@zerogravity.kawo2.rwth-aachen.d> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! We have to account the traffic of >450 IPs and also have to deny traffic to/from a few IPs. We are currently using a half-baken solution with ipfw and a config with 6 rules for each IP, which makes the stuff quite uncomfortable. (on high network load, "ipfw list" takes minutes, we have to check 6 rules for each IP, ...) We are now searching for other solutions and I wondered, if one could recommend them. I'd prefer something, that automatically accounts the traffic for all routed IPs (and, if possible, with some exceptions, e.g. only traffic, that leaves a certain subnet), and can also still deny some traffic. Anyone has some suggestions for us? Thanks Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 13:55:23 2001 Delivered-To: freebsd-net@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 548B037B401 for ; Mon, 16 Jul 2001 13:55:17 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id WAA50504; Mon, 16 Jul 2001 22:49:16 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200107162049.WAA50504@info.iet.unipi.it> Subject: Re: IP accounting/filtering for bigger setups In-Reply-To: <20010716220218.A7652@zerogravity.kawo2.rwth-aachen.d> from Alexander Langer at "Jul 16, 2001 10:02:18 pm" To: Alexander Langer Date: Mon, 16 Jul 2001 22:49:16 +0200 (CEST) Cc: freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org for accounting, you can use dynamic dummynet pipes as the final accept rule, e.g. replace all rules of the form accept ip from X to Y with pipe 9999 ip from X to Y and something like this for accounting on source ip ipfw pipe 9999 config mask src-ip 0xffffffff For managing the separate IPs, it really depends a lot on the actions you need to perform, e.g. you might be able to define a few classes of hosts and have rulesets for them, and then jump to the appropriate ruleset for each host depending on the IP, maybe using masks whenever possible to reduce the actual number of rules. of course if performance is an issue you might want to develop some special 'lookup' ipfw rule by modifying the ipfw kernel code. cheers luigi > Hi! > > We have to account the traffic of >450 IPs and also have to deny > traffic to/from a few IPs. > > We are currently using a half-baken solution with ipfw and a > config with 6 rules for each IP, which makes the stuff quite > uncomfortable. > (on high network load, "ipfw list" takes minutes, we have to check > 6 rules for each IP, ...) > > We are now searching for other solutions and I wondered, if one could > recommend them. > > I'd prefer something, that automatically accounts the traffic > for all routed IPs (and, if possible, with some exceptions, e.g. > only traffic, that leaves a certain subnet), and can also still deny > some traffic. > > Anyone has some suggestions for us? > > Thanks > > Alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 14:27:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from area51.vail (chrobd01.vailsys.com [63.210.102.138]) by hub.freebsd.org (Postfix) with ESMTP id 475E137B401 for ; Mon, 16 Jul 2001 14:27:47 -0700 (PDT) (envelope-from hal@vailsys.com) Received: from ghidra.vail (ghidra.vail [192.168.129.44]) by area51.vail (8.9.3/8.9.3) with ESMTP id QAA05088 for ; Mon, 16 Jul 2001 16:27:46 -0500 (CDT) (envelope-from hal@vailsys.com) Received: by ghidra.vail (Postfix, from userid 1000) id B045766ABB; Mon, 16 Jul 2001 16:27:46 -0500 (CDT) To: freebsd-net@freebsd.org Subject: Re: router question References: <7059E29D-7A17-11D5-B921-003065AD81C0@ibook.apple.com> From: Hal Snyder Date: 16 Jul 2001 16:27:46 -0500 In-Reply-To: <7059E29D-7A17-11D5-B921-003065AD81C0@ibook.apple.com> Message-ID: <874rscd0od.fsf@ghidra.vail> Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Canyonlands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Rob Braun writes: > Several companies, one of which is LanMedia Corporation (LMC), sell > PCI cards that handle T1s and include an integrated CSU/DSU. So, > yes, you can terminate a T1 on your PC. Find one of these cards and > you're all set. I believe FreeBSD already has a driver for the LMC > cards. LanMedia was bought by SBE (sbei.com). They make a T1 card (wanadapt-1E1T1, used to be LMC1200P) with built-in CSU/DSU so you can plug a in a raw T1. I am in process of merging their current driver into FreeBSD-current. OpenBSD and NetBSD support the card in Cisco-HDLC mode - no frame, no sync PPP, no E1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 14:44:46 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail.guest-tek.com (mail.guesttek.com [139.142.1.74]) by hub.freebsd.org (Postfix) with ESMTP id 0F85737B406 for ; Mon, 16 Jul 2001 14:44:42 -0700 (PDT) (envelope-from peter@guest-tek.com) Received: from localhost ([139.142.135.115]) by mail.guest-tek.com (8.9.3/8.8.7) with ESMTP id PAA27335 for ; Mon, 16 Jul 2001 15:41:46 -0600 Message-Id: <200107162141.PAA27335@mail.guest-tek.com> Date: Mon, 16 Jul 2001 15:44:40 -0600 Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v388) From: Peter Warrick To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.388) Content-Transfer-Encoding: 7bit Subject: Routing. :) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I hope I am not sending to the wrong address but here goes. :) I need to be able to alias an IP and route to another IP. For example.. I have a computer behind my BSD server with an IP of 1.2.3.4 and it requires a gateway IP of 1.2.3.1. So I simply issue an ifconfig en1 1.2.3.1 alias. But this results in the entire 1.x.x.x subnet to become a part of my server's network. I've been able to do this in Redhat Linux where I alias the gateway and then route the second address (1.2.3.4) with a gateway of 0.0.0.0 and a netmask of 255.255.255.255 on the en1 (or for linux the eth1) network. This results in just the 1.2.3.1 and 1.2.3.4 IPs existing on my network and it will still go out to 1.4.5.3 (just a random example IP) on the internet through en0 (If I have natd enabled). To give you an idea of what my Redhat Linux calls are to make this work.. They are.. ifconfig eth1:0 1.2.3.1 netmask 255.255.255.255 route add -host 1.2.3.4 dev eth1:0 In BSD the closest thing I have tried to this is... ifconfig en1 1.2.3.1 netmask 255.255.255.255 broadcast 1.255.255.255 alias route add -host 1.2.3.4 -interface en1 I added the broadcast to the ifconfig line in BSD because I noticed in linux my broadcast was 1.255.255.255 by default and BSD wasn't doing this. I hope this makes a little sense but in summary I wish to just bring 2 IPs into my network and route them so they can talk to each other without having to bring the entire subnet on to my network. Thanks for any help.. I've been struggling with this for the past week without success. Its frustrating that I know how to do it on Linux but not BSD. :( Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 15: 0:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 0742F37B405 for ; Mon, 16 Jul 2001 15:00:50 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f6GM0kh32704; Mon, 16 Jul 2001 18:00:46 -0400 (EDT) Message-ID: <000901c10e42$c507fcf0$0b2d2d0a@battleship> From: "Joseph Gleason" To: "Peter Warrick" , References: <200107162141.PAA27335@mail.guest-tek.com> Subject: Re: Routing. :) Date: Mon, 16 Jul 2001 18:00:46 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This very much sounds like you need to learn IP subnetting. I highly recommend the Cisco Press CCNA book. I can dig up ISBN number if you want. There are very few cases that call for a subnet mask of 255.255.255.255. You probably want 255.255.255.0 You can specify the subnetmask on the command line: ifconfig xyz0 alias 1.2.3.1 netmask 255.255.255.0 IP subnetting and routing is in my mind one of those things you can't just pick up. You really need some training or reading some text in addition to hands on experience to really know what is going on. ----- Original Message ----- From: "Peter Warrick" To: Sent: Monday, July 16, 2001 17:44 Subject: Routing. :) > I hope I am not sending to the wrong address but here goes. :) > > I need to be able to alias an IP and route to another IP. For example.. > I have a computer behind my BSD server with an IP of 1.2.3.4 and it > requires a gateway IP of 1.2.3.1. So I simply issue an ifconfig en1 > 1.2.3.1 alias. But this results in the entire 1.x.x.x subnet to become a > part of my server's network. > > I've been able to do this in Redhat Linux where I alias the gateway and > then route the second address (1.2.3.4) with a gateway of 0.0.0.0 and a > netmask of 255.255.255.255 on the en1 (or for linux the eth1) network. > This results in just the 1.2.3.1 and 1.2.3.4 IPs existing on my network > and it will still go out to 1.4.5.3 (just a random example IP) on the > internet through en0 (If I have natd enabled). > > To give you an idea of what my Redhat Linux calls are to make this > work.. They are.. > > ifconfig eth1:0 1.2.3.1 netmask 255.255.255.255 > route add -host 1.2.3.4 dev eth1:0 > > In BSD the closest thing I have tried to this is... > > ifconfig en1 1.2.3.1 netmask 255.255.255.255 broadcast 1.255.255.255 > alias > route add -host 1.2.3.4 -interface en1 > > I added the broadcast to the ifconfig line in BSD because I noticed in > linux my broadcast was 1.255.255.255 by default and BSD wasn't doing > this. > > I hope this makes a little sense but in summary I wish to just bring 2 > IPs into my network and route them so they can talk to each other > without having to bring the entire subnet on to my network. > > Thanks for any help.. I've been struggling with this for the past week > without success. Its frustrating that I know how to do it on Linux but > not BSD. :( > > Pete > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 15: 6:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 0B67437B401 for ; Mon, 16 Jul 2001 15:06:42 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id D4B7A81D07; Mon, 16 Jul 2001 17:06:31 -0500 (CDT) Date: Mon, 16 Jul 2001 17:06:31 -0500 From: Bill Fumerola To: Peter Warrick Cc: freebsd-net@freebsd.org Subject: Re: Routing. :) Message-ID: <20010716170631.O2759@elvis.mu.org> References: <200107162141.PAA27335@mail.guest-tek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107162141.PAA27335@mail.guest-tek.com>; from peter@guest-tek.com on Mon, Jul 16, 2001 at 03:44:40PM -0600 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Jul 16, 2001 at 03:44:40PM -0600, Peter Warrick wrote: > I hope I am not sending to the wrong address but here goes. :) you are. this should have been sent to freebsd-questions, but: from ifconfig(8): alias Establish an additional network address for this interface. This is sometimes useful when changing network numbers, and one wishes to accept packets addressed to the old interface. If the address is on the same subnet as the first network address for this in- terface, a netmask of 0xffffffff has to be specified. examples: # ifconfig fxp0 10.1.1.1 netmask 255.255.255.0 # ifconfig fxp0 10.1.1.2 netmask 255.255.255.255 alias # on the same subnet # ifconfig fxp0 10.1.2.1 netmask 255.255.255.0 alias # not on the same subnet -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 17:17:58 2001 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 683E737B407 for ; Mon, 16 Jul 2001 17:17:54 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 74472 invoked by uid 1000); 17 Jul 2001 00:17:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jul 2001 00:17:51 -0000 Date: Mon, 16 Jul 2001 19:17:51 -0500 (CDT) From: Mike Silbersack To: Niels Provos Cc: Kris Kennaway , Jonathan Lemon , , Subject: Re: TCP ISN algorithm breaks TIME_WAIT (Re: select fails to return incoming connect on FreeBSD-4.3) In-Reply-To: <20010716185135.B314F207C1@citi.umich.edu> Message-ID: <20010716191121.B74348-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 16 Jul 2001, Niels Provos wrote: > In message <20010715131148.A10745@xor.obsecurity.org>, Kris Kennaway writes: > >Sorry I've been ignoring this; I'm still getting caught up from my > >vacation. Niels, how has OpenBSD handled this? > Not. We have the same problem. I argue that the test is bogus. > > First of all, if we are getting a SYN for this 4-tuple, it is very > likely that all segments from the old connection have left the > network. > > The current code does not deal with wrap around either. The test may be bogus, but it must be respected. Every old BSD based system out there has it, and we can't update every system because we no longer like it. We should still be fine sending out randomized ISNs in SYNACKs; it appears to be SYNs sent out by us which must be monotonic. > On the other hand, there are already a number of operating systems > that use randomized ISNs. Linux has been doing this for quite some > time. As a result, we can not rely on monotonely increasing ISNs > anyway. I just looked at a copy of 2.4.1, and it appears to use a RFC1948-like algorithm. I think 2.0 was randomized, but more recent versions have not been. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 20:17:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id D371B37B641; Mon, 16 Jul 2001 20:14:59 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:4819:2000:c59e:339e:1140:d7ab]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id MAA19519; Tue, 17 Jul 2001 12:16:52 +0900 (JST) Date: Tue, 17 Jul 2001 12:14:57 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: bmah@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: <200107161716.f6GHGO207568@intruder.bmah.org> References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> <200107161716.f6GHGO207568@intruder.bmah.org> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 48 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Mon, 16 Jul 2001 10:16:23 -0700, >>>>> bmah@FreeBSD.ORG (Bruce A. Mah) said: >> Hmm, could you show us the contents of "rt" and "ln" at this point? > (kgdb) print rt > $1 = (struct rtentry *) 0x3 > (kgdb) print ln > $2 = (struct llinfo_nd6 *) 0x620000 Then rt and ln are surely broken. I have not got the reason yet, though... >> If possible, it would be helpful to see if the chain of llinfo >> starting at llinfo_nd6, too. > Typos filtered out...if this is supposed to be a circular linked list, > I think I got it all. Yes, the list seems okay. >> And I'd also like to know the result of >> % netstat -rn -M corefile -N kernel_binary > intruder:bmah% sudo netstat -rn -M /var/crash/vmcore.1 -N /usr/obj/usr/src/sys/N (snip) > Hope this helps...let me know if you need anything else. Thanks, then could you try the following command? intruder:bmah% sudo netstat -rna -M /var/crash/vmcore.1 -N /usr/obj/usr/src/sys/N (i.e. add a new option "-a" to netstat.) Also, please tell us the result of % ndp -an under your normal environment (after doing some IPv6 communication). Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 20:44:53 2001 Delivered-To: freebsd-net@freebsd.org Received: from imf10bis.bellsouth.net (mail110.mail.bellsouth.net [205.152.58.50]) by hub.freebsd.org (Postfix) with ESMTP id E94A837B403 for ; Mon, 16 Jul 2001 20:44:49 -0700 (PDT) (envelope-from jmurdock@itraktech.com) Received: from dc12 ([208.61.64.205]) by imf10bis.bellsouth.net (InterMail vM.5.01.01.01 201-252-104) with SMTP id <20010717034542.BBPL16224.imf10bis.bellsouth.net@dc12> for ; Mon, 16 Jul 2001 23:45:42 -0400 Message-ID: <004b01c10e72$d40766c0$0201a8c0@bellsouth.net> From: "Jerry Murdock" To: Subject: ipfw Bridge vs M$ FTP client Date: Mon, 16 Jul 2001 23:44:19 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2479.0006 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Is there any magic to get an active FTP client (M$ in this case) behind the inside interface to talk to an outside FTP server? (Without opening a huge hole.) This is on 4.3-STABLE. Alternatively, does anyone know if an OpenBSD/IPF bridge could/would handle it any better? Thanks, Jerry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 20:55:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id 556D637B405; Mon, 16 Jul 2001 20:55:12 -0700 (PDT) (envelope-from bmah@employees.org) Received: from intruder.bmah.org ([24.176.204.87]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010717035511.EUW14393.femail1.sdc1.sfba.home.com@intruder.bmah.org>; Mon, 16 Jul 2001 20:55:11 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.4/8.11.3) id f6H3tBG13515; Mon, 16 Jul 2001 20:55:11 -0700 (PDT) (envelope-from bmah) Message-Id: <200107170355.f6H3tBG13515@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: bmah@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> <200107161716.f6GHGO207568@intruder.bmah.org> Comments: In-reply-to JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= message dated "Tue, 17 Jul 2001 12:14:57 +0900." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-641166680P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 16 Jul 2001 20:55:11 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_-641166680P Content-Type: text/plain; charset=us-ascii If memory serves me right, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI= ?= wrote: > >>>>> On Mon, 16 Jul 2001 10:16:23 -0700, > >>>>> bmah@FreeBSD.ORG (Bruce A. Mah) said: > > (kgdb) print rt > > $1 = (struct rtentry *) 0x3 > > (kgdb) print ln > > $2 = (struct llinfo_nd6 *) 0x620000 > > Then rt and ln are surely broken. I have not got the reason yet, > though... Yes, rt in particular caught my eye. > Thanks, then could you try the following command? intruder:bmah% sudo netstat -rna -M /var/crash/vmcore.1 -N /usr/obj/usr/src/sys/NIMITZ/kernel.debug Password: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.1.1 UGSc 2 0 dc0 65.192.41.10 192.168.1.1 UGHW 1 61245 dc0 127.0.0.1 127.0.0.1 UH 2 21435 lo0 192.168.1 link#1 UC 3 0 dc0 => 192.168.1.1 0:0:c0:cb:bd:f2 UHLW 5 17908 dc0 => 192.168.1.3 0:0:f8:10:7a:a2 UHLW 0 119004 lo0 216.136.204.18 192.168.1.1 UGHW 1 57092 dc0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSc lo0 => default fe80::200:c0ff:fecb:bdf2%dc0 UGc dc0 ::1 ::1 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRSc lo0 fe80::/10 ::1 UGRSc lo0 fe80::%dc0/64 link#1 UC dc0 fe80::200:f8ff:fe10:7aa2%dc0 0:0:f8:10:7a:a2 UHL lo0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 fe80::1%lo0 link#3 UHL lo0 fec0::1:200:c0ff:fecb:bdf2 0:0:c0:cb:bd:f2 UHL dc0 fec0::1:200:f8ff:fe10:7aa2 0:0:f8:10:7a:a2 UHL lo0 ff01::/32 ::1 U lo0 ff02::/16 link#1 UCS dc0 ff02::%dc0/32 link#1 UC dc0 ff02::%lo0/32 ::1 UC lo0 > Also, please tell us the result of > > % ndp -an intruder:bmah% ndp -an Neighbor Linklayer Address Netif Expire St Flgs Prbs fe80::200:c0ff:fecb:bdf2%dc0 0:0:c0:cb:bd:f2 dc0 13h12m41s S R fe80::200:f8ff:fe10:7aa2%dc0 0:0:f8:10:7a:a2 dc0 permanent R fe80::1%lo0 (incomplete) lo0 permanent R fec0::1:200:c0ff:fecb:bdf2 0:0:c0:cb:bd:f2 dc0 23h57m59s S R fec0::1:200:f8ff:fe10:7aa2 0:0:f8:10:7a:a2 dc0 permanent R I should mention that the machine whose addresses are fe80::200:c0ff:fecb:bdf2%dc0 and fec0::1:200:c0ff:fecb:bdf2 is another FreeBSD 4.3-STABLE box (but running code from before the recent KAME merge). It is advertising the link-local prefix to this subnet. As before, please let me know what else I can do. Thanks! Bruce. --==_Exmh_-641166680P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7U7ce2MoxcVugUsMRAgrxAKDE7ov3r6qu7uqRLUbCqlMgTjp2XgCfTZZZ +OTWRJZuU/L1rTREjLt9QDg= =nktX -----END PGP SIGNATURE----- --==_Exmh_-641166680P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 22:27: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from blade.elitsat.net (blade.elitsat.net [209.239.78.129]) by hub.freebsd.org (Postfix) with ESMTP id 7D09437B408 for ; Mon, 16 Jul 2001 22:26:57 -0700 (PDT) (envelope-from amour@blade.elitsat.net) Received: from localhost (amour@localhost) by blade.elitsat.net (8.11.3/8.11.3) with ESMTP id f6H5Qn647955 for ; Tue, 17 Jul 2001 08:26:51 +0300 (EEST) (envelope-from amour@blade.elitsat.net) Date: Tue, 17 Jul 2001 08:26:48 +0300 (EEST) From: Alexander To: Subject: traceroute filter. Message-ID: <20010717082431.N47897-100000@blade.elitsat.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello. I was wondering if anyone knows how can I set ipfw rules to allow myself to traceroute anywhere but noone to be able to ping or traceroute me. I saw few examples in the ipfw tutorial on www.defcon1.org for filtering external pings but these examples don't allow me to traceroute somewhere. thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Jul 16 23: 0:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail13.sdc1.sfba.home.com (femail13.sdc1.sfba.home.com [24.0.95.140]) by hub.freebsd.org (Postfix) with ESMTP id 218ED37B406 for ; Mon, 16 Jul 2001 23:00:23 -0700 (PDT) (envelope-from btdang@home.com) Received: from home.com ([24.248.85.196]) by femail13.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010717060022.MSZB20529.femail13.sdc1.sfba.home.com@home.com> for ; Mon, 16 Jul 2001 23:00:22 -0700 Message-ID: <3B53D5AF.8D004696@home.com> Date: Mon, 16 Jul 2001 23:05:35 -0700 From: Bruce Dang Organization: Boys & Girls Clubs X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG Subject: Re: traceroute filter. References: <20010717082431.N47897-100000@blade.elitsat.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Alex, The last 'traceroute blocking' thread went on for a few weeks, so I think you should look into that. In addition to that, I think blocking ICMP packets, especially type 3 and 11 would allow you to traceroute. traceroute(8) works by sending UDP datagrams to destination, incrementing TTLs after every hop. If you block all ICMP packets, the intermediate routers will not be able to send back ICMP packets, which makes traceroute(8) almost useless ;(. Bruce Dang www.tbug.org i wonder how long this thread will go on... Alexander wrote: > > Hello. > I was wondering if anyone knows how can I set ipfw rules to allow myself > to traceroute anywhere but noone to be able to ping or traceroute me. > > I saw few examples in the ipfw tutorial on www.defcon1.org for filtering > external pings but these examples don't allow me to traceroute somewhere. > > thanks. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 1:20:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from softweyr.com (softweyr.com [208.247.99.111]) by hub.freebsd.org (Postfix) with ESMTP id 6E0A337B401 for ; Tue, 17 Jul 2001 01:20:35 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from localhost.softweyr.com ([127.0.0.1] helo=softweyr.com ident=25f6b9e92e251f8034eae016d27c390d) by softweyr.com with esmtp (Exim 3.16 #1) id 15MQAX-00012l-00; Tue, 17 Jul 2001 02:25:25 -0600 Message-ID: <3B53F675.2C04A740@softweyr.com> Date: Tue, 17 Jul 2001 02:25:25 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: Brooks Davis , net@FreeBSD.org Subject: Re: sysctl net.link.vlan.link.proto References: <20010713171342.A18472@Odin.AC.HMC.Edu> <200107141649.f6EGnEb01827@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Garrett Wollman wrote: > > < said: > > > I'm working on modernizing the vlan device (making it loadable, > > unloadable, and clonable) and I've run into this sysctl. It allows you > > to set the ethernet protocol used for vlan packets. This doesn't strike > > me as very useful [...] > > It has never proven useful to me, but all the VLAN-capable switches I > have seen allow the Ethertype to be configured, so I figured that > there must have been some need or requirement for it somewhere. You've never encountered IP in LLC (or SNAP) frames? How odd. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 3:34:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 61F0837B401 for ; Tue, 17 Jul 2001 03:34:12 -0700 (PDT) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.11.2/8.11.1) with SMTP id f6HAY7I34804; Tue, 17 Jul 2001 06:34:07 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: matt-l@pacbell.net ("matt") Cc: freebsd-net@freebsd.org Subject: Re: router question Date: Tue, 17 Jul 2001 06:34:06 -0400 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 16 Jul 2001 13:44:00 -0400, in sentex.lists.freebsd.net you wrote: http://www.etinc.com makes cards like that which support FreeBSD. ---Mike >Does anyone know if there's a inbound T1 line with RJ45 >connector will work with my FreeBSD box without >connecting to a CISCO router first? In another word, >hook FreeBSD box directly to the T1's RJ45. > >Or i have to buy a CISCO router to have the T1 RJ45 >connect to it, then from router to a switch, and then to >FreeBSD? > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >WWW.XGFORCE.COM >The Next Generation Load Balance and >Fail Safe Server Clustering Software >for the Internet. >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-net" in the body of the message Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 3:44:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 3EAC637B403 for ; Tue, 17 Jul 2001 03:44:13 -0700 (PDT) (envelope-from krepel@fokus.gmd.de) Received: from fokus.gmd.de (quant [193.175.133.183]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id MAA23454 for ; Tue, 17 Jul 2001 12:44:11 +0200 (MET DST) Message-ID: <3B5416FA.D84D899A@fokus.gmd.de> Date: Tue, 17 Jul 2001 12:44:10 +0200 From: Falco Krepel Organization: GMD FOKUS - CATS Group X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en, de-DE MIME-Version: 1.0 To: net@FreeBSD.org Subject: pxeboot doesn't work anymore Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I use the 3COM 3C905c TX-M with bootrom (PXE v2.20, MBA v4.30). Some time after 2001-05-14 the pxeboot is not working anymore. I have the following behavior: 1. The client gets his IP address and bootfile with DHCP. 2. TFTP starts with downloading the pxeboot and after approximatly 1 kbyte it stops and on the entire display, colored and flashing characters appear. I have no idea where the problem could be, because the pxeboot changes are only minor changes. Maybe somebody could help me. Thanx, Falco -- Falco Krepel Phone: +49-(0)30 - 34 63 - 7 276 GMD-FOKUS Fax: +49-(0)30 - 34 63 - 8 276 Kaiserin-Augusta-Allee 31 e-mail: krepel@fokus.gmd.de 10589 Berlin WWW: http://www.fokus.gmd.de/usr/krepel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 3:46: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id 0A2B637B407; Tue, 17 Jul 2001 03:46:00 -0700 (PDT) (envelope-from krepel@fokus.gmd.de) Received: from fokus.gmd.de (quant [193.175.133.183]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id MAA23803; Tue, 17 Jul 2001 12:45:59 +0200 (MET DST) Message-ID: <3B541766.ABD8BE9@fokus.gmd.de> Date: Tue, 17 Jul 2001 12:45:58 +0200 From: Falco Krepel Organization: GMD FOKUS - CATS Group X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en, de-DE MIME-Version: 1.0 To: net@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: pxeboot doesn't work anymore References: <3B5416FA.D84D899A@fokus.gmd.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I use FreeBSD 5.0. Falco Krepel wrote: > > I use the 3COM 3C905c TX-M with bootrom (PXE v2.20, MBA v4.30). Some > time after 2001-05-14 the pxeboot is not working anymore. > > I have the following behavior: > > 1. The client gets his IP address and bootfile with DHCP. > 2. TFTP starts with downloading the pxeboot and after approximatly 1 > kbyte it stops and on the entire display, colored and flashing > characters appear. > > I have no idea where the problem could be, because the pxeboot changes > are only minor changes. Maybe somebody could help me. > > Thanx, > > Falco -- Falco Krepel Phone: +49-(0)30 - 34 63 - 7 276 GMD-FOKUS Fax: +49-(0)30 - 34 63 - 8 276 Kaiserin-Augusta-Allee 31 e-mail: krepel@fokus.gmd.de 10589 Berlin WWW: http://www.fokus.gmd.de/usr/krepel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 8:15:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 68B0537B406; Tue, 17 Jul 2001 08:15:10 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:13ff::a]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id AAA24306; Wed, 18 Jul 2001 00:17:05 +0900 (JST) Date: Wed, 18 Jul 2001 00:15:07 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: bmah@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: <200107170355.f6H3tBG13515@intruder.bmah.org> References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> <200107161716.f6GHGO207568@intruder.bmah.org> <200107170355.f6H3tBG13515@intruder.bmah.org> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 43 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Mon, 16 Jul 2001 20:55:11 -0700, >>>>> bmah@FreeBSD.ORG (Bruce A. Mah) said: >> > (kgdb) print rt >> > $1 = (struct rtentry *) 0x3 >> > (kgdb) print ln >> > $2 = (struct llinfo_nd6 *) 0x620000 >> >> Then rt and ln are surely broken. I have not got the reason yet, >> though... > Yes, rt in particular caught my eye. I've almost got the problem. Unfortunately, all IPv6 autoconfigured nodes would panic every 24 hours. Since I guess I need some more work for a complete fix to this, I'll attach a workaround. Please try the following patch for the moment. The patch suppresses garbage collection of stale neighbor cache entries, but it would not matter for most users. Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp *** nd6.c.orig Wed Jul 18 00:06:30 2001 --- nd6.c Wed Jul 18 00:06:57 2001 *************** *** 500,507 **** --- 500,509 ---- case ND6_LLINFO_STALE: /* Garbage Collection(RFC 2461 5.3) */ + #if 0 /* XXX: short-term workaround to avoid panic */ if (ln->ln_expire) next = nd6_free(rt); + #endif break; case ND6_LLINFO_DELAY: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 13:29:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id AC82837B401; Tue, 17 Jul 2001 13:29:09 -0700 (PDT) (envelope-from bmah@employees.org) Received: from intruder.bmah.org ([24.176.204.87]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010717202909.IIUX17182.femail4.sdc1.sfba.home.com@intruder.bmah.org>; Tue, 17 Jul 2001 13:29:09 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.4/8.11.3) id f6HKT8o04714; Tue, 17 Jul 2001 13:29:08 -0700 (PDT) (envelope-from bmah) Message-Id: <200107172029.f6HKT8o04714@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: bmah@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> <200107161716.f6GHGO207568@intruder.bmah.org> <200107170355.f6H3tBG13515@intruder.bmah.org> Comments: In-reply-to JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= message dated "Wed, 18 Jul 2001 00:15:07 +0900." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1089202039P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 17 Jul 2001 13:29:08 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_1089202039P Content-Type: text/plain; charset=us-ascii If memory serves me right, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI= ?= wrote: > Please try the following patch for the moment. The patch suppresses > garbage collection of stale neighbor cache entries, but it would not > matter for most users. OK, patch applied, and I'm doing a buildkernel right now. Of course I won't be able to tell you very much if it works..... Thanks! Bruce. --==_Exmh_1089202039P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7VKAT2MoxcVugUsMRAgnnAKCvkWX8oh2f7w7hBvznW2pCby1DGgCdHio2 YYVEd4P9XMdu1Wi4h4+P6zU= =iIQN -----END PGP SIGNATURE----- --==_Exmh_1089202039P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 16:13: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from sirius.pc.cis.udel.edu (sirius.pc.cis.udel.edu [128.175.202.57]) by hub.freebsd.org (Postfix) with ESMTP id C23B037B405 for ; Tue, 17 Jul 2001 16:13:06 -0700 (PDT) (envelope-from jain@sirius.pc.cis.udel.edu) Received: from localhost (localhost [127.0.0.1]) by sirius.pc.cis.udel.edu (8.11.3/8.11.3) with ESMTP id f6HN8oB03558 for ; Tue, 17 Jul 2001 19:08:51 -0400 (EDT) (envelope-from jain@sirius.pc.cis.udel.edu) Date: Tue, 17 Jul 2001 19:08:50 -0400 (EDT) From: Manish Jain To: Subject: window scaling in TCP Message-ID: <20010717185128.Q3168-100000@sirius.pc.cis.udel.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I had posted a query regarding window scaling option in TCP sometime last week too. After that I did attempt to look in to the FreeBsd Code but could not find much. I am posting my query again. In my application program , I set the TCP send/recv buffer to 500 K bytes using setsock opt. Since this is greater than 64 K , TCP stack must set the wscale ( window scale option ) in the SYN packet. What I discovered is a bit interesting -- If I set the buffer to upto 200 Kbyte ( approx ) , the wscale bit is set ( I observed thru tcpdump ). But if I try to increase my buffer beyond that, then the wscale bit is set to 0 and the advertized window is 16 Kbyte. I think this is happening because of some MAX limit in the header/configuration file. Does anyone know of this ? manish. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 22: 1:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from chopin.n2.net (chopin.n2.net [207.113.132.15]) by hub.freebsd.org (Postfix) with ESMTP id CDF8A37B401 for ; Tue, 17 Jul 2001 22:01:17 -0700 (PDT) (envelope-from insane@oneinsane.net) Received: from the.oneinsane.net (postfix@the.oneinsane.net [66.42.61.25]) by chopin.n2.net (8.11.2/8.11.2) with ESMTP id f6I51HR04492 for ; Tue, 17 Jul 2001 22:01:17 -0700 (PDT) Received: from mental.oneinsane.net (mental.oneinsane.net [66.42.61.28]) by the.oneinsane.net (Postfix) with ESMTP id 3031B9BF7; Tue, 17 Jul 2001 22:01:16 -0700 (PDT) Received: by mental.oneinsane.net (Postfix, from userid 1000) id 4EBD8F912; Tue, 17 Jul 2001 22:01:24 -0700 (PDT) Date: Tue, 17 Jul 2001 22:01:23 -0700 From: Ron Rosson To: rlr@oneinsane.net, freebsd-net@freebsd.org Subject: Test Message-ID: <20010717220123.A71456@mental.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD mental.oneinsane.net 4.3-STABLE X-GPG-FINGERPRINT: 77F1 1310 119F 2594 4938 05D7 2E36 FC23 07DC 46FC X-Uptime: 10:01PM up 15:22, 5 users, load averages: 0.00, 0.04, 0.09 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a test message -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ Press every key to continue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Jul 17 23:43:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id A272037B401 for ; Tue, 17 Jul 2001 23:43:41 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:4819:2000:f4b9:a9c3:3362:c191]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id PAA00912 for ; Wed, 18 Jul 2001 15:45:39 +0900 (JST) Date: Wed, 18 Jul 2001 15:43:41 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: freebsd-net@FreeBSD.ORG Subject: avoiding unnecessary route deletion in rt_fixchange() User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 103 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As commented in defined in sys/net/route.c, rt_fixchange() has a bad effect, which would cause unnecessary route deletion: * Unfortunately, this has the obnoxious * property of also triggering for insertion /above/ a pre-existing network * route and clones. Sigh. This may be fixed some day. The effect has been even worse, because recent versions of route.c set the parent rtentry for cloned routes from an interface-direct route. For example, suppose that we have an interface "ne0" that has an IPv4 subnet "10.0.0.0/24". Then we may have a cloned route like 10.0.0.1 on the interface, whose parent route is 10.0.0.0/24 (to the interface ne0). Now, when we add the default route (i.e. 0.0.0.0/0), rt_fixchange() will remove the cloned route 10.0.0.1. The (bad) effect also prevents rt_setgate from configuring rt_gwroute, which would not be an intended behavior. As suggested in the comments to rt_fixchange(), we need stricter check in the function, to prevent unintentional route deletion. The attached is a proposed fix to this problem (for FreeBSD4-STABLE). Please review it, and merge it to the repository if acceptable. This fix will also solve the "IPV6 panic?" problem which was recently reported in this list. Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp *** route.c.orig Wed Jul 18 15:13:18 2001 --- route.c Wed Jul 18 15:18:15 2001 *************** *** 726,734 **** * network route and (cloned) host routes. For this reason, a simple check * of rt->rt_parent is insufficient; each candidate route must be tested * against the (mask, value) of the new route (passed as before in vp) ! * to see if the new route matches it. Unfortunately, this has the obnoxious ! * property of also triggering for insertion /above/ a pre-existing network ! * route and clones. Sigh. This may be fixed some day. * * XXX - it may be possible to do fixdelete() for changes and reserve this * routine just for adds. I'm not sure why I thought it was necessary to do --- 726,732 ---- * network route and (cloned) host routes. For this reason, a simple check * of rt->rt_parent is insufficient; each candidate route must be tested * against the (mask, value) of the new route (passed as before in vp) ! * to see if the new route matches it. * * XXX - it may be possible to do fixdelete() for changes and reserve this * routine just for adds. I'm not sure why I thought it was necessary to do *************** *** 747,754 **** struct rtfc_arg *ap = vp; struct rtentry *rt0 = ap->rt0; struct radix_node_head *rnh = ap->rnh; ! u_char *xk1, *xm1, *xk2; ! int i, len; #ifdef DEBUG if (rtfcdebug) --- 745,752 ---- struct rtfc_arg *ap = vp; struct rtentry *rt0 = ap->rt0; struct radix_node_head *rnh = ap->rnh; ! u_char *xk1, *xm1, *xk2, *xmp; ! int i, len, mlen; #ifdef DEBUG if (rtfcdebug) *************** *** 781,786 **** --- 779,806 ---- xk1 = (u_char *)rt_key(rt0); xm1 = (u_char *)rt_mask(rt0); xk2 = (u_char *)rt_key(rt); + + /* avoid applying a less specific route */ + xmp = (u_char *)rt_mask(rt->rt_parent); + mlen = ((struct sockaddr *)rt_key(rt->rt_parent))->sa_len; + if (mlen > ((struct sockaddr *)rt_key(rt0))->sa_len) { + #ifdef DEBUG + if (rtfcdebug) + printf("rt_fixchange: inserting a less " + "specific route\n"); + #endif + return 0; + } + for (i = rnh->rnh_treetop->rn_offset; i < mlen; i++) { + if ((xmp[i] & ~(xmp[i] ^ xm1[i])) != xmp[i]) { + #ifdef DEBUG + if (rtfcdebug) + printf("rt_fixchange: inserting a less " + "specific route\n"); + #endif + return 0; + } + } for (i = rnh->rnh_treetop->rn_offset; i < len; i++) { if ((xk2[i] & xm1[i]) != xk1[i]) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 0:53:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f197.law11.hotmail.com [64.4.17.197]) by hub.freebsd.org (Postfix) with ESMTP id 54B9037B401; Wed, 18 Jul 2001 00:53:46 -0700 (PDT) (envelope-from anandfranklin@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 18 Jul 2001 00:53:46 -0700 Received: from 203.200.20.3 by lw11fd.law11.hotmail.msn.com with HTTP; Wed, 18 Jul 2001 07:53:45 GMT X-Originating-IP: [203.200.20.3] From: "Anand Franklin J" To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Hi(some clarifcation about sysctl usage in ifconfig) Date: Wed, 18 Jul 2001 07:53:45 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jul 2001 07:53:46.0062 (UTC) FILETIME=[C5A916E0:01C10F5E] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, The below code is part of ifconfig which use sysctl: 1:mib[0] = CTL_NET; 2:mib[1] = PF_ROUTE; 3:mib[2] = 0; 4:mib[3] = 0; /* address family */ 5:mib[4] = NET_RT_IFLIST; 6:mib[5] = 0; /* if particular family specified, only ask about it */ 7:if (afp) 8: mib[3] = afp->af_af; 9:if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) 10: errx(1, "iflist-sysctl-estimate"); 11:if ((buf = malloc(needed)) == NULL) errx(1, "malloc"); 12:if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) errx(1, "actual retrieval of interface table"); the doubts are: 1) what is the purpose of the above c statements. 2)how are the mib values stored before finding its value line from 1->8 3)line from 9->11 is clear, that is it finds the length of the buffer to be allocated. 4)what is the significance of line 12 and what will the buf variable will contain. with regard's franklin. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 1: 3:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 1213C37B407; Wed, 18 Jul 2001 01:03:01 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f6I81wk12805; Wed, 18 Jul 2001 11:01:58 +0300 (EEST) (envelope-from ru) Date: Wed, 18 Jul 2001 11:01:58 +0300 From: Ruslan Ermilov To: JINMEI Tatuya Cc: Garrett Wollman , net@FreeBSD.org Subject: Re: avoiding unnecessary route deletion in rt_fixchange() Message-ID: <20010718110158.A12171@sunbay.com> Mail-Followup-To: JINMEI Tatuya , Garrett Wollman , net@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jinmei@isl.rdc.toshiba.co.jp on Wed, Jul 18, 2001 at 03:43:41PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Yay, cool! Unless Garrett commits this in a few days, I will on Friday. And yes, this fixes the "mysterious" problem when gwroute was not allocated when adding the "default" route. Thanks! On Wed, Jul 18, 2001 at 03:43:41PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > As commented in defined in sys/net/route.c, rt_fixchange() has a bad > effect, which would cause unnecessary route deletion: > > * Unfortunately, this has the obnoxious > * property of also triggering for insertion /above/ a pre-existing network > * route and clones. Sigh. This may be fixed some day. > > The effect has been even worse, because recent versions of route.c set > the parent rtentry for cloned routes from an interface-direct route. > For example, suppose that we have an interface "ne0" that has an IPv4 > subnet "10.0.0.0/24". Then we may have a cloned route like 10.0.0.1 > on the interface, whose parent route is 10.0.0.0/24 (to the interface > ne0). Now, when we add the default route (i.e. 0.0.0.0/0), > rt_fixchange() will remove the cloned route 10.0.0.1. The (bad) effect > also prevents rt_setgate from configuring rt_gwroute, which would not > be an intended behavior. > > As suggested in the comments to rt_fixchange(), we need stricter check > in the function, to prevent unintentional route deletion. The > attached is a proposed fix to this problem (for FreeBSD4-STABLE). > Please review it, and merge it to the repository if acceptable. > > This fix will also solve the "IPV6 panic?" problem which was recently > reported in this list. > > Thanks, > > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center, Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp > > *** route.c.orig Wed Jul 18 15:13:18 2001 > --- route.c Wed Jul 18 15:18:15 2001 > *************** > *** 726,734 **** > * network route and (cloned) host routes. For this reason, a simple check > * of rt->rt_parent is insufficient; each candidate route must be tested > * against the (mask, value) of the new route (passed as before in vp) > ! * to see if the new route matches it. Unfortunately, this has the obnoxious > ! * property of also triggering for insertion /above/ a pre-existing network > ! * route and clones. Sigh. This may be fixed some day. > * > * XXX - it may be possible to do fixdelete() for changes and reserve this > * routine just for adds. I'm not sure why I thought it was necessary to do > --- 726,732 ---- > * network route and (cloned) host routes. For this reason, a simple check > * of rt->rt_parent is insufficient; each candidate route must be tested > * against the (mask, value) of the new route (passed as before in vp) > ! * to see if the new route matches it. > * > * XXX - it may be possible to do fixdelete() for changes and reserve this > * routine just for adds. I'm not sure why I thought it was necessary to do > *************** > *** 747,754 **** > struct rtfc_arg *ap = vp; > struct rtentry *rt0 = ap->rt0; > struct radix_node_head *rnh = ap->rnh; > ! u_char *xk1, *xm1, *xk2; > ! int i, len; > > #ifdef DEBUG > if (rtfcdebug) > --- 745,752 ---- > struct rtfc_arg *ap = vp; > struct rtentry *rt0 = ap->rt0; > struct radix_node_head *rnh = ap->rnh; > ! u_char *xk1, *xm1, *xk2, *xmp; > ! int i, len, mlen; > > #ifdef DEBUG > if (rtfcdebug) > *************** > *** 781,786 **** > --- 779,806 ---- > xk1 = (u_char *)rt_key(rt0); > xm1 = (u_char *)rt_mask(rt0); > xk2 = (u_char *)rt_key(rt); > + > + /* avoid applying a less specific route */ > + xmp = (u_char *)rt_mask(rt->rt_parent); > + mlen = ((struct sockaddr *)rt_key(rt->rt_parent))->sa_len; > + if (mlen > ((struct sockaddr *)rt_key(rt0))->sa_len) { > + #ifdef DEBUG > + if (rtfcdebug) > + printf("rt_fixchange: inserting a less " > + "specific route\n"); > + #endif > + return 0; > + } > + for (i = rnh->rnh_treetop->rn_offset; i < mlen; i++) { > + if ((xmp[i] & ~(xmp[i] ^ xm1[i])) != xmp[i]) { > + #ifdef DEBUG > + if (rtfcdebug) > + printf("rt_fixchange: inserting a less " > + "specific route\n"); > + #endif > + return 0; > + } > + } > > for (i = rnh->rnh_treetop->rn_offset; i < len; i++) { > if ((xk2[i] & xm1[i]) != xk1[i]) { -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 3:35:33 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id F1A3A37B403 for ; Wed, 18 Jul 2001 03:35:27 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id MAA45467 for ; Wed, 18 Jul 2001 12:35:27 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6IAZPV02985 for ; Wed, 18 Jul 2001 12:35:26 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Wed, 18 Jul 2001 12:35:25 +0200 From: Christophe Prévotaux To: net@freebsd.org Subject: MPLS Message-Id: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented under FreeBSD ? I know that Juniper has implemented them and whole bunch of other neat thing over FreeBSD and that the latest JUNOS is a somewhat modified FreeBSD 4.x Is anyone (or maybe Juniper ? :)) working on implementing this under FreeBSD ? Also when will AltQ be part of the FreeBSD system ? -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 5:42:40 2001 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 555A337B403 for ; Wed, 18 Jul 2001 05:42:25 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f6ICfcR52220; Wed, 18 Jul 2001 15:41:38 +0300 (EEST) (envelope-from ru) Date: Wed, 18 Jul 2001 15:41:38 +0300 From: Ruslan Ermilov To: Ari Suutari , plk@in.nextra.sk, freebsd-net@FreeBSD.ORG Subject: Re: natd and ICMP 3.4 packets Message-ID: <20010718154138.B50252@sunbay.com> Mail-Followup-To: Ari Suutari , plk@in.nextra.sk, freebsd-net@FreeBSD.ORG References: <20010710110934.D1048@in.nextra.sk> <20010712124152.A80584@sunbay.com> <20010713120211.B4366@in.nextra.sk> <017d01c10b87$b573a4f0$0e05a8c0@coffee> <20010713135855.A65898@sunbay.com> <01f101c10b9e$41482530$0e05a8c0@coffee> <20010713164803.A87098@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="s2ZSL+KKDSLx8OML" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010713164803.A87098@sunbay.com>; from ru@FreeBSD.ORG on Fri, Jul 13, 2001 at 04:48:03PM +0300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --s2ZSL+KKDSLx8OML Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jul 13, 2001 at 04:48:03PM +0300, Ruslan Ermilov wrote: > On Fri, Jul 13, 2001 at 04:18:05PM +0300, Ari Suutari wrote: > > > > > > > > Doesn't sound good that IP header with private IP address > > > > gets sent to internet. - after all, the 195.168.3.210 host on internet > > knows > > > > nothing about 10.10.1.2... > > > > > > > We have discussed this before with Brian and Charles, and have come > > > up to an agreement that FIREWALL should block these packets, not NAT. > > > > > > > There must be something I don't understand now ? How is the host > > on the internet now going to know that smaller MTU is required when > > it sends packets to host inside nat'ed network ? > > > Give me a few days guys, OK? I will come up with a solution. > OK, as was promised... Please try the attached patch. You'll have to recompile/install both libalias and natd. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --s2ZSL+KKDSLx8OML Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: alias.c =================================================================== RCS file: /home/ncvs/src/lib/libalias/alias.c,v retrieving revision 1.29 diff -u -p -r1.29 alias.c --- alias.c 2001/06/04 15:09:51 1.29 +++ alias.c 2001/07/18 12:37:25 @@ -518,6 +518,10 @@ IcmpAliasOut2(struct ip *pip) struct udphdr *ud; struct tcphdr *tc; struct alias_link *link; + u_short *sptr; + int accumulate; + struct in_addr alias_address; + u_short alias_port, alias_id; ic = (struct icmp *) ((char *) pip + (pip->ip_hl << 2)); ip = &ic->icmp_ip; @@ -546,11 +550,6 @@ IcmpAliasOut2(struct ip *pip) { if (ip->ip_p == IPPROTO_UDP || ip->ip_p == IPPROTO_TCP) { - u_short *sptr; - int accumulate; - struct in_addr alias_address; - u_short alias_port; - alias_address = GetAliasAddress(link); alias_port = GetAliasPort(link); @@ -565,18 +564,6 @@ IcmpAliasOut2(struct ip *pip) accumulate -= alias_port; ADJUST_CHECKSUM(accumulate, ic->icmp_cksum); -/* - * Alias address in IP header if it comes from the host - * the original TCP/UDP packet was destined for. - */ - if (pip->ip_src.s_addr == ip->ip_dst.s_addr) { - DifferentialChecksum(&pip->ip_sum, - (u_short *) &alias_address, - (u_short *) &pip->ip_src, - 2); - pip->ip_src = alias_address; - } - /* Alias address and port number of original IP packet fragment contained in ICMP data section */ ip->ip_dst = alias_address; @@ -584,11 +571,6 @@ fragment contained in ICMP data section } else if (ip->ip_p == IPPROTO_ICMP) { - u_short *sptr; - int accumulate; - struct in_addr alias_address; - u_short alias_id; - alias_address = GetAliasAddress(link); alias_id = GetAliasPort(link); @@ -603,23 +585,25 @@ fragment contained in ICMP data section accumulate -= alias_id; ADJUST_CHECKSUM(accumulate, ic->icmp_cksum); -/* - * Alias address in IP header if it comes from the host - * the original ICMP message was destined for. - */ - if (pip->ip_src.s_addr == ip->ip_dst.s_addr) { - DifferentialChecksum(&pip->ip_sum, - (u_short *) &alias_address, - (u_short *) &pip->ip_src, - 2); - pip->ip_src = alias_address; - } - /* Alias address of original IP packet and sequence number of embedded ICMP datagram */ ip->ip_dst = alias_address; ic2->icmp_id = alias_id; } + +/* + * Alias address in IP header. + * If the message is from an intermediate router, + * make it look as if it comes from the NAT box. + */ + if (pip->ip_src.s_addr != ip->ip_dst.s_addr) + alias_address = FindAliasAddress(pip->ip_src); + DifferentialChecksum(&pip->ip_sum, + (u_short *) &alias_address, + (u_short *) &pip->ip_src, + 2); + pip->ip_src = alias_address; + return(PKT_ALIAS_OK); } return(PKT_ALIAS_IGNORED); --s2ZSL+KKDSLx8OML-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 8: 9:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id AC6A337B405; Wed, 18 Jul 2001 08:09:24 -0700 (PDT) (envelope-from bmah@employees.org) Received: from intruder.bmah.org ([24.176.204.87]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010718150923.NKKW8703.femail1.sdc1.sfba.home.com@intruder.bmah.org>; Wed, 18 Jul 2001 08:09:23 -0700 Received: (from bmah@localhost) by intruder.bmah.org (8.11.4/8.11.3) id f6IF9Nn07454; Wed, 18 Jul 2001 08:09:23 -0700 (PDT) (envelope-from bmah) Message-Id: <200107181509.f6IF9Nn07454@intruder.bmah.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= Cc: bmah@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: IPV6 panic? In-Reply-To: References: <200107121019.f6CAJqI85911@zibbi.icomtek.csir.co.za> <200107121548.f6CFmZF15294@intruder.bmah.org> <200107150827.f6F8Rxh02585@intruder.bmah.org> <200107161716.f6GHGO207568@intruder.bmah.org> <200107170355.f6H3tBG13515@intruder.bmah.org> <200107172029.f6HKT8o04714@intruder.bmah.org> Comments: In-reply-to JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= message dated "Wed, 18 Jul 2001 15:46:46 +0900." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_685578394P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 18 Jul 2001 08:09:22 -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --==_Exmh_685578394P Content-Type: text/plain; charset=us-ascii If memory serves me right, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI= ?= wrote: > The essential point of this problem is not in the IPv6 stack, but in > net/route.c. > > The attached patch (which you may already have seen) would be a > complete fix to this problem. Please try it. OK. I un-did your workaround, applied the patch you posted to -net, and am now building up a new kernel.....stay tuned..... Thanks! Bruce. --==_Exmh_685578394P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: Exmh version 2.3.1+ 05/14/2001 iD8DBQE7Vaah2MoxcVugUsMRAnpRAJ0RjxEm9bDS07QC5M7Cco27hV2XPwCdF5tg D2XyvIkLznJuRkdy6Tdjtv4= =jVwq -----END PGP SIGNATURE----- --==_Exmh_685578394P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 8:53:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 5DB8637B401; Wed, 18 Jul 2001 08:53:19 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id B34514CFAF; Wed, 18 Jul 2001 11:53:13 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id LAA11960; Wed, 18 Jul 2001 11:53:13 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id IAA18523; Wed, 18 Jul 2001 08:53:12 -0700 (PDT) Message-Id: <200107181553.IAA18523@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: dcs@freebsd.org Subject: Re: 802.1q and multicasting Cc: freebsd-net@freebsd.org Date: Wed, 18 Jul 2001 08:53:12 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The vlan driver doesn't set up the multicast filters correctly on the underlying interface. I've got a patch sitting in my CVS tree that I should probably just commit... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 8:57:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 9519D37B405; Wed, 18 Jul 2001 08:57:08 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id E5AE44CF8C; Wed, 18 Jul 2001 11:57:07 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id LAA12070; Wed, 18 Jul 2001 11:57:07 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id IAA18929; Wed, 18 Jul 2001 08:57:06 -0700 (PDT) Message-Id: <200107181557.IAA18929@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: dcs@freebsd.org Subject: Re: 802.1q and multicasting Cc: freebsd-net@freebsd.org Date: Wed, 18 Jul 2001 08:57:06 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Actually, I guess I *did* commit them, in -current. I will look at merging them next week. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 9:45: 3 2001 Delivered-To: freebsd-net@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 9F71537B405; Wed, 18 Jul 2001 09:44:56 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.138.210.Dial1.SanJose1.Level3.net [209.247.138.210]) by falcon.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id JAA02119; Wed, 18 Jul 2001 09:44:54 -0700 (PDT) Message-ID: <3B55BD2B.7CB85DF1@mindspring.com> Date: Wed, 18 Jul 2001 09:45:31 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Anand Franklin J Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Hi(some clarifcation about sysctl usage in ifconfig) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Anand Franklin J wrote: > The below code is part of ifconfig which use sysctl: > 1:mib[0] = CTL_NET; > 2:mib[1] = PF_ROUTE; > 3:mib[2] = 0; > 4:mib[3] = 0; /* address family */ > 5:mib[4] = NET_RT_IFLIST; > 6:mib[5] = 0; > > /* if particular family specified, only ask about it */ > 7:if (afp) > 8: mib[3] = afp->af_af; > > 9:if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) > 10: errx(1, "iflist-sysctl-estimate"); > 11:if ((buf = malloc(needed)) == NULL) > errx(1, "malloc"); > 12:if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) > errx(1, "actual retrieval of interface table"); > the doubts are: > 1) what is the purpose of the above c statements. > 2)how are the mib values stored before finding its value > line from 1->8 In the kernel. In other words, they are _not_ writable, they are readable from the kernel. > 3)line from 9->11 is clear, that is it finds the length of the buffer to be > allocated. > 4)what is the significance of line 12 and what will the buf variable will > contain. 9->11 calculate the space and allocate a region for storing the interface list. 12 actually retrieves the list into the allocation space provided (buf). After it runs, if it runs successfully, it will contain a list of interfaces. Probably you want to look at using getifaddrs(3) instead; see the manual page for this library function. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 12:10:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from femail11.sdc1.sfba.home.com (femail11.sdc1.sfba.home.com [24.0.95.107]) by hub.freebsd.org (Postfix) with ESMTP id 4970937B401 for ; Wed, 18 Jul 2001 12:10:07 -0700 (PDT) (envelope-from btdang@home.com) Received: from home.com ([24.248.85.196]) by femail11.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010718191002.ZGPO18785.femail11.sdc1.sfba.home.com@home.com>; Wed, 18 Jul 2001 12:10:02 -0700 Message-ID: <3B55E050.9C03E8A5@home.com> Date: Wed, 18 Jul 2001 12:15:28 -0700 From: Bruce Dang Organization: Boys & Girls Clubs X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christophe =?iso-8859-1?Q?Pr=E9votaux?= Cc: net@FreeBSD.ORG Subject: Re: MPLS References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Monsieur Prevotaux, As of now, I do not believe FreeBSD has MPLS implemented. there is always vlan tagging though (802.1q). maybe someone will implement it in 5.x. bruce "Christophe Prévotaux" wrote: > > Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented > under FreeBSD ? > > I know that Juniper has implemented them and whole bunch of other > neat thing over FreeBSD and that the latest JUNOS is a somewhat modified > FreeBSD 4.x > > Is anyone (or maybe Juniper ? :)) working on implementing this under FreeBSD ? > > Also when will AltQ be part of the FreeBSD system ? > > -- > =================================================================== > Christophe Prevotaux Email: c.prevotaux@hexanet.fr > HEXANET SARL URL: http://www.hexanet.fr/ > Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 > 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 > BP415 Fax: +33 (0)3 26 79 30 06 > 51689 Reims Cedex 2 > FRANCE > =================================================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 12:17:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from herbelot.dyndns.org (d211.dhcp212-26.cybercable.fr [212.198.26.211]) by hub.freebsd.org (Postfix) with ESMTP id B56C137B401 for ; Wed, 18 Jul 2001 12:17:12 -0700 (PDT) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id VAA03089; Wed, 18 Jul 2001 21:14:21 +0200 (CEST) (envelope-from thierry@herbelot.com) Message-ID: <3B55E08B.72202BA7@herbelot.com> Date: Wed, 18 Jul 2001 21:16:27 +0200 From: Thierry Herbelot X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christophe Privotaux Cc: net@FreeBSD.ORG Subject: Re: MPLS References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Christophe Privotaux wrote: > > Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented > under FreeBSD ? have-you had a look at the archives ? ISTR a post where someone announced work with MPLS .... > > I know that Juniper has implemented them and whole bunch of other > neat thing over FreeBSD and that the latest JUNOS is a somewhat modified > FreeBSD 4.x I would be very surprised (but very happy) if Juniper would make its routing software public : this is the core of their business and where they have a competitive advantage when compared to other startups (this includes MPLS, which may be tied to their routing ASIC, and BGP-4) TfH > > Is anyone (or maybe Juniper ? :)) working on implementing this under FreeBSD ? > > Also when will AltQ be part of the FreeBSD system ? > -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 17: 4:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from lorax.cse.ucsc.edu (lorax.cse.ucsc.edu [128.114.49.184]) by hub.freebsd.org (Postfix) with SMTP id 18ACA37B403; Wed, 18 Jul 2001 17:04:09 -0700 (PDT) (envelope-from carvalho@soe.ucsc.edu) Received: from localhost (carvalho@localhost) by lorax.cse.ucsc.edu (8.6.10/8.6.12) with ESMTP id RAA22221; Wed, 18 Jul 2001 17:04:07 -0700 X-Authentication-Warning: lorax.cse.ucsc.edu: carvalho owned process doing -bs Date: Wed, 18 Jul 2001 17:04:06 -0700 (PDT) From: Marcelo Carvalho X-Sender: carvalho@lorax.cse.ucsc.edu To: freebsd-net@FreeBSD.org Cc: freebsd-newbies@FreeBSD.org Subject: Adding new files to netinet Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I'm currently trying to modify some files and add others in the /usr/src/sys/netinet directory. I'm following the procedures of kernel compilation but, apparently, the files I've added don't seem to have compiled. How do I know that they have been compiled successfuly and what else should I do apart from the sequence "config/make depend/make/make install/reboot"? Do I have to change any specific makefile? Where? I'm new to all this stuff. I would really appreciate if someone could give me some guidance here. Thanks, -- Marcelo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 18:46:10 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 125B937B406 for ; Wed, 18 Jul 2001 18:46:08 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id 1678D81D05; Wed, 18 Jul 2001 20:46:08 -0500 (CDT) Date: Wed, 18 Jul 2001 20:46:08 -0500 From: Bill Fumerola To: =?iso-8859-1?Q?Christophe_Pr=E9votaux?= Cc: net@freebsd.org Subject: Re: MPLS Message-ID: <20010718204608.R2759@elvis.mu.org> References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010718123525.7df2028c.c.prevotaux@hexanet.fr>; from c.prevotaux@hexanet.fr on Wed, Jul 18, 2001 at 12:35:25PM +0200 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jul 18, 2001 at 12:35:25PM +0200, Christophe Prévotaux wrote: > I know that Juniper has implemented them and whole bunch of other > neat thing yes (including mpls). > over FreeBSD mostly wrong. > and that the latest JUNOS is a somewhat modified > FreeBSD 4.x wrong. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Jul 18 20:23:39 2001 Delivered-To: freebsd-net@freebsd.org Received: from degler.net (crusoe.degler.net [160.79.55.71]) by hub.freebsd.org (Postfix) with ESMTP id 980E837B403 for ; Wed, 18 Jul 2001 20:23:33 -0700 (PDT) (envelope-from sdegler@degler.net) Received: (from sdegler@localhost) by degler.net (8.11.3/8.11.0) id f6J3MQm70241; Wed, 18 Jul 2001 23:22:26 -0400 (EDT) Date: Wed, 18 Jul 2001 23:22:26 -0400 From: Stephen Degler To: "JINMEI Tatuya / ?$B?@L@C#:H?(B" Cc: freebsd-net@FreeBSD.ORG Subject: Re: avoiding unnecessary route deletion in rt_fixchange() Message-ID: <20010718232226.B69977@crusoe.degler.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jinmei@isl.rdc.toshiba.co.jp on Wed, Jul 18, 2001 at 03:43:41PM +0900 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, Applied. I'll let you (and the list) know if I have any issues. Thanks, skd On Wed, Jul 18, 2001 at 03:43:41PM +0900, JINMEI Tatuya / ?$B?@L@C#:H?(B wrote: > As commented in defined in sys/net/route.c, rt_fixchange() has a bad > effect, which would cause unnecessary route deletion: > > * Unfortunately, this has the obnoxious > * property of also triggering for insertion /above/ a pre-existing network > * route and clones. Sigh. This may be fixed some day. > > The effect has been even worse, because recent versions of route.c set > the parent rtentry for cloned routes from an interface-direct route. > For example, suppose that we have an interface "ne0" that has an IPv4 > subnet "10.0.0.0/24". Then we may have a cloned route like 10.0.0.1 > on the interface, whose parent route is 10.0.0.0/24 (to the interface > ne0). Now, when we add the default route (i.e. 0.0.0.0/0), > rt_fixchange() will remove the cloned route 10.0.0.1. The (bad) effect > also prevents rt_setgate from configuring rt_gwroute, which would not > be an intended behavior. > > As suggested in the comments to rt_fixchange(), we need stricter check > in the function, to prevent unintentional route deletion. The > attached is a proposed fix to this problem (for FreeBSD4-STABLE). > Please review it, and merge it to the repository if acceptable. > > This fix will also solve the "IPV6 panic?" problem which was recently > reported in this list. > > Thanks, > > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center, Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp > > *** route.c.orig Wed Jul 18 15:13:18 2001 > --- route.c Wed Jul 18 15:18:15 2001 > *************** > *** 726,734 **** > * network route and (cloned) host routes. For this reason, a simple check > * of rt->rt_parent is insufficient; each candidate route must be tested > * against the (mask, value) of the new route (passed as before in vp) > ! * to see if the new route matches it. Unfortunately, this has the obnoxious > ! * property of also triggering for insertion /above/ a pre-existing network > ! * route and clones. Sigh. This may be fixed some day. > * > * XXX - it may be possible to do fixdelete() for changes and reserve this > * routine just for adds. I'm not sure why I thought it was necessary to do > --- 726,732 ---- > * network route and (cloned) host routes. For this reason, a simple check > * of rt->rt_parent is insufficient; each candidate route must be tested > * against the (mask, value) of the new route (passed as before in vp) > ! * to see if the new route matches it. > * > * XXX - it may be possible to do fixdelete() for changes and reserve this > * routine just for adds. I'm not sure why I thought it was necessary to do > *************** > *** 747,754 **** > struct rtfc_arg *ap = vp; > struct rtentry *rt0 = ap->rt0; > struct radix_node_head *rnh = ap->rnh; > ! u_char *xk1, *xm1, *xk2; > ! int i, len; > > #ifdef DEBUG > if (rtfcdebug) > --- 745,752 ---- > struct rtfc_arg *ap = vp; > struct rtentry *rt0 = ap->rt0; > struct radix_node_head *rnh = ap->rnh; > ! u_char *xk1, *xm1, *xk2, *xmp; > ! int i, len, mlen; > > #ifdef DEBUG > if (rtfcdebug) > *************** > *** 781,786 **** > --- 779,806 ---- > xk1 = (u_char *)rt_key(rt0); > xm1 = (u_char *)rt_mask(rt0); > xk2 = (u_char *)rt_key(rt); > + > + /* avoid applying a less specific route */ > + xmp = (u_char *)rt_mask(rt->rt_parent); > + mlen = ((struct sockaddr *)rt_key(rt->rt_parent))->sa_len; > + if (mlen > ((struct sockaddr *)rt_key(rt0))->sa_len) { > + #ifdef DEBUG > + if (rtfcdebug) > + printf("rt_fixchange: inserting a less " > + "specific route\n"); > + #endif > + return 0; > + } > + for (i = rnh->rnh_treetop->rn_offset; i < mlen; i++) { > + if ((xmp[i] & ~(xmp[i] ^ xm1[i])) != xmp[i]) { > + #ifdef DEBUG > + if (rtfcdebug) > + printf("rt_fixchange: inserting a less " > + "specific route\n"); > + #endif > + return 0; > + } > + } > > for (i = rnh->rnh_treetop->rn_offset; i < len; i++) { > if ((xk2[i] & xm1[i]) != xk1[i]) { > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 0:29:59 2001 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id BEE6437B401; Thu, 19 Jul 2001 00:29:38 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f6J7MsJ78183; Thu, 19 Jul 2001 10:22:54 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Jul 2001 10:22:54 +0300 From: Ruslan Ermilov To: Marcelo Carvalho Cc: freebsd-net@FreeBSD.ORG, freebsd-newbies@FreeBSD.ORG Subject: Re: Adding new files to netinet Message-ID: <20010719102254.E69276@sunbay.com> Mail-Followup-To: Marcelo Carvalho , freebsd-net@FreeBSD.ORG, freebsd-newbies@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from carvalho@soe.ucsc.edu on Wed, Jul 18, 2001 at 05:04:06PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jul 18, 2001 at 05:04:06PM -0700, Marcelo Carvalho wrote: > > Hi, > > I'm currently trying to modify some files and add others in the > /usr/src/sys/netinet directory. I'm following the procedures of kernel > compilation but, apparently, the files I've added don't seem to have > compiled. How do I know that they have been compiled successfuly and what > else should I do apart from the sequence "config/make depend/make/make > install/reboot"? > > Do I have to change any specific makefile? Where? > > I'm new to all this stuff. I would really appreciate if someone > could give me some guidance here. > You'll need to edit the sys/conf/files file. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 1: 1:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from plk.in.nextra.sk (fw.in.nextra.sk [195.168.29.2]) by hub.freebsd.org (Postfix) with ESMTP id 5495137B403; Thu, 19 Jul 2001 01:01:47 -0700 (PDT) (envelope-from plk@in.nextra.sk) Received: (from plk@localhost) by plk.in.nextra.sk (8.11.2/8.11.2) id f6J81jO03260; Thu, 19 Jul 2001 10:01:45 +0200 Date: Thu, 19 Jul 2001 10:01:45 +0200 From: Bohuslav Plucinsky To: ru@FreeBSD.ORG Cc: Ari Suutari , freebsd-net@FreeBSD.ORG Subject: Re: natd and ICMP 3.4 packets Message-ID: <20010719100145.A32669@in.nextra.sk> Reply-To: plk@in.nextra.sk References: <20010710110934.D1048@in.nextra.sk> <20010712124152.A80584@sunbay.com> <20010713120211.B4366@in.nextra.sk> <017d01c10b87$b573a4f0$0e05a8c0@coffee> <20010713135855.A65898@sunbay.com> <01f101c10b9e$41482530$0e05a8c0@coffee> <20010713164803.A87098@sunbay.com> <20010718154138.B50252@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010718154138.B50252@sunbay.com>; from ru@FreeBSD.ORG on Wed, Jul 18, 2001 at 03:41:38PM +0300 Organization: NEXTRA, Bratislava, SLOVAKIA X-NCC-RegID: sk.nextra Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Yes, now it seems OK. Natd aliases ip_src as well as the host inside ICMP packet. Thanks. Bohus On Wed, Jul 18, 2001 at 03:41:38PM +0300, Ruslan Ermilov wrote: > On Fri, Jul 13, 2001 at 04:48:03PM +0300, Ruslan Ermilov wrote: > > On Fri, Jul 13, 2001 at 04:18:05PM +0300, Ari Suutari wrote: > > > > > > > > > > Doesn't sound good that IP header with private IP address > > > > > gets sent to internet. - after all, the 195.168.3.210 host on internet > > > knows > > > > > nothing about 10.10.1.2... > > > > > > > > > We have discussed this before with Brian and Charles, and have come > > > > up to an agreement that FIREWALL should block these packets, not NAT. > > > > > > > > > > There must be something I don't understand now ? How is the host > > > on the internet now going to know that smaller MTU is required when > > > it sends packets to host inside nat'ed network ? > > > > > Give me a few days guys, OK? I will come up with a solution. > > > OK, as was promised... Please try the attached patch. > You'll have to recompile/install both libalias and natd. > > > Cheers, > -- > Ruslan Ermilov Oracle Developer/DBA, > ru@sunbay.com Sunbay Software AG, > ru@FreeBSD.org FreeBSD committer, > +380.652.512.251 Simferopol, Ukraine > > http://www.FreeBSD.org The Power To Serve > http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 2:23:52 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9C1B737B405 for ; Thu, 19 Jul 2001 02:23:46 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id LAA67213; Thu, 19 Jul 2001 11:23:45 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6J9NjN01144; Thu, 19 Jul 2001 11:23:45 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Thu, 19 Jul 2001 11:23:45 +0200 From: Christophe Prévotaux To: Thierry Herbelot Cc: net@freebsd.org Subject: Re: MPLS Message-Id: <20010719112345.2bf5369e.c.prevotaux@hexanet.fr> In-Reply-To: <3B55E08B.72202BA7@herbelot.com> References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> <3B55E08B.72202BA7@herbelot.com> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 18 Jul 2001 21:16:27 +0200 Thierry Herbelot wrote: > Christophe Privotaux wrote: > > > > Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented > > under FreeBSD ? > > have-you had a look at the archives ? ISTR a post where someone > announced work with MPLS .... No I haven't but if you know who develops it and where the information is located, maybe you could point me in the right direction ? : > > > > > I know that Juniper has implemented them and whole bunch of other > > neat thing over FreeBSD and that the latest JUNOS is a somewhat modified > > FreeBSD 4.x > > I would be very surprised (but very happy) if Juniper would make its > routing software public : this is the core of their business and where > they have a competitive advantage when compared to other startups (this > includes MPLS, which may be tied to their routing ASIC, and BGP-4) Well I know you can download junos 4.4 and run it over a FreeBSD machine and use MPLS without any trouble whatsoever. The fact that the MPLS is tied to their ASICs is a fact , but I know it can also run over a standard FreeBSD without any ASICS > > TfH > > > > Is anyone (or maybe Juniper ? :)) working on implementing this under FreeBSD ? > > > > Also when will AltQ be part of the FreeBSD system ? > > > > -- > Thierry Herbelot > -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 2:25:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3E1AE37B406 for ; Thu, 19 Jul 2001 02:25:16 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id LAA67301; Thu, 19 Jul 2001 11:25:15 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6J9PEN01165; Thu, 19 Jul 2001 11:25:15 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Thu, 19 Jul 2001 11:25:14 +0200 From: Christophe Prévotaux To: Bill Fumerola Cc: net@freebsd.org Subject: Re: MPLS Message-Id: <20010719112514.7fae3f50.c.prevotaux@hexanet.fr> In-Reply-To: <20010718204608.R2759@elvis.mu.org> References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> <20010718204608.R2759@elvis.mu.org> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org What is mostly wrong ? Why don't you just try to get your hands on a JunOS 4.4 and install it over a 4.x FreeBSD and see by yourself ? On Wed, 18 Jul 2001 20:46:08 -0500 Bill Fumerola wrote: > On Wed, Jul 18, 2001 at 12:35:25PM +0200, Christophe Prévotaux wrote: > > > I know that Juniper has implemented them and whole bunch of other > > neat thing > > yes (including mpls). > > > over FreeBSD > > mostly wrong. > > > and that the latest JUNOS is a somewhat modified > > FreeBSD 4.x > > wrong. > > -- > Bill Fumerola - security yahoo / Yahoo! inc. > - fumerola@yahoo-inc.com / billf@FreeBSD.org > > > > -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 2:53:35 2001 Delivered-To: freebsd-net@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 7723A37B406 for ; Thu, 19 Jul 2001 02:53:31 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id 6C48D81D01; Thu, 19 Jul 2001 04:53:21 -0500 (CDT) Date: Thu, 19 Jul 2001 04:53:21 -0500 From: Bill Fumerola To: =?iso-8859-1?Q?Christophe_Pr=E9votaux?= Cc: net@freebsd.org Subject: Re: MPLS Message-ID: <20010719045321.U2759@elvis.mu.org> References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> <20010718204608.R2759@elvis.mu.org> <20010719112514.7fae3f50.c.prevotaux@hexanet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010719112514.7fae3f50.c.prevotaux@hexanet.fr>; from c.prevotaux@hexanet.fr on Thu, Jul 19, 2001 at 11:25:14AM +0200 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jul 19, 2001 at 11:25:14AM +0200, Christophe Prévotaux wrote: > What is mostly wrong ? mpls is done as a filter-based forward in junos, not much different then the firewall component of junos. this is all done on the IP-II. so did you actually setup a network of these machines? if that worked, they have some sort of emulation layer in the absence of the IP-II. I was pretty sure such an emulation layer existed, but to my knowledge only in developer builds. in any event, juniper isn't going to part with any of that code. > Why don't you just try to get your hands on > a JunOS 4.4 and install it over a 4.x FreeBSD > and see by yourself ? because if I was going to do that, I'd just install olive. and just because you install it over 4.x freebsd and it works, doesn't mean its 4.x freebsd based, it means you have a working a.out interpreter. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 3:55:17 2001 Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 8918437B401; Thu, 19 Jul 2001 03:55:01 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f6JAsN712022; Thu, 19 Jul 2001 13:54:23 +0300 (EEST) (envelope-from ru) Date: Thu, 19 Jul 2001 13:54:23 +0300 From: Ruslan Ermilov To: Bruce Evans , Kris Kennaway Cc: "Daniel C. Sobral" , Bill Fenner , net@FreeBSD.org Subject: Re: cvs commit: src/sys/netinet ip_output.c Message-ID: <20010719135423.G69276@sunbay.com> Mail-Followup-To: Bruce Evans , Kris Kennaway , "Daniel C. Sobral" , Bill Fenner , net@FreeBSD.org References: <200107190710.f6J7AVl44738@freefall.freebsd.org> <20010719011806.A28830@xor.obsecurity.org> <200107190710.f6J7AVl44738@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bde@zeta.org.au on Thu, Jul 19, 2001 at 05:46:38PM +1000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jul 19, 2001 at 05:46:38PM +1000, Bruce Evans wrote: > > Modified files: > > sys/netinet ip_output.c > > Log: > > Backout non-functional changes from revision 1.128. > > > > Not objected to by: dcs > > This reduces the bugs in rev.1.128 to style bugs on every line, and: > > ./@/netinet/ip_output.c: In function `ip_output': > ./@/netinet/ip_output.c:127: warning: `ifp' might be used uninitialized in this function > ./@/netinet/ip_output.c:132: warning: `ia' might be used uninitialized in this function > ./@/netinet/ip_output.c:133: warning: `isbroadcast' might be used uninitialized in this function > > The warning is because the variables were initialized only in each arm of an > if-else clause, and the commit adds an elseif which doesn't do anything. > Are you going to fix this too? I don't really understand this. > You are attacking the wrong person here. Daniel did the actual commit. In fact, warnings about `ifp' and `isbroadcast' were mostly harmless. gcc(1) just can't realize that these variables are either unused or really get initialized in the code path that is affected by the following conditional (let's call it "multicast destination" block), due to (probably) using goto's: if (IN_MULTICAST(ntohl(ip->ip_dst.s_addr))) { ... } This block then jumps to either `sendit' or `done' labels. `ifp' is properly initialized within the block, and `isbroadcast' wasn't used below in `sendit' and `done'. The warning for `ifp' is easily fixable. Another story is with `ia'. `ia' is used later to update per-address statistics counters: : /* Record statistics for this interface address. */ : if (!(flags & IP_FORWARDING)) { : ia->ia_ifa.if_opackets++; : ia->ia_ifa.if_obytes += m->m_pkthdr.len; : } (And yet in one place below, for "fragmentation" case.) The following patch: 1) Fixes the `ifp' warning. 2) Doesn't fix the `isbroadcast' (harmless) warning. ??? 3) Tries to fix the `ia' warning, but: What happens if the interface in question (imo->imo_multicast_ifp) doesn't have any INET addresses bound to it? IFP_TO_IA(ifp, ia) will set `ia' to 0, and the statistics code will later panic. It's unclear to me at all whether this should be allowed (multicasting over an interface with no addresses), and if yes, then the statistics code should be modified to check whether `ia' is zero or not (I've put this in the patch). But there's still race possible in the "multicast destination" block, when it initializes the unspecified (INADDR_ANY) source address of a datagram using the address of an interface. NetBSD (see below) should panic here. Index: ip_output.c =================================================================== RCS file: /home/ncvs/src/sys/netinet/ip_output.c,v retrieving revision 1.130 diff -u -p -r1.130 ip_output.c --- ip_output.c 2001/07/19 07:10:30 1.130 +++ ip_output.c 2001/07/19 10:49:09 @@ -253,14 +253,13 @@ ip_output(m0, opt, ro, flags, imo) ip->ip_ttl = 1; isbroadcast = in_broadcast(dst->sin_addr, ifp); } else if (IN_MULTICAST(ntohl(ip->ip_dst.s_addr)) && - (imo != NULL) && - (imo->imo_multicast_ifp != NULL)) { + imo != NULL && imo->imo_multicast_ifp != NULL) { /* - * bypass the normal routing lookup for - * multicast packets if the interface is - * specified + * Bypass the normal routing lookup for multicast + * packets if the interface is specified. */ - /* No Operation */ + ifp = imo->imo_multicast_ifp; + IFP_TO_IA(ifp, ia); } else { /* * If this is the case, we probably don't want to allocate @@ -303,8 +302,6 @@ ip_output(m0, opt, ro, flags, imo) */ if (imo != NULL) { ip->ip_ttl = imo->imo_multicast_ttl; - if (imo->imo_multicast_ifp != NULL) - ifp = imo->imo_multicast_ifp; if (imo->imo_multicast_vif != -1) ip->ip_src.s_addr = ip_mcast_src(imo->imo_multicast_vif); @@ -325,13 +322,9 @@ ip_output(m0, opt, ro, flags, imo) * of outgoing interface. */ if (ip->ip_src.s_addr == INADDR_ANY) { - register struct in_ifaddr *ia1; - - TAILQ_FOREACH(ia1, &in_ifaddrhead, ia_link) - if (ia1->ia_ifp == ifp) { - ip->ip_src = IA_SIN(ia1)->sin_addr; - break; - } + /* XXX: interface may have no addresses. */ + if (ia != NULL) + ip->ip_src = IA_SIN(ia)->sin_addr; } IN_LOOKUP_MULTI(ip->ip_dst, ifp, inm); @@ -824,7 +817,7 @@ pass: } /* Record statistics for this interface address. */ - if (!(flags & IP_FORWARDING)) { + if (!(flags & IP_FORWARDING) && ia) { ia->ia_ifa.if_opackets++; ia->ia_ifa.if_obytes += m->m_pkthdr.len; } @@ -964,7 +957,7 @@ sendorfree: /* clean ipsec history once it goes out of the node */ ipsec_delaux(m); #endif - if (error == 0) { + if (error == 0 && ia) { /* Record statistics for this interface address. */ ia->ia_ifa.if_opackets++; ia->ia_ifa.if_obytes += m->m_pkthdr.len; Finally, I have looked at NetBSD code, and they seem to: 1) look the route to the destination, as we did it before. 2) check that `ia' is non-zero in the per-address statistics code. 3) not check that `ia' is non-zero in the "multicast destination" block, in the following code snippet: : /* : * See if the caller provided any multicast options : */ : if (imo != NULL) { : ip->ip_ttl = imo->imo_multicast_ttl; : if (imo->imo_multicast_ifp != NULL) { : ifp = imo->imo_multicast_ifp; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ : mtu = ifp->if_mtu; : } : } else : ip->ip_ttl = IP_DEFAULT_MULTICAST_TTL; [...] : /* : * If source address not specified yet, use an address : * of outgoing interface. : */ : if (in_nullhost(ip->ip_src)) { : struct in_ifaddr *ia; : IFP_TO_IA(ifp, ia); : ip->ip_src = ia->ia_addr.sin_addr; : } There's a race in the last two lines if `ifp' doesn't have addresses bound. Sorry, I'm not too familiar with the multicast code, so probably some MCAST geeks like Bill Fenner could speak up? :-) Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 4:13: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 64ADE37B401 for ; Thu, 19 Jul 2001 04:13:04 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id NAA69821; Thu, 19 Jul 2001 13:13:03 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6JBD2N01448; Thu, 19 Jul 2001 13:13:02 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Thu, 19 Jul 2001 13:13:02 +0200 From: Christophe Prévotaux To: Bill Fumerola Cc: net@freebsd.org Subject: Re: MPLS Message-Id: <20010719131302.292b8c2f.c.prevotaux@hexanet.fr> In-Reply-To: <20010719045321.U2759@elvis.mu.org> References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> <20010718204608.R2759@elvis.mu.org> <20010719112514.7fae3f50.c.prevotaux@hexanet.fr> <20010719045321.U2759@elvis.mu.org> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 19 Jul 2001 04:53:21 -0500 Bill Fumerola wrote: > On Thu, Jul 19, 2001 at 11:25:14AM +0200, Christophe Prévotaux wrote: > > What is mostly wrong ? > > mpls is done as a filter-based forward in junos, not much different > then the firewall component of junos. this is all done on the IP-II. > > so did you actually setup a network of these machines? if that worked, > they have some sort of emulation layer in the absence of the IP-II. > I was pretty sure such an emulation layer existed, but to my knowledge > only in developer builds. > > in any event, juniper isn't going to part with any of that code. Well I agree, but they are not going to hold on to it forever when MPLS comes out in Linux which I am sure will happen, then their advantage will be lessened on that side, I don't think their only advantage comes from their software the hardware architecture (ASICS et all) is also clearly a differentiation point. Of course one can argue that their software and their algorithms may also be better implemented than a linux or freebsd solution, but that is not sure. Right now almost no one has interest in MPLS (except telcos and large operator or ISP) but I am confident that this will change. > > > Why don't you just try to get your hands on > > a JunOS 4.4 and install it over a 4.x FreeBSD > > and see by yourself ? > > because if I was going to do that, I'd just install olive. Olive is used for Training , a plain JunOS 4.4 works just as well with full features > > and just because you install it over 4.x freebsd and it works, doesn't > mean its 4.x freebsd based, it means you have a working a.out interpreter. > > -- > Bill Fumerola - security yahoo / Yahoo! inc. > - fumerola@yahoo-inc.com / billf@FreeBSD.org > > > > -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 6:58:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id A946A37B401 for ; Thu, 19 Jul 2001 06:58:20 -0700 (PDT) (envelope-from csg@waterspout.com) Received: from dustdevil.waterspout.com (squall.waterspout.com [208.13.56.12]) by squall.waterspout.com (Postfix) with ESMTP id 7F4949B17 for ; Thu, 19 Jul 2001 08:57:58 -0500 (EST) Received: (from csg@localhost) by dustdevil.waterspout.com (8.11.4/8.11.2) id f6JDwlx41787; Thu, 19 Jul 2001 08:58:47 -0500 (EST) (envelope-from csg@waterspout.com) X-Authentication-Warning: dustdevil.waterspout.com: csg set sender to csg@waterspout.com using -f Date: Thu, 19 Jul 2001 08:57:27 -0500 From: "C. Stephen Gunn" To: Brooks Davis Cc: net@FreeBSD.ORG Subject: Re: sysctl net.link.vlan.link.proto Message-ID: <20010719085727.A41774@progeny.com> References: <20010713171342.A18472@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010713171342.A18472@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Fri, Jul 13, 2001 at 05:13:42PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Jul 13, 2001 at 05:13:42PM -0700, Brooks Davis wrote: > I'm working on modernizing the vlan device (making it loadable, > unloadable, and clonable) and I've run into this sysctl. This shoud allow you to move the check for 802.1q packets down into the normal ether_demux() which classifies packets based on ethertype. The former code was a check right above the main switch statement in ether_demux() because it was a sysctl, not a constant. I have some other patches around that ease the interrupt-time requirements by scheduling a NETISR for vlan traffic. I wasn't ever sure if that was a true win, so I didn't contrib them. I could dig them up if you're really interested in spiffing up the VLAN code. ;-) - Steve -- C. Stephen Gunn | Waterspout Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 8:41:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 56B8337B405; Thu, 19 Jul 2001 08:41:17 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id B76101E24B; Thu, 19 Jul 2001 11:41:12 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id LAA04616; Thu, 19 Jul 2001 11:41:11 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id IAA12475; Thu, 19 Jul 2001 08:41:10 -0700 (PDT) Message-Id: <200107191541.IAA12475@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: ru@freebsd.org Subject: Re: cvs commit: src/sys/netinet ip_output.c Cc: bde@zeta.org.au, kris@obsecurity.org, dcs@freebsd.org, net@freebsd.org References: <200107190710.f6J7AVl44738@freefall.freebsd.org> <20010719011806.A28830@xor.obsecurity.org> <20010719135423.G69276@sunbay.com> Date: Thu, 19 Jul 2001 08:41:10 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Sorry, I'm not too familiar with the multicast code, so probably >some MCAST geeks like Bill Fenner could speak up? :-) Boy, has this code ever evolved since 1997 =) I haven't had a chance to look at this yet (tomorrow's Internet-Draft deadline is crushing me right now), but I think ruslan's analysis is correct (in particular, it should be allowed to send a multicast with all-zeroes source address on an interface with no addresses). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 9: 8:20 2001 Delivered-To: freebsd-net@freebsd.org Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129]) by hub.freebsd.org (Postfix) with ESMTP id DA67E37B406 for ; Thu, 19 Jul 2001 09:08:17 -0700 (PDT) (envelope-from pingpan@juniper.net) Received: from juniper.net ([172.16.167.234]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id f6JG7jH80518; Thu, 19 Jul 2001 09:07:45 -0700 (PDT) (envelope-from pingpan@juniper.net) Message-ID: <3B570742.BFF70763@juniper.net> Date: Thu, 19 Jul 2001 09:13:54 -0700 From: Ping Pan Organization: Juniper Networks X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christophe =?iso-8859-1?Q?Pr=E9votaux?= Cc: net@FreeBSD.ORG Subject: Re: MPLS References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> <20010718204608.R2759@elvis.mu.org> <20010719112514.7fae3f50.c.prevotaux@hexanet.fr> <20010719045321.U2759@elvis.mu.org> <20010719131302.292b8c2f.c.prevotaux@hexanet.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Christophe Prévotaux" wrote: > > Of course one can argue that their software and their algorithms may also be better > implemented than a linux or freebsd solution, but that is not sure. OK. So why don't you stop speculating, implement it yourself and benchmark it against Junos? :-) > Right now almost no one has interest in MPLS (except telcos and large operator or ISP) > but I am confident that this will change. > Will that change before or after we see your MPLS implementation? :-) - Ping To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 9:17:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 5D83437B401 for ; Thu, 19 Jul 2001 09:17:39 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f6JGHVn08972; Thu, 19 Jul 2001 12:17:31 -0400 (EDT) (envelope-from wollman) Date: Thu, 19 Jul 2001 12:17:31 -0400 (EDT) From: Garrett Wollman Message-Id: <200107191617.f6JGHVn08972@khavrinen.lcs.mit.edu> To: "C. Stephen Gunn" Cc: Brooks Davis , net@FreeBSD.ORG Subject: Re: sysctl net.link.vlan.link.proto In-Reply-To: <20010719085727.A41774@progeny.com> References: <20010713171342.A18472@Odin.AC.HMC.Edu> <20010719085727.A41774@progeny.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > I have some other patches around that ease the interrupt-time requirements > by scheduling a NETISR for vlan traffic. I wasn't ever sure if that was > a true win, so I didn't contrib them. I think it's actually a substantial lose, since all that will happen is that the VLAN code will spin for a cycle or two to locate the correct pseudo-interface and then stick the decapsulated packet on a different soft ISR's queue instead. Better to decapsulate immediately and avoid an extra queueing step. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 9:32:16 2001 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 6EBDA37B403 for ; Thu, 19 Jul 2001 09:32:13 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f6JGWBV09171; Thu, 19 Jul 2001 12:32:11 -0400 (EDT) (envelope-from wollman) Date: Thu, 19 Jul 2001 12:32:11 -0400 (EDT) From: Garrett Wollman Message-Id: <200107191632.f6JGWBV09171@khavrinen.lcs.mit.edu> To: Bill Fenner Cc: net@FreeBSD.ORG Subject: Re: cvs commit: src/sys/netinet ip_output.c In-Reply-To: <200107191541.IAA12475@windsor.research.att.com> References: <200107190710.f6J7AVl44738@freefall.freebsd.org> <20010719011806.A28830@xor.obsecurity.org> <20010719135423.G69276@sunbay.com> <200107191541.IAA12475@windsor.research.att.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org < said: > correct (in particular, it should be allowed to send a multicast with > all-zeroes source address on an interface with no addresses). It should also be allowed to send a broadcast with a zero source on such an interface -- something which has been broken since The Dawn of Time so far as I can tell. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 11:18: 8 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 939D937B40C for ; Thu, 19 Jul 2001 11:18:01 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id UAA81249 for ; Thu, 19 Jul 2001 20:18:00 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6JII0N02745 for ; Thu, 19 Jul 2001 20:18:00 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Thu, 19 Jul 2001 20:18:00 +0200 From: Christophe Prévotaux To: net@freebsd.org Subject: G703 PCI Card Message-Id: <20010719201800.5a80a1a3.c.prevotaux@hexanet.fr> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I am looking for a G703 capable PCI interface card supported by FreeBSD does such a thing exists ? -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 11:34:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3042C37B43E for ; Thu, 19 Jul 2001 11:34:49 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id UAA81431 for ; Thu, 19 Jul 2001 20:34:48 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6JIYmN02803 for ; Thu, 19 Jul 2001 20:34:48 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Thu, 19 Jul 2001 20:34:48 +0200 From: Christophe Prévotaux To: net@freebsd.org Subject: Re: MPLS Message-Id: <20010719203448.27f86d69.c.prevotaux@hexanet.fr> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org oh oh , I did not say I would and I am quite incapable of implementing MPLS, but I don't understand what triggered your anger at me ? On Thu, 19 Jul 2001 09:13:54 -0700 Ping Pan wrote: > "Christophe Prévotaux" wrote: > > > > Of course one can argue that their software and their algorithms may also be better > > implemented than a linux or freebsd solution, but that is not sure. > > OK. So why don't you stop speculating, implement it yourself and > benchmark it against Junos? :-) Why are you so vindicative ? Don't you think such a thing as a FreeBSD MPLS implementation could ever exists ? I consider it would be a good thing and I see no reason why in the end it would not be equal or better than JunOS ? Can you explain why you think it is not possible ? I mean apart from the fact that you work at Juniper and you are trying to defend their products which in itself is understandable. At least I(we) could maybe learn something then . I know that a FreeBSD based MPLS solution can not rival with a Juniper Hardware and that is not the point, but one could at least use any PCI based interface card with it (even if it does not do 160 Gbps it would still be useful) > > > Right now almost no one has interest in MPLS (except telcos and large operator or ISP) > > but I am confident that this will change. > > > > Will that change before or after we see your MPLS implementation? :-) unfortunately , I think you will never see it in this lifetime because as I said earlier I don't the technical abilities to make such a implementation and I won't even try to. But that does not mean I can't speak about it after all we all live in free countries and all have the right to free speech no ? > > - Ping > -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 13:56:27 2001 Delivered-To: freebsd-net@freebsd.org Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129]) by hub.freebsd.org (Postfix) with ESMTP id 38A1637B401 for ; Thu, 19 Jul 2001 13:56:23 -0700 (PDT) (envelope-from pingpan@juniper.net) Received: from juniper.net (panther.juniper.net [172.17.12.226]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id f6JKtpH97759; Thu, 19 Jul 2001 13:55:51 -0700 (PDT) (envelope-from pingpan@juniper.net) Message-ID: <3B574957.97AE126E@juniper.net> Date: Thu, 19 Jul 2001 13:55:51 -0700 From: Ping Pan Organization: Juniper Networks X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Christophe =?iso-8859-1?Q?Pr=E9votaux?= Cc: net@FreeBSD.ORG Subject: Re: MPLS References: <20010719203448.27f86d69.c.prevotaux@hexanet.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry, there was no anger. I am not comfortable to see non-technical speculation on freebsd lists. I come on to the list to see what's cool lately in FreeBSD. If I want to gossip about company, Linux and market future etc., , I'd have gone to other lists.... Could we stop this thread now? Many thanks! - Ping "Christophe Prévotaux" wrote: > > oh oh , I did not say I would and I am quite incapable of implementing > MPLS, but I don't understand what triggered your anger at me ? > > On Thu, 19 Jul 2001 09:13:54 -0700 > Ping Pan wrote: > > > "Christophe Prévotaux" wrote: > > > > > > Of course one can argue that their software and their algorithms may also be better > > > implemented than a linux or freebsd solution, but that is not sure. > > > > OK. So why don't you stop speculating, implement it yourself and > > benchmark it against Junos? :-) > > Why are you so vindicative ? Don't you think such a thing as a FreeBSD MPLS implementation > could ever exists ? I consider it would be a good thing and I see no reason why in the end > it would not be equal or better than JunOS ? Can you explain why you think it is not possible ? > I mean apart from the fact that you work at Juniper and you are trying to defend their products > which in itself is understandable. > > At least I(we) could maybe learn something then . > > I know that a FreeBSD based MPLS solution can not rival with a Juniper Hardware > and that is not the point, but one could at least use any PCI based interface card > with it (even if it does not do 160 Gbps it would still be useful) > > > > > > Right now almost no one has interest in MPLS (except telcos and large operator or ISP) > > > but I am confident that this will change. > > > > > > > Will that change before or after we see your MPLS implementation? :-) > > unfortunately , I think you will never see it in this lifetime because > as I said earlier I don't the technical abilities to make such a implementation > and I won't even try to. But that does not mean I can't speak about it > after all we all live in free countries and all have the right to free speech > no ? > > > > > - Ping > > > > -- > =================================================================== > Christophe Prevotaux Email: c.prevotaux@hexanet.fr > HEXANET SARL URL: http://www.hexanet.fr/ > Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 > 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 > BP415 Fax: +33 (0)3 26 79 30 06 > 51689 Reims Cedex 2 > FRANCE > =================================================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 18:39: 2 2001 Delivered-To: freebsd-net@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id EB4A537B405 for ; Thu, 19 Jul 2001 18:38:50 -0700 (PDT) (envelope-from chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id f6K1clV72266 for ; Fri, 20 Jul 2001 11:38:47 +1000 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.3.R) for ; Fri, 20 Jul 2001 11:37:28 +1000 Reply-To: From: "Chris Knight" To: Subject: RE: G703 PCI Card Date: Fri, 20 Jul 2001 11:37:27 +1000 Message-ID: <007e01c110bc$892872b0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010719201800.5a80a1a3.c.prevotaux@hexanet.fr> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-net@freebsd.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Howdy, SBE (www.sbe.com) have one - the wanADAPT-1T1E1. Has drivers for FreeBSD, NetBSD, Linux and Solaris. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Christophe > Privotaux > Sent: Friday, 20 July 2001 4:18 > To: net@FreeBSD.ORG > Subject: G703 PCI Card > > > I am looking for a G703 capable PCI interface card supported > by FreeBSD > does such a thing exists ? > > -- > =================================================================== > Christophe Prevotaux Email: c.prevotaux@hexanet.fr > HEXANET SARL URL: http://www.hexanet.fr/ > Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 > 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 > BP415 Fax: +33 (0)3 26 79 30 06 > 51689 Reims Cedex 2 > FRANCE > =================================================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 18:48:43 2001 Delivered-To: freebsd-net@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id ECA6B37B406 for ; Thu, 19 Jul 2001 18:48:34 -0700 (PDT) (envelope-from chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.10.2]) by postoffice.aims.com.au with ESMTP id f6K1mXV72312 for ; Fri, 20 Jul 2001 11:48:33 +1000 (EST) (envelope-from chris@aims.com.au) Received: from ntsts1 by aims.com.au with SMTP (MDaemon.v3.5.3.R) for ; Fri, 20 Jul 2001 11:47:57 +1000 Reply-To: From: "Chris Knight" To: Subject: RE: G703 PCI Card Date: Fri, 20 Jul 2001 11:47:55 +1000 Message-ID: <007f01c110bd$ffc37ef0$020aa8c0@aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <007e01c110bc$892872b0$020aa8c0@aims.private> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal X-Return-Path: chris@aims.com.au X-MDaemon-Deliver-To: freebsd-net@freebsd.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Howdy, Sorry, wrong URL. Try www.sbei.com. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Chris Knight > Sent: Friday, 20 July 2001 11:37 > To: freebsd-net@FreeBSD.ORG > Subject: RE: G703 PCI Card > > > Howdy, > > SBE (www.sbe.com) have one - the wanADAPT-1T1E1. Has drivers > for FreeBSD, > NetBSD, Linux and Solaris. > > Regards, > Chris Knight > Systems Administrator > AIMS Independent Computer Professionals > Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 > Web: http://www.aims.com.au > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 19:33: 4 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 7DB8A37B407 for ; Thu, 19 Jul 2001 19:33:00 -0700 (PDT) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.11.2/8.11.1) with SMTP id f6K2Wxc17621; Thu, 19 Jul 2001 22:32:59 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: fenner@research.att.com (Bill Fenner) Cc: freebsd-net@freebsd.org Subject: Re: 802.1q and multicasting Date: Thu, 19 Jul 2001 22:32:58 -0400 Message-ID: <5u5fltgbumrpo82hbfs98nluu5riv5mtd6@4ax.com> References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 18 Jul 2001 11:53:46 -0400, in sentex.lists.freebsd.net you wrote: > >The vlan driver doesn't set up the multicast filters correctly on >the underlying interface. I've got a patch sitting in my CVS tree >that I should probably just commit... Hi, On a different issue, do you have any patches by chance that fix the issue of runt frames discussed at http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D226447+229060+/usr/local/ww= w/db/text/2000/freebsd-net/20000528.freebsd-net ... "But there's another problem with small ip packet. When BSD router strip ethernet header for payload < 46 it strip padding bytes also. But when it reinserted data with another vlan header it don't add padding bytes and we have runts packets on interface..." Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 20: 1:44 2001 Delivered-To: freebsd-net@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id DC31F37B406 for ; Thu, 19 Jul 2001 20:01:42 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id B8F7E4DDC3; Thu, 19 Jul 2001 23:01:36 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id XAA17989; Thu, 19 Jul 2001 23:01:36 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id UAA24883; Thu, 19 Jul 2001 20:01:35 -0700 (PDT) Message-Id: <200107200301.UAA24883@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: mike@sentex.net Subject: Re: 802.1q and multicasting Cc: freebsd-net@freebsd.org References: <5u5fltgbumrpo82hbfs98nluu5riv5mtd6@4ax.com> Date: Thu, 19 Jul 2001 20:01:35 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry, no, I can't answer these problems. I'm still working on getting multicast completely working. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Jul 19 20:10:38 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id E31A637B405 for ; Thu, 19 Jul 2001 20:10:35 -0700 (PDT) (envelope-from mike@sentex.net) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.11.2/8.11.1) with SMTP id f6K3AIc25316; Thu, 19 Jul 2001 23:10:18 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: c.prevotaux@hexanet.fr (=?ISO-8859-1?Q?Christophe_Pr=E9votaux?=) Cc: freebsd-net@freebsd.org Subject: Re: MPLS Date: Thu, 19 Jul 2001 23:10:18 -0400 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 18 Jul 2001 06:35:39 -0400, in sentex.lists.freebsd.net you wrote: >Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented >under FreeBSD ?=20 No idea, but there is _talk_ about it from time to time on www.zebra.org ---Mike Mike Tancsa (mdtancsa@sentex.net) =09 Sentex Communications Corp, =09 Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers=20 could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 2:32:34 2001 Delivered-To: freebsd-net@freebsd.org Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165]) by hub.freebsd.org (Postfix) with ESMTP id 44B3137B401 for ; Fri, 20 Jul 2001 02:32:32 -0700 (PDT) (envelope-from raviprasad20@netscape.net) Received: from raviprasad20@netscape.net by imo-m10.mx.aol.com (mail_out_v31.7.) id n.c7.86a987 (16213) for ; Fri, 20 Jul 2001 05:32:24 -0400 (EDT) Received: from netscape.com (mow-m05.webmail.aol.com [64.12.184.133]) by air-in01.mail.aol.com (v79.27) with ESMTP id MAILININ11-0720053223; Fri, 20 Jul 2001 05:32:23 -0400 Date: Fri, 20 Jul 2001 05:32:23 -0400 From: raviprasad20@netscape.net To: freebsd-net@freebsd.org Subject: addresses ::1/128 and ff01::/32 Message-ID: <2FAB92FB.78BCF400.9513E96F@netscape.net> X-Mailer: Atlas Mailer 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, The following lines are from the Kame implementation notes "Each interface joins the solicited multicast address and the link-local all-nodes multicast addresses (e.g. fe80::1:ff01:6317 and ff02::1, respectively, on the link the interface is attached). In addition to a link-local address, the loopback address (::1) will be assigned to the loopback interface. Also, ::1/128 and ff01::/32 are automatically added to routing table, and loopback interface joins node-local multicast group ff01::1." Can anybody please mail me why ::1/128 & ff01::/32 addresses are put to the routing table? what does "128" and "32" indicate? regards ravi prasad __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 2:50:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from imo-m01.mx.aol.com (imo-m01.mx.aol.com [64.12.136.4]) by hub.freebsd.org (Postfix) with ESMTP id 7A75037B405 for ; Fri, 20 Jul 2001 02:50:52 -0700 (PDT) (envelope-from raviprasad20@netscape.net) Received: from raviprasad20@netscape.net by imo-m01.mx.aol.com (mail_out_v31.9.) id n.af.85d6fb (16239) for ; Fri, 20 Jul 2001 05:50:46 -0400 (EDT) Received: from netscape.com (mow-m01.webmail.aol.com [64.12.184.129]) by air-in03.mail.aol.com (v79.27) with ESMTP id MAILININ33-0720055045; Fri, 20 Jul 2001 05:50:45 -0400 Date: Fri, 20 Jul 2001 05:50:45 -0400 From: raviprasad20@netscape.net To: freebsd-net@freebsd.org Subject: why mbuf? Message-ID: <7F8F8796.33735BFF.9513E96F@netscape.net> X-Mailer: Atlas Mailer 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, My question is why did you choose mbuf? is it because you are writing the code in unix systems? Is it because mbufs allow us to avoid coping as much as possible? I feel that a linear buffer might have saved some of the mbuf modifications. regards ravi prasad __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 3:45:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailserver.KOM.e-technik.tu-darmstadt.de (drum.kom.e-technik.tu-darmstadt.de [130.83.139.190]) by hub.freebsd.org (Postfix) with ESMTP id B5C8A37B405 for ; Fri, 20 Jul 2001 03:45:09 -0700 (PDT) (envelope-from Martin.Karsten@KOM.tu-darmstadt.de) Received: from KOM.tu-darmstadt.de by mailserver.KOM.e-technik.tu-darmstadt.de (8.7.5/8.7.5) with ESMTP id MAA28155; Fri, 20 Jul 2001 12:45:06 +0200 (MET DST) From: Martin Karsten Received: from KOM.tu-darmstadt.de by KOM.tu-darmstadt.de (8.9.3/8.7.5) id MAA03987; Fri, 20 Jul 2001 12:45:06 +0200 Message-Id: <200107201045.MAA03987@KOM.tu-darmstadt.de> Subject: Re: MPLS In-Reply-To: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> from =?ISO-8859-1?Q?Christophe_Pr=E9votaux?= at "Jul 18, 2001 12:35:25 pm" To: =?ISO-8859-1?Q?Christophe_Pr=E9votaux?= Date: Fri, 20 Jul 2001 12:45:06 +0200 (CEST) Cc: net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org MPLS has been implemented for FreeBSD in the Nistswitch project http://www.antd.nist.gov/itg/nistswitch/ but I don't know the current project status. I've added rudimentary MPLS signalling support to RSVP (label distribution and explicit routing according to draft-ietf-mpls-rsvp-lsp-tunnel-07.txt), but the code has not been released yet. It works with two Linux-based MPLS forwarding planes and I'm ready to integrate it with any current FreeBSD forwarding plane, if such a thing becomes available. If you are interested, please have a look at http://www.kom.e-technik.tu-darmstadt.de/rsvp once in a while. Greetings, Martin > Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented > under FreeBSD ? > > I know that Juniper has implemented them and whole bunch of other > neat thing over FreeBSD and that the latest JUNOS is a somewhat modified > FreeBSD 4.x > > Is anyone (or maybe Juniper ? :)) working on implementing this under FreeBSD ? > > Also when will AltQ be part of the FreeBSD system ? > > > > -- > =================================================================== > Christophe Prevotaux Email: c.prevotaux@hexanet.fr > HEXANET SARL URL: http://www.hexanet.fr/ > Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 > 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 > BP415 Fax: +33 (0)3 26 79 30 06 > 51689 Reims Cedex 2 > FRANCE > =================================================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 5:10:31 2001 Delivered-To: freebsd-net@freebsd.org Received: from ns1.hexanet.fr (ns1.hexanet.fr [194.98.140.1]) by hub.freebsd.org (Postfix) with ESMTP id C0EBF37B401 for ; Fri, 20 Jul 2001 05:10:24 -0700 (PDT) (envelope-from c.prevotaux@hexanet.fr) Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by ns1.hexanet.fr (8.9.3/8.9.3) with ESMTP id OAA96461; Fri, 20 Jul 2001 14:10:20 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.11.2/8.11.2) with SMTP id f6KCAKe01908; Fri, 20 Jul 2001 14:10:20 +0200 (CEST) (envelope-from c.prevotaux@hexanet.fr) Date: Fri, 20 Jul 2001 14:10:19 +0200 From: Christophe Prévotaux To: Martin Karsten Cc: net@FreeBSD.ORG Subject: Re: MPLS Message-Id: <20010720141019.36efa1a9.c.prevotaux@hexanet.fr> In-Reply-To: <200107201045.MAA03987@KOM.tu-darmstadt.de> References: <20010718123525.7df2028c.c.prevotaux@hexanet.fr> <200107201045.MAA03987@KOM.tu-darmstadt.de> X-Mailer: Sylpheed version 0.4.66 (GTK+ 1.2.7; i386--freebsd4.2) Organization: HEXANET Sarl Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 20 Jul 2001 12:45:06 +0200 (CEST) Martin Karsten wrote: > MPLS has been implemented for FreeBSD in the Nistswitch project > http://www.antd.nist.gov/itg/nistswitch/ > but I don't know the current project status. > > I've added rudimentary MPLS signalling support to RSVP (label distribution > and explicit routing according to draft-ietf-mpls-rsvp-lsp-tunnel-07.txt), isn't it http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-tunnel-08.txt ? 07 does not seem to exist Maybe you already know about all this stuff: http://www.mplsforum.org http://www.mplsrc.com http://www.mplsworld.com But I just thought i'd put it here , for other people who might have an interest in either knowing what is MPLS or for others that are looking for technical ressources in order to implement it or use it. > but the code has not been released yet. It works with two Linux-based MPLS > forwarding planes and I'm ready to integrate it with any current FreeBSD > forwarding plane, if such a thing becomes available. If you are interested, > please have a look at > http://www.kom.e-technik.tu-darmstadt.de/rsvp > once in a while. > > Greetings, > Martin > > > Will MPLS and MPLS-TE (and MPLS VPL L2 and L3) be implemented > > under FreeBSD ? > > > > I know that Juniper has implemented them and whole bunch of other > > neat thing over FreeBSD and that the latest JUNOS is a somewhat modified > > FreeBSD 4.x > > > > Is anyone (or maybe Juniper ? :)) working on implementing this under FreeBSD ? > > > > Also when will AltQ be part of the FreeBSD system ? > > > > > > > > -- > > =================================================================== > > Christophe Prevotaux Email: c.prevotaux@hexanet.fr > > HEXANET SARL URL: http://www.hexanet.fr/ > > Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 > > 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 > > BP415 Fax: +33 (0)3 26 79 30 06 > > 51689 Reims Cedex 2 > > FRANCE > > =================================================================== > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > > > -- =================================================================== Christophe Prevotaux Email: c.prevotaux@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 5:21:14 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailguard.fgan.de (mailguard.fgan.de [128.7.3.5]) by hub.freebsd.org (Postfix) with ESMTP id B24E037B403 for ; Fri, 20 Jul 2001 05:21:11 -0700 (PDT) (envelope-from leventi@fgan.de) Received: from rufsun5.ffm.fgan.de ([128.7.2.5]) by mailguard.fgan.de (8.11.2/8.11.2) with ESMTP id f6KCL6Y09085 for ; Fri, 20 Jul 2001 14:21:06 +0200 Received: from melle.fkie.fgan.de (melle.ffm.fgan.de [128.7.5.11]) by rufsun5.ffm.fgan.de (8.8.6/8.8.8) with ESMTP id OAA08372; Fri, 20 Jul 2001 14:21:06 +0200 (MET DST) Received: (from lev@localhost) by melle.fkie.fgan.de (8.10.2+Sun/8.10.2) id f6KCL5C03383; Fri, 20 Jul 2001 14:21:05 +0200 (MEST) Date: Fri, 20 Jul 2001 14:21:05 +0200 (MEST) Message-Id: <200107201221.f6KCL5C03383@melle.fkie.fgan.de> From: Anastasia Leventi-Peetz To: freebsd-net@freebsd.org Cc: leventi@fgan.de, karg@fgan.de Subject: address autoconfiguration and Generic Kernel Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have tried to start address autoconfiguration on my FreeBSD-4.0 system by putting ip6mode="autohost" rtsol="YES" rtsol_flags="sm1" # set your interface here in rc.conf and rebooting the system. After reboot I still had only Link-Local-Address only, though a router makes advertisement in Net. Then I started per hand rtsol -d interfacename and got that the kernel is not accepting router advertisements. I tried to build a custom kernel, to edit KERNEL in /usr/src/sys/i386/conf but there is nop available option to make router or host out of it. The file LINT with more options doesn't give anything in thr direction, and the suggested documents http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html are also not helpful. Does anybody know an advise? thanks in advance:Anastasia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 6:48:47 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailguard.fgan.de (mailguard.fgan.de [128.7.3.5]) by hub.freebsd.org (Postfix) with ESMTP id 69E3E37B401 for ; Fri, 20 Jul 2001 06:48:44 -0700 (PDT) (envelope-from leventi@fgan.de) Received: from rufsun5.ffm.fgan.de ([128.7.2.5]) by mailguard.fgan.de (8.11.2/8.11.2) with ESMTP id f6KDmgY13447 for ; Fri, 20 Jul 2001 15:48:42 +0200 Received: from melle.fkie.fgan.de (melle.ffm.fgan.de [128.7.5.11]) by rufsun5.ffm.fgan.de (8.8.6/8.8.8) with ESMTP id PAA10512; Fri, 20 Jul 2001 15:48:41 +0200 (MET DST) Received: (from lev@localhost) by melle.fkie.fgan.de (8.10.2+Sun/8.10.2) id f6KDmea03483; Fri, 20 Jul 2001 15:48:40 +0200 (MEST) Date: Fri, 20 Jul 2001 15:48:40 +0200 (MEST) Message-Id: <200107201348.f6KDmea03483@melle.fkie.fgan.de> From: Anastasia Leventi-Peetz To: freebsd-net@FreeBSD.ORG Cc: leventi@fgan.de In-reply-to: <200107201221.f6KCL5C03383@melle.fkie.fgan.de> (message from Anastasia Leventi-Peetz on Fri, 20 Jul 2001 14:21:05 +0200 (MEST)) Subject: Re: address autoconfiguration and Generic Kernel Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >I have tried to start address autoconfiguration on my FreeBSD-4.0 system >by putting >ip6mode="autohost" >rtsol="YES" rtsol_flags="xl0" # set your interface here >in rc.conf and rebooting the system. >After reboot I still had only Link-Local-Address only, though a router makes >advertisement in Net. Then I started per hand rtsol -d interfacename >and got that the kernel is not accepting router advertisements. >I tried to build a custom kernel, to edit KERNEL in >/usr/src/sys/i386/conf >but there is nop available option to make router or host >out of it. The file LINT with more options >doesn't give anything in thr direction, and the suggested documents Sorry for the inconvenience. I have changed net.inet6.ip6.accept_rtadv=1 in /etc/rc.network6 and interactively with sysctl -w net.inet6.ip6.accept_rtadv=1 and it has worked with the stateless address autoconfiguration. Still I believe the message was misleading. In the case of Linux SuSe it is in fact a matter of kernel Configuration. Here it is probably not. One doesn't reconfigure the kernel with sysctl. Anastasia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 6:53:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from smtp2.enst.fr (matrix2.enst.fr [137.194.2.14]) by hub.freebsd.org (Postfix) with ESMTP id C637C37B405 for ; Fri, 20 Jul 2001 06:53:23 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from email.enst.fr (muse.enst.fr [137.194.2.33]) by smtp2.enst.fr (Postfix) with ESMTP id 7A1B67D1B; Fri, 20 Jul 2001 15:53:20 +0200 (MEST) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by email.enst.fr (8.9.3/8.9.3) with ESMTP id PAA11889; Fri, 20 Jul 2001 15:53:21 +0200 (MET DST) Received: (from beyssac@localhost) by bofh.enst.fr (8.11.3/8.11.3) id f6KDrKc79172; Fri, 20 Jul 2001 15:53:20 +0200 (CEST) (envelope-from beyssac) Date: Fri, 20 Jul 2001 15:53:20 +0200 From: Pierre Beyssac To: =?iso-8859-1?Q?Christophe_Pr=E9votaux?= Cc: net@FreeBSD.ORG Subject: Re: G703 PCI Card Message-ID: <20010720155320.A78913@bofh.enst.fr> References: <20010719201800.5a80a1a3.c.prevotaux@hexanet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010719201800.5a80a1a3.c.prevotaux@hexanet.fr>; from c.prevotaux@hexanet.fr on Thu, Jul 19, 2001 at 08:18:00PM +0200 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jul 19, 2001 at 08:18:00PM +0200, Christophe Prévotaux wrote: > I am looking for a G703 capable PCI interface card supported by FreeBSD > does such a thing exists ? Depends on what kind of link you want to put this on. I'm looking for the same thing (for a E3 link) and I have found the following: - the WANic cards by Lightstream (www.imagestream.com). They told me they provide a Linux driver with sources, should be portable to FreeBSD. - the SBEI cards (ex Lanmedia) (www.sbei.net), but they don't do E3, only E1/T1/T3. - Emerging Technologies (www.etinc.com) also have nice cards, with a HSSI interface instead of BNC G703, and it's not clear at all from their website whether or not they can do E3. I'm haven't tried any of those, currently. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 7:52:45 2001 Delivered-To: freebsd-net@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 277E937B405 for ; Fri, 20 Jul 2001 07:52:41 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.3+3.4W/8.11.3/light) with UUCP id f6KEqO020272; Fri, 20 Jul 2001 23:52:24 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from peace.mahoroba.org (IDENT:AD5lsZOoBmXv3MU+2mCohdZtiuVOA4VZf8bqEMtUzoMOq9kGnlzs1RpyL6NkGDe1@peace.mahoroba.org [3ffe:505:2:0:200:f8ff:fe05:3eae]) (authenticated as ume with CRAM-MD5) by mail.mahoroba.org (8.11.4/8.11.4/chaos) with ESMTP/inet6 id f6KEq9L15194; Fri, 20 Jul 2001 23:52:09 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Fri, 20 Jul 2001 23:52:08 +0900 (JST) Message-Id: <20010720.235208.101781550.ume@mahoroba.org> To: leventi@fgan.de Cc: freebsd-net@freebsd.org, karg@fgan.de Subject: Re: address autoconfiguration and Generic Kernel From: Hajimu UMEMOTO In-Reply-To: <200107201221.f6KCL5C03383@melle.fkie.fgan.de> References: <200107201221.f6KCL5C03383@melle.fkie.fgan.de> X-Mailer: xcite1.38> Mew version 1.95b119 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-Operating-System: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Fri, 20 Jul 2001 14:21:05 +0200 (MEST) >>>>> Anastasia Leventi-Peetz said: leventi> I have tried to start address autoconfiguration on my FreeBSD-4.0 system leventi> by putting leventi> ip6mode="autohost" leventi> rtsol="YES" rtsol_flags="sm1" # set your interface here leventi> in rc.conf and rebooting the system. It seems you specified as NetBSD manner. Please put ipv6_enable="YES" and ipv6_network_interfaces="sm1" in your rc.conf. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 11:18:19 2001 Delivered-To: freebsd-net@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id A350837B406 for ; Fri, 20 Jul 2001 11:18:14 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA05453; Fri, 20 Jul 2001 13:11:31 -0700 (PDT) Date: Fri, 20 Jul 2001 13:11:30 -0700 (PDT) From: Julian Elischer To: raviprasad20@netscape.net Cc: freebsd-net@freebsd.org Subject: Re: why mbuf? In-Reply-To: <7F8F8796.33735BFF.9513E96F@netscape.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Do you mean why did the original BSD people choose the methos used in the mbuf code in 1982 (or whenever)? 1/ copying data is a waste of time 2/ incoming packets are of unpredictable size but tend to be either full-size or small with few in between. 3/ memory was expensive and slow On Fri, 20 Jul 2001 raviprasad20@netscape.net wrote: > Hi, > > My question is why did you choose mbuf? > is it because you are writing the code in unix systems? > Is it because mbufs allow us to avoid coping as much as possible? > > I feel that a linear buffer might have saved some of the mbuf > modifications. > > regards > ravi prasad > > > > __________________________________________________________________ > Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ > > Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 11:49:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id BB0CD37B401 for ; Fri, 20 Jul 2001 11:49:54 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from itojun.org (localhost [127.0.0.1]) by coconut.itojun.org (Postfix) with ESMTP id 4ED554B28; Sat, 21 Jul 2001 03:49:46 +0900 (JST) To: raviprasad20@netscape.net, freebsd-net@freebsd.org In-reply-to: julian's message of Fri, 20 Jul 2001 13:11:30 MST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: why mbuf? From: itojun@iijlab.net Date: Sat, 21 Jul 2001 03:49:45 +0900 Message-ID: <9681.995654985@itojun.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> My question is why did you choose mbuf? >> is it because you are writing the code in unix systems? >> Is it because mbufs allow us to avoid coping as much as possible? >> >> I feel that a linear buffer might have saved some of the mbuf >> modifications. general suggestion: you send a lot of questions to the list these days, but most of them are answered in books by Richard Stevens. I suggest you to go through at least "TCP/IP Illustrated vol.II". i guess Stevens can give better answer than almost anyone else. ISBN 0-201-63354-X itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 11:59:25 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 4F6C637B408; Fri, 20 Jul 2001 11:59:17 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KIxHV13195; Fri, 20 Jul 2001 11:59:17 -0700 Date: Fri, 20 Jul 2001 11:59:17 -0700 From: Brooks Davis To: net@freebsd.org, hackers@freebsd.org Subject: interface cloning MFC Message-ID: <20010720115917.A12408@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I plan to MFC the network interface cloning support and the gif modularization early next week unless someone has objections. I'd like to get it in before the code slush and since I'll be leaving for a week on the 31st, that means sometime early to mid next week to allow for any bug reports. I don't really expect any problems. A diff is available at: http://people.freebsd.org/~brooks/patches/gif-stable.diff apply with: cd /usr/src mkdir sys/modules/if_gif sys/modules/if_stf patch < gif-stable.diff -- Brooks --=20 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 --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WH+EXY6L6fI4GtQRAshQAKDOlk6+HByY2Uq2P0vHFEU9EooHGQCgzWBo t7BFPcqq68lqe2XXGW/j51g= =FQ+o -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 12:38: 5 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 9D80A37B407; Fri, 20 Jul 2001 12:37:53 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KJbpl26743; Fri, 20 Jul 2001 20:37:51 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KJbog13481; Fri, 20 Jul 2001 20:37:50 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200107201937.f6KJbog13481@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brooks Davis Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: interface cloning MFC In-Reply-To: Message from Brooks Davis of "Fri, 20 Jul 2001 11:59:17 PDT." <20010720115917.A12408@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Jul 2001 20:37:50 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > I plan to MFC the network interface cloning support and the gif > modularization early next week unless someone has objections. I'd like > to get it in before the code slush and since I'll be leaving for a week > on the 31st, that means sometime early to mid next week to allow for any > bug reports. I don't really expect any problems. Good stuff. > A diff is available at: > > http://people.freebsd.org/~brooks/patches/gif-stable.diff You forgot: Index: LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v retrieving revision 1.749.2.64 diff -u -r1.749.2.64 LINT --- LINT 2001/06/29 21:14:24 1.749.2.64 +++ LINT 2001/07/20 19:35:42 @@ -509,7 +509,7 @@ options ETHER_SNAP # enable Ethernet_802.2/SNAP frame # for IPv6 -pseudo-device gif 4 #IPv6 and IPv4 tunneling +pseudo-device gif #IPv6 and IPv4 tunneling pseudo-device faith 1 #for IPv6 and IPv4 translation pseudo-device stf #6to4 IPv6 over IPv4 encapsulation I'm just rebuilding the world now :) I'll let you know how I get on. Thanks for your work. -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 12:52: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 8C38737B405; Fri, 20 Jul 2001 12:52:03 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KJpq619635; Fri, 20 Jul 2001 12:51:52 -0700 Date: Fri, 20 Jul 2001 12:51:52 -0700 From: Brooks Davis To: Brian Somers Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: interface cloning MFC Message-ID: <20010720125152.A18620@Odin.AC.HMC.Edu> References: <200107201937.f6KJbog13481@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107201937.f6KJbog13481@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Fri, Jul 20, 2001 at 08:37:50PM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 20, 2001 at 08:37:50PM +0100, Brian Somers wrote: > > A diff is available at: > >=20 > > http://people.freebsd.org/~brooks/patches/gif-stable.diff >=20 > You forgot: >=20 > Index: LINT > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v > retrieving revision 1.749.2.64 > diff -u -r1.749.2.64 LINT > --- LINT 2001/06/29 21:14:24 1.749.2.64 > +++ LINT 2001/07/20 19:35:42 > @@ -509,7 +509,7 @@ > options ETHER_SNAP # enable Ethernet_802.2/SNAP frame > =20 > # for IPv6 > -pseudo-device gif 4 #IPv6 and IPv4 tunneling > +pseudo-device gif #IPv6 and IPv4 tunneling > pseudo-device faith 1 #for IPv6 and IPv4 translation > pseudo-device stf #6to4 IPv6 over IPv4 encapsulation Oops, I've updated the diff. I'll be committing the appropriate fix to NOTES shortly, since I forgot that in the first round. -- Brooks --=20 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 --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WIvXXY6L6fI4GtQRAqsVAKCejQ+LbtXD0n3nzwIWpzG+zkTeHACgkdLz i1YyLERB2qCNxYuy5HJSKKg= =rl2p -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 15:37:29 2001 Delivered-To: freebsd-net@freebsd.org Received: from web14408.mail.yahoo.com (web14408.mail.yahoo.com [216.136.174.78]) by hub.freebsd.org (Postfix) with SMTP id 3D1CE37B401 for ; Fri, 20 Jul 2001 15:37:25 -0700 (PDT) (envelope-from marcelomcarvalho@yahoo.com) Message-ID: <20010720223725.76454.qmail@web14408.mail.yahoo.com> Received: from [128.114.63.148] by web14408.mail.yahoo.com via HTTP; Fri, 20 Jul 2001 15:37:25 PDT Date: Fri, 20 Jul 2001 15:37:25 -0700 (PDT) From: Marcelo Carvalho Subject: porting BSD to Freebsd To: freebsd-questions@FreeBSD.org Cc: freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, In BSD, the /sys/malloc.h file has a list of definitions of "types of memory to be allocated" that doesn't appear in the corresponding file in Freebsd. Does anybody know where can I find the corresponding information in FreeBSD? Are they defined as well? Thanks. __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 15:43:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id EAB5D37B403; Fri, 20 Jul 2001 15:43:23 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KMhMW10423; Fri, 20 Jul 2001 15:43:22 -0700 Date: Fri, 20 Jul 2001 15:43:22 -0700 From: Brooks Davis To: Marcelo Carvalho Cc: freebsd-questions@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: porting BSD to Freebsd Message-ID: <20010720154322.A9531@Odin.AC.HMC.Edu> References: <20010720223725.76454.qmail@web14408.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010720223725.76454.qmail@web14408.mail.yahoo.com>; from marcelomcarvalho@yahoo.com on Fri, Jul 20, 2001 at 03:37:25PM -0700 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 20, 2001 at 03:37:25PM -0700, Marcelo Carvalho wrote: > In BSD, the /sys/malloc.h file has a list of > definitions of "types of memory to be allocated" that > doesn't appear in the corresponding file in Freebsd.=20 >=20 > Does anybody know where can I find the corresponding > information in FreeBSD? Are they defined as well? They are defined via the MALLOC_DEFINE macro. Current practice seems to be to create a malloc type for each driver so its memory can be tracked seperatly. If you want to find them all you need to grep the /usr/src/sys for them. I've found glimpse very handy for this sort of thing recently. -- Brooks --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WLQJXY6L6fI4GtQRAuWhAJ9STclOAHzc4oupw3BevjdV8W6BQgCg2HHS QFqJqu8d6e+wEivumWNOY2o= =GXTX -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 16:29:22 2001 Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 884B637B401; Fri, 20 Jul 2001 16:29:16 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KNTDL00732; Sat, 21 Jul 2001 00:29:14 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6KNTDg17187; Sat, 21 Jul 2001 00:29:13 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200107202329.f6KNTDg17187@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Brooks Davis Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: interface cloning MFC In-Reply-To: Message from Brooks Davis of "Fri, 20 Jul 2001 11:59:17 PDT." <20010720115917.A12408@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Jul 2001 00:29:13 +0100 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > I plan to MFC the network interface cloning support and the gif > modularization early next week unless someone has objections. I'd like > to get it in before the code slush and since I'll be leaving for a week > on the 31st, that means sometime early to mid next week to allow for any > bug reports. I don't really expect any problems. > > A diff is available at: > > http://people.freebsd.org/~brooks/patches/gif-stable.diff > > apply with: > > cd /usr/src > mkdir sys/modules/if_gif sys/modules/if_stf > patch < gif-stable.diff > > -- Brooks This works nicely on my -stale box. Thanks. One niggle though :) It's probably worth changing ``$FreeBSD: ........$'' to ``$FreeBSD$'' in your patched version. Without this, mergemaster assumes that the new version in /usr/src/etc is the same as the /etc version (same Ids). This caused a problem here, I fixed the problem and went to prepare a patch for you.... the patch file came up empty -- you already had the missing ``create'' in your patches (of course) :*D Cheers. -- Brian http://www.freebsd-services.com/ Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 16:35:37 2001 Delivered-To: freebsd-net@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 4AF5437B405; Fri, 20 Jul 2001 16:35:32 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6KNZTH17835; Fri, 20 Jul 2001 16:35:29 -0700 Date: Fri, 20 Jul 2001 16:35:29 -0700 From: Brooks Davis To: Brian Somers Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: interface cloning MFC Message-ID: <20010720163529.A16952@Odin.AC.HMC.Edu> References: <200107202329.f6KNTDg17187@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107202329.f6KNTDg17187@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Sat, Jul 21, 2001 at 12:29:13AM +0100 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 21, 2001 at 12:29:13AM +0100, Brian Somers wrote: > This works nicely on my -stale box. Thanks. >=20 > One niggle though :) It's probably worth changing=20 > ``$FreeBSD: ........$'' to ``$FreeBSD$'' in your patched version. =20 > Without this, mergemaster assumes that the new version in /usr/src/etc=20 > is the same as the /etc version (same Ids). This caused a problem=20 > here, I fixed the problem and went to prepare a patch for you.... the=20 > patch file came up empty -- you already had the missing ``create'' in=20 > your patches (of course) :*D I've updated the patch again. I'd run into that problem but didn't think to just unexpand the $FreeBSD$ and then promptly forgot about it. Thanks, Brooks --=20 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 --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7WMBAXY6L6fI4GtQRArnqAKDPTEYpw1WAqplg9RkswXuCEzm/MgCg3FEo Bc8amOhnFtHbb7FSrSujYiM= =OVqW -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Jul 20 19: 9:13 2001 Delivered-To: freebsd-net@freebsd.org Received: from web14407.mail.yahoo.com (web14407.mail.yahoo.com [216.136.174.77]) by hub.freebsd.org (Postfix) with SMTP id A177037B407 for ; Fri, 20 Jul 2001 19:09:07 -0700 (PDT) (envelope-from marcelomcarvalho@yahoo.com) Message-ID: <20010721020907.99984.qmail@web14407.mail.yahoo.com> Received: from [128.114.63.148] by web14407.mail.yahoo.com via HTTP; Fri, 20 Jul 2001 19:09:07 PDT Date: Fri, 20 Jul 2001 19:09:07 -0700 (PDT) From: Marcelo Carvalho Subject: Re: porting BSD to Freebsd To: Kris Kennaway Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <20010720171028.A94827@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --- Kris Kennaway wrote: > You'll have to include more information about what > you're trying to > do. > > Kris > Thanks Kris. I'll try to be more specific: Currently, I'm porting a /sys/sys/malloc.h from BSD to FreeBSD. It turns out that the file I'm working on has some "types of memory" added to the original list that I've mentioned before ("types of memory"). I got an e-mail telling me that these definitions are now done through the MACRO_DEFINE file (in freebsd). However, I found out that not all definitions are there. They are now scattered in other files (as the guy also suggested me to find out). My problem is, since this is a NEW definition of type of memory, I need to know where I should include it appropriately. I have a very weak knowledge in kernel programming. I'm kind of lost now. It is supposed to be just two lines of definitions, but in which file now? Maybe I still didn't get the idea of how the macros work... I hope I was more clear now. I would really appreciate if some of you could give me some help on this thing. Thanks, Marcelo. __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Jul 21 23:24:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 083E037B401 for ; Sat, 21 Jul 2001 23:24:26 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:13ff::a]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id PAA04045; Sun, 22 Jul 2001 15:26:24 +0900 (JST) Date: Sun, 22 Jul 2001 14:47:09 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: raviprasad20@netscape.net Cc: freebsd-net@FreeBSD.ORG Subject: Re: addresses ::1/128 and ff01::/32 In-Reply-To: <2FAB92FB.78BCF400.9513E96F@netscape.net> References: <2FAB92FB.78BCF400.9513E96F@netscape.net> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 20 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>>>> On Fri, 20 Jul 2001 05:32:23 -0400, >>>>> raviprasad20@netscape.net said: > Can anybody please mail me why ::1/128 & ff01::/32 addresses are put > to the routing table? Otherwise, the sending node cannot make a packet sent to ::1 (or ff01::xxx) looped-back on the node itself. We can do it by adding special cases in the IPv6 output routine, but it would be much more convenient to just use the existing routing table engine. > what does "128" and "32" indicate? The length of prefix (I'm not sure if this is really the answer you want, though). JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message