From owner-freebsd-net Mon Aug 16 23:22:30 1999 Delivered-To: freebsd-net@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 2D9BB14E0D for ; Mon, 16 Aug 1999 23:21:32 -0700 (PDT) (envelope-from Chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.0.2]) by postoffice.aims.com.au (8.9.3/8.9.3) with ESMTP id QAA00538 for ; Tue, 17 Aug 1999 16:21:55 +1000 (EST) (envelope-from Chris@aims.com.au) Received: from nts-ts1 by aims.com.au with SMTP (MDaemon.v2.84.R) for ; Tue, 17 Aug 1999 16:18:46 +1000 From: "Chris Knight" To: Cc: Subject: pipsecd Date: Tue, 17 Aug 1999 16:18:45 +1000 Message-ID: <001d01bee878$5cea4890$0200a8c0@nts-ts1.aims.private> 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 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal X-MDaemon-Deliver-To: freebsd-net@freebsd.org X-Return-Path: Chris@aims.com.au Reply-To: chris@aims.com.au Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy, I've just noticed that pipsecd has appeared in the ports tre. Does anyone know how to use it? On machine A, I have in my pipsecd.conf: sa ipesp spi=1000 enc=blowfish_cbc ekey= dest= sa ipesp spi=1001 enc=blowfish_cbc ekey= if /dev/tun1 local_spi=1001 remote_spi=1000 On machine B, I have in my pipsecd.conf: sa ipesp spi=1000 enc=blowfish_cbc ekey= sa ipesp spi=1001 enc=blowfish_cbc ekey= dest= if /dev/tun1 local_spi=1000 remote_spi=1001 On machine A, I add: ifconfig tun1 192.168.3.1 192.168.3.2 netmask 0xffffff00 mtu 1440 On machine B, I add: ifconfig tun1 192.168.3.2 192.168.3.1 netmaks 0xffffff00 mtu 1440 The update probes are sent and received, but pinging the remote end of the tun1 device sends the packet via my default route. What am I doing wrong? Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Tue Aug 17 2: 6:49 1999 Delivered-To: freebsd-net@freebsd.org Received: from enst.enst.fr (enst.enst.fr [137.194.2.16]) by hub.freebsd.org (Postfix) with ESMTP id 65A4514F1C for ; Tue, 17 Aug 1999 02:06:43 -0700 (PDT) (envelope-from beyssac@enst.fr) Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37]) by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id LAA27730; Tue, 17 Aug 1999 11:05:38 +0200 (MET DST) Received: by bofh.enst.fr (Postfix, from userid 12426) id D762BD21B; Tue, 17 Aug 1999 11:02:47 +0200 (CEST) Message-ID: <19990817110247.A70931@enst.fr> Date: Tue, 17 Aug 1999 11:02:47 +0200 From: Pierre Beyssac To: chris@aims.com.au, freebsd-net@FreeBSD.ORG Cc: pb@fasterix.freenix.org Subject: Re: pipsecd References: <001d01bee878$5cea4890$0200a8c0@nts-ts1.aims.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <001d01bee878$5cea4890$0200a8c0@nts-ts1.aims.private>; from Chris Knight on Tue, Aug 17, 1999 at 04:18:45PM +1000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 17, 1999 at 04:18:45PM +1000, Chris Knight wrote: > On machine A, I add: > ifconfig tun1 192.168.3.1 192.168.3.2 netmask 0xffffff00 mtu 1440 > > The update probes are sent and received, but pinging the remote end of the > tun1 device sends the packet via my default route. What does netstat -rn say? And ifconfig? After your ifconfig above, there should be a host route to interface tun1. -- Pierre Beyssac pb@enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 18 13:16: 1 1999 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 916BF14F01 for ; Wed, 18 Aug 1999 13:15:49 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA14712 for ; Wed, 18 Aug 1999 13:14:15 -0700 (PDT) Date: Wed, 18 Aug 1999 13:15:27 -0700 (PDT) From: Julian Elischer To: net@freebsd.org Subject: [Fwd: Samba 2.0.5 on FreeBSD 3.1-RELEASE - very very slow writing to Samba from win98] (fwd) 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 Ok, here is a problem.... Samba (the newest version) has slowed down on FreeBSD by an order of magnitude. The cnage that was made was to replace soem read() calls from sockets to recv() calls, and making use of the MSG_WAITALL flag. Under alltheother Unix versions, (inc linux) this has resulted in a smaller number of syscalls. They don't want to have a #ifdef __FreeBSD__ in the sources so they have asked for help in isolating the problem. Here is a piece of email that details some specifics... anyone have any ideas? I looked at the code in soreceive() and it doesn't seem to have changed for ages, and (to brief inspection) seems to be correct. (as regards to MSG_WAITALL anyhow). julian ---------- Forwarded message ---------- Date: Wed, 18 Aug 1999 09:17:42 -0700 From: Jeremy Allison To: Julian Elischer Subject: [Fwd: Samba 2.0.5 on FreeBSD 3.1-RELEASE - very very slow writing to Samba from win98] Julian - confirmation it's the MSG_WAITALL flag that's causing the problem. Jeremy. Johan Kerckaert wrote: > > Hi, > > Jeremy Allison wrote: > > Ok, thanks for the confirmation. Now I nweed to work out > > with the FreeBSD guys why this change has such a great > > effect. It may be that the use of the MSG_WAITALL flag in > > the recv() call is causing problems. > > Indeed, I tried replacing the MSG_WAITALL flag with 0 in the recv () calls, > in util_sock.c, and then it's ok > Using recv calls is also faster than using read calls: > I got 1.3 Mb/s using read, 1.6 Mb/s using recv () with no flags, on a 100 Mbit > crossover. > > Kind regards, > -- > Johan Kerckaert > BricsNet -- -------------------------------------------------------- Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. -------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 18 22:15:12 1999 Delivered-To: freebsd-net@freebsd.org Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124]) by hub.freebsd.org (Postfix) with SMTP id BE2BA14F0F for ; Wed, 18 Aug 1999 22:15:09 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.104 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 18 Aug 1999 22:12:11 -0700 (Pacific Daylight Time) Received: by INET-IMC-02 with Internet Mail Service (5.5.2448.0) id ; Wed, 18 Aug 1999 22:12:11 -0700 Message-ID: From: George Chung To: "'freebsd-net@freebsd.org'" Subject: on dual-homed machine, how to specify outgoing interface to send multicast packets Date: Wed, 18 Aug 1999 22:12:02 -0700 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Platform: FreeBSD 3.2 RELEASE, "default" kernel on a dual-homed box Experience level: newbie On a dual-homed machine, there is no "network" portion of the destination Class D address to make any kind of determination as to which outgoing interface to use. So I make a call to setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &inaddr, sizeof(struct in_addr)); I confirm that this call works. Plus I doublechecked by giving it a bogus inaddr, and it gave me errno 49 EADDRNOTAVAIL. However, when I try send a packet to "225.0.0.1", I get errno 65 EHOSTUNREACH. Please help! :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 18 22:30:13 1999 Delivered-To: freebsd-net@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 79D8914EA4 for ; Wed, 18 Aug 1999 22:30:05 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA22334; Thu, 19 Aug 1999 01:26:53 -0400 Date: Thu, 19 Aug 1999 01:26:53 -0400 (EDT) From: Mike Nowlin To: George Chung Cc: "'freebsd-net@freebsd.org'" Subject: Re: on dual-homed machine, how to specify outgoing interface to send multicast packets 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 a dual-homed machine, there is no "network" portion of the destination > Class D address to make any kind of determination as to which outgoing > interface to use. > > So I make a call to > > setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &inaddr, sizeof(struct > in_addr)); > > I confirm that this call works. Plus I doublechecked by giving it a bogus > inaddr, and it gave me errno 49 EADDRNOTAVAIL. However, when I try send a > packet to "225.0.0.1", I get errno 65 EHOSTUNREACH. First guess is that it's a routing problem... Try pinging that address -- if you get a "route not available" (or similar message), that's probably it. (I'm too brain-fried right now to go into much more detail than that... :) ) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 18 22:59:23 1999 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 5C9711509D for ; Wed, 18 Aug 1999 22:59:20 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 18 Aug 1999 22:56:45 -0700 (Pacific Daylight Time) Received: by INET-IMC-05 with Internet Mail Service (5.5.2524.0) id ; Wed, 18 Aug 1999 22:46:43 -0700 Message-ID: From: George Chung To: 'Mike Nowlin' Cc: "'freebsd-net@freebsd.org'" Subject: RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets Date: Wed, 18 Aug 1999 22:46:41 -0700 X-Mailer: Internet Mail Service (5.5.2524.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org you're right, I can't ping the address. so how do I fix that?! :-) -----Original Message----- From: Mike Nowlin [mailto:mike@argos.org] Sent: Wednesday, August 18, 1999 10:27 PM To: George Chung Cc: 'freebsd-net@freebsd.org' Subject: Re: on dual-homed machine, how to specify outgoing interface to send multicast packets > On a dual-homed machine, there is no "network" portion of the destination > Class D address to make any kind of determination as to which outgoing > interface to use. > > So I make a call to > > setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &inaddr, sizeof(struct > in_addr)); > > I confirm that this call works. Plus I doublechecked by giving it a bogus > inaddr, and it gave me errno 49 EADDRNOTAVAIL. However, when I try send a > packet to "225.0.0.1", I get errno 65 EHOSTUNREACH. First guess is that it's a routing problem... Try pinging that address -- if you get a "route not available" (or similar message), that's probably it. (I'm too brain-fried right now to go into much more detail than that... :) ) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Wed Aug 18 23:23: 1 1999 Delivered-To: freebsd-net@freebsd.org Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124]) by hub.freebsd.org (Postfix) with SMTP id 8CFE3150BD for ; Wed, 18 Aug 1999 23:22:57 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.104 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 18 Aug 1999 23:21:28 -0700 (Pacific Daylight Time) Received: by INET-IMC-02 with Internet Mail Service (5.5.2448.0) id ; Wed, 18 Aug 1999 23:21:28 -0700 Message-ID: From: George Chung To: George Chung , 'Mike Nowlin' Cc: "'freebsd-net@freebsd.org'" Subject: RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets Date: Wed, 18 Aug 1999 23:21:25 -0700 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After some digging, I tried the following and it seemed to work, although I can't say that I know exactly what's going on: route add -net 225.0.0.1 -netmask 0xF0000000 -interface 10.100.100.100 Is it the case that since this is a "fake" network with no actual router, that I need to manually add entries to the routing table? How do I do this automagically? TIA, George -----Original Message----- From: George Chung [mailto:gchung@microsoft.com] Sent: Wednesday, August 18, 1999 10:47 PM To: 'Mike Nowlin' Cc: 'freebsd-net@freebsd.org' Subject: RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets you're right, I can't ping the address. so how do I fix that?! :-) -----Original Message----- From: Mike Nowlin [mailto:mike@argos.org] Sent: Wednesday, August 18, 1999 10:27 PM To: George Chung Cc: 'freebsd-net@freebsd.org' Subject: Re: on dual-homed machine, how to specify outgoing interface to send multicast packets > On a dual-homed machine, there is no "network" portion of the destination > Class D address to make any kind of determination as to which outgoing > interface to use. > > So I make a call to > > setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &inaddr, sizeof(struct > in_addr)); > > I confirm that this call works. Plus I doublechecked by giving it a bogus > inaddr, and it gave me errno 49 EADDRNOTAVAIL. However, when I try send a > packet to "225.0.0.1", I get errno 65 EHOSTUNREACH. First guess is that it's a routing problem... Try pinging that address -- if you get a "route not available" (or similar message), that's probably it. (I'm too brain-fried right now to go into much more detail than that... :) ) --mike 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 19 10:26:27 1999 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 C5C4D15203 for ; Thu, 19 Aug 1999 10:26:23 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 19 Aug 1999 10:24:48 -0700 (Pacific Daylight Time) Received: by INET-IMC-05 with Internet Mail Service (5.5.2524.0) id ; Thu, 19 Aug 1999 10:24:47 -0700 Message-ID: From: George Chung To: "'freebsd-net@freebsd.org'" Subject: PLEASE HELP: mcast weirdness on private network Date: Thu, 19 Aug 1999 10:24:43 -0700 X-Mailer: Internet Mail Service (5.5.2524.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Gurus: On a "normal" network (routers, connected to the inet), an app on NT4 and FreeBSD 3.2 can join an mcast group (225.0.0.1) and send/receive messages to each other on that address. However, when I move the binaries to a private network (no router) with NT4 and FreeBSD: An NT box is able to communicate bidrectionally with another NT box. The FreeBSD boxes are able to communicate bidrectionally with each other. The FreeBSD boxes are able to receive mcast packets from the NT boxes. BUT, the NT boxes aren't able to pick up mcast packets from FreeBSD!! Here's the network: m1 10.100.100.100 FreeBSD dual-homed (the 2nd interface is unconfigured). m2 10.100.100.102 FreeBSD dual-homed (the 2nd interface is unconfigured). m3 10.100.100.200 NT4 m4 10.100.100.202 W2K I had to tweak the FreeBSD boxes to get them to even work by adding a route for 225.0.0.1 (otherwise, I got a EHOSTUNREACH error when pinging 225.0.0.1). I am not sure I did this correctly. Here's my command: route add -net 225.0.0.1 -netmask 0xf0000000 -interface 10.100.100.100 The mcast code on FreeBSD does the following above and beyond the default (because they are multihomed): in the call to join the group, I specify the specific interface to receive on. I also call setsockopt to set the outgoing interface on mcast sends. I am scratching my head. The only thing I can think of is that Windows NT is filtering out IP packets whose source IP address it doesn't "know". But the only way I know how to do that for UDP sockets is to explicitly connect it to an endpoint. Any help would be greatly appreciated. Thanks, George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 19 11:50: 8 1999 Delivered-To: freebsd-net@freebsd.org Received: from inet-vrs-02.microsoft.com (mail2.microsoft.com [131.107.3.124]) by hub.freebsd.org (Postfix) with SMTP id D61C81521E for ; Thu, 19 Aug 1999 11:50:00 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.104 by inet-vrs-02.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 19 Aug 1999 11:48:45 -0700 (Pacific Daylight Time) Received: by INET-IMC-02 with Internet Mail Service (5.5.2448.0) id ; Thu, 19 Aug 1999 11:48:45 -0700 Message-ID: From: George Chung To: George Chung , "'freebsd-net@freebsd.org'" Subject: RE: PLEASE HELP: mcast weirdness on private network Date: Thu, 19 Aug 1999 11:48:36 -0700 X-Mailer: Internet Mail Service (5.5.2448.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org BTW, there is no problem when using the all-hosts address 224.0.0.1. > -----Original Message----- > From: George Chung > Sent: Thursday, August 19, 1999 10:25 AM > To: 'freebsd-net@freebsd.org' > Subject: PLEASE HELP: mcast weirdness on private network > > Hi Gurus: > On a "normal" network (routers, connected to the inet), an app on NT4 and > FreeBSD 3.2 can join an mcast group (225.0.0.1) and send/receive messages > to each other on that address. > > However, when I move the binaries to a private network (no router) with > NT4 and FreeBSD: > An NT box is able to communicate bidrectionally with another NT box. > The FreeBSD boxes are able to communicate bidrectionally with each other. > The FreeBSD boxes are able to receive mcast packets from the NT boxes. > BUT, the NT boxes aren't able to pick up mcast packets from FreeBSD!! > > Here's the network: > m1 10.100.100.100 FreeBSD dual-homed (the 2nd interface is unconfigured). > m2 10.100.100.102 FreeBSD dual-homed (the 2nd interface is unconfigured). > m3 10.100.100.200 NT4 > m4 10.100.100.202 W2K > > I had to tweak the FreeBSD boxes to get them to even work by adding a > route for 225.0.0.1 (otherwise, I got a EHOSTUNREACH error when pinging > 225.0.0.1). I am not sure I did this correctly. Here's my command: > > route add -net 225.0.0.1 -netmask 0xf0000000 -interface 10.100.100.100 > > The mcast code on FreeBSD does the following above and beyond the default > (because they are multihomed): > in the call to join the group, I specify the specific interface to receive > on. > I also call setsockopt to set the outgoing interface on mcast sends. > > I am scratching my head. The only thing I can think of is that Windows NT > is filtering out IP packets whose source IP address it doesn't "know". But > the only way I know how to do that for UDP sockets is to explicitly > connect it to an endpoint. Any help would be greatly appreciated. > > Thanks, > George > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Thu Aug 19 13: 2:22 1999 Delivered-To: freebsd-net@freebsd.org Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122]) by hub.freebsd.org (Postfix) with SMTP id 0EF2A15202 for ; Thu, 19 Aug 1999 13:02:12 -0700 (PDT) (envelope-from gchung@microsoft.com) Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 19 Aug 1999 13:01:30 -0700 (Pacific Daylight Time) Received: by INET-IMC-04 with Internet Mail Service (5.5.2524.0) id ; Thu, 19 Aug 1999 13:01:29 -0700 Message-ID: From: George Chung To: George Chung , "'freebsd-net@freebsd.org'" Subject: RE: PLEASE HELP: mcast weirdness on private network Date: Thu, 19 Aug 1999 13:01:26 -0700 X-Mailer: Internet Mail Service (5.5.2524.0) Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org issue resolved. the bsd boxes incorrectly specified a gateway. -----Original Message----- From: George Chung [mailto:gchung@microsoft.com] Sent: Thursday, August 19, 1999 11:49 AM To: George Chung; 'freebsd-net@freebsd.org' Subject: RE: PLEASE HELP: mcast weirdness on private network BTW, there is no problem when using the all-hosts address 224.0.0.1. > -----Original Message----- > From: George Chung > Sent: Thursday, August 19, 1999 10:25 AM > To: 'freebsd-net@freebsd.org' > Subject: PLEASE HELP: mcast weirdness on private network > > Hi Gurus: > On a "normal" network (routers, connected to the inet), an app on NT4 and > FreeBSD 3.2 can join an mcast group (225.0.0.1) and send/receive messages > to each other on that address. > > However, when I move the binaries to a private network (no router) with > NT4 and FreeBSD: > An NT box is able to communicate bidrectionally with another NT box. > The FreeBSD boxes are able to communicate bidrectionally with each other. > The FreeBSD boxes are able to receive mcast packets from the NT boxes. > BUT, the NT boxes aren't able to pick up mcast packets from FreeBSD!! > > Here's the network: > m1 10.100.100.100 FreeBSD dual-homed (the 2nd interface is unconfigured). > m2 10.100.100.102 FreeBSD dual-homed (the 2nd interface is unconfigured). > m3 10.100.100.200 NT4 > m4 10.100.100.202 W2K > > I had to tweak the FreeBSD boxes to get them to even work by adding a > route for 225.0.0.1 (otherwise, I got a EHOSTUNREACH error when pinging > 225.0.0.1). I am not sure I did this correctly. Here's my command: > > route add -net 225.0.0.1 -netmask 0xf0000000 -interface 10.100.100.100 > > The mcast code on FreeBSD does the following above and beyond the default > (because they are multihomed): > in the call to join the group, I specify the specific interface to receive > on. > I also call setsockopt to set the outgoing interface on mcast sends. > > I am scratching my head. The only thing I can think of is that Windows NT > is filtering out IP packets whose source IP address it doesn't "know". But > the only way I know how to do that for UDP sockets is to explicitly > connect it to an endpoint. Any help would be greatly appreciated. > > Thanks, > George > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 20 3:15:58 1999 Delivered-To: freebsd-net@freebsd.org Received: from mh.acorn.co.uk (mh.acorn.co.uk [136.170.131.2]) by hub.freebsd.org (Postfix) with ESMTP id CE5D014DCB for ; Fri, 20 Aug 1999 03:15:48 -0700 (PDT) (envelope-from kbracey@e-14.com) Received: from kbracey.acorn.co.uk (kbracey [136.170.129.213]) by mh.acorn.co.uk (8.8.6/8.8.6) with SMTP id LAA00320 for ; Fri, 20 Aug 1999 11:15:46 +0100 (BST) Date: Fri, 20 Aug 1999 11:15:54 +0100 From: Kevin Bracey To: freebsd-net@freebsd.org Subject: RE: on dual-homed machine, how to specify outgoing interface to s end multicast packets Message-ID: <35277e3449%kbracey@kbracey.acorn.co.uk> In-Reply-To: X-Organization: Acorn Computers Ltd, Cambridge, United Kingdom X-Mailer: Messenger v1.40f for RISC OS MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Posting-Agent: RISC OS Newsbase 0.61b Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message George Chung wrote: > you're right, I can't ping the address. so how do I fix that?! :-) > > -----Original Message----- > From: Mike Nowlin [mailto:mike@argos.org] > Sent: Wednesday, August 18, 1999 10:27 PM > To: George Chung > Cc: 'freebsd-net@freebsd.org' > Subject: Re: on dual-homed machine, how to specify outgoing interface to > send multicast packets > > > > > On a dual-homed machine, there is no "network" portion of the destination > > Class D address to make any kind of determination as to which outgoing > > interface to use. > > > > So I make a call to > > > > setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &inaddr, sizeof(struct > > in_addr)); > > > > I confirm that this call works. Plus I doublechecked by giving it a bogus > > inaddr, and it gave me errno 49 EADDRNOTAVAIL. However, when I try send a > > packet to "225.0.0.1", I get errno 65 EHOSTUNREACH. > > First guess is that it's a routing problem... Try pinging that address -- > if you get a "route not available" (or similar message), that's probably > it. > This is a known BSD bug - even if you specify an interface manually for multicasts, you need a route set up for multicast packets :( As a side- effect, IGMP messages won't get sent either, unless you have a multicast route set up. -- Kevin Bracey, Senior Software Engineer Pace Micro Technology plc Tel: +44 (0) 1223 518566 645 Newmarket Road Fax: +44 (0) 1223 518526 Cambridge, CB5 8PB, United Kingdom WWW: http://www.acorn.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message From owner-freebsd-net Fri Aug 20 10:34:14 1999 Delivered-To: freebsd-net@freebsd.org Received: from super-g.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 1C729154A6 for ; Fri, 20 Aug 1999 10:34:11 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.com (Postfix) with SMTP id 77453B8C0; Fri, 20 Aug 1999 13:31:58 -0400 (EDT) Date: Fri, 20 Aug 1999 13:31:58 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: jonathan michaels Cc: Brian Somers , Brian Somers , Robert Watson , freebsd-net@FreeBSD.ORG Subject: Re: "Invitation to participate in PPPoE Trial" (fwd) In-Reply-To: <19990803225325.E10638@caamora.com.au> 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, 3 Aug 1999, jonathan michaels wrote: > i realise that all things bright and shiney are seen as must > haves, but could you (briefly and not so technically) explain > to me and the others who may also be wondering what real > advantage PPPoE would offer to endusers. It's great!! Your ISP has to shell out for a Redback box to terminate these connections (they co-authored the RFC w/UUNet), so right there if you are a customer with stock in RedBack, you make a little cash. On top of that, you bandwidth goes down a bit as you encapsulate umpteen protocols inside each other, you get a sloppier network design from your dsl provider as they realize that with PPPoE they can think of their dsl cloud as a "Big LAN", and you get to put that new PIII's spare cycles to use doing PPP on your 1.6Mb link. And don't forget how your dedicated dsl line now requires you to "dial up" each time you want to do something... Those redback folks have an excellent sales team. I don't much care for the idea. Charles > or, please point to a reading list, bibliography, rfc, etc etc. > > regards, > > jonathan > > -- > =============================================================================== > Jonathan Michaels > PO Box 144, Rosebery, NSW 1445 Australia > =========================================================== > > > > 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