From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.ufw2.com([216.163.21.20]) (3164 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Sun, 15 Oct 2000 12:18:37 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from hardb ([216.163.21.59]) by mail.ufw2.com (Build 101 8.9.3/NT-8.9.3) with SMTP id LAA02755 for ; Sun, 15 Oct 2000 11:19:02 -0500 Message-Id: <3.0.6.32.20001015112823.007b1150@mail.ufw2.com> X-Sender: bharding@mail.ufw2.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 15 Oct 2000 11:28:23 -0500 To: speakup@braille.uwo.ca From: Brent Harding Subject: Re: network configuration problem In-Reply-To: References: <3.0.6.32.20001013132246.007b2100@mail.ufw2.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" List-Id: Cool, which script does stuff like this get added to? I never did get how all that symbolic linking and priority stuff on when to have such things load. I know for some reason debian just won't compile a lot of programs, as the kernel source headers are messed up from most ways other more popular distros like redhat and slackware use. I was thinking of getting a CD of redhat, but where I checked wanted $170.00 for the server version, the only one they sell. 12:41 AM 10/15/00 +1100, you wrote: >Hi: > >If I understand you correctly, you want to be able to listen to shoutcast >servers and windows media servers via IP masquerading. This works >already. Perhaps windows media could work better (I'm not sure), but it >does work. Shoutcast works fine already. Realaudio works better with the >raudio ipmasq module, but it can work without it. A lot of the time, you >can deal with this stuff pretty easily. IP masquerading works fine without >modification for protocols where the replies come back on the same port >number as the requests. This is how IP masquerading works in the first >place. If it comes back on some other port, the firewall has no way of >knowing that that packet is meant for the windows machine. But you can >deal with this. If it's a simple matter of port forwarding, you can use >something like ipmasqadm to do this. Here's a solution I used to enable >buddy phone: > >ipmasqadm portfw -a -P udp -L `ipofif ppp0` 701 -R picard.home 701 > >Can't remember what the -a does, RTFM for ipmasqadm if you want to >know. -p sets the protocol (tcp or udp). -l sets the local IP >address. In this case, I call a neat little script that obtains the IP >address of the specified interface. This is just a shell script that comes >with debian's ipmasq package, so let me know if you want it. -r is the >remote IP address, that is, the machine to which the port should be >forwarded, which is picard.home (the windows machine). The 701 is the port >number. So I'm saying here, please forward all UDP packets received on >port 701 of my PPP0 interface to my windows machine on the same port. > >Geoff. > > >-- Geoff >Shang ICQ number 43634701 > > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >