From owner-freebsd-net Sun Nov 14 6:58:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-25.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.153]) by hub.freebsd.org (Postfix) with ESMTP id F1EBA14CFF for ; Sun, 14 Nov 1999 06:58:36 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA01072; Sun, 14 Nov 1999 14:58:19 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id OAA00461; Sun, 14 Nov 1999 14:48:17 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911141448.OAA00461@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Josh Tiefenbach Cc: Julian Elischer , freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Problems using ppp(8) and PPPoE In-Reply-To: Message from Josh Tiefenbach of "Fri, 12 Nov 1999 23:33:05 EST." <19991112233305.C8235@snickers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Nov 1999 14:48:17 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > cerebus:~# tcpdump -nev -s 256 ether proto 0x8863 or ether proto 0x8864 > tcpdump: listening on de0 > 23:23:18.010000 0:c0:f0:22:35:e1 ff:ff:ff:ff:ff:ff 8863 24: > 1109 0000 0004 0101 0000 > 23:23:18.728783 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 61: > 1107 0000 0029 0101 0000 0102 001d 3133 > 3034 3130 3439 3931 3833 3632 2d73 6d73 > 322d 746f 726f 6e74 6f36 3301 0100 00 > 23:23:19.005733 0:c0:f0:22:35:e1 ff:ff:ff:ff:ff:ff 8863 24: > 1109 0000 0004 0101 0000 > 23:23:19.728640 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 61: > 1107 0000 0029 0101 0000 0102 001d 3133 > 3034 3130 3439 3931 3833 3632 2d73 6d73 > 322d 746f 726f 6e74 6f36 3301 0100 00 [.....] I've updated tcpdump. It now understands PPPoE, so these packets should be easier to interpret. I've got a version of pppoed that I'd be happy to provide to people (it's currently at freefall:~brian/pppoed for those with freefall accounts). I've got problems interpreting the incoming PADO packets that are produced by server-side PPPoE.... I'm still talking with Julian about this. Cheers. -- Brian 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 Sun Nov 14 14:12:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 9EBB014D04 for ; Sun, 14 Nov 1999 14:12:04 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id XAA03238 for ; Sun, 14 Nov 1999 23:11:57 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id XAA02093 for freebsd-net@freebsd.org; Sun, 14 Nov 1999 23:11:42 +0100 (CET) (envelope-from andreas) Date: Sun, 14 Nov 1999 23:11:42 +0100 From: Andreas Klemm To: freebsd-net@freebsd.org Subject: routed -s => routed[674]: sendto(xe0, 224.0.0.1): No route to host Message-ID: <19991114231142.A1814@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i X-Operating-System: FreeBSD 3.3-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What am I missing. I want to send rip updates into the network and started routed -s. Why does it not work and why do I get the messages mentioned in the subject ? I set sysctl -w net.inet.ip.forwarding=1 manually ... What do I wrong, what's missing ? root# cat /etc/gateways ripv2 root# ifconfig -a tun0: flags=8010 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 atalk 0.0 range 0-0 phase 2 xe0: flags=8943 mtu 1500 inet 172.16.3.6 netmask 0xfffffffc broadcast 172.16.3.7 atalk 100.200 range 0-65534 phase 2 broadcast 0.255 inet 172.16.5.1 netmask 0xfffffffc broadcast 172.16.5.3 inet 172.16.5.4 netmask 0xfffffffc broadcast 172.16.5.7 inet 172.16.5.8 netmask 0xfffffffc broadcast 172.16.5.11 ether 00:80:c7:61:c2:9f media: 10baseT/UTP supported media: autoselect 10baseT/UTP 100baseTX root# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire 127.0.0.1 127.0.0.1 UH 1 6 lo0 172.16.1/24 172.16.3.5 UGc 0 0 xe0 172.16.2/24 172.16.3.5 UGc 2 4 xe0 172.16.3/30 172.16.3.5 UGc 0 0 xe0 172.16.3.4/30 link#3 UC 0 0 xe0 172.16.3.5 0:e0:1e:65:33:40 UHLW 6 0 xe0 535 172.16.3.6 0:80:c7:61:c2:9f UHLW 2 2 lo0 172.16.5/30 link#3 UC 0 0 xe0 172.16.5.4/30 link#3 UC 0 0 xe0 172.16.5.8/30 link#3 UC 0 0 xe0 172.16.200.111 172.16.3.5 UGH 0 0 xe0 172.16.201/24 172.16.3.5 UGc 0 0 xe0 [...] Thanks Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 14:49:47 1999 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 E31A614BC7 for ; Sun, 14 Nov 1999 14:49:45 -0800 (PST) (envelope-from justin@walker3.apple.com) Received: from mailgate2.apple.com ([17.129.100.225]) by mail-out1.apple.com (8.9.3/8.9.3) with ESMTP id OAA13575 for ; Sun, 14 Nov 1999 14:49:44 -0800 (PST) Received: from scv1.apple.com (scv1.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Sun, 14 Nov 1999 14:49:36 -0800 Received: from walker3.apple.com (walkeridsl1.apple.com [17.219.158.66]) by scv1.apple.com (8.9.3/8.9.3) with ESMTP id OAA20873 for ; Sun, 14 Nov 1999 14:49:35 -0800 (PST) Received: by walker3.apple.com (8.9.1/8.9.1) id OAA00738 for freebsd-net@freebsd.org; Sun, 14 Nov 1999 14:49:40 -0800 (PST) Message-Id: <199911142249.OAA00738@walker3.apple.com> To: freebsd-net@freebsd.org Subject: Question about netmask retrieval Date: Sun, 14 Nov 1999 14:49:39 -0800 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a quickie, I think: in doing the obvious (to me) thing to retrieve the netmask associated with an IP address assigned to an interface, I use SIOCGIFNETMASK with an ifreq struct that I get from SIOCGIFCONF. If there are aliases assigned, I see the netmask associated with the "primary" (?) IP address, rather than that of the alias address in question (the one specified in the ifreq). This seems to be caused by the fact that the kernel code find the "first" ifaddr struct for the interface, and stops looking. Bug? Feature? I know there are alternative ways to do this, but I'm curious about the reason for this behavior. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | Men are from Earth. Apple Computer, Inc. | Women are from Earth. 2 Infinite Loop | Deal with it. Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 15:33:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id C794214CCA for ; Sun, 14 Nov 1999 15:33:39 -0800 (PST) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id 040F93D19; Sun, 14 Nov 1999 18:33:38 -0500 (EST) Date: Sun, 14 Nov 1999 18:33:38 -0500 From: Josh Tiefenbach To: Julian Elischer Cc: Josh Tiefenbach , freebsd-net@FreeBSD.ORG Subject: Re: Problems using ppp(8) and PPPoE Message-ID: <19991114183338.A75368@snickers.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Hah Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Nov 13, 1999 at 11:27:51PM -0800, Julian Elischer wrote: > Any news? Now I cant even get a response from the server with just a simple PADI (with no Host-Uniq tag). I've even powered up/down the modem. Swapping ethernet cards is not an option, seeing as one machine is a laptop. (this is odd, since I could send stuff from 2 different MAC addresses before). Anyways, I sniffed the windows client making a connection. The results are *very* wierd: cerebus:~# tcpdump -i de1 -nev -s 256 ether proto 0x8863 tcpdump: listening on de1 18:15:52.599957 0:80:c7:d3:b1:73 ff:ff:ff:ff:ff:ff 8863 60: 1109 0000 000e 0103 0006 0080 c7d3 b173 0101 0000 00b6 0000 2045 4f45 4344 4546 4545 4a45 4645 4745 4645 4f45 4345 18:15:53.601846 0:10:67:0:3c:ee 0:80:c7:d3:b1:73 8863 71: 1107 0000 0033 0103 0006 0080 c7d3 b173 0101 0000 0102 001d 3133 3034 3130 3439 3931 3833 3632 2d73 6d73 322d 746f 726f 6e74 6f36 3301 0100 00 18:15:53.604529 0:80:c7:d3:b1:73 0:10:67:0:3c:ee 8863 60: 1119 0000 000e 0103 0006 0080 c7d3 b173 0101 0000 ee00 ffff ffff ffff 0080 c7d3 b173 0800 4500 00e0 651f 0000 8011 18:15:54.628027 0:10:67:0:3c:ee 0:80:c7:d3:b1:73 8863 67: 1165 06b2 002f 0103 0006 0080 c7d3 b173 0101 0000 0102 001d 3133 3034 3130 3439 3931 3833 3632 2d73 6d73 322d 746f 726f 6e74 6f36 33 Notice how it *is* using the Host-Uniq tag, and jamming the MAC address of the ethernet card in. What I dont understand is all the garbage after the Service-Name tag. Perhaps the windows client isnt nulling out a buffer somewhere? (another data-point, probably unrelated: I just noticed that I'm getting a *completely* different range of IPs today than I did Friday night. I'm wondering if when they made that change, that they also mucked around with the SMS) I did notice some if_ethersubr.c and ng_pppoe.c changes hit the tree, but I havent gotten them yet. I'll see if I can do some more testing later this evening. josh -- "To succeed in the world, it is not enough to be stupid, you must also be well-mannered" -- Voltaire To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 17:49:40 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-5.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.133]) by hub.freebsd.org (Postfix) with ESMTP id CF90A14BF9 for ; Sun, 14 Nov 1999 17:49:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA00430; Mon, 15 Nov 1999 01:49:19 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id BAA02102; Mon, 15 Nov 1999 01:52:39 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911150152.BAA02102@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Josh Tiefenbach Cc: Julian Elischer , freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Problems using ppp(8) and PPPoE In-Reply-To: Message from Josh Tiefenbach of "Sun, 14 Nov 1999 18:33:38 EST." <19991114183338.A75368@snickers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Nov 1999 01:52:39 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [.....] > I did notice some if_ethersubr.c and ng_pppoe.c changes hit the tree, but I > havent gotten them yet. I'll see if I can do some more testing later this > evening. > > josh [.....] I've just sent some patches to julian that make things work here - not for pppoed, but they should be ok for ppp(8). I'm going to bed ! -- Brian 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 Sun Nov 14 18:58:18 1999 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 E9F6914C49 for ; Sun, 14 Nov 1999 18:58:15 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA03983; Sun, 14 Nov 1999 21:57:55 -0500 (EST) (envelope-from wollman) Date: Sun, 14 Nov 1999 21:57:55 -0500 (EST) From: Garrett Wollman Message-Id: <199911150257.VAA03983@khavrinen.lcs.mit.edu> To: Peter Wemm Cc: freebsd-net@FreeBSD.ORG Subject: Re: BIND 8.2.x - IRS, newer resolver functions In-Reply-To: <19991112144847.CF6271C6D@overcee.netplex.com.au> References: <19991112144847.CF6271C6D@overcee.netplex.com.au> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > How would people react to libc supporting *only* "files" and "irpd" (ie: no > dns or yp). Rather badly, I expect, since that would make it more difficult to run/debug machines on the network in single-user mode. (But don't expect anyone to actually complain until after you've made the change....) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 19: 0:35 1999 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 B1AD814BF8 for ; Sun, 14 Nov 1999 19:00:30 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA03998; Sun, 14 Nov 1999 22:00:24 -0500 (EST) (envelope-from wollman) Date: Sun, 14 Nov 1999 22:00:24 -0500 (EST) From: Garrett Wollman Message-Id: <199911150300.WAA03998@khavrinen.lcs.mit.edu> To: Luigi Rizzo Cc: freebsd-net@FreeBSD.ORG Subject: Re: FreeBSD networking problems In-Reply-To: <199911121435.PAA05210@info.iet.unipi.it> References: <199911102211.QAA12891@cs.rice.edu> <199911121435.PAA05210@info.iet.unipi.it> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > related issue -- kern.ipc.maxsockbuf can also be a source of problem. > It bounds the gross amount of buffer space used by a socket -- this > means if you allocate a 2KB cluster and only use it to hold a small > packet (e.g. 512 bytes) your gross amount of buffer space is charged > the full 2KB and the kern.ipc.maxsockbuf limit might hit before > net.inet.tcp.sendspace (or however you override it with the > setsockopt() calls) Not quite. It's charged against the maximum mbuf size (sb_maxmb), which is sockbuf_waste_factor * sb_hiwat. This is an intentional trade-off between speed and memory wastage. (That doesn't mean it's not time to revisit this tradeoff; it just means that the original reasons still need to be considered.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 19: 7:44 1999 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 B0D6214D32 for ; Sun, 14 Nov 1999 19:07:42 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA04027; Sun, 14 Nov 1999 22:07:41 -0500 (EST) (envelope-from wollman) Date: Sun, 14 Nov 1999 22:07:41 -0500 (EST) From: Garrett Wollman Message-Id: <199911150307.WAA04027@khavrinen.lcs.mit.edu> To: Mohit Aron Cc: freebsd-net@freebsd.org Subject: FreeBSD networking problems In-Reply-To: <199911102211.QAA12891@cs.rice.edu> References: <199911102211.QAA12891@cs.rice.edu> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Ridiculous Cc list trimmed.] < said: > 1) FreeBSD tries to determine the max size of socket buffers from cached > routing information. This is done even after an application wants to set the > application buffer to a large value. This is a long-standing bug. You're welcome to submit a patch which reorders the tests to ensure that the Right Thing happens in all cases (including the default). > the unscaled value of advertised window. The fix is the following patch to > tcp_input.c (taken from FreeBSD-3.3-RELEASE): Make it a PR, please. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 19:14:44 1999 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 3ECE514D32 for ; Sun, 14 Nov 1999 19:14:41 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA04068; Sun, 14 Nov 1999 22:14:36 -0500 (EST) (envelope-from wollman) Date: Sun, 14 Nov 1999 22:14:36 -0500 (EST) From: Garrett Wollman Message-Id: <199911150314.WAA04068@khavrinen.lcs.mit.edu> To: "Vince Kosmac" Cc: Subject: Help with MAX sockets In-Reply-To: <002d01bf2b8e$ee857fa0$1eea6bce@vince_svr.travauto.com> References: <002d01bf2b8e$ee857fa0$1eea6bce@vince_svr.travauto.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Does anyone know the resource requirements for a single BSD=20 > socket ? I am tring to open 2,000 sockets on a single machine with=20 > 512meg of ram. I can only get 648 sockets before it locks up. I did a = Please do not send HTML-mail. It really irritates a lot of people, and makes you look like a clueless newbie. To answer your question: a TCP socket requires 448 (tcpcb) + 192 (socket) + 64 (file) = 704 bytes of kernel state for each open socket. Closed sockets in TIME_WAIT state require 640 bytes (everything but the file struct). As to why you can only get 648 sockets before ``it locks up'', I can't help you unless you are far more specific. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 19:16:38 1999 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 1706614D32 for ; Sun, 14 Nov 1999 19:16:29 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA04079; Sun, 14 Nov 1999 22:15:51 -0500 (EST) (envelope-from wollman) Date: Sun, 14 Nov 1999 22:15:51 -0500 (EST) From: Garrett Wollman Message-Id: <199911150315.WAA04079@khavrinen.lcs.mit.edu> To: G Muthukumar Cc: freebsd-net@FreeBSD.ORG Subject: BIND 8.2.x - IRS, newer resolver functions In-Reply-To: <199911101356.TAA03656@wipro.wipsys.sequent.com> References: <199911101356.TAA03656@wipro.wipsys.sequent.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > If this is not considered due to some valid reasons, would it be > possible for me to get those reasons? Any pointers are also welcome. ISTR at one time there was some issue with the licensing terms for bind > 8.1, but I don't recall if/how that was resolved. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 19:35:37 1999 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 B3EFE14DFF for ; Sun, 14 Nov 1999 19:35:27 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA04148; Sun, 14 Nov 1999 22:35:23 -0500 (EST) (envelope-from wollman) Date: Sun, 14 Nov 1999 22:35:23 -0500 (EST) From: Garrett Wollman Message-Id: <199911150335.WAA04148@khavrinen.lcs.mit.edu> To: justin@apple.com Cc: freebsd-net@FreeBSD.ORG Subject: Question about netmask retrieval In-Reply-To: <199911142249.OAA00738@walker3.apple.com> References: <199911142249.OAA00738@walker3.apple.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > Bug? Feature? I know there are alternative ways to do this, but > I'm curious about the reason for this behavior. I'd call it a misbug. It's probably a bug, but anything that stops people from using the dain-bramaged old interface is a feature. Use sysctl or PF_ROUTE, as appropriate. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 19:40:33 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id D2ABB14E22 for ; Sun, 14 Nov 1999 19:40:25 -0800 (PST) (envelope-from justin@rhapture.apple.com) Received: from mailgate1.apple.com (A17-128-100-225.apple.com [17.128.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id TAA10374 for ; Sun, 14 Nov 1999 19:38:56 -0800 (PST) Received: from scv3.apple.com (scv3.apple.com) by mailgate1.apple.com (mailgate1.apple.com- SMTPRS 2.0.15) with ESMTP id for ; Sun, 14 Nov 1999 19:40:18 -0800 Received: from rhapture.apple.com (rhapture.apple.com [17.202.40.59]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id TAA00265 for ; Sun, 14 Nov 1999 19:40:18 -0800 (PST) Received: (from justin@localhost) by rhapture.apple.com (8.9.1/8.9.1) id TAA00768 for freebsd-net@FreeBSD.ORG; Sun, 14 Nov 1999 19:40:17 -0800 (PST) Message-Id: <199911150340.TAA00768@rhapture.apple.com> To: freebsd-net@freebsd.org Subject: Re: Question about netmask retrieval In-Reply-To: <199911142249.OAA00738@walker3.apple.com> Date: Sun, 14 Nov 1999 19:40:17 -0800 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Garrett Wollman > Date: 1999-11-14 19:35:43 -0800 > To: justin@apple.com > Subject: Question about netmask retrieval > Cc: freebsd-net@FreeBSD.ORG > In-reply-to: <199911142249.OAA00738@walker3.apple.com> > Delivered-to: freebsd-net@freebsd.org > X-Loop: FreeBSD.org > > < > said: > > > Bug? Feature? I know there are alternative ways to do this, but > > I'm curious about the reason for this behavior. > > I'd call it a misbug. It's probably a bug, but anything that stops > people from using the dain-bramaged old interface is a feature. Use > sysctl or PF_ROUTE, as appropriate. Thanks; I'd forgotten about the brain damage. j -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | When crypto is outlawed, Apple Computer, Inc. | Only outlaws will have crypto. 2 Infinite Loop | Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Nov 14 20:11:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 9CD9414C03 for ; Sun, 14 Nov 1999 20:11:23 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id UAA73563; Sun, 14 Nov 1999 20:11:20 -0800 (PST) Date: Sun, 14 Nov 1999 20:11:13 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: Josh Tiefenbach Cc: freebsd-net@FreeBSD.ORG Subject: Re: Problems using ppp(8) and PPPoE In-Reply-To: <19991114183338.A75368@snickers.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 14 Nov 1999, Josh Tiefenbach wrote: > On Sat, Nov 13, 1999 at 11:27:51PM -0800, Julian Elischer wrote: > > Any news? > > Now I cant even get a response from the server with just a simple PADI (with > no Host-Uniq tag). I've even powered up/down the modem. Swapping ethernet > cards is not an option, seeing as one machine is a laptop. > > (this is odd, since I could send stuff from 2 different MAC addresses before). > > Anyways, I sniffed the windows client making a connection. The results are > *very* wierd: Because you have run pppoe from your Windows machine, the exchange will no lnger accept packets from you.. Sympatico seem to be caching teh MAC address to associate with each DSL line. Complain like hell and maybe they may get someone to fix it.. > > cerebus:~# tcpdump -i de1 -nev -s 256 ether proto 0x8863 > tcpdump: listening on de1 > 18:15:52.599957 0:80:c7:d3:b1:73 ff:ff:ff:ff:ff:ff 8863 60: > 1109 0000 000e 0103 0006 0080 c7d3 b173 > 0101 0000 00b6 0000 2045 4f45 4344 4546 > 4545 4a45 4645 4745 4645 4f45 4345 > 18:15:53.601846 0:10:67:0:3c:ee 0:80:c7:d3:b1:73 8863 71: > 1107 0000 0033 0103 0006 0080 c7d3 b173 > 0101 0000 0102 001d 3133 3034 3130 3439 > 3931 3833 3632 2d73 6d73 322d 746f 726f > 6e74 6f36 3301 0100 00 > 18:15:53.604529 0:80:c7:d3:b1:73 0:10:67:0:3c:ee 8863 60: > 1119 0000 000e 0103 0006 0080 c7d3 b173 > 0101 0000 ee00 ffff ffff ffff 0080 c7d3 > b173 0800 4500 00e0 651f 0000 8011 > 18:15:54.628027 0:10:67:0:3c:ee 0:80:c7:d3:b1:73 8863 67: > 1165 06b2 002f 0103 0006 0080 c7d3 b173 > 0101 0000 0102 001d 3133 3034 3130 3439 > 3931 3833 3632 2d73 6d73 322d 746f 726f > 6e74 6f36 33 > > Notice how it *is* using the Host-Uniq tag, and jamming the MAC address of the > ethernet card in. What I dont understand is all the garbage after the > Service-Name tag. Perhaps the windows client isnt nulling out a buffer > somewhere? Ethernet packets are ALWAYS padded to 64 bytes.. ignore that.. you saw it on the wire so it will be padded (with junk). > > (another data-point, probably unrelated: I just noticed that I'm getting a > *completely* different range of IPs today than I did Friday night. I'm > wondering if when they made that change, that they also mucked around with the > SMS) I bet they were screwing with it when you tried before.. This is what happenned to us at the test site. we got so f*cking confused as to what was going on that we gave up for 3 days and let it settle. We also discovered the MAC Caching "feature". > > I did notice some if_ethersubr.c and ng_pppoe.c changes hit the tree, but I > havent gotten them yet. I'll see if I can do some more testing later this > evening. I just committed some more changes too. > > josh > > -- > "To succeed in the world, it is not enough to be stupid, you must also be > well-mannered" -- Voltaire > > > 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 Nov 15 4:39:34 1999 Delivered-To: freebsd-net@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B17D715030 for ; Mon, 15 Nov 1999 04:39:28 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E5C7A1C6D; Mon, 15 Nov 1999 20:39:27 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: BIND 8.2.x - IRS, newer resolver functions In-reply-to: Your message of "Sun, 14 Nov 1999 21:57:55 EST." <199911150257.VAA03983@khavrinen.lcs.mit.edu> Date: Mon, 15 Nov 1999 20:39:27 +0800 From: Peter Wemm Message-Id: <19991115123927.E5C7A1C6D@overcee.netplex.com.au> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Garrett Wollman wrote: > < said: > > > How would people react to libc supporting *only* "files" and "irpd" (ie: no > > dns or yp). > > Rather badly, I expect, since that would make it more difficult to > run/debug machines on the network in single-user mode. (But don't > expect anyone to actually complain until after you've made the > change....) > > -GAWollman Well, when you start networking, you could still start irpd in order to get DNS access.. It's just a thought. Anyway, 8.2.5 has a target to remove the crypto and still enable it to build, which means we can ignore the problem for the time being. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Nov 15 5:38:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from usgate.ibmmail.com (usgate.ibmmail.com [204.146.55.142]) by hub.freebsd.org (Postfix) with ESMTP id 82A9314F29 for ; Mon, 15 Nov 1999 05:38:38 -0800 (PST) (envelope-from Adam_Woodbeck@KeykertUSA.com) Received: Received: by usgate.ibmmail.com with SMTP id NAA50506 for ; Mon, 15 Nov 1999 13:37:41 GMT Received: by SCH.ADVANTIS.COM (Soft-Switch LMS 3.2) with snapi via USCCRG01 id 0039010009346445; Mon, 15 Nov 1999 08:37:41 -0500 From: "Adam Woodbeck (KEYKERTUSA)" To: Subject: No Subject Message-ID: <0039010009346445000002L152*@MHS> Date: Mon, 15 Nov 1999 08:37:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org unsubscribe freebsd-net = To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 16 12:43:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp.interlog.com (smtp.interlog.com [207.34.202.37]) by hub.freebsd.org (Postfix) with ESMTP id 38F1D14EFE for ; Tue, 16 Nov 1999 12:43:42 -0800 (PST) (envelope-from al.feldman@sangoma.com) Received: from alex (dm.interlog.com [199.212.154.24]) by smtp.interlog.com (8.9.1/8.9.1) with SMTP id PAA17951 for ; Tue, 16 Nov 1999 15:43:41 -0500 (EST) Message-ID: <004001bf3074$33255f10$7801a8c0@alex.SANGOMA.COM> From: "Alex Feldman" To: Subject: Network interface name Date: Tue, 16 Nov 1999 15:50:21 -0500 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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm writting multiple device/protocol driver. My netowork interface name includes number in the middle of the name (ex. xx1_xxx12). when I check is network interface is already attached to kernel, I use 'ifunit' function. But, as I see its source code, FreeBSD not permit the number inside the network interface name. Is someone went into this problem? How can I solve this problem (without changing the name)? I think that enoght to change only 'ifunit' function.. Is it correct? Thank you for any help.. Regards, Alex Feldman E-mail : al.feldman@sangoma.com Sangoma Technologies Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 16 22: 7: 6 1999 Delivered-To: freebsd-net@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 358A615017 for ; Tue, 16 Nov 1999 22:06:56 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11nyEx-0001iY-00; Wed, 17 Nov 1999 12:06:47 +0600 Date: Wed, 17 Nov 1999 12:06:46 +0600 (ALMT) From: Boris Popov To: Alex Feldman Cc: net@FreeBSD.ORG Subject: Re: Network interface name In-Reply-To: <004001bf3074$33255f10$7801a8c0@alex.SANGOMA.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 16 Nov 1999, Alex Feldman wrote: > I'm writting multiple device/protocol driver. > My netowork interface name includes number in the middle of the name (ex. > xx1_xxx12). when I check is network interface is already attached to kernel, > I use 'ifunit' function. But, as I see its source code, FreeBSD not permit > the number inside the network interface name. > Is someone went into this problem? How can I solve this problem (without > changing the name)? > I think that enoght to change only 'ifunit' function.. Is it correct? Right, only ifunit() code depends on it. Having ability to create subinterfaces (like ed0f1) is very useful and this syntax is already supported for disks (wd0s1a). Patches for ifunit() function you can extract from the if_ef driver: ftp://ftp.butya.kz/pub/ipx/ifef-1.2.tar.gz -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Nov 16 23:31: 0 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B7DC315381; Tue, 16 Nov 1999 23:30:56 -0800 (PST) (envelope-from julian@whistle.com) Received: from home.elischer.org (home.elischer.org [207.76.204.203]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id XAA71813; Tue, 16 Nov 1999 23:30:50 -0800 (PST) Date: Tue, 16 Nov 1999 23:30:54 -0800 (PST) From: Julian Elischer X-Sender: julian@home.elischer.org To: freebsd-stable@freebsd.org Cc: net@freebsd.org Subject: Heads Up! Netgraph moves to -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Netgraph code has moved to -current. at this stage it's not being compiled in but that will happen over a few days. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 17 13:25:31 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-23.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.151]) by hub.freebsd.org (Postfix) with ESMTP id 101F11523C; Wed, 17 Nov 1999 13:25:16 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA01782; Wed, 17 Nov 1999 21:23:34 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id VAA02251; Wed, 17 Nov 1999 21:28:02 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911172128.VAA02251@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Blaz Zupan Cc: brian@FreeBSD.org, freebsd-net@FreeBSD.org Subject: Re: rinit: wrong ifa (0xc09ba580) was (0xc0854880) - candidate for removal In-Reply-To: Message from Blaz Zupan of "Wed, 17 Nov 1999 09:26:33 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Nov 1999 21:28:02 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Nothing's changed of late here. Ppp will use whatever ``hostname'' resolves to as a default local address unless a ``set ifaddr'' is done. As you've got a ``set ifaddr'', I find it surprising that you see this message. Personally, my laptop is configured with a lo0 alias address of my hostname. When I plug the NIC in, I get the message because I'm assigning the same IP number to the ep0 device. Personally, I think the message should only be displayed if another interface is found configured with that address *AND* it's not a POINTOPOINT interface. In fact, I'll do this soon if nobody objects (freebsd-net cc'd). > The message in the subject is being printed on the console of a customers > machine. I looked through the mailing list archives and found a posting by > Garrett A. Wollman, who says: > > > What this means is that, in the process of trying to configure a network > > interface, the address which was specified for the new interface matched > > one that already belonged to another interface. The code is basically > > giving you a very cryptic warning to the effect that `what you asked me > > to do doesn't make any sense, but I'll force it through anyway'. > > I looked through the machine and noticed, that the tun0 interface contains > all IP numbers that were assigned to the machine (IP numbers are > dynamically assigned) as secondary addresses. > > This is a change in behaviour since FBSD 3.2, where the IP address has > been simply replaced on the interface and I believe the cryptic "wrong > ifa" message is being caused by this. > > Is this the intended behaviour? I was using a modified default > configuration from 3.3, but then changed to my "standard" config file that > I use on all dialup masquerading boxes, but the problem remains. > > Here is the ppp.conf file from the box: > > default: > set device /dev/cuaa0 > # set log Phase Chat LCP IPCP CCP tun command > set speed 115200 > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATB40 OK \\dATDI\\T TIMEOUT 40 CONNECT" > disable lqr > deny lqr > papchap: > set phone 088932410 > set authname someuser > set authkey somepass > set timeout 110 > set openmode active > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 > delete ALL > add 0 0 HISADDR > alias enable yes > > I looked through the ppp commit logs if there was any mention of this > behaviour, but could not find anything - but I may have missed something. > > Any help will be appreciated. > > Regards, > > Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > -- Brian 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 Wed Nov 17 13:38:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by hub.freebsd.org (Postfix) with ESMTP id E491414C8D for ; Wed, 17 Nov 1999 13:38:34 -0800 (PST) (envelope-from blaz@amis.net) Received: by titanic.medinet.si (Postfix, from userid 1000) id 06ECC55EE; Wed, 17 Nov 1999 22:38:32 +0100 (CET) Date: Wed, 17 Nov 1999 22:38:31 +0100 (CET) From: Blaz Zupan To: Brian Somers Cc: freebsd-net@FreeBSD.org Subject: Re: rinit: wrong ifa (0xc09ba580) was (0xc0854880) - candidate for removal In-Reply-To: <199911172128.VAA02251@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 17 Nov 1999, Brian Somers wrote: > Nothing's changed of late here. Ppp will use whatever ``hostname'' > resolves to as a default local address unless a ``set ifaddr'' is > done. As you've got a ``set ifaddr'', I find it surprising that > you see this message. Actually, I guess you probably did not notice the rest of my message. IMHO the behaviour change in ppp is, that now when ppp receives an IP address (assigned by the dialup server it is dialing to), it does NOT replace the IP address on the tunX interface, but simply adds it as an alias on the interface. So every time you dial the internet, the interface receives another IP address as an alias. In our case, after a day or two, there are about 60 IP aliases assigned on the tunX interface. Previous versions of ppp simply _replaced_ the IP address that was present on the interface before a new IP was assigned by the ppp peer. For example, after the machine is freshly rebooted, we see this: gatekeeper# ifconfig tun0 tun0: flags=8051 mtu 1500 inet 10.0.0.1 --> 10.0.0.2 netmask 0xffffffff After we dial the internet, the above addresses are _not_ replaced, but the new addresses are added as an alias to the interface: gatekeeper# ifconfig tun0 tun0: flags=8051 mtu 1500 inet 10.0.0.1 --> 10.0.0.2 netmask 0xffffffff inet 212.18.37.102 --> 212.18.32.20 netmask 0xffffff00 As time goes on, those secondary addresses pile up on the interface. I believe that's why I get the "wrong ifa" message. Is there any reasoning behind the secondary addresses or is this behaviour a bug? Regards, Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Nov 17 15:47:55 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-27.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.155]) by hub.freebsd.org (Postfix) with ESMTP id 3DD8614FD3 for ; Wed, 17 Nov 1999 15:47:50 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA02171; Wed, 17 Nov 1999 23:06:46 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA03573; Wed, 17 Nov 1999 23:11:14 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911172311.XAA03573@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Blaz Zupan Cc: Brian Somers , freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: rinit: wrong ifa (0xc09ba580) was (0xc0854880) - candidate for removal In-Reply-To: Message from Blaz Zupan of "Wed, 17 Nov 1999 22:38:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Nov 1999 23:11:14 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Sorry, I mustn't have read the whole message. This is a feature :-) It defeats the first-connection problem with dynamic IP numbers. It can be disabled with ``disable iface-alias'' and can be kept in control with an ``iface clear'' in ppp.linkdown - see share/examples/ppp.linkdown.sample. > On Wed, 17 Nov 1999, Brian Somers wrote: > > Nothing's changed of late here. Ppp will use whatever ``hostname'' > > resolves to as a default local address unless a ``set ifaddr'' is > > done. As you've got a ``set ifaddr'', I find it surprising that > > you see this message. > > Actually, I guess you probably did not notice the rest of my message. > > IMHO the behaviour change in ppp is, that now when ppp receives an IP > address (assigned by the dialup server it is dialing to), it does NOT > replace the IP address on the tunX interface, but simply adds it as an > alias on the interface. So every time you dial the internet, the interface > receives another IP address as an alias. In our case, after a day or two, > there are about 60 IP aliases assigned on the tunX interface. > > Previous versions of ppp simply _replaced_ the IP address that was present > on the interface before a new IP was assigned by the ppp peer. > > For example, after the machine is freshly rebooted, we see this: > > gatekeeper# ifconfig tun0 > tun0: flags=8051 mtu 1500 > inet 10.0.0.1 --> 10.0.0.2 netmask 0xffffffff > > After we dial the internet, the above addresses are _not_ replaced, but > the new addresses are added as an alias to the interface: > > gatekeeper# ifconfig tun0 > tun0: flags=8051 mtu 1500 > inet 10.0.0.1 --> 10.0.0.2 netmask 0xffffffff > inet 212.18.37.102 --> 212.18.32.20 netmask 0xffffff00 > > As time goes on, those secondary addresses pile up on the interface. I > believe that's why I get the "wrong ifa" message. Is there any reasoning > behind the secondary addresses or is this behaviour a bug? > > Regards, > > Blaz Zupan, blaz@amis.net, http://home.amis.net/blaz/ > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > -- Brian 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 Thu Nov 18 6:46:42 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id 15B37153E6 for ; Thu, 18 Nov 1999 06:46:32 -0800 (PST) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id BCC733D17; Thu, 18 Nov 1999 09:46:31 -0500 (EST) Date: Thu, 18 Nov 1999 09:46:31 -0500 From: Josh Tiefenbach To: freebsd-net@freebsd.org Subject: PPPoE Redux. Message-ID: <19991118094631.A9305@snickers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: Hah Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I feel like I'm in some sort of Skinnerian cage with this whole thing. But anyways.. Good news and bad news with my ongoing efforts to get PPPoE working with my MiserableISPFromHell: 1. The PPPoE discovery phase (complete with Host-Uniq tags) seems to be working: 21:06:02.737380 0:c0:f0:22:35:e1 Broadcast 8863 32: 1109 0000 000c 0101 0000 0103 0004 c0f9 a0c0 21:06:02.928455 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 69: 1107 0000 0031 0101 0000 0103 0004 c0f9 a0c0 0102 001d 3133 3034 3130 3439 3931 3833 3632 2d73 6d73 322d 746f 726f 6e74 6f36 3301 0100 00 21:06:02.928830 0:c0:f0:22:35:e1 0:10:67:0:3c:ee 8863 65: 1119 0000 002d 0101 0000 0102 001d 3133 3034 3130 3439 3931 3833 3632 2d73 6d73 322d 746f 726f 6e74 6f36 3301 0300 04c0 f9a0 c0 21:06:03.958884 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 65: 1165 04ad 002d 0101 0000 0103 0004 c0f9 a0c0 0102 001d 3133 3034 3130 3439 3931 3833 3632 2d73 6d73 322d 746f 726f 6e74 6f36 33 As you can see, the whole PADI/PADO/PADR/PADS/Pad Thai exchange seems to be working. This is the good news. 2. As I've come to expect, once I clear one hurdle, another one smacks me in the face :) In this case, it would appear that ppp(8) seems to think that once we've negotiated the session ID (04ad in this case), that it can drop the link. In /var/log/ppp.log, I see the phase going from connected -> disconnected, and I see this on the wire: 21:06:03.971178 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: 1100 04ad 0014 c021 0110 0012 0104 05d4 0304 c023 0506 00fd 386a 0000 cc65 fb54 ce6c 641d 066e 0714 001c 0000 0500 21:06:07.088464 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: 1100 04ad 0014 c021 0110 0012 0104 05d4 0304 c023 0506 00fd 386a 00e0 292c 61df 0101 0000 0044 0043 0134 2213 0101 21:06:10.088100 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: 1100 04ad 0014 c021 0110 0012 0104 05d4 0304 c023 0506 00fd 386a 0000 cc65 fb54 ce6c 641d 066e 0714 001c 0000 0500 21:06:13.088356 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: 1100 04ad 0014 c021 0110 0012 0104 05d4 0304 c023 0506 00fd 386a 8206 0000 0000 8406 0000 0000 6174 6963 6f2e 6361 21:06:16.091095 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: 1100 04ad 0014 c021 0110 0012 0104 05d4 0304 c023 0506 00fd 386a 0000 cc65 fb55 ce6c 641d 066e 0714 001c 0000 0500 [Lots more follows] It certainly looks like that the SMS is sending some sort of PPP packet to me, but ppp(8) has already given up on life, and isnt listening. This would be the bad news. I'm not entirely sure if this is a bogon on my part. My ppp.conf file looks something like: -----8<----- default: set device PPPoE:de0 set authname foo set authkey bar set timeout 120 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR -----8<----- I'm using files from /sys/netgraph/* , /sys/net/if_ethersubr.c, and /usr/src/usr.sbin/ppp/* from about 4pm EDT yesterday. As always, I'm open to suggestions. josh -- Malkovitch! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 7:45:26 1999 Delivered-To: freebsd-net@freebsd.org Received: from sugar.pharlap.com (sugar.pharlap.com [192.107.36.1]) by hub.freebsd.org (Postfix) with ESMTP id 5445315360 for ; Thu, 18 Nov 1999 07:45:20 -0800 (PST) (envelope-from clark@pharlap.com) Received: from clark ([192.107.36.171]) by sugar.pharlap.com (Post.Office MTA v3.5.2 release 221 ID# 0-56365U200L2S100V35) with SMTP id com; Thu, 18 Nov 1999 10:45:21 -0500 From: clark@pharlap.com (Clark Jarvis) Date: Thu, 18 Nov 1999 10:50:02 -0500 To: Brian Somers , freebsd-net@FreeBSD.org In-Reply-To: <199911172311.XAA03573@hak.lan.Awfulhak.org> Subject: Re: rinit: wrong ifa (0xc09ba580) was (0xc0854880) - candidate for removal X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v1.76 b76 Message-ID: <19991118154521924.AAA306@sugar.pharlap.com@clark> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In <199911172311.XAA03573@hak.lan.Awfulhak.org>, on 11/17/99 at 11:11 PM, Brian Somers said: >This is a feature :-) It defeats the first-connection problem with >dynamic IP numbers. It can be disabled with ``disable iface-alias'' and >can be kept in control with an ``iface clear'' in ppp.linkdown - see >share/examples/ppp.linkdown.sample. Brian, can you quickly describe the first-connection-... problem? I don't remember seeing anything about this. A pointer to a description in the code or somesuch would be OK too, of course. -- Thanks, Clark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 10:57:57 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C937215120 for ; Thu, 18 Nov 1999 10:57:43 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA21985; Thu, 18 Nov 1999 10:57:39 -0800 (PST) Date: Thu, 18 Nov 1999 10:57:39 -0800 (PST) From: Julian Elischer To: Josh Tiefenbach Cc: freebsd-net@FreeBSD.ORG Subject: Re: PPPoE Redux. In-Reply-To: <19991118094631.A9305@snickers.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think this is a matter for Brian, but I'm glad to see that the pppoe negotiation code is doing th eright thing now.. Did it just "magically" start working, or did you change something? Julian On Thu, 18 Nov 1999, Josh Tiefenbach wrote: > I feel like I'm in some sort of Skinnerian cage with this whole thing. But > anyways.. > > Good news and bad news with my ongoing efforts to get PPPoE working with my > MiserableISPFromHell: > > 1. The PPPoE discovery phase (complete with Host-Uniq tags) seems to be > working: > > 21:06:02.737380 0:c0:f0:22:35:e1 Broadcast 8863 32: > 1109 0000 000c 0101 0000 0103 0004 c0f9 > a0c0 > 21:06:02.928455 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 69: > 1107 0000 0031 0101 0000 0103 0004 c0f9 > a0c0 0102 001d 3133 3034 3130 3439 3931 > 3833 3632 2d73 6d73 322d 746f 726f 6e74 > 6f36 3301 0100 00 > 21:06:02.928830 0:c0:f0:22:35:e1 0:10:67:0:3c:ee 8863 65: > 1119 0000 002d 0101 0000 0102 001d 3133 > 3034 3130 3439 3931 3833 3632 2d73 6d73 > 322d 746f 726f 6e74 6f36 3301 0300 04c0 > f9a0 c0 > 21:06:03.958884 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8863 65: > 1165 04ad 002d 0101 0000 0103 0004 c0f9 > a0c0 0102 001d 3133 3034 3130 3439 3931 > 3833 3632 2d73 6d73 322d 746f 726f 6e74 > 6f36 33 > > As you can see, the whole PADI/PADO/PADR/PADS/Pad Thai exchange seems to be > working. This is the good news. PADthai.. Hah ha > > 2. As I've come to expect, once I clear one hurdle, another one smacks me in > the face :) In this case, it would appear that ppp(8) seems to think that once > we've negotiated the session ID (04ad in this case), that it can drop the > link. In /var/log/ppp.log, I see the phase going from connected -> > disconnected, and I see this on the wire: Maybe brian can give you more info on this bit.. > > 21:06:03.971178 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: > 1100 04ad 0014 c021 0110 0012 0104 05d4 > 0304 c023 0506 00fd 386a 0000 cc65 fb54 > ce6c 641d 066e 0714 001c 0000 0500 > 21:06:07.088464 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: > 1100 04ad 0014 c021 0110 0012 0104 05d4 > 0304 c023 0506 00fd 386a 00e0 292c 61df > 0101 0000 0044 0043 0134 2213 0101 > 21:06:10.088100 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: > 1100 04ad 0014 c021 0110 0012 0104 05d4 > 0304 c023 0506 00fd 386a 0000 cc65 fb54 > ce6c 641d 066e 0714 001c 0000 0500 > 21:06:13.088356 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: > 1100 04ad 0014 c021 0110 0012 0104 05d4 > 0304 c023 0506 00fd 386a 8206 0000 0000 > 8406 0000 0000 6174 6963 6f2e 6361 > 21:06:16.091095 0:10:67:0:3c:ee 0:c0:f0:22:35:e1 8864 60: > 1100 04ad 0014 c021 0110 0012 0104 05d4 > 0304 c023 0506 00fd 386a 0000 cc65 fb55 > ce6c 641d 066e 0714 001c 0000 0500 > > [Lots more follows] > > It certainly looks like that the SMS is sending some sort of PPP packet to me, > but ppp(8) has already given up on life, and isnt listening. > > This would be the bad news. > > I'm not entirely sure if this is a bogon on my part. My ppp.conf file looks > something like: > > -----8<----- > default: > set device PPPoE:de0 > set authname foo > set authkey bar > set timeout 120 > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 > add default HISADDR > -----8<----- > > I'm using files from /sys/netgraph/* , /sys/net/if_ethersubr.c, and > /usr/src/usr.sbin/ppp/* from about 4pm EDT yesterday. > > As always, I'm open to suggestions. > > josh > > -- > Malkovitch! > > > 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 Nov 18 11:47:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail.snickers.org (snickers.org [216.126.90.2]) by hub.freebsd.org (Postfix) with ESMTP id 6525015039 for ; Thu, 18 Nov 1999 11:47:13 -0800 (PST) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id CD39F3D17; Thu, 18 Nov 1999 14:47:10 -0500 (EST) Date: Thu, 18 Nov 1999 14:47:10 -0500 From: Josh Tiefenbach To: Julian Elischer Cc: Josh Tiefenbach , freebsd-net@FreeBSD.ORG Subject: Re: PPPoE Redux. Message-ID: <19991118144710.A17531@snickers.org> References: <19991118094631.A9305@snickers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Hah Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 18, 1999 at 10:57:39AM -0800, Julian Elischer wrote: > I think this is a matter for Brian, but I'm glad to see that > the pppoe negotiation code is doing th eright thing now.. > Did it just "magically" start working, or did you change something? No. Not really. I just let the modem sit turned off for a day. Came back. Updated sources and recompiled. Turned on modem. Bam. It worked. 'Course. It magically stopped working after I rebooted, but I'm not really going to worry 'bout that excessively right now. > Maybe brian can give you more info on this bit.. Hopefully. Brian? :) josh -- Malkovitch! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 12:34:56 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-18.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.146]) by hub.freebsd.org (Postfix) with ESMTP id 0F55F154BD for ; Thu, 18 Nov 1999 12:34:50 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA03408; Thu, 18 Nov 1999 20:34:45 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA02780; Thu, 18 Nov 1999 20:39:19 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911182039.UAA02780@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: clark@pharlap.com (Clark Jarvis) Cc: Brian Somers , freebsd-net@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: rinit: wrong ifa (0xc09ba580) was (0xc0854880) - candidate for removal In-Reply-To: Message from clark@pharlap.com (Clark Jarvis) of "Thu, 18 Nov 1999 10:50:02 EST." <19991118154521924.AAA306@sugar.pharlap.com@clark> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Nov 1999 20:39:19 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In <199911172311.XAA03573@hak.lan.Awfulhak.org>, on 11/17/99 > at 11:11 PM, Brian Somers said: > > >This is a feature :-) It defeats the first-connection problem with > >dynamic IP numbers. It can be disabled with ``disable iface-alias'' and > >can be kept in control with an ``iface clear'' in ppp.linkdown - see > >share/examples/ppp.linkdown.sample. > > Brian, can you quickly describe the first-connection-... problem? I don't > remember seeing anything about this. A pointer to a description in the > code or somesuch would be OK too, of course. It's mentioned at http://www.FreeBSD.org/FAQ/userppp.html somewhere. > -- > Thanks, > Clark -- Brian 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 Thu Nov 18 14:10:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from netcom.com (netcom19.netcom.com [199.183.9.119]) by hub.freebsd.org (Postfix) with ESMTP id BFA72154B7 for ; Thu, 18 Nov 1999 14:10:35 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id OAA08900 for freebsd-net@FreeBSD.ORG; Thu, 18 Nov 1999 14:10:35 -0800 (PST) From: Stan Brown Message-Id: <199911182210.OAA08900@netcom.com> Subject: Road Runer cable modem network, and FreeBSD To: freebsd-net@FreeBSD.ORG Date: Thu, 18 Nov 1999 17:10:34 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am using a FreeBSD machine for my gateway to my cablemodem provider. Works really great, and I am as pleased as punch with it. Thanks for all the good work. Now a friend of mine has a cablemodem, and I want toset up a machine for him. However he is on the Road Runer netowk (Time Warner?). It is my understanding that the following are true of the: 1. They _require_ DHCP. 2. They require some sort of "login" after establishing the network layer connection. Bith of these are different from my cablemodem provider, and since he is in a different cty, having the mahcine set up as closely as possibe to a working system would be benefical. So, can anyone point me to a source of information on using FreeBSD for this? Can anyone confir that they have this working? Thanks. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 15: 8:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id CD86B1557C for ; Thu, 18 Nov 1999 15:07:47 -0800 (PST) (envelope-from coady@egroups.com) Received: from ahp3 (ahp.ne.mediaone.net [24.128.184.250]) by chmls05.mediaone.net (8.8.7/8.8.7) with SMTP id SAA27658; Thu, 18 Nov 1999 18:07:45 -0500 (EST) From: "coady" To: Cc: "Stan Brown" Subject: RE: Road Runer cable modem network, and FreeBSD Date: Thu, 18 Nov 1999 18:07:46 -0500 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) In-Reply-To: <199911182210.OAA08900@netcom.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm using FreeBSD 3.3 Release with a Road Runner (MediaOne) cable modem in the Boston area. I just set it up last week, so I'm a BSD newbie. It was not problem for me to get it working, once I was able to get FreeBSD to recognize my ethernet card. With the network card and cable modem both plugged in and working, I just selected DHCP when configuring the ethernet adapter in the sysinstall Networking --> Interfaces menu. It took about four seconds and sysintall bought up the correct parameters on the screen (IP address, host name, DNS server, etc.). If DHCP fails, sysinstall will bring up an error message and prompt you for the parameters. That happened to me when the "ep" driver in FreeBSD was not correctly recognizing the base address of my old 3COM ISA Etherlink III 3C509 based network adapter. During boot up, if DHCP fails, you will get a bunch of error messages at the tail end of the boot that relate to starting up network services. If DHCP succeeds, then "ifconfig -a" will show you the IP address you were assigned and "ping" etc. should work no problem. BTW, if you do have to run sysinstall more than once, you might want to check your /etc/rc.conf file to make sure it didn't get a bunch of junk added to it. At least in Boston, no login is required for the cable network. The only two places you need a login are: 1) checking your POP email 2) dialing into the network via a phone line (MediaOne calls this "remote access"). These situations are no different than any other ISP. Allen > -----Original Message----- > From: owner-freebsd-net@FreeBSD.ORG > [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Stan Brown > Sent: Thursday, November 18, 1999 5:11 PM > To: freebsd-net@FreeBSD.ORG > Subject: Road Runer cable modem network, and FreeBSD > > > I am using a FreeBSD machine for my gateway to my cablemodem provider. > Works really great, and I am as pleased as punch with it. Thanks for > all the good work. > > Now a friend of mine has a cablemodem, and I want toset up a machine > for him. However he is on the Road Runer netowk (Time Warner?). It is > my understanding that the following are true of the: > > 1. They _require_ DHCP. > 2. They require some sort of "login" after establishing the network > layer connection. > > Bith of these are different from my cablemodem provider, and since he > is in a different cty, having the mahcine set up as closely as possibe > to a working system would be benefical. > > So, can anyone point me to a source of information on using FreeBSD for > this? > > Can anyone confir that they have this working? > > Thanks. > > -- > Stan Brown stanb@netcom.com 404-996-6955 > Factory Automation Systems > Atlanta Ga. > -- > Look, look, see Windows 95. Buy, lemmings, buy! > Pay no attention to that cliff ahead... Henry Spencer > (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 15:22:36 1999 Delivered-To: freebsd-net@freebsd.org Received: from sol.microgate.com (www.microgate.com [216.30.46.105]) by hub.freebsd.org (Postfix) with ESMTP id 22E811508E for ; Thu, 18 Nov 1999 15:22:29 -0800 (PST) (envelope-from paulkf@microgate.com) Received: from diemos (diemos.microgate.com [192.168.0.12]) by sol.microgate.com (8.8.7/8.8.7) with SMTP id QAA17524; Thu, 18 Nov 1999 16:52:47 -0600 Message-ID: <001f01bf3216$735569b0$0c00a8c0@microgate.com> From: "Paul Fulghum" To: "Stan Brown" , References: <199911182210.OAA08900@netcom.com> Subject: Re: Road Runer cable modem network, and FreeBSD Date: Thu, 18 Nov 1999 16:44:19 -0600 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From Stan Brown > a friend of mine has a cablemodem, and I want toset up a machine > for him. However he is on the Road Runer netowk (Time Warner?). It is > my understanding that the following are true of the: > > 1. They _require_ DHCP. > 2. They require some sort of "login" after establishing the network > layer connection. ...Snip... > Can anyone confir that they have this working? I have FreeBSD (3.2) working as my gateway for Timer Warner Road Runner (aka Road Kill) in Austin, TX. The DHCP was not a problem, I used a dhcp client package in the ports (widedhcp I think). Directions for this package are straight forward. The user login, on the other hand, is a problem. There is a package on the net (search for rrlogin) that sort of worked some of the time :( Fortunately, at least in Austin, TW recently removed the login requirement unless you are changing account names/passwords etc over the net. So, if the login in your area is only required for acct maintenance then it should be smooth sailing (apart from the spotty service of RR), otherwise you may be struggling. Good Luck Paul Fulghum paulkf@microgate.com Microgate Corporation www.microgate.com 9501 Capital of Texas Hwy Austin, Texas 78759 (512)-345-7791 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 21: 0:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from tim.281.com (tim.281.com [209.84.39.7]) by hub.freebsd.org (Postfix) with ESMTP id 4F2801508E for ; Thu, 18 Nov 1999 21:00:33 -0800 (PST) (envelope-from rjoe@tim.281.com) Received: (from rjoe@localhost) by tim.281.com (8.9.2/8.9.2) id XAA55688 for freebsd-net@freebsd.org; Thu, 18 Nov 1999 23:00:33 -0600 (CST) (envelope-from rjoe) Date: Thu, 18 Nov 1999 23:00:33 -0600 (CST) From: Joe Schwartz Message-Id: <199911190500.XAA55688@tim.281.com> To: freebsd-net@freebsd.org Subject: oldest Y2K release? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry to bother you folks, but I regard you all as the most knowledgable. I have several 2.6 machines at customer sites and am trying to locate info on how far back the Y2K compiancy goes. What is the oldest Y2K release? Thankyou, Joe Schwartz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Nov 18 21:12:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 9C95815260 for ; Thu, 18 Nov 1999 21:12:37 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FLF002M8IGZW1@mta4.rcsntx.swbell.net> for freebsd-net@FreeBSD.ORG; Thu, 18 Nov 1999 23:12:36 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id XAA18652; Thu, 18 Nov 1999 23:13:47 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Thu, 18 Nov 1999 23:13:45 -0600 From: Chris Costello Subject: Re: oldest Y2K release? In-reply-to: <199911190500.XAA55688@tim.281.com> To: Joe Schwartz Cc: freebsd-net@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991118231345.T7229@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199911190500.XAA55688@tim.281.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 18, 1999, Joe Schwartz wrote: > I have several 2.6 machines at customer sites and am trying to locate > info on how far back the Y2K compiancy goes. > > What is the oldest Y2K release? Specifically what are you talking about? The most recent Y2K fix was in 3.3-RELEASE. This means it wasn't fixed until then. I assume by '2.6' you mean '2.2.6'. -- |Chris Costello |Your password is pitifully obvious. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 1: 8:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from ASN.WN.Com.UA (asn.wn.com.ua [194.44.146.154]) by hub.freebsd.org (Postfix) with ESMTP id B94A914CE3 for ; Fri, 19 Nov 1999 01:08:14 -0800 (PST) (envelope-from romik@ASN.WN.Com.UA) Received: (from romik@localhost) by ASN.WN.Com.UA (8.9.3/8.9.3) id LAA02763 for freebsd-net@FreeBSD.ORG; Sun, 19 Dec 1999 11:08:38 +0200 (EET) (envelope-from romik) Date: Sun, 19 Dec 1999 11:08:37 +0200 From: "Roman N. Dmitrik" To: freebsd-net@FreeBSD.ORG Subject: /kernel: -- warning, refcnt now 0, decreasing Message-ID: <19991219110837.A2757@WN.NET.UA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i X-Operating-System: FreeBSD ASN.WN.Com.UA 3.2-RELEASE FreeBSD 3.2-RELEASE Organization: WN Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All! I have a FreeBSD 3.2-RELEASE and using DUMMYNET. The freebsd reboot time to time. In log I see this messages kernel: -- warning, refcnt now 0, decreasing kernen: -- warning, refcnt now -1, decreasing kernen: -- warning, refcnt now -2, decreasing How can solve this problem? -- Regards, Roman D. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 13:42:59 1999 Delivered-To: freebsd-net@freebsd.org Received: from sierrahill.com (sierrahill.com [209.198.135.2]) by hub.freebsd.org (Postfix) with ESMTP id 58547156CC for ; Fri, 19 Nov 1999 13:42:30 -0800 (PST) (envelope-from rjoe@sierrahill.com) Received: (from rjoe@localhost) by smtp.sierrahill.com (8.8.8/8.8.8) id WAA24696 for freebsd-net@freebsd.org; Thu, 18 Nov 1999 22:41:16 -0600 (CST) (envelope-from rjoe) Date: Thu, 18 Nov 1999 22:41:16 -0600 (CST) From: Joe Schwartz Message-Id: <199911190441.WAA24696@smtp.sierrahill.com> To: freebsd-net@freebsd.org Subject: oldest Y2K release? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry to bother you folks, but I regard you all as the most knowledgable. I have several 2.6 machines at customer sites and am trying to locate info on how far back the Y2K compiancy goes. What is the oldest Y2K release? Thankyou, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 13:43:22 1999 Delivered-To: freebsd-net@freebsd.org Received: from sierrahill.com (sierrahill.com [209.198.135.2]) by hub.freebsd.org (Postfix) with ESMTP id 393FD15713 for ; Fri, 19 Nov 1999 13:42:30 -0800 (PST) (envelope-from rjoe@sierrahill.com) Received: (from rjoe@localhost) by sierrahill.com (8.8.8/8.8.8) id WAA24616 for freebsd-net@freebsd.org; Thu, 18 Nov 1999 22:23:07 -0600 (CST) (envelope-from rjoe) Date: Thu, 18 Nov 1999 22:23:07 -0600 (CST) From: Joe Schwartz Message-Id: <199911190423.WAA24616@sierrahill.com> To: freebsd-net@freebsd.org Subject: oldest Y2K release? Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, Sorry to bother you folks, but I regard you all as the most knowledgable. I have several 2.6 machines at customer sites and am trying to locate info on how far back the Y2K compiancy goes. What is the oldest Y2K release? Thankyou, Joe Schwartz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 13:43:39 1999 Delivered-To: freebsd-net@freebsd.org Received: from sierrahill.com (sierrahill.com [209.198.135.2]) by hub.freebsd.org (Postfix) with ESMTP id 8278515793 for ; Fri, 19 Nov 1999 13:42:30 -0800 (PST) (envelope-from rjoe@sierrahill.com) Received: (from rjoe@localhost) by sierrahill.com (8.8.8/8.8.8) id HAA22701 for freebsd-net@freebsd.org; Thu, 18 Nov 1999 07:32:04 -0600 (CST) (envelope-from rjoe) From: Joe Schwartz Message-Id: <199911181332.HAA22701@sierrahill.com> Subject: oldest FreeBSD Y2K release ? To: freebsd-net@freebsd.org Date: Thu, 18 Nov 1999 07:32:04 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry to bother you folks, but I regard you all as the most knowledgable. I have several 2.6 machines at customer sites and am trying to locate info on how far back the Y2K compiancy goes. What is the oldest Y2K release? Thankyou, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 14: 0: 7 1999 Delivered-To: freebsd-net@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 27D0D15296 for ; Fri, 19 Nov 1999 13:59:55 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FLG00128T1XX8@mta1.rcsntx.swbell.net> for freebsd-net@FreeBSD.ORG; Fri, 19 Nov 1999 15:58:49 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id PAA20635; Fri, 19 Nov 1999 15:59:53 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Fri, 19 Nov 1999 15:59:48 -0600 From: Chris Costello Subject: Re: oldest FreeBSD Y2K release ? In-reply-to: <199911181332.HAA22701@sierrahill.com> To: Joe Schwartz Cc: freebsd-net@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991119155948.X7229@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199911181332.HAA22701@sierrahill.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 18, 1999, Joe Schwartz wrote: ... Stop posting your question. I answered it the first time. What more do you want? What do you expect to accomplish by posting it three times to the same mailing list, _in addition_ to the first time? -- |Chris Costello |Breaking Windows isn't just for kids anymore.... `------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 14:20:43 1999 Delivered-To: freebsd-net@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8175C14BCE for ; Fri, 19 Nov 1999 14:20:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA94026; Fri, 19 Nov 1999 14:19:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Joe Schwartz Cc: freebsd-net@FreeBSD.ORG Subject: Re: oldest Y2K release? In-reply-to: Your message of "Thu, 18 Nov 1999 22:23:07 CST." <199911190423.WAA24616@sierrahill.com> Date: Fri, 19 Nov 1999 14:19:59 -0800 Message-ID: <94016.943049999@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have several 2.6 machines at customer sites and am trying to locate > info on how far back the Y2K compiancy goes. 1. 5 copies of this message was really over the top. If you do this kind of thing again, expect to get yourself banned from the mailing lists altogether. Mailing list usage is not a right, it's a privilege, and abusing that privilege is really not encouraged. 2. We've never released a "2.6" version, leading me to wonder if you're actually talking about Solaris here. If so, you've *really* gone over the top in the mailing list abuse department. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Nov 19 14:55:33 1999 Delivered-To: freebsd-net@freebsd.org Received: from awfulhak.org (dynamic-8.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.136]) by hub.freebsd.org (Postfix) with ESMTP id 7E8C814CF8 for ; Fri, 19 Nov 1999 14:55:27 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id UAA02313; Fri, 19 Nov 1999 20:31:14 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA00312; Fri, 19 Nov 1999 17:26:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911191726.RAA00312@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Josh Tiefenbach Cc: Julian Elischer , freebsd-net@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: PPPoE Redux. In-Reply-To: Message from Josh Tiefenbach of "Thu, 18 Nov 1999 14:47:10 EST." <19991118144710.A17531@snickers.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Nov 1999 17:26:04 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, Nov 18, 1999 at 10:57:39AM -0800, Julian Elischer wrote: > > I think this is a matter for Brian, but I'm glad to see that > > the pppoe negotiation code is doing th eright thing now.. > > Did it just "magically" start working, or did you change something? > > No. Not really. I just let the modem sit turned off for a day. Came back. > Updated sources and recompiled. Turned on modem. Bam. It worked. 'Course. It > magically stopped working after I rebooted, but I'm not really going to worry > 'bout that excessively right now. Hmm, you didn't update tcpdump ? It'd be nice to see the PPPoE packets interpreted (which the -current tcpdump now does). > > Maybe brian can give you more info on this bit.. > > Hopefully. Brian? :) Maybe not without a log file. I *suspect* you need to ``set cd 3'' (or maybe higher). Currently, ppp polls the netgraph node every second to see if it's received a SUCCESS message. It does this only for the carrier detect timeout, which is 1 second by default. ``set cd'' changes this. This is a limitation we're stuck with 'till I abstract the ``set dial'' and ``set hangup'' commands so that they're device specific - on my todo list. For the time being, ppp can't select() on the descriptor during negotiation. > josh > > -- > Malkovitch! -- Brian 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 Sat Nov 20 6: 1:25 1999 Delivered-To: freebsd-net@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 7B41514CC0 for ; Sat, 20 Nov 1999 06:01:23 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id IAA34440; Sat, 20 Nov 1999 08:01:21 -0600 (CST) From: Joe Greco Message-Id: <199911201401.IAA34440@aurora.sol.net> Subject: Re: RIPv2/OSPF over tun0 using GateD? In-Reply-To: from Mike Wade at "Oct 28, 1999 2:42:15 pm" To: mwade@cdc.net (Mike Wade) Date: Sat, 20 Nov 1999 08:01:21 -0600 (CST) Cc: net@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Is it possible to use GateD with RIPv2/OSPF over the tunnel interfaces? > ie: tun0 and friends? If so, how? Of course, I do it regularly with OSPF. Specify it as a point-to-point link. OSPF doesn't care. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 20 11: 2:30 1999 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 5A18114C94 for ; Sat, 20 Nov 1999 11:02:23 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id TAA01210; Sat, 20 Nov 1999 19:43:04 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <199911201843.TAA01210@info.iet.unipi.it> Subject: Re: /kernel: -- warning, refcnt now 0, decreasing In-Reply-To: <19991219110837.A2757@WN.NET.UA> from "Roman N. Dmitrik" at "Dec 19, 1999 11:08:37 am" To: "Roman N. Dmitrik" Date: Sat, 20 Nov 1999 19:43:04 +0100 (CET) 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 X-Loop: FreeBSD.org > Hi All! > > I have a FreeBSD 3.2-RELEASE and using DUMMYNET. > The freebsd reboot time to time. > In log I see this messages > > kernel: -- warning, refcnt now 0, decreasing > kernen: -- warning, refcnt now -1, decreasing > kernen: -- warning, refcnt now -2, decreasing there is a simple patch i will commit next week to ip_dummynet.c are you using the"forward" option by chance ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 20 12:37:41 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 7A66514C88; Sat, 20 Nov 1999 12:37:20 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.38]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA101C; Sat, 20 Nov 1999 21:37:17 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA46513; Sat, 20 Nov 1999 21:37:14 +0100 (CET) (envelope-from asmodai) Date: Sat, 20 Nov 1999 21:37:13 +0100 From: Jeroen Ruigrok/Asmodai To: net@freebsd.org Cc: cvs-committers@freebsd.org Subject: Patches for socket.h Message-ID: <19991120213713.N41154@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="cWoXeonUoKmBZSoM" X-Mailer: Mutt 1.0pre3i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Hi, in an effort to sync us with NetBSD and be more compliant with SUSv2 I present two patches. One to socket.h, which introduces the type socklen_t which replaces the unsigned integer in some areas. One caveat for now is the sa_family_t type, which would be the type for sa_family in the sockaddr struct. Also, the msg_name and msg_control members of msghdr have now been made pointers of type void. The patch in uipc_syscalls.c is needed to cast msg_control to caddr_t. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html Beauty is a short-lived reign... --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="socket.h.diff" --- sys/sys/socket.h.orig Sat Nov 20 19:27:48 1999 +++ sys/sys/socket.h Sat Nov 20 21:10:06 1999 @@ -42,6 +42,11 @@ */ /* + * Data types. + */ +typedef unsigned int socklen_t; + +/* * Types */ #define SOCK_STREAM 1 /* stream socket */ @@ -289,13 +294,13 @@ * Used value-result for recvmsg, value only for sendmsg. */ struct msghdr { - caddr_t msg_name; /* optional address */ - u_int msg_namelen; /* size of address */ - struct iovec *msg_iov; /* scatter/gather array */ - u_int msg_iovlen; /* # elements in msg_iov */ - caddr_t msg_control; /* ancillary data, see below */ - u_int msg_controllen; /* ancillary data buffer len */ - int msg_flags; /* flags on received message */ + void *msg_name; /* optional address */ + socklen_t msg_namelen; /* size of address */ + struct iovec *msg_iov; /* scatter/gather array */ + u_int msg_iovlen; /* # elements in msg_iov */ + void *msg_control; /* ancillary data, see below */ + socklen_t msg_controllen; /* ancillary data buffer len */ + int msg_flags; /* flags on received message */ }; #define MSG_OOB 0x1 /* process out-of-band data */ @@ -316,9 +321,9 @@ * of message elements headed by cmsghdr structures. */ struct cmsghdr { - u_int cmsg_len; /* data byte count, including hdr */ - int cmsg_level; /* originating protocol */ - int cmsg_type; /* protocol-specific type */ + socklen_t cmsg_len; /* data byte count, including hdr */ + int cmsg_level; /* originating protocol */ + int cmsg_type; /* protocol-specific type */ /* followed by u_char cmsg_data[]; */ }; @@ -414,22 +419,22 @@ #include __BEGIN_DECLS -int accept __P((int, struct sockaddr *, int *)); -int bind __P((int, const struct sockaddr *, int)); -int connect __P((int, const struct sockaddr *, int)); -int getpeername __P((int, struct sockaddr *, int *)); -int getsockname __P((int, struct sockaddr *, int *)); -int getsockopt __P((int, int, int, void *, int *)); +int accept __P((int, struct sockaddr *, socklen_t *)); +int bind __P((int, const struct sockaddr *, socklen_t)); +int connect __P((int, const struct sockaddr *, socklen_t)); +int getpeername __P((int, struct sockaddr *, socklen_t *)); +int getsockname __P((int, struct sockaddr *, socklen_t *)); +int getsockopt __P((int, int, int, void *, socklen_t *)); int listen __P((int, int)); ssize_t recv __P((int, void *, size_t, int)); -ssize_t recvfrom __P((int, void *, size_t, int, struct sockaddr *, int *)); +ssize_t recvfrom __P((int, void *, size_t, int, struct sockaddr *, socklen_t *)); ssize_t recvmsg __P((int, struct msghdr *, int)); ssize_t send __P((int, const void *, size_t, int)); ssize_t sendto __P((int, const void *, - size_t, int, const struct sockaddr *, int)); + size_t, int, const struct sockaddr *, socklen_t)); ssize_t sendmsg __P((int, const struct msghdr *, int)); int sendfile __P((int, int, off_t, size_t, struct sf_hdtr *, off_t *, int)); -int setsockopt __P((int, int, int, const void *, int)); +int setsockopt __P((int, int, int, const void *, socklen_t)); int shutdown __P((int, int)); int socket __P((int, int, int)); int socketpair __P((int, int, int, int *)); --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="uipc_syscalls.c.diff" --- sys/kern/uipc_syscalls.c.orig Sat Nov 20 20:44:24 1999 +++ sys/kern/uipc_syscalls.c Sat Nov 20 20:34:28 1999 @@ -805,7 +805,7 @@ len -= tocopy; m = m->m_next; } - mp->msg_controllen = ctlbuf - mp->msg_control; + mp->msg_controllen = ctlbuf - (caddr_t)mp->msg_control; } out: if (fromsa) --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 20 15:56:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from foo.sics.se (foo.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 9350814C84; Sat, 20 Nov 1999 15:56:08 -0800 (PST) (envelope-from assar@foo.sics.se) Received: (from assar@localhost) by foo.sics.se (8.9.3/8.9.3) id AAA00792; Sun, 21 Nov 1999 00:56:16 +0100 (CET) (envelope-from assar) To: Jeroen Ruigrok/Asmodai Cc: net@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: Patches for socket.h References: <19991120213713.N41154@daemon.ninth-circle.org> From: Assar Westerlund Date: 21 Nov 1999 00:56:15 +0100 In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Sat, 20 Nov 1999 21:37:13 +0100" Message-ID: <5l903sn2e8.fsf@foo.sics.se> Lines: 19 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeroen Ruigrok/Asmodai writes: > One to socket.h, which introduces the type socklen_t which replaces the > unsigned integer in some areas. ok > One caveat for now is the sa_family_t type, which would be the type for > sa_family in the sockaddr struct. typedef u_char sa_family_t or is it more complicated than that? > --- sys/sys/socket.h.orig Sat Nov 20 19:27:48 1999 > +++ sys/sys/socket.h Sat Nov 20 21:10:06 1999 > + u_int msg_iovlen; /* # elements in msg_iov */ Shouldn't this be `int'? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Nov 20 16: 4:27 1999 Delivered-To: freebsd-net@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 3443214C84; Sat, 20 Nov 1999 16:04:23 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.38]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA197C; Sun, 21 Nov 1999 01:04:22 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id BAA47121; Sun, 21 Nov 1999 01:04:16 +0100 (CET) (envelope-from asmodai) Date: Sun, 21 Nov 1999 01:04:16 +0100 From: Jeroen Ruigrok/Asmodai To: Assar Westerlund Cc: net@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: Patches for socket.h Message-ID: <19991121010416.R41154@daemon.ninth-circle.org> References: <19991120213713.N41154@daemon.ninth-circle.org> <5l903sn2e8.fsf@foo.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <5l903sn2e8.fsf@foo.sics.se> Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [19991121 00:58], Assar Westerlund (assar@sics.se) wrote: >Jeroen Ruigrok/Asmodai writes: >> One to socket.h, which introduces the type socklen_t which replaces the >> unsigned integer in some areas. > >ok Ok, kernel compiles and works ok, I forgot to patch the uthread stuff though. I am testing make world with those patches now. Don't know if I am awake when it's done though. >> One caveat for now is the sa_family_t type, which would be the type for >> sa_family in the sockaddr struct. > >typedef u_char sa_family_t or is it more complicated than that? That should be it. But like uthread, I didn't want to bump into other surprises. >> --- sys/sys/socket.h.orig Sat Nov 20 19:27:48 1999 >> +++ sys/sys/socket.h Sat Nov 20 21:10:06 1999 > >> + u_int msg_iovlen; /* # elements in msg_iov */ > >Shouldn't this be `int'? Duh, I removed the file after I changed a little too much and reworked the patches. I forgot to change this back again to int. Thanks. I'll make a new patchset tomorrow. Thanks for taking the time to test it. -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html Life is just one damned thing after another. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message