From owner-freebsd-net Sun Dec 3 13:33: 4 2000 From owner-freebsd-net@FreeBSD.ORG Sun Dec 3 13:33:03 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from relay.flashnet.it (ems.flashnet.it [194.247.160.44]) by hub.freebsd.org (Postfix) with ESMTP id 5253037B400 for ; Sun, 3 Dec 2000 13:33:02 -0800 (PST) Received: from smtp.flashnet.it (ip114.pool-173.cyb.it [195.191.181.115]) by relay.flashnet.it (EMS-RELAY/8.10.0) with SMTP id eB3LWxU13567 for ; Sun, 3 Dec 2000 22:33:00 +0100 Message-Id: <200012032133.eB3LWxU13567@relay.flashnet.it> To: freebsd-net@freebsd.org Priority: Normal X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Sun, 3 Dec 2000 22:33:00 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: ppp server help: found out! Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there! This is what I sent some days ago: >I'm trying to set up a ppp server on a 4.1.1-R system; the modem answers correctly, but I >get the following in /var/log/ppp.log: >... Now, I did some research and what I found out is that ppp does not de-HDLC-fy the packets it receives: it behaves correctly when I dial out to my ISP through my ISDN card, but it does not remove the hdlc header before giving the packet to LCP when I use it as a server on my modem. Similarly it does not add the HDLC header and terminations to packets it sends, so the peer complains about fcs errors. Right now I'm using pppd which behaves correctly, but in the end I'd rather be using user-ppp. Do anyone knows how to force it to use hdlc (if I "set log hdlc", I see no message at all)? Did I found a bug in 4.1.1-R? Bye & Thanks av. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 3 22:43:43 2000 From owner-freebsd-net@FreeBSD.ORG Sun Dec 3 22:43:41 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from osku.suutari.iki.fi (osku.syncrontech.com [213.28.98.4]) by hub.freebsd.org (Postfix) with ESMTP id E3A2A37B401 for ; Sun, 3 Dec 2000 22:43:40 -0800 (PST) Received: from coffee (adsl-nat.syncrontech.com [213.28.98.3]) by osku.suutari.iki.fi (8.9.3/8.9.3) with SMTP id IAA76655; Mon, 4 Dec 2000 08:43:32 +0200 (EET) (envelope-from ari@suutari.iki.fi) Message-ID: <001801c05dbd$859d1400$0e05a8c0@intranet.syncrontech.com> From: "Ari Suutari" To: "Dominick LaTrappe" Cc: References: Subject: Re: filtering ipsec traffic (fwd) Date: Mon, 4 Dec 2000 08:43:32 +0200 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > On Fri, 1 Dec 2000, Ari Suutari wrote: > > But what if we are running in IPsec tunnel mode ? > > Then there's no problem. Please read the original post. I thought that I read it but maybe I didn't understand. > > > Last time I tried that adding on 'ipfw pass any from 192.168.x.x .....' > > also allowed non-ipsec traffic between these nodes. > > Of course, because you didn't specify any particular protocol in the rule. Hmmm (I tested this with FreeBSD 4.1). I didn't want any protocol limitation between VPN sites, since they trust each other (they are just different offices in same company). I just wanted that between IPsec tunnel gateways only esp is allowed and there are no limitations betwen VPN sites *EXCEPT* that packets must be coming through IPsec tunnel. So what I was missing is something like ipfw pass any from 192.168.x.x to .... via this-ipsec-tunnel I am able to configure system this way when using pipsecd, since it passes traffic coming from tunnel to tunX device. > > This is a security hole, which allows someone to > > send packets with spoofed source address to your system. > > IP spoofing is a routing issue, totally irrelevant to this thread. The spoofing was only one problem that comes to my mind with this. The real problem is that I wasn't able to force use of IPsec with ipfw + kame. Ari S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sun Dec 3 23:29:19 2000 From owner-freebsd-net@FreeBSD.ORG Sun Dec 3 23:29:17 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from operamail.com (OperaMail.com [199.29.68.79]) by hub.freebsd.org (Postfix) with ESMTP id 425C237B400 for ; Sun, 3 Dec 2000 23:29:17 -0800 (PST) X-WM-Posted-At: operamail.com; Mon, 4 Dec 00 02:29:16 -0500 X-WebMail-UserID: whelkman Date: Mon, 4 Dec 2000 02:29:16 -0500 Sender: Robert Kosinski From: Robert Kosinski To: freebsd-net@freebsd.org X-EXP32-SerialNo: 00000000 Subject: Odd TCP / DNS behavior in 4.x Message-ID: <3A2B9094@operamail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: InterChange (Hydra) SMTP v3.61.08 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greets to all. I posted this message in freebsd-questions before but did not receive a response; I am hoping this list may be more appropriate for this situation. I am using FreeBSD 4.2-STABLE (CTM 4.0342), but this problem has persisted throughout several upgrades of the machine. This box is used as a packet filtering firewall with network address translation for a small, private class-C network (192.168.0.0/24). Besides a minor problem with ICQ logging off about every ten minutes and then coming back on, all machines behind the firewall have as normal TCP, UDP, etc. access as you could expect from NAT. The problem is: TCP access on the actual FreeBSD machine is flaky at best. For some reason, I can only connect to about 50% of all sites I have attempted. This problem affects FTP (and the ports collection), HTTP (and the Squid proxy), and probably all TCP-based traffic. The same 50% of the sites I cannot access remain constant. ICMP (ping and traceroute) seems not affected. What appears to happen on the "dead" sites is a DNS lookup and an eventual timeout. The same DNS servers are used by the FreeBSD machine as well as machines behind the firewall, so I do not believe I am a victim of defective DNS servers. Manually resolving the IPs of affected sites and attempting to connect to the IP results in failure as well. I know this is not a problem with the NAT configuration because I have shut off NAT completely and used the FreeBSD machine as a regular client. Of course the problem persists. I have to load at least a minimal IPFW rule set since the machine's ports are closed by default. For now, I am using a minor variation of the "open" rule set from FreeBSD's default rc.firewall. Neither the original rc.firewall rule set nor the set I'm using result in proper communication from the physical FreeBSD machine. For record, the IPFW rule set is /sbin/ipfw -f flush /sbin/ipfw add divert natd all from any to any via tun0 /sbin/ipfw add pass all from any to any /sbin/ipfw add 100 pass all from any to any via lo0 /sbin/ipfw add 200 deny all from any to 127.0.0.0/8 and the natd rule set is log no deny_incoming no same_ports yes dynamic yes verbose no interface tun0 redirect_port tcp 192.168.0.2:2000-2020 2000-2020 Any help would be greatly appreciated. I am utterly stumpted as to what is causing this error, and I am out of ideas. Thank you all for your time and consideration. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 4 8: 4: 1 2000 From owner-freebsd-net@FreeBSD.ORG Mon Dec 4 08:03:57 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E63537B400 for ; Mon, 4 Dec 2000 08:03:57 -0800 (PST) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id JAA47380; Mon, 4 Dec 2000 09:03:46 -0700 (MST) Date: Mon, 4 Dec 2000 09:03:45 -0700 (MST) From: Nick Rogness To: Robert Kosinski Cc: freebsd-net@freebsd.org Subject: Re: Odd TCP / DNS behavior in 4.x In-Reply-To: <3A2B9094@operamail.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 Mon, 4 Dec 2000, Robert Kosinski wrote: Hard to say what it is. Did you try running on different hardware? Any unusual syslog entries? More comments below. > I am using FreeBSD 4.2-STABLE (CTM 4.0342), but this problem has persisted > throughout several upgrades of the machine. This box is used as a packet > filtering firewall with network address translation for a small, private > class-C > network (192.168.0.0/24). Besides a minor problem with ICQ logging off about > every ten minutes and then coming back on, all machines behind the firewall > have > as normal TCP, UDP, etc. access as you could expect from NAT. > > The problem is: TCP access on the actual FreeBSD machine is flaky at best. > For > some reason, I can only connect to about 50% of all sites I have attempted. > This problem affects FTP (and the ports collection), HTTP (and the Squid > proxy), > and probably all TCP-based traffic. The same 50% of the sites I cannot access > remain constant. ICMP (ping and traceroute) seems not affected. > > What appears to happen on the "dead" sites is a DNS lookup and an eventual > timeout. The same DNS servers are used by the FreeBSD machine as well as > machines behind the firewall, so I do not believe I am a victim of defective > DNS > servers. Are you running bind? If so, your /etc/resolv.conf file should look someting like: domain domainname.com nameserver 127.0.0.1 You should be querying your local nameserver before going out to ask others. Do you have forwarders configured? Manually resolving the IPs of affected sites and attempting to > connect > to the IP results in failure as well. > > I know this is not a problem with the NAT configuration because I have shut > off > NAT completely and used the FreeBSD machine as a regular client. Of course > the > problem persists. > > I have to load at least a minimal IPFW rule set since the machine's ports are > closed by default. For now, I am using a minor variation of the "open" rule > set > from FreeBSD's default rc.firewall. Neither the original rc.firewall rule set > nor the set I'm using result in proper communication from the physical FreeBSD > machine. > > For record, the IPFW rule set is > > /sbin/ipfw -f flush > /sbin/ipfw add divert natd all from any to any via tun0 > /sbin/ipfw add pass all from any to any > /sbin/ipfw add 100 pass all from any to any via lo0 > /sbin/ipfw add 200 deny all from any to 127.0.0.0/8 > What is the output of `ipfw -a l' ? If you are going to use rule numbers use rule numbers on every rule. Makes it easier to understand (IMO). Rule #100 and #200 never get used in the above ruleset. Move them to before the natd statement. > and the natd rule set is > > log no > deny_incoming no > same_ports yes > dynamic yes > verbose no > interface tun0 > redirect_port tcp 192.168.0.2:2000-2020 2000-2020 > Turn off deny_incoming while testing. Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 4 11:31: 7 2000 From owner-freebsd-net@FreeBSD.ORG Mon Dec 4 11:31:04 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1907537B400 for ; Mon, 4 Dec 2000 11:31:04 -0800 (PST) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Dec 2000 19:31:02 +0000 (GMT) To: freebsd-net@freebsd.org Cc: iedowse@maths.tcd.ie Subject: panic in nd6_dad_timer when removing pccard Date: Mon, 04 Dec 2000 19:31:01 +0000 From: Ian Dowse Message-ID: <200012041931.aa09203@salmon.maths.tcd.ie> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got a panic today on 4.1-STABLE when removing a pccard shortly after it was inserted. I was running with "options INVARIANTS", which may have helped to trigger the problem. I was able to determine that the panic was caused by an outstanding nd6_dad_timer on a 'struct ifaddr' from a detached interface. The struct ifaddr was still valid, since a reference count system is used; however its ifa_ifp pointed to a memory region that had been freed. I think (though unfortunately I don't have the crash dump any more) that the problem occurred at the lines /* * We have more NS to go. Send NS packet for DAD. */ nd6_dad_ns_output(dp, ifa); dp->dad_timer = timeout((void (*) __P((void *)))nd6_dad_timer, (void *)ifa, nd_ifinfo[ifa->ifa_ifp->if_index].retrans * hz / 1000); since the stale ifa_ifp is dereferenced there. It seems that there is currently no way to determine if a struct ifaddr points to a detached interface - how about a fix such as the one below? It sets all stale ifa_ifp pointers to NULL in if_detach, and checks for this case in nd6_dad_timer. Ian Index: net/if.c =================================================================== RCS file: /home/iedowse/CVS/src/sys/net/if.c,v retrieving revision 1.85.2.3 diff -u -r1.85.2.3 if.c --- net/if.c 2000/08/22 18:06:20 1.85.2.3 +++ net/if.c 2000/12/04 16:23:23 @@ -270,6 +270,7 @@ } #endif /* INET6 */ TAILQ_REMOVE(&ifp->if_addrhead, ifa, ifa_link); + ifa->ifa_ifp = NULL; IFAFREE(ifa); } Index: netinet6/nd6_nbr.c =================================================================== RCS file: /home/iedowse/CVS/src/sys/netinet6/nd6_nbr.c,v retrieving revision 1.4.2.2 diff -u -r1.4.2.2 nd6_nbr.c --- netinet6/nd6_nbr.c 2000/07/15 07:14:36 1.4.2.2 +++ netinet6/nd6_nbr.c 2000/12/04 16:29:18 @@ -1083,6 +1083,14 @@ log(LOG_ERR, "nd6_dad_timer: DAD structure not found\n"); goto done; } + if (ifa->ifa_ifp == NULL) { + /* Interface has gone away */ + TAILQ_REMOVE(&dadq, (struct dadq *)dp, dad_list); + free(dp, M_IP6NDP); + dp = NULL; + IFAFREE(ifa); + goto done; + } if (ia->ia6_flags & IN6_IFF_DUPLICATED) { log(LOG_ERR, "nd6_dad_timer: called with duplicated address " "%s(%s)\n", To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 4 13:42:29 2000 From owner-freebsd-net@FreeBSD.ORG Mon Dec 4 13:42:28 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from user2.pro-ns.net (user2.pro-ns.net [208.200.182.45]) by hub.freebsd.org (Postfix) with ESMTP id 6A4B137B400 for ; Mon, 4 Dec 2000 13:42:27 -0800 (PST) Received: from Debug (ds1.pro-ns.net [208.200.182.29]) by user2.pro-ns.net (8.11.1/8.11.1) with SMTP id eB4LgOW49981 for ; Mon, 4 Dec 2000 15:42:24 -0600 (CST) Message-Id: <200012042142.eB4LgOW49981@user2.pro-ns.net> To: freebsd-net@freebsd.org From: mwright@pro-ns.net Subject: Is it possible to use a LanMedia LMC1200 with frame relay? Date: Mon, 4 Dec 2000 15:42:23 CST X-Mailer: Endymion MailMan Standard Edition v3.0.19 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have any experience using a LanMedia 1200 with frame relay? How did they configure it? MarkScottWright@hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 4 14: 2:18 2000 From owner-freebsd-net@FreeBSD.ORG Mon Dec 4 14:02:16 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 051A437B402 for ; Mon, 4 Dec 2000 14:02:11 -0800 (PST) Received: from gaborone-09.budapest.interware.hu ([195.70.52.137] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 1433gX-0002hS-00; Mon, 04 Dec 2000 23:02:09 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2C144D.FF557FFE@elischer.org> Date: Mon, 04 Dec 2000 14:01:49 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: mwright@pro-ns.net Cc: freebsd-net@freebsd.org Subject: Re: Is it possible to use a LanMedia LMC1200 with frame relay? References: <200012042142.eB4LgOW49981@user2.pro-ns.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org mwright@pro-ns.net wrote: > > Does anyone have any experience using a LanMedia 1200 with frame relay? How > did they configure it? > > MarkScottWright@hotmail.com If it's supported by one of the drivers that supports netgraph then yes it can do frame relay.. check the examples in /usr/share/examples/netgraph and substitute in the appropriate driver name. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 4 14: 6:17 2000 From owner-freebsd-net@FreeBSD.ORG Mon Dec 4 14:06:14 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from operamail.com (OperaMail.com [199.29.68.79]) by hub.freebsd.org (Postfix) with ESMTP id 4259E37B400 for ; Mon, 4 Dec 2000 14:06:14 -0800 (PST) X-WM-Posted-At: operamail.com; Mon, 4 Dec 00 17:06:12 -0500 X-WebMail-UserID: whelkman Date: Mon, 4 Dec 2000 17:06:12 -0500 Sender: Robert Kosinski From: Robert Kosinski To: Nick Rogness Cc: freebsd-net X-EXP32-SerialNo: 00000000 Subject: RE: Odd TCP / DNS behavior in 4.x Message-ID: <3A2CF65D@operamail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: InterChange (Hydra) SMTP v3.61.08 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thank you for your prompt reply, Mr. Rogness. > Did you try running on different hardware? No, but I do not see how the outgoing device can be at fault. The outgoing device is a US Robotics 56K Voice/Fax modem (yuck, I know). It has given me flawless operation under several operating systems and even appears to function normally under FreeBSD. As I said, there are no problems NAT-ting through the box, just using the FreeBSD machine itself. The only hardware I have to swap in place of it is another USR 56k modem. > Any unusual syslog entries? There aren't any normal syslog entries at all, but if I browse through Squid, I receive the following log entries in access.log several minutes after attempting to access the site: 975964740.216 240966 192.168.0.2 TCP_MISS/504 1039 GET http://litestep.org/ - DIRECT/litestep.org - Of course, I have attempted to connect to litestep.org (which is just a redirect to litestep.net which does not work, either). 975965019.609 241570 192.168.0.2 TCP_MISS/504 1041 GET http://209.116.0.210/ - DIRECT/209.116.0.210 - I resolved litestep.org to its IP, 209.116.0.210, and attempted to connect to that. litestep.org, www.litestep.org, litestep.net, and www.litestep.net all share the same IP. A 504 is a gateway timeout, I know, but that's about all I can say regarding it. Just to refresh, by turning off Squid (which resides on the FreeBSD box) and connecting to a site without it from a machine behind the firewall (i.e. using packet forwarding), the site will load correctly. > Are you running bind? No. > Rule #100 and #200 never get used in the above ruleset. Move them > to before the natd statement. I was wondering about that. I didn't think there was a chance they would get used, either. Truth is, I just ripped that off of FreeBSD Diary and never paid attention to the rules since those and the FreeBSD shipped "open" ruleset function the same as far as connections from the physical FreeBSD machine are concerned. > If you are going to use rule numbers use rule numbers on every rule. > Makes it easier to understand (IMO). I agree. Whenever I get around to writing my own firewall, I will place numbers before each rule, but that firewall isn't mine. > What is the output of `ipfw -a l' ? After moving 100 and 200 above the natd statement per your suggestion, the output is: 00100 0 0 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 20 1767 divert 8668 ip from any to any via tun0 00400 274 15868 allow ip from any to any 65535 4 237 deny ip from any to any > Turn off deny_incoming while testing. Done. Well, that's about all I can say for now. Thank you very much for your reply. I appreciate it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Mon Dec 4 17:17: 4 2000 From owner-freebsd-net@FreeBSD.ORG Mon Dec 4 17:17:02 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id 9135737B400 for ; Mon, 4 Dec 2000 17:17:01 -0800 (PST) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA01482; Tue, 5 Dec 2000 10:16:51 +0900 (JST) To: Ian Dowse Cc: freebsd-net@freebsd.org In-reply-to: iedowse's message of Mon, 04 Dec 2000 19:31:01 GMT. <200012041931.aa09203@salmon.maths.tcd.ie> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: panic in nd6_dad_timer when removing pccard From: itojun@iijlab.net Date: Tue, 05 Dec 2000 10:16:51 +0900 Message-ID: <1480.975979011@coconut.itojun.org> Sender: itojun@itojun.org Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I got a panic today on 4.1-STABLE when removing a pccard shortly >after it was inserted. I was running with "options INVARIANTS", >which may have helped to trigger the problem. migrate to 4.2, it should be much better. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 0:26:15 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 00:26:13 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from brisefer.cediti.be (brisefer.cediti.be [193.190.156.67]) by hub.freebsd.org (Postfix) with ESMTP id 64F0337B400 for ; Tue, 5 Dec 2000 00:26:13 -0800 (PST) Received: by brisefer.cediti.be with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Dec 2000 09:27:33 +0100 Message-ID: From: Olivier Cherrier To: "'freebsd-net@freebsd.org'" Subject: Date: Tue, 5 Dec 2000 09:27:32 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. I am interesting in your opinion. I have a BSD firewall. Now, I would like to allow remote windows connections securily. I see Poptop (http://poptop.lineo.com) and mpd 3.2. What do you suggest me in using poptop or mpd ? Is mpd such secure and powerful than poptop ? Has anybody ever used successfuly mpd ? Thanks for your opinion. Olivier. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 1: 0:55 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 01:00:53 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from bjapp6.163.net (unknown [202.108.255.216]) by hub.freebsd.org (Postfix) with ESMTP id 0B23837B400 for ; Tue, 5 Dec 2000 01:00:53 -0800 (PST) Received: by bjapp6.163.net (Postfix, from userid 1005) id 4DFFB1CD7621C; Tue, 5 Dec 2000 16:59:41 +0800 (CST) MIME-Version: 1.0 Message-Id: <3A2CAE7D.25590@bjapp6.163.net> Date: Tue, 5 Dec 2000 16:59:41 +0800 (CST) From: oscar@163.net To: freebsd-net@freebsd.org Subject: get tun0's ip from my program X-Priority: 3 X-Originating-IP: [61.130.62.5] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I want to get tun0's two ip addresses. and add ipfw rules to system at my program. How can I do it?is there a function? or have document describe it. someone please tell me! thank you! oscar oscar@163.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ “200家连锁网站,让眼睛尝尝鲜” http://www.chinese.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 163电子邮局,给您更完美Email服务! http://www.163.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 1:12:28 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 01:12:26 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (f101.law6.hotmail.com [216.32.241.101]) by hub.freebsd.org (Postfix) with ESMTP id 122CA37B401 for ; Tue, 5 Dec 2000 01:12:26 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 5 Dec 2000 01:12:25 -0800 Received: from 61.9.178.117 by lw6fd.law6.hotmail.msn.com with HTTP; Tue, 05 Dec 2000 09:12:25 GMT X-Originating-IP: [61.9.178.117] From: "Aaron Hill" To: oscar@163.net, freebsd-net@freebsd.org Subject: Re: get tun0's ip from my program Date: Tue, 05 Dec 2000 09:12:25 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 05 Dec 2000 09:12:25.0820 (UTC) FILETIME=[7BE941C0:01C05E9B] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I want to get tun0's two ip addresses. >and add ipfw rules to system at my program. >How can I do it?is there a function? or >have document describe it. someone please tell me! I found a good example of modifying the rc.firewall file at... http://people.freebsd.org/~jmb/PPPoE.configuration ... and modified it for my needs. In particular here's how the IP address for the tun0 interface is detected... red_if="tun0" red=`ifconfig ${red_if} | grep netmask | cut -f 2 -d ' ' | tail -1` Next the red_if and red objects are referenced in the firewall configuration with the following kind of line... ${fwcmd} add 100 deny log all from ${red} to any in recv ${red_if} So if you need to pull the two IP addresses from tun0 I'm sure you could make two objects like red_ip1 and red_ip2, then pull the relevant IP address for each one with different uses of the head and tail utilities with the above commands. Check out the above mentioned web site for a more complete picture of how to modify /etc/rc.firewall and how to execute it. I hope that helps. Aaron Hill _____________________________________________________________________________________ Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 1:44:17 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 01:44:15 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 81F2937B400 for ; Tue, 5 Dec 2000 01:44:14 -0800 (PST) Received: from timbuktu-59.budapest.interware.hu ([195.70.51.251] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 143Edw-0007FR-00; Tue, 05 Dec 2000 10:44:13 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2CB6EF.76859CB3@elischer.org> Date: Tue, 05 Dec 2000 01:35:43 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Olivier Cherrier Cc: "'freebsd-net@freebsd.org'" Subject: Re: References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Olivier Cherrier wrote: > > Hello. > > I am interesting in your opinion. > I have a BSD firewall. Now, I would like to allow remote windows connections > securily. I see Poptop (http://poptop.lineo.com) and mpd 3.2. > > What do you suggest me in using poptop or mpd ? > Is mpd such secure and powerful than poptop ? > Has anybody ever used successfuly mpd ? > > Thanks for your opinion. > > Olivier. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message I have used MPD it can supply the Windows name serve as part of the ppp negotiations, which poptop cannot do (to my knowledge). It can also serve N (a largish number) of PTP sessions at once from one mpd program running. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 1:45:28 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 01:45:26 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 1383A37B400 for ; Tue, 5 Dec 2000 01:45:25 -0800 (PST) Received: from timbuktu-59.budapest.interware.hu ([195.70.51.251] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 143Ef5-0007JO-00; Tue, 05 Dec 2000 10:45:23 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2CB91D.1F1E73E2@elischer.org> Date: Tue, 05 Dec 2000 01:45:01 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Olivier Cherrier , "'freebsd-net@freebsd.org'" Subject: Re: References: <3A2CB6EF.76859CB3@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Olivier Cherrier wrote: > > > > Hello. > > > > I am interesting in your opinion. > > I have a BSD firewall. Now, I would like to allow remote windows connections > > securily. I see Poptop (http://poptop.lineo.com) and mpd 3.2. > > > > What do you suggest me in using poptop or mpd ? > > Is mpd such secure and powerful than poptop ? > > Has anybody ever used successfuly mpd ? > > > > Thanks for your opinion. > > > > Olivier. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > I have used MP it can supply the Windows name serve as part of the ppp negotiations, which poptop cannot do (to my knowledge). It can also serve N (a largish number) of PTP sessions at once from one mpd program running. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 5:18:47 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 05:18:45 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from alijku04.edvz.uni-linz.ac.at (alijku04.edvz.uni-linz.ac.at [140.78.182.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D34237B400 for ; Tue, 5 Dec 2000 05:18:44 -0800 (PST) Received: from sondermuell.oeh.uni-linz.ac.at (root@sondermuell.oeh.uni-linz.ac.at [140.78.214.105]) by alijku04.edvz.uni-linz.ac.at (8.8.8/8.8.8) with ESMTP id OAA134372 for ; Tue, 5 Dec 2000 14:18:42 +0100 Received: from atommuell.oeh.uni-linz.ac.at (root@atommuell.oeh.uni-linz.ac.at [140.78.214.101]) by sondermuell.oeh.uni-linz.ac.at (8.9.3/8.9.3) with ESMTP id OAA06006 for ; Tue, 5 Dec 2000 14:18:54 +0100 Received: from localhost (ferdl@localhost) by atommuell.oeh.uni-linz.ac.at (8.9.3/8.9.3) with ESMTP id OAA16027 for ; Tue, 5 Dec 2000 14:18:53 +0100 (CET) (envelope-from ferdl@atommuell.oeh.uni-linz.ac.at) Date: Tue, 5 Dec 2000 14:18:52 +0100 (CET) From: Ferdinand Goldmann To: freebsd-net@freebsd.org Subject: hints on mbuf calculation needed 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 Greetings. I have three questions about the value of NMBCLUSTERS: - Is there any way to tell in advance how high I need to set this value to have enough? I.e., I have a machine which does forwarding to a proxy and firewalling/traffic shaping for about 6-700 clients, no local users - how high should the value of NMBCLUSTERS be? Current usage is: $ netstat -m 748/1360/16384 mbufs in use (current/peak/max): 163 mbufs allocated to data 585 mbufs allocated to packet headers 163/582/4096 mbuf clusters in use (current/peak/max) 1504 Kbytes allocated to network (12% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines This short after a reboot, the value of mbuf clusters rises to ~2000 after some time. - Memory consumption: How much memory does one mbuf eat up? I'd like to have a formula to answer the question "I have 32MB RAM, how many NMBCLUSTERS can I compile into my kernel until that RAM will be eaten up?" - What's the difference between 'mbuf' and 'mbuf clusters' *blush*? Regards, Ferdinand Goldmann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 9:16:34 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 09:16:33 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from sierrahill.com (sierrahill.com [209.198.135.2]) by hub.freebsd.org (Postfix) with ESMTP id 9529637B402 for ; Tue, 5 Dec 2000 09:16:28 -0800 (PST) Received: (from rjoe@localhost) by sierrahill.com (8.9.3/8.9.3) id LAA52477 for freebsd-net@FreeBSD.ORG; Tue, 5 Dec 2000 11:16:25 -0600 (CST) (envelope-from rjoe) From: Joe Schwartz Message-Id: <200012051716.LAA52477@sierrahill.com> Subject: pc anywhere & natd To: freebsd-net@FreeBSD.ORG Date: Tue, 5 Dec 2000 11:16:25 -0600 (CST) X-Mailer: ELM [version 2.5 PL3] 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 There is a PC running pcanywhere with a public IP address attempting to get to a PC on a private network. The FreeBSD server is running natd and I used the option -redirect_address to attempt a conduit through the FreeBSD machine to the PC on the private net. The PC on the public net pointed the pcanywhere client to the IP public IP address of the FreeBSD machine. It didn't work. Should I expect it to? Suggestions? Alternate approaches? /usr/sbin/natd -redirect_address 192.168.1.54 24.??.??.??? -n vx0 24.??.??.??? 192.168.1.?? public natd private PC ------------ FreeBSD ----------------PC Thanks, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 9:29:45 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 09:29:43 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from apollo.ocsny.com (apollo.ocsny.com [204.107.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 6624137B400 for ; Tue, 5 Dec 2000 09:29:42 -0800 (PST) Received: from ocsinternet.com (fw234.ocsny.com [204.107.76.234]) by apollo.ocsny.com (8.9.2/8.9.3) with ESMTP id MAA14112; Tue, 5 Dec 2000 12:29:22 -0500 (EST) Message-ID: <3A2D256E.427E0BFC@ocsinternet.com> Date: Tue, 05 Dec 2000 12:27:10 -0500 From: mikel X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; I) X-Accept-Language: en MIME-Version: 1.0 To: Joe Schwartz Cc: freebsd-net@FreeBSD.ORG Subject: Re: pc anywhere & natd References: <200012051716.LAA52477@sierrahill.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joe, Are you allowing 5631 tcp and 5632 udp in? cheers, mikel Joe Schwartz wrote: > There is a PC running pcanywhere with a public IP address > attempting to get to a PC on a private network. The FreeBSD > server is running natd and I used the option -redirect_address > to attempt a conduit through the FreeBSD machine to the PC on the > private net. The PC on the public net pointed the pcanywhere client > to the IP public IP address of the FreeBSD machine. > > It didn't work. > > Should I expect it to? > > Suggestions? > > Alternate approaches? > > /usr/sbin/natd -redirect_address 192.168.1.54 24.??.??.??? -n vx0 > > 24.??.??.??? 192.168.1.?? > public natd private > PC ------------ FreeBSD ----------------PC > > Thanks, > > Joe > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 10:45: 4 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 10:44:59 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 9480637B404 for ; Tue, 5 Dec 2000 10:44:58 -0800 (PST) Received: from casablanca-41.budapest.interware.hu ([195.70.53.41] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 143N5B-0004Pf-00; Tue, 05 Dec 2000 19:44:53 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2CFFB6.3A503606@elischer.org> Date: Tue, 05 Dec 2000 06:46:14 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: mwright@pro-ns.net, freebsd-net@freebsd.org Subject: Re: Is it possible to use a LanMedia LMC1200 with frame relay? References: <200012042142.eB4LgOW49981@user2.pro-ns.net> <3A2C144D.FF557FFE@elischer.org> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > mwright@pro-ns.net wrote: > > > > Does anyone have any experience using a LanMedia 1200 with frame relay? How > > did they configure it? > > > > MarkScottWright@hotmail.com > > If it's supported by one of the drivers that supports netgraph then yes it > can do frame relay.. > check the examples in /usr/share/examples/netgraph and substitute in the > appropriate driver name. To answer my own question, the 'lmc' driver has the following constant in it: LMC_CTL_CARDTYPE_LMC1200 so I presume it can.. in which case, use Netgraph to supply your frame relay -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 10:56:20 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 10:56:17 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 3B53537B400 for ; Tue, 5 Dec 2000 10:56:17 -0800 (PST) Received: by mailman.thenap.com with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Dec 2000 14:06:32 -0500 Message-ID: From: "Drew J. Weaver" To: "'freebsd-net@freebsd.org'" Subject: Really odd problem Date: Tue, 5 Dec 2000 14:06:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C05EEE.7B2A43EE" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C05EEE.7B2A43EE Content-Type: text/plain; charset="iso-8859-1" We have a Freebsd 4.2 box on our network, after the box boots, it brings up the network and everything is great, I can telnet into it.. everything good, but about 30-60 minutes later no incoming traffic is getting to the server. If i ping the machine, or telnet to it, I get nothing. If I go to the terminal and ping anything then it "wakes up" does anyone have any idea what would cause it to stop "listening" to incoming network requests? This is becoming very tiresome and i've done everything known to me. Thanks, -Drew ------_=_NextPart_001_01C05EEE.7B2A43EE Content-Type: text/html; charset="iso-8859-1" Really odd problem
          We have a Freebsd 4.2 box on our network, after the box boots, it brings up the network and everything is great, I can telnet into it.. everything good, but about 30-60 minutes later no incoming traffic is getting to the server. If i ping the machine, or telnet to it, I get nothing. If I go to the terminal and ping anything then it "wakes up" does anyone have any idea what would cause it to stop "listening" to incoming network requests? This is becoming very tiresome and i've done everything known to me.

Thanks,
-Drew




------_=_NextPart_001_01C05EEE.7B2A43EE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 11: 1: 9 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 11:00:55 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from folgat.dgtu.donetsk.ua (folgat.dgtu.donetsk.ua [194.44.183.2]) by hub.freebsd.org (Postfix) with ESMTP id BF56637B400; Tue, 5 Dec 2000 11:00:45 -0800 (PST) Received: (from yk@localhost) by folgat.dgtu.donetsk.ua (8.9.3/8.9.3) id VAA01782; Tue, 5 Dec 2000 21:05:38 +0200 (EET) (envelope-from yk) Date: Tue, 5 Dec 2000 21:05:38 +0200 From: Yury Yaroshevsky To: freebsd-stable@freebsd.org Cc: freebsd-net@freebsd.org Subject: Kernel panic on VLAN ... Message-ID: <20001205210538.A1386@folgat.dgtu.donetsk.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying setup vlan on my FreeBSD box. My OS - FreeBSD 3.5-SABLE at 28 Nov 2000. This is my kernel config: # # machine "i386" ident FOLGAT maxusers 128 options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" options FAILSAFE options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on da0 ##################################################################### # SMP OPTIONS: ##################################################################### # CPU OPTIONS cpu "I686_CPU" # aka Pentium Pro(tm) ##################################################################### # COMPATIBILITY OPTIONS options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG ##################################################################### # DEBUGGING OPTIONS options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor ##################################################################### # NETWORKING OPTIONS options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device vlan 4 pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 2 #Tunnel driver pseudo-device ppp 4 options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPFILTER #kernel ipfilter support options IPFILTER_LOG #ipfilter logging #options IPFILTER_LKM #kernel support for ip_fil.o LKM options IPSTEALTH #support for stealth forwarding options "ICMP_BANDLIM" options DUMMYNET ##################################################################### # FILESYSTEM OPTIONS options FFS #Fast filesystem options "CD9660" #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES options QUOTA #enable disk quotas ##################################################################### # POSIX P1003.1B ##################################################################### # SCSI DEVICES controller scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) options SCSI_REPORT_GEOMETRY ##################################################################### # MISCELLANEOUS DEVICES AND OPTIONS pseudo-device pty 32 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver pseudo-device vinum #Vinum concat/mirror/raid driver options VINUMDEBUG #enable Vinum debugging hooks options "MSGBUF_SIZE=40960" ##################################################################### # HARDWARE DEVICE CONFIGURATION controller isa0 options "AUTO_EOI_1" #options "AUTO_EOI_2" options "MAXMEM=(128*1024)" options PPS_SYNC controller pnp0 controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? tty options MAXCONS=16 # number of virtual consoles options SC_HISTORY_SIZE=600 # number of history buffer lines options SC_DISABLE_REBOOT # disable reboot key sequence device npx0 at isa? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? disable port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" tty flags 0x10 irq 3 device pca0 at isa? port "IO_TIMER1" tty controller ahc0 controller pci0 device fxp0 controller smbus0 controller intpm0 device smb0 at smbus? options "NSFBUFS=4096" Result of dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.5-STABLE #0: Tue Nov 28 17:13:27 EET 2000 root@folgat.dgtu.donetsk.ua:/usr/src/sys/compile/FOLGAT Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 334092225 Hz CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbff real memory = 134217728 (131072K bytes) avail memory = 126832640 (123860K bytes) Preloaded elf kernel "kernel" at 0xc0360000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc036009c. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 intpm0: rev 0x01 on pci0.4.3 intpm0: I/O mapped e800 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 intsmb0: smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: rev 0x00 int a irq 12 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x05 int a irq 10 on pci0.11.0 fxp0: Ethernet address 00:90:27:2f:73:b3 vga0: rev 0x01 int a irq 11 on pci0.12.0 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 flags 0x10 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (atapi): , removable, accel, ovlap, dma, iordis acd0: drive speed 4134KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging ccd0-3: Concatenated disk drivers DUMMYNET initialized (000212) IP Filter: initialized. Default = pass all, Logging = enabled Waiting 2 seconds for SCSI devices to settle vinum: loaded changing root device to da0s1a da2 at ahc0 bus 0 target 12 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) vinum: reading configuration from /dev/da1s1e vinum: updating configuration from /dev/da0s1e After recompile kernel and reloading I'm try: ifconfig fxp0 10.0.0.1 ifconfig vlan0 vlan 2 vlandev fxp0 ifconfig vlan0 192.168.1.1 fxp0 situated in 2 VLANs. 1-st - untagged, 2-nd - use 802.1q After this manipulations I can ping any host in 192.168.1.0/24, but after trying setup any tcp connections with host in 192.168.1.0/24 my kernel panic. # gdb -k /var/crash/kernel.2 /var/crash/vmcore.2 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD 3612672 initial pcb at 249f58 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2000081 fault code = supervisor read, page not present instruction pointer = 0x8:0xc018e9f5 stack pointer = 0x10:0xc7889f74 frame pointer = 0x10:0xc7889f80 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 337 (rc5des) interrupt mask = net tty trap number = 12 panic: page fault syncing disks... 70 70 53 29 9 done Uptime: 7m38s dumping to dev 20411, offset 262144 dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc01506b3 in boot () (kgdb) bt #0 0xc01506b3 in boot () #1 0xc0150938 in at_shutdown () #2 0xc01f66d5 in trap_fatal () #3 0xc01f63b3 in trap_pfault () #4 0xc01f6056 in trap () #5 0xc018e9f5 in ether_input () #6 0xc01b89d6 in fxp_intr () #7 0x807f2c2 in ?? () Cannot access memory at address 0xa0e56f09. At this moment I can't check VLAN on 4.2-STABLE. It is working on 3.5-STABLE or I'm need upgrade my system up to 4.2-STABLE? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 11:30:11 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 11:30:09 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 4AA6A37B400 for ; Tue, 5 Dec 2000 11:30:08 -0800 (PST) Received: from casablanca-41.budapest.interware.hu ([195.70.53.41] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 143Nmv-0008Ny-00; Tue, 05 Dec 2000 20:30:05 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2D4228.C586BFF6@elischer.org> Date: Tue, 05 Dec 2000 11:29:44 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Drew J. Weaver" Cc: "'freebsd-net@freebsd.org'" Subject: Re: Really odd problem References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > "Drew J. Weaver" wrote: > > We have a Freebsd 4.2 box on our network, after the box boots, it > brings up the network and everything is great, I can telnet into it.. > everything good, but about 30-60 minutes later no incoming traffic is getting > to the server. If i ping the machine, or telnet to it, I get nothing. If I go > to the terminal and ping anything then it "wakes up" does anyone have any idea > what would cause it to stop "listening" to incoming network requests? This is > becoming very tiresome and i've done everything known to me. Are you getting messages on the console? possibly the card is bad and dies after a while.. the transmit timeout for many drivers will try reinitialise the chip. Which may bring it back to life... (for a while) you could always add 'ping -i 120 [some address]' to some startup script :-) > > Thanks, > -Drew -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 11:31:52 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 11:31:46 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 5F02E37B400 for ; Tue, 5 Dec 2000 11:31:46 -0800 (PST) Received: by mailman.thenap.com with Internet Mail Service (5.5.2650.21) id ; Tue, 5 Dec 2000 14:42:01 -0500 Message-ID: From: "Drew J. Weaver" To: 'Julian Elischer' Cc: "'freebsd-net@freebsd.org'" Subject: RE: Really odd problem Date: Tue, 5 Dec 2000 14:42:01 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C05EF3.700E0AEA" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C05EF3.700E0AEA Content-Type: text/plain; charset="iso-8859-1" I *could* do that, whats the hostname of your mail server? I'll have it ping that =p No messages on the console at all, and again i've tried two seperate NIC cards both the (onboard intel) and the offboard PCI Intel 10/100 -Drew -----Original Message----- From: Julian Elischer [mailto:julian@elischer.org] Sent: Tuesday, December 05, 2000 2:30 PM To: Drew J. Weaver Cc: 'freebsd-net@freebsd.org' Subject: Re: Really odd problem > "Drew J. Weaver" wrote: > > We have a Freebsd 4.2 box on our network, after the box boots, it > brings up the network and everything is great, I can telnet into it.. > everything good, but about 30-60 minutes later no incoming traffic is getting > to the server. If i ping the machine, or telnet to it, I get nothing. If I go > to the terminal and ping anything then it "wakes up" does anyone have any idea > what would cause it to stop "listening" to incoming network requests? This is > becoming very tiresome and i've done everything known to me. Are you getting messages on the console? possibly the card is bad and dies after a while.. the transmit timeout for many drivers will try reinitialise the chip. Which may bring it back to life... (for a while) you could always add 'ping -i 120 [some address]' to some startup script :-) > > Thanks, > -Drew -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v ------_=_NextPart_001_01C05EF3.700E0AEA Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Really odd problem

I *could* do that, whats the hostname of your mail = server? I'll have it ping that =3Dp No messages on the console at all, = and again i've tried two seperate NIC cards both the (onboard intel) = and the offboard PCI Intel 10/100

-Drew


-----Original Message-----
From: Julian Elischer [mailto:julian@elischer.org]
Sent: Tuesday, December 05, 2000 2:30 PM
To: Drew J. Weaver
Cc: 'freebsd-net@freebsd.org'
Subject: Re: Really odd problem


> "Drew J. Weaver" wrote:
>
>          = ; We have a Freebsd 4.2 box on our network, after the box boots, = it
> brings up the network and everything is great, = I can telnet into it..
> everything good, but about 30-60 minutes later = no incoming traffic is getting
> to the server. If i ping the machine, or telnet = to it, I get nothing. If I go
> to the terminal and ping anything then it = "wakes up" does anyone have any idea
> what would cause it to stop = "listening" to incoming network requests? This is
> becoming very tiresome and i've done everything = known to me.

Are you getting messages on the console?

possibly the card is bad and dies after a = while..
the transmit timeout for many drivers will try = reinitialise the chip.
Which may bring it back to life... (for a = while)

you could always add 'ping -i 120 [some address]' =
to some startup script 

:-)


>
> Thanks,
> -Drew

--
      __--_|\  Julian = Elischer
     = /       \ julian@elischer.org
    (   = OZ    ) World tour 2000
---> X_.---._/  presently in:  = Budapest
          &nb= sp; v

------_=_NextPart_001_01C05EF3.700E0AEA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 12:12:47 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 12:12:44 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from measurement-factory.com (unknown [204.144.128.85]) by hub.freebsd.org (Postfix) with ESMTP id 9F4D337B400 for ; Tue, 5 Dec 2000 12:12:44 -0800 (PST) Received: from localhost (rousskov@localhost) by measurement-factory.com (8.9.3/8.9.3) with ESMTP id NAA01217; Tue, 5 Dec 2000 13:12:38 -0700 (MST) (envelope-from rousskov@measurement-factory.com) Date: Tue, 5 Dec 2000 13:12:38 -0700 (MST) From: Alex Rousskov To: "Drew J. Weaver" Cc: freebsd-net@FreeBSD.ORG Subject: Re: Really odd problem In-Reply-To: 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, 5 Dec 2000, Drew J. Weaver wrote: > We have a Freebsd 4.2 box on our network, after the box boots, it > brings up the network and everything is great, I can telnet into it.. > everything good, but about 30-60 minutes later no incoming traffic is > getting to the server. If i ping the machine, or telnet to it, I get > nothing. If I go to the terminal and ping anything then it "wakes up" does > anyone have any idea what would cause it to stop "listening" to incoming > network requests? This is becoming very tiresome and i've done everything > known to me. Drew, We have seen similar (and worse) effects with the combination of "wake-up on LAN" and "power-save mode" BIOS features. Make sure that your [BIOS] settings disable funky features that FreeBSD does not support [well]. Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 14:42:17 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 14:42:14 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121]) by hub.freebsd.org (Postfix) with SMTP id EAFCC37B400 for ; Tue, 5 Dec 2000 14:42:13 -0800 (PST) Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 05 Dec 2000 11:41:29 -0800 (Pacific Standard Time) Received: by inet-imc-05.redmond.corp.microsoft.com with Internet Mail Service (5.5.2651.58) id ; Tue, 5 Dec 2000 11:41:27 -0800 Message-ID: <3393DB26DFC047419FEDA98FA76479110179A227@red-msg-05.redmond.corp.microsoft.com> From: George Chung To: Joe Schwartz , freebsd-net@FreeBSD.ORG Subject: RE: pc anywhere & natd Date: Tue, 5 Dec 2000 11:41:06 -0800 X-Mailer: Internet Mail Service (5.5.2651.58) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i don't know if this helps, but... i have the exact same situation. but i use ssh port forwarding to get to the private machine on the two pcanywhere ports. i wasn't able to get this to work until i found an obscure knowledge base article on symantec's site on how to get pcanywhere to use tcp instead of udp on those ports. -----Original Message----- From: Joe Schwartz [mailto:rjoe@sierrahill.com] Sent: Tuesday, December 05, 2000 9:16 AM To: freebsd-net@FreeBSD.ORG Subject: pc anywhere & natd There is a PC running pcanywhere with a public IP address attempting to get to a PC on a private network. The FreeBSD server is running natd and I used the option -redirect_address to attempt a conduit through the FreeBSD machine to the PC on the private net. The PC on the public net pointed the pcanywhere client to the IP public IP address of the FreeBSD machine. It didn't work. Should I expect it to? Suggestions? Alternate approaches? /usr/sbin/natd -redirect_address 192.168.1.54 24.??.??.??? -n vx0 24.??.??.??? 192.168.1.?? public natd private PC ------------ FreeBSD ----------------PC Thanks, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Dec 5 17:47:31 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 17:47:28 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id C38FC37B400 for ; Tue, 5 Dec 2000 17:47:26 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB61iUM10362; Wed, 6 Dec 2000 01:44:30 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB61lQH00846; Wed, 6 Dec 2000 01:47:26 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012060147.eB61lQH00846@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrea Venturoli Cc: freebsd-net@FreeBSD.org, brian@Awfulhak.org Subject: Re: ppp server help: found out! In-Reply-To: Message from Andrea Venturoli of "Sun, 03 Dec 2000 22:33:00 EST." <200012032133.eB3LWxU13567@relay.flashnet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 01:47:26 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You wouldn't happen to have a ``set speed sync'' line in your config would you ? If so, this would tell ppp to do this... When you open an i4b device, ppp knows that you must be talking synchronously and does the right thing.... > Hello there! > > This is what I sent some days ago: > > >I'm trying to set up a ppp server on a 4.1.1-R system; the modem answers correctly, but I > >get the following in /var/log/ppp.log: > >... > > Now, I did some research and what I found out is that ppp does not de-HDLC-fy the packets it > receives: it behaves correctly when I dial out to my ISP through my ISDN card, but it does > not remove the hdlc header before giving the packet to LCP when I use it as a server on my > modem. > Similarly it does not add the HDLC header and terminations to packets it sends, so the peer > complains about fcs errors. > > Right now I'm using pppd which behaves correctly, but in the end I'd rather be using > user-ppp. Do anyone knows how to force it to use hdlc (if I "set log hdlc", I see no message > at all)? > Did I found a bug in 4.1.1-R? > > Bye & Thanks > av. -- 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 Tue Dec 5 17:52:58 2000 From owner-freebsd-net@FreeBSD.ORG Tue Dec 5 17:52:56 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 7706B37B400 for ; Tue, 5 Dec 2000 17:52:37 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB61n4M10392; Wed, 6 Dec 2000 01:49:04 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB61q0H00910; Wed, 6 Dec 2000 01:52:00 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012060152.eB61q0H00910@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: oscar@163.net Cc: freebsd-net@FreeBSD.org, brian@Awfulhak.org Subject: Re: get tun0's ip from my program In-Reply-To: Message from oscar@163.net of "Tue, 05 Dec 2000 16:59:41 +0800." <3A2CAE7D.25590@bjapp6.163.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <903.976067520.1@hak.lan.Awfulhak.org> Date: Wed, 06 Dec 2000 01:52:00 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I want to get tun0's two ip addresses. > and add ipfw rules to system at my program. > How can I do it?is there a function? or > have document describe it. someone please tell me! > thank you! If you're using ppp, you can call a script with the primary interface address from ppp.linkup like this: MYADDR: !bg myscript MYADDR There's no way to get your hands on any secondary IP numbers though... unless you do something like MYADDR: !bg myscript INTERFACE and then have a script that does something like #! /bin/sh ips=`ifconfig $1 | sed -n 's/ *inet \([^ ]*\) .*/\1/p'` ..... If you're doing this from a program, have a look at the code in ppp/iface.c to see how ppp does it. > oscar > oscar@163.net -- 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 Dec 6 3:53:49 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 03:53:47 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mage.trollkarl.net (fw.trollkarl.net [207.167.5.66]) by hub.freebsd.org (Postfix) with ESMTP id CC13537B400 for ; Wed, 6 Dec 2000 03:53:46 -0800 (PST) Received: from trollkarl.skafte.org (root@trollkarl [192.168.100.16]) by mage.trollkarl.net (8.11.1/8.11.1) with ESMTP id eB6BrfF18040 for ; Wed, 6 Dec 2000 04:53:41 -0700 (MST) (envelope-from skafte@trollkarl.net) Received: (from skafte@localhost) by trollkarl.skafte.org (8.11.1/8.11.1) id eB6BrdP19663 for freebsd-net@FreeBSD.ORG; Wed, 6 Dec 2000 04:53:39 -0700 (MST) (envelope-from skafte) Date: Wed, 6 Dec 2000 04:53:39 -0700 From: Greg Skafte To: freebsd-net@FreeBSD.ORG Subject: Re: pc anywhere & natd Message-ID: <20001206045338.A19445@trollkarl.skafte.org> References: <200012051716.LAA52477@sierrahill.com> <3A2D256E.427E0BFC@ocsinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A2D256E.427E0BFC@ocsinternet.com>; from mikel@ocsinternet.com on Tue, Dec 05, 2000 at 12:27:10PM -0500 Organization: Gregs Hidey Hole Sender: skafte@trollkarl.net Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org this is a common problem there are some registry keys that are outlined on the symantec website. These keys will allow you to force a TCP only connection as opposed to a UDP ( I usually heavily restrict UDP based services ). http://service1.symantec.com/SUPPORT/pca.nsf/9f19833cbd7241aa85256758005492c7/223ca40cc3042cd1882565d8000eb89b?OpenDocument&ExpandSection=2#_Section2 covers the various registry keys. Quoting mikel (mikel@ocsinternet.com) On Subject: Re: pc anywhere & natd Date: Tue, Dec 05, 2000 at 12:27:10PM -0500 > Joe, > > Are you allowing 5631 tcp and 5632 udp in? > > cheers, > mikel > > Joe Schwartz wrote: > > > There is a PC running pcanywhere with a public IP address > > attempting to get to a PC on a private network. The FreeBSD > > server is running natd and I used the option -redirect_address > > to attempt a conduit through the FreeBSD machine to the PC on the > > private net. The PC on the public net pointed the pcanywhere client > > to the IP public IP address of the FreeBSD machine. > > > > It didn't work. > > > > Should I expect it to? > > > > Suggestions? > > > > Alternate approaches? > > > > /usr/sbin/natd -redirect_address 192.168.1.54 24.??.??.??? -n vx0 > > > > 24.??.??.??? 192.168.1.?? > > public natd private > > PC ------------ FreeBSD ----------------PC > > > > Thanks, > > > > Joe > > > > 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 -- Email: skafte@trollkarl.net ICQ: 93234105 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 7:56:45 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 07:56:42 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from relay2.flashnet.it (libra.cyb.it [212.11.95.209]) by hub.freebsd.org (Postfix) with ESMTP id 88AF537B404 for ; Wed, 6 Dec 2000 07:56:38 -0800 (PST) Received: from smtp.flashnet.it (ip057.pool-173.cyb.it [195.191.181.58]) by relay2.flashnet.it (EMS-RELAY/8.10.0) with SMTP id eB6FuTR21907 for ; Wed, 6 Dec 2000 16:56:30 +0100 Message-Id: <200012061556.eB6FuTR21907@relay2.flashnet.it> To: freebsd-net@FreeBSD.org Priority: Normal X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Wed, 6 Dec 2000 16:56:26 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: Re: ppp server help: found out! Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** Reply to note from Brian Somers Wed, 06 Dec 2000 01:47:26 +0000 > You wouldn't happen to have a ``set speed sync'' line in your config > would you ? If so, this would tell ppp to do this... Yes, I have, but it's in another section. I have: default: .... papchap: set speed sync .... modemin: .... It shouldn't apply this way, should it? Anyway, this was the problem, putting set speed 57600 in the modemin section solved the problem. Bye & Thanks a lot av. cc: freebsd-net@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 8:10:33 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 08:10:30 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from rmx441-mta.mail.com (rmx441-mta.mail.com [165.251.48.44]) by hub.freebsd.org (Postfix) with ESMTP id 9A20C37B402 for ; Wed, 6 Dec 2000 08:10:29 -0800 (PST) Received: from web582-mc (web582-mc.mail.com [165.251.48.95]) by rmx441-mta.mail.com (8.9.3/8.9.3) with SMTP id LAA18708 for ; Wed, 6 Dec 2000 11:10:27 -0500 (EST) Message-ID: <383058475.976119027283.JavaMail.root@web582-mc> Date: Wed, 6 Dec 2000 11:10:27 -0500 (EST) From: Hamid Moghadam To: freebsd-net@freebsd.org Subject: IPSec Netgraph node Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: mail.com X-Originating-IP: 195.96.140.54 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there Does anyone have any idea about implementation of IPSEC Netgraph node ? Or is there any work in progress for doing that ? /Hamid ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 8:11:40 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 08:11:38 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from pfa0frpk001.panasonicfa.com (unknown [38.248.119.1]) by hub.freebsd.org (Postfix) with ESMTP id 71DCB37B400 for ; Wed, 6 Dec 2000 08:11:37 -0800 (PST) Received: by exchange.panasonicfa.com with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Dec 2000 10:11:32 -0600 Message-ID: <054F7DAA9E54D311AD090008C74CE9BD01F1E759@exchange.panasonicfa.com> From: "Zaitsau, Andrei" To: "'freebsd-net@freebsd.org'" Subject: Small weird problem.... Date: Wed, 6 Dec 2000 10:11:28 -0600 Return-Receipt-To: "Zaitsau, Andrei" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Everyone, I have a small problem. I have 5 computers at home all connected via hub. They are all connected to the internet via gateway running FreeBSD 3.4 using ADSL connection. The problem is when I try to open SSH session from Win2K pro machine to SparcSation IPC running OpenBSD 2.8, when SSH session between these 2 machines is established. Gateway computer (FreeBSD) drops ADSL connection, cutting the rest of the network from the internet. If I reboot gateway machine it does not connect to the internet. And until SSH session is terminated, gateway can not connect to the internet. I have no Idea what could be the reason why it's doing it to me. Can anyone help me or explain me what could be the problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 8:12:51 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 08:12:47 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mailman.thenap.com (mailman.thenap.com [209.190.0.10]) by hub.freebsd.org (Postfix) with ESMTP id DB60D37B400 for ; Wed, 6 Dec 2000 08:12:46 -0800 (PST) Received: by mailman.thenap.com with Internet Mail Service (5.5.2650.21) id ; Wed, 6 Dec 2000 11:23:03 -0500 Message-ID: From: "Drew J. Weaver" To: "'Zaitsau, Andrei'" , "'freebsd-net@freebsd.org'" Subject: RE: Small weird problem.... Date: Wed, 6 Dec 2000 11:23:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C05FA0.CED8C936" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C05FA0.CED8C936 Content-Type: text/plain; charset="iso-8859-1" I had a similar problem, then I went and got a Linksys BFSR Dsl/Cable router for like 80 dollars on amazon.com. It works great. -Drew -----Original Message----- From: Zaitsau, Andrei [mailto:AZaitsau@panasonicfa.com] Sent: Wednesday, December 06, 2000 11:11 AM To: 'freebsd-net@freebsd.org' Subject: Small weird problem.... Hello Everyone, I have a small problem. I have 5 computers at home all connected via hub. They are all connected to the internet via gateway running FreeBSD 3.4 using ADSL connection. The problem is when I try to open SSH session from Win2K pro machine to SparcSation IPC running OpenBSD 2.8, when SSH session between these 2 machines is established. Gateway computer (FreeBSD) drops ADSL connection, cutting the rest of the network from the internet. If I reboot gateway machine it does not connect to the internet. And until SSH session is terminated, gateway can not connect to the internet. I have no Idea what could be the reason why it's doing it to me. Can anyone help me or explain me what could be the problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message ------_=_NextPart_001_01C05FA0.CED8C936 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Small weird problem....

I had a similar problem, then I went and got a = Linksys BFSR Dsl/Cable router for like 80 dollars on amazon.com. It = works great.

-Drew


-----Original Message-----
From: Zaitsau, Andrei [mailto:AZaitsau@panasonicfa.com= ]
Sent: Wednesday, December 06, 2000 11:11 AM
To: 'freebsd-net@freebsd.org'
Subject: Small weird problem....


Hello Everyone,
I have a small problem. I have 5 computers at home = all connected via hub.
They are all connected to the internet via gateway = running FreeBSD 3.4 using
ADSL connection. The problem is when I try to open = SSH session from Win2K
pro machine to SparcSation IPC running OpenBSD 2.8, = when SSH session between
these 2 machines is established. Gateway computer = (FreeBSD) drops ADSL
connection, cutting the rest of the network from the = internet. If I reboot
gateway machine it does not connect to the internet. = And until SSH session
is terminated, gateway can not connect to the = internet.
I have no Idea what could be the reason why it's = doing it to me. Can anyone
help me or explain me what could be the = problem?


To Unsubscribe: send mail to = majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body = of the message

------_=_NextPart_001_01C05FA0.CED8C936-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 12:32: 0 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 12:31:55 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 2E33037B404 for ; Wed, 6 Dec 2000 12:31:55 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G5500MMLY8WBY@falla.videotron.net> for freebsd-net@FreeBSD.ORG; Wed, 6 Dec 2000 15:29:20 -0500 (EST) Date: Wed, 06 Dec 2000 15:30:15 -0500 (EST) From: Bosko Milekic Subject: Re: hints on mbuf calculation needed In-reply-to: To: Ferdinand Goldmann Cc: freebsd-net@FreeBSD.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 Tue, 5 Dec 2000, Ferdinand Goldmann wrote: > Greetings. > > I have three questions about the value of NMBCLUSTERS: > > - Is there any way to tell in advance how high I need to set this value to > have enough? I.e., I have a machine which does forwarding to a proxy and > firewalling/traffic shaping for about 6-700 clients, no local users - > how high should the value of NMBCLUSTERS be? > Current usage is: > $ netstat -m > 748/1360/16384 mbufs in use (current/peak/max): > 163 mbufs allocated to data > 585 mbufs allocated to packet headers > 163/582/4096 mbuf clusters in use (current/peak/max) > 1504 Kbytes allocated to network (12% of mb_map in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > This short after a reboot, the value of mbuf clusters rises to ~2000 after > some time. Personally, I would crank NMBCLUSTERS up to 8192 in this case, just to be safe. Plus, it doesn't really cost you much to increase them just a bit, as all you're really losing is a rather insignificant amount of address space. > - Memory consumption: How much memory does one mbuf eat up? I'd like to > have a formula to answer the question "I have 32MB RAM, how many NMBCLUSTERS > can I compile into my kernel until that RAM will be eaten up?" This shouldn't be the way you determine to what to set NMBCLUSTERS to. Your first point above shows a much more effective way to do it. But to answer your question, an mbuf is presently 256 bytes and an mbuf cluster is 2KB. > - What's the difference between 'mbuf' and 'mbuf clusters' *blush*? I think that the mbuf(9) man page should clear up quite a few points. Although, the man page is only available in -CURRENT so if you don't run -CURRENT, you should be able to find it via the FreeBSD web site. Specifically: "An mbuf is a basic unit of memory management in the kernel IPC subsystem." and "If small enough, data is stored in the mbuf's internal data buffer. If the data is sufficiently large, another mbuf may be added to the chain or external storage may be associated with the mbuf. MHLEN bytes of data can fit into an mbuf with the M_PKTHDR flag set, MLEN bytes can otherwise." ... "The system also supplies a default type of external storage buffer called an ``mbuf cluster''." > Regards, > Ferdinand Goldmann Cheers, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 13:47:28 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 13:47:25 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id E65C237B400 for ; Wed, 6 Dec 2000 13:47:23 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB6LiBm16273; Wed, 6 Dec 2000 21:44:11 GMT (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB6Lktt07510; Wed, 6 Dec 2000 21:46:55 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012062146.eB6Lktt07510@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrea Venturoli Cc: freebsd-net@FreeBSD.org, brian@Awfulhak.org Subject: Re: ppp server help: found out! In-Reply-To: Message from Andrea Venturoli of "Wed, 06 Dec 2000 16:56:26 EST." <200012061556.eB6FuTR21907@relay2.flashnet.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Dec 2000 21:46:55 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm glad this is sorted out. The only comment I can really make is that ppp has no concept of ``initial settings'' for a physical link, except for the settings that it starts off at. If at any time during the life of a link, you do a ``set speed sync'', it'll stay synchronous 'till a ``set speed nnn'' is done. In your case, if you did a ``load papchap'' at some point (even via pppctl), then a ``load modemin'', the end result would be a synchronous link. Does that make sense ? > ** Reply to note from Brian Somers Wed, 06 Dec 2000 01:47:26 +0000 > > > > You wouldn't happen to have a ``set speed sync'' line in your config > > would you ? If so, this would tell ppp to do this... > > Yes, I have, but it's in another section. I have: > > default: > .... > > papchap: > set speed sync > .... > > modemin: > .... > > > It shouldn't apply this way, should it? > > > > Anyway, this was the problem, putting > set speed 57600 > in the modemin section solved the problem. > > Bye & Thanks a lot > av. > > > > > cc: freebsd-net@FreeBSD.org -- 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 Dec 6 14:10:12 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 14:10:06 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (mail.dobox.com [208.187.122.44]) by hub.freebsd.org (Postfix) with ESMTP id 05B9A37B400 for ; Wed, 6 Dec 2000 14:10:06 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 143mny-0000Lq-00; Wed, 06 Dec 2000 15:12:50 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A2EB9E2.B44DE118@softweyr.com> Date: Wed, 06 Dec 2000 15:12:50 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Somers Cc: oscar@163.net, freebsd-net@FreeBSD.org Subject: Re: get tun0's ip from my program References: <200012060152.eB61q0H00910@hak.lan.Awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian Somers wrote: > > > I want to get tun0's two ip addresses. > > and add ipfw rules to system at my program. > > How can I do it?is there a function? or > > have document describe it. someone please tell me! > > thank you! > > If you're using ppp, you can call a script with the primary interface > address from ppp.linkup like this: > > MYADDR: > !bg myscript MYADDR > > There's no way to get your hands on any secondary IP numbers though... > unless you do something like If he was looking for the address of the other end of the tunnel, it is similarly available as HISADDR. We use these values to re-write the scripts I mentioned earlier when using PPPoE. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 17:28:37 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 17:28:35 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from bjapp4.163.net (unknown [202.108.255.214]) by hub.freebsd.org (Postfix) with ESMTP id 2DF2537B400 for ; Wed, 6 Dec 2000 17:28:35 -0800 (PST) Received: by bjapp4.163.net (Postfix, from userid 1005) id 9454F1D4D96D9; Thu, 7 Dec 2000 09:27:41 +0800 (CST) MIME-Version: 1.0 Message-Id: <3A2EE78D.29432@bjapp4.163.net> Date: Thu, 7 Dec 2000 09:27:41 +0800 (CST) From: oscar@163.net To: freebsd-net@freebsd.org Subject: get tun0's ip from my program C X-Priority: 3 X-Originating-IP: [61.130.54.94] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thank for all replys from friends. But I want to know use C program to get the ip address, not script. it must use network-interface ioctl and SIOCSIFADDR as param.But I do not know how to do this. Can anyone write a small example function to do this? thanks a lot. oscar > I want to get tun0's two ip addresses. > and add ipfw rules to system at my program. > How can I do it?is there a function? or > have document describe it. someone please tell me! > thank you! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ “200家连锁网站,让眼睛尝尝鲜” http://www.chinese.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 163电子邮局,给您更完美Email服务! http://www.163.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Dec 6 18: 4:31 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 18:04:29 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 7940037B400 for ; Wed, 6 Dec 2000 18:04:28 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB722Wx19107; Thu, 7 Dec 2000 02:02:32 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB725Ft44208; Thu, 7 Dec 2000 02:05:15 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012070205.eB725Ft44208@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: oscar@163.net Cc: freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: get tun0's ip from my program C In-Reply-To: Message from oscar@163.net of "Thu, 07 Dec 2000 09:27:41 +0800." <3A2EE78D.29432@bjapp4.163.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 07 Dec 2000 02:05:15 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thank for all replys from friends. > But I want to know use C program to get = > the ip address, not script. > it must use network-interface ioctl and SIOCSIFADDR > as param.But I do not know how to do this. > Can anyone write a small example function to do this? src/usr.sbin/ppp/iface.c does this sort of thing using sysctl(). > thanks a lot. > = > oscar -- = 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 Dec 6 23:20:50 2000 From owner-freebsd-net@FreeBSD.ORG Wed Dec 6 23:20:44 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from osku.suutari.iki.fi (osku.syncrontech.com [213.28.98.4]) by hub.freebsd.org (Postfix) with ESMTP id 0069A37B400; Wed, 6 Dec 2000 23:20:43 -0800 (PST) Received: from coffee (adsl-nat.syncrontech.com [213.28.98.3]) by osku.suutari.iki.fi (8.9.3/8.9.3) with SMTP id JAA81936; Thu, 7 Dec 2000 09:20:40 +0200 (EET) (envelope-from ari@suutari.iki.fi) Message-ID: <001301c0601e$34cab880$0e05a8c0@intranet.syncrontech.com> From: "Ari Suutari" To: , Subject: IPFW & IPsec tunnel mode Date: Thu, 7 Dec 2000 09:20:40 +0200 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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have been setting up a VPN between two offices in same company using FreeBSD + KAME ipsec. Works OK otherwise, but I think that ipfw capabilities should be enhanced to understand more about ipsec. My setup is something like this: Office A uses network nnn.nnn.nnn.0 Office B uses network mmm.mmm.mmm.0 Both ones have FreeBSD 4.1 as firewall, office A has public address aaa.aaa.aaa.aaa and office B has public address bbb.bbb.bbb.bbb. First, I setup a IPsec policy to use tunnel mode between these networks, without using any ipfw rules (ie. ipfw pass ip from any to any). Works without any problems. Then, I limit traffice with ipfw: Office A's firewall: ipfw add pass esp from bbb.bbb.bbb.bbb to aaa.aaa.aaa.aaa ipfw add pass esp from aaa.aaa.aaa.aaa to bbb.bbb.bbb.bbb Office B's firewall: ipfw add pass esp from aaa.aaa.aaa.aaa to bbb.bbb.bbb.bbb ipfw add pass esp from bbb.bbb.bbb.bbb to aaa.aaa.aaa.aaa Now, ESP packets are allowed through. But of course, no services (example telnet) work, because they dont' have any ipfw pass rule that they match. OK, I added following rules to make telnet work: Office A's firewall: ipfw add pass tcp from any to any established ipfw add pass tcp from mmm.mmm.mmm.0/24 to nnn.nnn.nnn.0/24 23 setup Office B's firewall: ipfw add pass tcp from any to any established ipfw add pass tcp from nnn.nnn.nnn.0/24 to mmm.mmm.mmm.0/24 23 setup Now telnet works and it looks like all done. However, these last rules allow hosts in nnn.nnn.nnn.0 & mmm.mmm.mmm.0 to exchange telnet traffic without IPsec also, since there is no way to state in these rules that they should only match to packets coming from a specific IPsec tunnel. I were unable to sleep my mights peacefully because I realized that if someone in the internet disguises himself as nnn.nnn.nnn.0 or mmm.mmm.mm.0 host my IPsec protection can be bypassed (I also realize that not everyone is capable of doing something like this). So, I switched to using pipsecd which passes tunnel packets to tun-device and the problem was solved: I can add 'via tun0' to those last rules to make sure that they match only the packes coming from tunnel. However, pipsecd only supports fixed keys and Kame seems more like the future way to go. Would it be possible to enhance ipfw & kame to work together better in same way (like having some kind of name for each tunnel and allowing ipfw rule to use them in similar way as 'via' is used with interfaces) ? Ari S. Ari S. -- Ari Suutari Lemi, Finland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 0:33: 1 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 00:33:00 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (jason.argos.org [216.233.245.106]) by hub.freebsd.org (Postfix) with ESMTP id CB25F37B400 for ; Thu, 7 Dec 2000 00:32:58 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id eB78SCY21852 for ; Thu, 7 Dec 2000 03:28:12 -0500 Date: Thu, 7 Dec 2000 03:28:11 -0500 (EST) From: Mike Nowlin To: freebsd-net@freebsd.org Subject: NAT & IRC 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'm running a lot of DHCP clients (issued 10.0.0.0/8 addrs) through a FBSD NATD proxy. It's a pretty basic NAT setup - no keepalives, etc. (That might(?) be the answer to my problem?) Earlier today, I set up x-chat on one of the clients. It was able to connect to irc.openprojects.net without any problems, but when I tried to connect to irc.freebsd.org, the server responded with something like "Sorry, you must be running ident to connect.." Understanding the reasoning for this, what's the solution? --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 4:39:56 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 04:39:54 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from relay2.flashnet.it (libra.cyb.it [212.11.95.209]) by hub.freebsd.org (Postfix) with ESMTP id CA25C37B400 for ; Thu, 7 Dec 2000 04:39:52 -0800 (PST) Received: from smtp.flashnet.it (ip085.pool-173.cyb.it [195.191.181.86]) by relay2.flashnet.it (EMS-RELAY/8.10.0) with SMTP id eB7CdoR10358 for ; Thu, 7 Dec 2000 13:39:50 +0100 Message-Id: <200012071239.eB7CdoR10358@relay2.flashnet.it> To: freebsd-net@FreeBSD.org Priority: Normal X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Thu, 7 Dec 2000 13:39:42 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: Re: ppp server help: found out! Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ** Reply to note from Brian Somers Wed, 06 Dec 2000 21:46:55 +0000 > If at any time during the life of a link, you do a ``set speed > sync'', it'll stay synchronous 'till a ``set speed nnn'' is done. In > your case, if you did a ``load papchap'' at some point (even via > pppctl), then a ``load modemin'', the end result would be a > synchronous link. > > Does that make sense ? Well, getty (or mgetty) invokes ppp for me, and it uses the "modemin" parameters, so it doesn't load the other label first. Anyway, I've solve id now. Bye & Thanks av. cc: freebsd-net@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 5: 6:45 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 05:06:43 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from inetfw.sonycsl.co.jp (inetfw.SonyCSL.CO.JP [203.137.129.4]) by hub.freebsd.org (Postfix) with ESMTP id C003937B400 for ; Thu, 7 Dec 2000 05:06:42 -0800 (PST) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.9.3+3.2W/3.7Ws3/inetfw/2000050701/smtpfeed 1.07) with ESMTP id WAA66836; Thu, 7 Dec 2000 22:06:41 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.9.3+3.2W/3.7Ws3/hotaka/2000061722) with ESMTP id WAA99291; Thu, 7 Dec 2000 22:06:41 +0900 (JST) To: freebsd-net@freebsd.org, tech-net@netbsd.org, tech@openbsd.org Subject: altq-3.0 is available X-Mailer: Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001207220641L.kjc@csl.sony.co.jp> Date: Thu, 07 Dec 2000 22:06:41 +0900 From: Kenjiro Cho X-Dispatcher: imput version 20000228(IM140) Lines: 38 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A new version of ALTQ that supports FreeBSD-4.2/4.1/4.1.1, NetBSD-1.5 and OpenBSD-2.8 is now available. http://www.csl.sony.co.jp/~kjc/software.html -Kenjiro From README: ALTQ -- Version 3.0 December 6, 2000 This is a release of Alternate Queueing for BSD UNIX. ALTQ provides queueing schemes required to realize resource-sharing and quality of service. The ALTQ release is intended to be a flexible platform to promote network research and gain field experience. Now that ALTQ is being developed in the KAME repository, this standalone ALTQ release is back-ported from KAME, and supports only FreeBSD-4.2R/4.1R, NetBSD-1.5 and OpenBSD-2.8. Other platform support (FreeBSD-2.2.8/3.5) is available in KAME snap releases. (some tools and documents haven't been merged into KAME, and are available only in this release.) What's New since version 2.2: - based on a new framework design - PRIQ (priority queueing) - supports FreeBSD-4.2, 4.1 (4.1.1), NetBSD-1.5 and OpenBSD-2.8 - tbrconfig tool for simple interface shaping w/o any discipline (a by-product of the new framework) - more supported drivers - code cleanup/bug fixes You can get the latest ALTQ release from or To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 5:54:49 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 05:54:48 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 84E1737B400 for ; Thu, 7 Dec 2000 05:54:47 -0800 (PST) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.9.3/8.9.3) with SMTP id IAA64739; Thu, 7 Dec 2000 08:54:36 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <000f01c06055$ca376ad0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Mike Nowlin" , References: Subject: Re: NAT & IRC Date: Thu, 7 Dec 2000 08:58:25 -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 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm running a lot of DHCP clients (issued 10.0.0.0/8 addrs) through a FBSD > NATD proxy. It's a pretty basic NAT setup - no keepalives, etc. (That > might(?) be the answer to my problem?) > > Earlier today, I set up x-chat on one of the clients. It was able to > connect to irc.openprojects.net without any problems, but when I tried to > connect to irc.freebsd.org, the server responded with something like > "Sorry, you must be running ident to connect.." Understanding the > reasoning for this, what's the solution? IRC networks use ident to better track abusers of the IRC network. What you need to do is run the ident service on any machine that is going to be running IRC, and add the appropriate firewall rules to allow ident packets to/from that host. One point - on a NAT network, I believe it's only possible for one "inside" client to be running ident, as the port must be forwarded explicitly. If you want to enable ident for the entire network, you could run it on the firewall machine, but that may open up certain security holes. -- Matthew Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 6:12:39 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 06:12:33 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from server.sito.it (server.sito.it [195.191.47.194]) by hub.freebsd.org (Postfix) with ESMTP id 7540937B400 for ; Thu, 7 Dec 2000 06:11:14 -0800 (PST) Received: from dado ([212.110.20.254]) by server.sito.it (#.#.#/?.?.?) with SMTP id PAA91873 for ; Thu, 7 Dec 2000 15:11:16 +0100 (CET) Message-ID: <023201c06057$7a7541a0$0a01a8c0@dado.gruppoidea.it> Reply-To: "Davide Lemma" From: "Davide Lemma" To: Subject: Re: Really odd problem Date: Thu, 7 Dec 2000 15:10:39 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_022F_01C0605F.DBFFADE0" 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 This is a multi-part message in MIME format. ------=_NextPart_000_022F_01C0605F.DBFFADE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I had the same problem... my server was an ADM-II K6-400, the = motherboard was a SOYO and 3Com50X as ethernet card, by now the problem = is solved by changing the motherboard and the case. For my personal opinion it is something linked to the APM, or some = strange bug in the motherboard's chipset, not the nic card... because = now it works right. =20 bye Davide =20 =20 I *could* do that, whats the hostname of your mail server? I'll have = it ping that =3Dp No messages on the console at all, and again i've = tried two seperate NIC cards both the (onboard intel) and the offboard = PCI Intel 10/100 -Drew=20 =20 =20 -----Original Message-----=20 From: Julian Elischer [mailto:julian@elischer.org]=20 Sent: Tuesday, December 05, 2000 2:30 PM=20 To: Drew J. Weaver=20 Cc: 'freebsd-net@freebsd.org'=20 Subject: Re: Really odd problem=20 =20 =20 > "Drew J. Weaver" wrote:=20 >=20 > We have a Freebsd 4.2 box on our network, after the box = boots, it=20 > brings up the network and everything is great, I can telnet into = it..=20 > everything good, but about 30-60 minutes later no incoming traffic = is getting=20 > to the server. If i ping the machine, or telnet to it, I get = nothing. If I go=20 > to the terminal and ping anything then it "wakes up" does anyone = have any idea=20 > what would cause it to stop "listening" to incoming network = requests? This is=20 > becoming very tiresome and i've done everything known to me.=20 Are you getting messages on the console?=20 possibly the card is bad and dies after a while..=20 the transmit timeout for many drivers will try reinitialise the = chip.=20 Which may bring it back to life... (for a while)=20 you could always add 'ping -i 120 [some address]'=20 to some startup script =20 :-)=20 =20 =20 >=20 > Thanks,=20 > -Drew=20 --=20 __--_|\ Julian Elischer=20 / \ julian@elischer.org=20 ( OZ ) World tour 2000=20 ---> X_.---._/ presently in: Budapest=20 v=20 ------=_NextPart_000_022F_01C0605F.DBFFADE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Really odd problem

I had the=20 same problem... my server was an ADM-II K6-400, the motherboard was = a SOYO=20 and 3Com50X as ethernet card, by now the problem is solved by = changing the=20 motherboard and the case.
For my personal opinion it is something linked = to the APM,=20 or some strange bug in the motherboard's chipset, not the nic = card...=20 because now it works right.
 
bye Davide

 

I *could* do that, whats the hostname of your mail = server?=20 I'll have it ping that =3Dp No messages on the console at all, and = again i've=20 tried two seperate NIC cards both the (onboard intel) and the = offboard PCI=20 Intel 10/100

-Drew


-----Original Message-----
From:=20 Julian Elischer [mailto:julian@elischer.org]=20
Sent: Tuesday, December 05, 2000 2:30 PM =
To: Drew J. Weaver

Cc:=20 'freebsd-net@freebsd.org'
Subject: Re: = Really odd=20 problem


> "Drew J. Weaver" wrote: =
>

>          = We=20 have a Freebsd 4.2 box on our network, after the box boots, = it=20
> brings up the network and everything is = great, I can=20 telnet into it..
> everything good, but = about=20 30-60 minutes later no incoming traffic is getting
> to the server. If i ping the machine, or telnet to it, = I get=20 nothing. If I go
> to the terminal and = ping=20 anything then it "wakes up" does anyone have any = idea=20
> what would cause it to stop = "listening" to=20 incoming network requests? This is
> = becoming=20 very tiresome and i've done everything known to me.

Are you getting messages on the console? =

possibly the card is bad and dies after a = while..=20
the transmit timeout for many drivers will try = reinitialise=20 the chip.
Which may bring it back to = life... (for a=20 while)

you could always add 'ping -i 120 [some address]'=20
to some startup script 

:-)


>
> Thanks, =
> -Drew

--
     =20 __--_|\  Julian Elischer
     = /       \=20 julian@elischer.org
    = (  =20 OZ    ) World tour 2000
--->=20 X_.---._/  presently in:  Budapest
          &nbs= p;=20 v

------=_NextPart_000_022F_01C0605F.DBFFADE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 10: 2:26 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 10:02:24 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from virtual.sysadmin-inc.com (lists.sysadmin-inc.com [209.16.228.140]) by hub.freebsd.org (Postfix) with ESMTP id 75A4C37B402 for ; Thu, 7 Dec 2000 10:02:20 -0800 (PST) Received: from wkst ([209.16.228.146]) by virtual.sysadmin-inc.com (8.9.1/8.9.1) with SMTP id NAA17886 for ; Thu, 7 Dec 2000 13:04:32 -0500 Reply-To: From: "Peter Brezny" To: Subject: bind version Date: Thu, 7 Dec 2000 13:01:26 -0800 Message-ID: <000a01c06090$dd81c3c0$46010a0a@sysadmininc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What version of bind does 4.2 ship with? And in general, how can i tell what version of bind is running? I searched the mail list archives since I'm sure it's in there somewhere, but I think the search engine is not working a search for bind and version on all archives returned NO results. TIA Peter Brezny SysAdmin Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 10:11:39 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 10:11:37 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id D9E6C37B400 for ; Thu, 7 Dec 2000 10:11:36 -0800 (PST) Received: (qmail 1123 invoked from network); 7 Dec 2000 18:11:32 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 7 Dec 2000 18:11:32 -0000 From: "Patrick Bihan-Faou" To: Subject: Problem with PPP, tcpmssd and routing socket messages Date: Thu, 7 Dec 2000 13:12:00 -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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am playing around with tcpmssd and an ADSL link. I use tcpmssd with the "-i" option to indicate which interface it should obtain the MTU information from. With this option, tcpmssd starts listening to the routing socket and updates its knowledge of the MTU based on the information received from the routing socket. The problem is that tcpmssd is started before the ppp negotiation is finished, so the initial MTU information is "incorrect" (1500). When the PPP negotiation is done, the MTU for the tun0 interface is updated to the correct value (1492) (as shown in ifconfig), but tcpmssd never receives any notification of that fact. The only routing update related to the tun0 interface that is received by tcpmssd is the "NEWADDR" message indicating the negotiated IP address, I do not see any IFINFO messages (which are the ones used for the MTU updates). If I update the MTU manually (using ifconfig), everything works fine: tcpmssd receives the RTM_IFINFO messages and the new MTU is used. Am I missing something ? Is the routing socket supposed to be "reliable" or can some messages get lost ? Does the fact that multiple processes are listening on the routing socket (natd etc.) changes the behaviour ? I am a bit lost here, I looked at the ppp code and the kernel code that does the MTU updates and the way I understand it, there should always be a routing message generated, however I can not see it anywhere... Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 10:21:46 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 10:21:45 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from hotmail.com (law2-f186.hotmail.com [216.32.181.186]) by hub.freebsd.org (Postfix) with ESMTP id 31BC137B400 for ; Thu, 7 Dec 2000 10:21:45 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 7 Dec 2000 10:21:42 -0800 Received: from 204.124.82.48 by lw2fd.hotmail.msn.com with HTTP; Thu, 07 Dec 2000 18:21:42 GMT X-Originating-IP: [204.124.82.48] From: "Mark Wright" To: peter@sysadmin-inc.com, freebsd-net@freebsd.org Subject: Re: bind version Date: Thu, 07 Dec 2000 18:21:42 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 07 Dec 2000 18:21:42.0245 (UTC) FILETIME=[8C4C2150:01C0607A] Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From: "Peter Brezny" >What version of bind does 4.2 ship with? And in general, how can i tell >what version of bind is running? named -v Mark _____________________________________________________________________________________ Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 10:52: 7 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 10:52:05 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 2CA1137B400 for ; Thu, 7 Dec 2000 10:52:04 -0800 (PST) Received: from luanda-33.budapest.interware.hu ([195.70.51.33] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14469C-0004JV-00; Thu, 07 Dec 2000 19:52:02 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2FA28E.D16D1BC3@elischer.org> Date: Thu, 07 Dec 2000 06:45:34 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Hamid Moghadam Cc: freebsd-net@freebsd.org Subject: Re: IPSec Netgraph node References: <383058475.976119027283.JavaMail.root@web582-mc> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hamid Moghadam wrote: > > Hi there > > Does anyone have any idea about implementation of IPSEC Netgraph node ? Or > is there any work in progress for doing that ? > > /Hamid I guess it hasn't been considered since it;s already in the standard networking code.. Negtraph is Suplimentary to the standard code (though there are many things that could be better done using netgraph.) > > ______________________________________________ > FREE Personalized Email at Mail.com > Sign up at http://www.mail.com/?sr=signup > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 11: 1:22 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 11:01:18 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id B67A037B400 for ; Thu, 7 Dec 2000 11:01:17 -0800 (PST) Received: from luanda-33.budapest.interware.hu ([195.70.51.33] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 1446I7-00054u-00; Thu, 07 Dec 2000 20:01:15 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A2FDE62.9E7C83CB@elischer.org> Date: Thu, 07 Dec 2000 11:00:50 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Patrick Bihan-Faou Cc: freebsd-net@freebsd.org Subject: Re: Problem with PPP, tcpmssd and routing socket messages References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Patrick Bihan-Faou wrote: > > Hi, > > I am playing around with tcpmssd and an ADSL link. > I use tcpmssd with the "-i" option to indicate which interface it should > obtain the MTU information from. With this option, tcpmssd starts listening > to the routing socket and updates its knowledge of the MTU based on the > information received from the routing socket. ppp now has tcpmssd build in (in at least one version... check with brian@freebsd.org) > > The problem is that tcpmssd is started before the ppp negotiation is > finished, so the initial MTU information is "incorrect" (1500). When the PPP > negotiation is done, the MTU for the tun0 interface is updated to the > correct value (1492) (as shown in ifconfig), but tcpmssd never receives any > notification of that fact. > > The only routing update related to the tun0 interface that is received by > tcpmssd is the "NEWADDR" message indicating the negotiated IP address, I do > not see any IFINFO messages (which are the ones used for the MTU updates). > > If I update the MTU manually (using ifconfig), everything works fine: > tcpmssd receives the RTM_IFINFO messages and the new MTU is used. > > Am I missing something ? Is the routing socket supposed to be "reliable" or > can some messages get lost ? Does the fact that multiple processes are > listening on the routing socket (natd etc.) changes the behaviour ? > > I am a bit lost here, I looked at the ppp code and the kernel code that does > the MTU updates and the way I understand it, there should always be a > routing message generated, however I can not see it anywhere... > > Patrick. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 11:16:16 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 11:16:14 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id E924C37B401 for ; Thu, 7 Dec 2000 11:16:13 -0800 (PST) Received: (qmail 3967 invoked from network); 7 Dec 2000 19:16:08 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 7 Dec 2000 19:16:08 -0000 From: "Patrick Bihan-Faou" To: "Julian Elischer" Cc: Subject: RE: Problem with PPP, tcpmssd and routing socket messages Date: Thu, 7 Dec 2000 14:16:35 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <3A2FDE62.9E7C83CB@elischer.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Julian, > ppp now has tcpmssd build in (in at least one version... > check with brian@freebsd.org) Thanks for the info, but I think that it is not yet in stable (I follow the CVS mailing list and I only saw commits for the head and the "NETGRAPH" branch). And the machine I have to make it work on definitely does not have this fix. My workaround for now is to invalidate the MTU information if I see any message on the routing socket that are related to the interface I am monitoring. Then when I have to modify a packet, I refetch the correct MTU at that point. This is just a workaround for the problem that the RTM_IFINFO is never received, which looks like a bug to me. If you give me some pointers as to where to look, I can spend some time on it. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 11:39:36 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 11:39:34 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 8AE4637B401 for ; Thu, 7 Dec 2000 11:39:33 -0800 (PST) Received: (qmail 5012 invoked from network); 7 Dec 2000 19:39:29 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 7 Dec 2000 19:39:29 -0000 From: "Patrick Bihan-Faou" To: Subject: RE: Problem with PPP, tcpmssd and routing socket messages Date: Thu, 7 Dec 2000 14:39:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Patrick Bihan-Faou [mailto:patrick@netzuno.com] > > My workaround for now is to invalidate the MTU information if I > see any message on the routing socket that are related to the > interface I am monitoring. Then when I have to modify a packet, I > refetch the correct MTU at that point. > > This is just a workaround for the problem that the RTM_IFINFO is > never received, which looks like a bug to me. If you give me some > pointers as to where to look, I can spend some time on it. I am happy to report that this workaround works just fine. I'd be happy to trace the "lost RTM_IFINFO" message issue if somebody can provide me with a couple of starting points. Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Dec 7 23:52:49 2000 From owner-freebsd-net@FreeBSD.ORG Thu Dec 7 23:52:47 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 19D5E37B400; Thu, 7 Dec 2000 23:52:43 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id eB87qPo69647; Fri, 8 Dec 2000 09:52:25 +0200 (EET) (envelope-from ru) Date: Fri, 8 Dec 2000 09:52:25 +0200 From: Ruslan Ermilov To: Patrick Bihan-Faou Cc: freebsd-net@FreeBSD.ORG, Brian Somers Subject: Re: Problem with PPP, tcpmssd and routing socket messages Message-ID: <20001208095225.A69062@sunbay.com> Mail-Followup-To: Patrick Bihan-Faou , freebsd-net@FreeBSD.ORG, Brian Somers References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from patrick@netzuno.com on Thu, Dec 07, 2000 at 02:39:56PM -0500 Sender: ru@whale.sunbay.crimea.ua Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Dec 07, 2000 at 02:39:56PM -0500, Patrick Bihan-Faou wrote: > > > > From: Patrick Bihan-Faou [mailto:patrick@netzuno.com] > > > > My workaround for now is to invalidate the MTU information if I > > see any message on the routing socket that are related to the > > interface I am monitoring. Then when I have to modify a packet, I > > refetch the correct MTU at that point. > > > > This is just a workaround for the problem that the RTM_IFINFO is > > never received, which looks like a bug to me. If you give me some > > pointers as to where to look, I can spend some time on it. > > > I am happy to report that this workaround works just fine. I'd be happy to > trace the "lost RTM_IFINFO" message issue if somebody can provide me with a > couple of starting points. > I do not know what happens here, though that's me who originally added the support for MTU change reports through route(4) socket: RCS file: /home/ncvs/src/sys/net/if.c,v Working file: if.c head: 1.95 branch: locks: strict access list: keyword substitution: kv total revisions: 116; selected revisions: 1 description: ---------------------------- revision 1.83 date: 2000/01/24 08:53:39; author: ru; state: Exp; lines: +4 -2 Notify user processes about interface's MTU change. Reviewed by: wollman, freebsd-net ==================================================================== Probably, if_tun.c needs a similar functionality added. Sorry, I can't investigate more at this time... I would suggest you to communicate with Brian Somers. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 8 8:56:16 2000 From owner-freebsd-net@FreeBSD.ORG Fri Dec 8 08:56:14 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 2091637B400 for ; Fri, 8 Dec 2000 08:56:13 -0800 (PST) Received: (qmail 5560 invoked by uid 3001); 8 Dec 2000 16:56:06 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 8 Dec 2000 16:56:06 -0000 Received: (qmail 31751 invoked by uid 1001); 8 Dec 2000 16:56:06 -0000 Date: Fri, 8 Dec 2000 11:56:06 -0500 From: Brian Reichert To: freebsd-net@freebsd.org Subject: cron messages: yp_next: clnt_call: RPC: Timed out Message-ID: <20001208115606.B31578@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: reichert@natto.numachi.com Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I asked this quesion on -isp, but there were no takers. Maybe someone here has some insight... ----- Forwarded message from Brian Reichert ----- Date: Fri, 1 Dec 2000 13:23:37 -0500 From: Brian Reichert To: freebsd-isp@freebsd.org Subject: cron messages: yp_next: clnt_call: RPC: Timed out Under FreeBSD 3.4-R, under a NIS client environment, I cannot seem to keep cron messages quiet. Harmless things like 'atrun' generate mail: From root Fri Dec 1 02:00:10 2000 Return-Path: Received: (from root@localhost) by private.internal.mydomain.com (8.9.3/8.9.3) id CAA75601; Fri, 1 Dec 2000 02:00:10 GMT (envelope-from root) Date: Fri, 1 Dec 2000 02:00:10 GMT Message-Id: <200012010200.CAA75601@private.internal.mydomain.com> From: root (Cron Daemon) To: root Subject: Cron /usr/libexec/atrun X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: X-Cron-Env: yp_next: clnt_call: RPC: Timed out (I've obfuscated the hostnames.) On this machine, root is a local account, not an NIS account. The NIS server is nis1% uname -a SunOS nis1 5.7 Generic_106542-04 i86pc i386 i86pc Does anyone have any advice on this matter? -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 8 10: 2:18 2000 From owner-freebsd-net@FreeBSD.ORG Fri Dec 8 10:02:16 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id 3CAD037B401 for ; Fri, 8 Dec 2000 10:02:16 -0800 (PST) Received: (qmail 54208 invoked from network); 8 Dec 2000 18:02:14 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 8 Dec 2000 18:02:14 -0000 From: "Patrick Bihan-Faou" To: "Ruslan Ermilov" Cc: , "Brian Somers" Subject: RE: Problem with PPP, tcpmssd and routing socket messages Date: Fri, 8 Dec 2000 13:02:56 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20001208095225.A69062@sunbay.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Ruslan, > > I do not know what happens here, though that's me who originally added > the support for MTU change reports through route(4) socket: > > RCS file: /home/ncvs/src/sys/net/if.c,v > Working file: if.c > head: 1.95 > branch: > locks: strict > access list: > keyword substitution: kv > total revisions: 116; selected revisions: 1 > description: > ---------------------------- > revision 1.83 > date: 2000/01/24 08:53:39; author: ru; state: Exp; lines: +4 -2 > Notify user processes about interface's MTU change. > Reviewed by: wollman, freebsd-net > ==================================================================== > > Probably, if_tun.c needs a similar functionality added. > Sorry, I can't investigate more at this time... > I would suggest you to communicate with Brian Somers. > I've looked in if.c already. Isn't the code you did called for all interface related IOCTLs ? Namely if I do a "ioctl(s, SIOCSIFMTU, &ifr)", it should be first handled by if.c then dispatched to if_tun.c right ? So that means that in all cases the RTM_IFINFO message should be sent. The funny thing is that if I do a ifconfig tun0 mtu 1333, I see the proper RTM_IFINFO messages... Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 8 21:31:38 2000 From owner-freebsd-net@FreeBSD.ORG Fri Dec 8 21:31:36 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102]) by hub.freebsd.org (Postfix) with ESMTP id 1542E37B400 for ; Fri, 8 Dec 2000 21:31:35 -0800 (PST) Received: from Beyond.cwc.nus.edu.sg ([172.16.3.32]) by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with ESMTP id NAA26816 for ; Sat, 9 Dec 2000 13:30:05 +0800 (SGT) Message-Id: <5.0.2.1.0.20001209132608.00a38ec0@postman.cwc.nus.edu.sg> X-Sender: yipmf@postman.cwc.nus.edu.sg X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 09 Dec 2000 13:32:36 +0800 To: freebsd-net@FreeBSD.ORG From: Yip Mann Fai Subject: Configuring rtadvd interfaces In-Reply-To: <200011280217.VAA00201@khavrinen.lcs.mit.edu> References: <5.0.2.1.0.20001128095340.00a4a5c0@postman.cwc.nus.edu.sg> <5.0.2.1.0.20001128095340.00a4a5c0@postman.cwc.nus.edu.sg> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've turned on rtadvd to advertise a IPv6 router on our IPv6 testbed. The router works fine and is able to route the IPv6 traffic properly. But there's one thing that's annoying me. It keeps giving me an error message that says " sending on gif0: Network is down". I got the same for gif1, gif2 and gif3. I'm using the stf0 interface instead of the gif interfaces. How can I suppress rtadvd from advertising on the gif interfaces?? Please help. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Dec 8 21:46:24 2000 From owner-freebsd-net@FreeBSD.ORG Fri Dec 8 21:46:23 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 6E2E137B400 for ; Fri, 8 Dec 2000 21:46:22 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 144ctG-0000Br-00; Fri, 08 Dec 2000 22:49:46 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A31C7FA.79B0E7E5@softweyr.com> Date: Fri, 08 Dec 2000 22:49:46 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Emmerton Cc: Mike Nowlin , freebsd-net@FreeBSD.ORG Subject: Re: NAT & IRC References: <000f01c06055$ca376ad0$1200a8c0@gsicomp.on.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Emmerton wrote: > > > I'm running a lot of DHCP clients (issued 10.0.0.0/8 addrs) through a FBSD > > NATD proxy. It's a pretty basic NAT setup - no keepalives, etc. (That > > might(?) be the answer to my problem?) > > > > Earlier today, I set up x-chat on one of the clients. It was able to > > connect to irc.openprojects.net without any problems, but when I tried to > > connect to irc.freebsd.org, the server responded with something like > > "Sorry, you must be running ident to connect.." Understanding the > > reasoning for this, what's the solution? > > IRC networks use ident to better track abusers of the IRC network. > > What you need to do is run the ident service on any machine that is going to > be running IRC, and add the appropriate firewall rules to allow ident > packets to/from that host. One point - on a NAT network, I believe it's > only possible for one "inside" client to be running ident, as the port must > be forwarded explicitly. If you want to enable ident for the entire > network, you could run it on the firewall machine, but that may open up > certain security holes. Fools trust ident. Use an identd that refuses to disclose information about your systems by returning a random ident string. If you use a NAT router, run it on the router. If not, configure your router to redirect all ident requests to one machine that has such an ident server running. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Dec 9 9: 3:59 2000 From owner-freebsd-net@FreeBSD.ORG Sat Dec 9 09:03:56 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 7619A37B400 for ; Sat, 9 Dec 2000 09:03:53 -0800 (PST) Received: from localhost (IDENT:zkhiqnLMg4H/3Xay4pLcmNoFQwZgDcaWINIeDV4nMZaOjjRP0QIOpc0IZ1FJzSo7@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.1/8.11.1/peace) with ESMTP/inet6 id eB9H1NE87823; Sun, 10 Dec 2000 02:01:24 +0900 (JST) (envelope-from ume@FreeBSD.org) Date: Sun, 10 Dec 2000 02:01:20 +0900 (JST) Message-Id: <20001210.020120.48458307.ume@FreeBSD.org> To: yipmf@cwc.nus.edu.sg Cc: freebsd-net@FreeBSD.ORG Subject: Re: Configuring rtadvd interfaces From: Hajimu UMEMOTO In-Reply-To: <5.0.2.1.0.20001209132608.00a38ec0@postman.cwc.nus.edu.sg> References: <5.0.2.1.0.20001128095340.00a4a5c0@postman.cwc.nus.edu.sg> <200011280217.VAA00201@khavrinen.lcs.mit.edu> <5.0.2.1.0.20001209132608.00a38ec0@postman.cwc.nus.edu.sg> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Sat, 09 Dec 2000 13:32:36 +0800 >>>>> Yip Mann Fai said: yipmf> I've turned on rtadvd to advertise a IPv6 router on our IPv6 testbed. The yipmf> router works fine and is able to route the IPv6 traffic properly. But yipmf> there's one thing that's annoying me. It keeps giving me an error message yipmf> that says " sending on gif0: Network is down". I got the same yipmf> for gif1, gif2 and gif3. I'm using the stf0 interface instead of the gif yipmf> interfaces. How can I suppress rtadvd from advertising on the gif interfaces?? Do you include gifN in ipv6_network_interfaces? If you don't need static address assignment to gifN, please exclude gifN from ipv6_network_interfaces. Or, if you need, please apply following patch: Index: rc.network6 =================================================================== RCS file: /home/ncvs/src/etc/rc.network6,v retrieving revision 1.15 diff -u -r1.15 rc.network6 --- rc.network6 2000/11/14 15:49:31 1.15 +++ rc.network6 2000/12/09 16:59:37 @@ -211,7 +211,7 @@ '') for i in ${ipv6_network_interfaces}; do case $i in - stf*) + gif*|stf*|faith*) continue ;; *) -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Dec 9 12:48:27 2000 From owner-freebsd-net@FreeBSD.ORG Sat Dec 9 12:48:25 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id C3BAB37B400; Sat, 9 Dec 2000 12:48:23 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB9KkKH09748; Sat, 9 Dec 2000 20:46:20 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB9KnQl54447; Sat, 9 Dec 2000 20:49:26 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012092049.eB9KnQl54447@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Patrick Bihan-Faou" Cc: "Ruslan Ermilov" , freebsd-net@FreeBSD.ORG, "Brian Somers" , brian@Awfulhak.org Subject: Re: Problem with PPP, tcpmssd and routing socket messages In-Reply-To: Message from "Patrick Bihan-Faou" of "Fri, 08 Dec 2000 13:02:56 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Dec 2000 20:49:26 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi Ruslan, > > > > > I do not know what happens here, though that's me who originally added > > the support for MTU change reports through route(4) socket: > > > > RCS file: /home/ncvs/src/sys/net/if.c,v > > Working file: if.c > > head: 1.95 > > branch: > > locks: strict > > access list: > > keyword substitution: kv > > total revisions: 116; selected revisions: 1 > > description: > > ---------------------------- > > revision 1.83 > > date: 2000/01/24 08:53:39; author: ru; state: Exp; lines: +4 -2 > > Notify user processes about interface's MTU change. > > Reviewed by: wollman, freebsd-net > > ==================================================================== > > > > Probably, if_tun.c needs a similar functionality added. > > Sorry, I can't investigate more at this time... > > I would suggest you to communicate with Brian Somers. > > > > > I've looked in if.c already. Isn't the code you did called for all interface > related IOCTLs ? Namely if I do a "ioctl(s, SIOCSIFMTU, &ifr)", it should be > first handled by if.c then dispatched to if_tun.c right ? So that means that > in all cases the RTM_IFINFO message should be sent. > > The funny thing is that if I do a ifconfig tun0 mtu 1333, I see the proper > RTM_IFINFO messages... ppp sets the interface mtu using TUNSIFINFO rather than SIOCSIFMTU. See src/usr.sbin/ppp/tun.c. > Patrick. -- 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 Dec 9 15:43:47 2000 From owner-freebsd-net@FreeBSD.ORG Sat Dec 9 15:43:45 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from modemcable101.200-201-24.mtl.mc.videotron.ca (modemcable140.61-201-24.mtl.mc.videotron.ca [24.201.61.140]) by hub.freebsd.org (Postfix) with SMTP id B406C37B400 for ; Sat, 9 Dec 2000 15:43:44 -0800 (PST) Received: (qmail 21411 invoked from network); 9 Dec 2000 23:43:43 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 9 Dec 2000 23:43:43 -0000 From: "Patrick Bihan-Faou" To: "Brian Somers" Cc: Subject: RE: Problem with PPP, tcpmssd and routing socket messages Date: Sat, 9 Dec 2000 18:44:09 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: <200012092049.eB9KnQl54447@hak.lan.Awfulhak.org> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Brian, > > The funny thing is that if I do a ifconfig tun0 mtu 1333, I see > the proper > > RTM_IFINFO messages... > > ppp sets the interface mtu using TUNSIFINFO rather than SIOCSIFMTU. > See src/usr.sbin/ppp/tun.c. > OK now I see it... This seems to be the culprit. I guess that this ioctl as well as possibly TUNSIFMODE should generate the proper routing socket messages (RTM_IFINFO). Do you want me to do that and send you a patch, or do you want to handle it yourself ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Sat Dec 9 15:59:50 2000 From owner-freebsd-net@FreeBSD.ORG Sat Dec 9 15:59:48 2000 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id E441137B400 for ; Sat, 9 Dec 2000 15:59:46 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id eB9NviH10566; Sat, 9 Dec 2000 23:57:44 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id eBA00nk55811; Sun, 10 Dec 2000 00:00:49 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200012100000.eBA00nk55811@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Patrick Bihan-Faou" Cc: "Brian Somers" , freebsd-net@freebsd.org, brian@Awfulhak.org Subject: Re: Problem with PPP, tcpmssd and routing socket messages In-Reply-To: Message from "Patrick Bihan-Faou" of "Sat, 09 Dec 2000 18:44:09 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Dec 2000 00:00:49 +0000 From: Brian Somers Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A patch'd be good :-) Cheers. > Hi Brian, > > > > > The funny thing is that if I do a ifconfig tun0 mtu 1333, I see > > the proper > > > RTM_IFINFO messages... > > > > ppp sets the interface mtu using TUNSIFINFO rather than SIOCSIFMTU. > > See src/usr.sbin/ppp/tun.c. > > > > OK now I see it... This seems to be the culprit. I guess that this ioctl as > well as possibly TUNSIFMODE should generate the proper routing socket > messages (RTM_IFINFO). Do you want me to do that and send you a patch, or do > you want to handle it yourself ? > > > Patrick. -- 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