[braveheart]

Having a little trouble getting my aDSL connection to IPshare with my airport network. I FINALLY become available for DSL in my area (long story), so when I have my G4 Tower (origional 500) connected, i sometimes need to IP-share it with my G4PB. Not often but just enough for this to matter.

my DSL connects via PPPoE and I run the following script on startup:
#!/bin/sh
/usr/sbin/natd -dynamic -interface en0
/sbin/ipfw -f flush
/sbin/ipfw add divert natd all from any to any via en0
/sbin/ipfw add pass all from any to any

i changed my /etc/hostconfig file so that IPFORWARDING=-YES-

My network control panel (or whatever you call it in 10) connects by the built in ethernet via pppoe...and my Airport is set up with:
IP 10.0.1.1
Subnet 255.255.255.0
the rest is blank

my PB TCP is set up with Airport:
IP 10.0.1.2
subnet 255.255.255.0
gateway 10.0.1.1
DNS as my server DNS

when I ping the PB all is well, but can not surf
what step did I miss?

thanks for the help...good luck interpreting all this

PS: I KNOW i can't spell hehe

[nonhuman]

Maybe you did this and just forgot to mention it but...

You need to create a Computer to computer network and have both of your comps connected to it.

[braveheart]

yeah...in the mass long typing i forgot it. but yes I do have a comp to comp network set up. And yes, I can transfer files between the two, so I know it's not that. But I turn appletalk off when I'm tring the IPsharing.

[nonhuman]

When you say you have the script run on startup do you mean you made it into a startup item, or you manually run it on startup? If the first (how do you do that, I haven't figured it out yet) then have you tried re-running the script? I'm have essentially the same setup, and I find that this usually solves whatever problem I'm having (although not the one I'm having at the moment where I can't even ping my other comp...).

[theonlyfrizzo]

maybe instead of having a script run at startup you could try one of the utilities that you could get off of versiontracker.com. I know I looked at one once called gNAT. It might help share your connection better. Also, do you have a cisco router? 675 or 678? because if you do, your cisco can actually serve out DHCP and you wouldn't need to worry about NAT from a system point of view. I even know a way to run DHCP and static IPs side by side with the Cisco routers. So if you need some help with that, please let me know, I can tell you how it's done.

[schwa]

An alternate, easier (IMHO) solution: geeRoute.
<http://www.versiontracker.com/moreinfo.fcgi?id=11908&db=mac>

I installed it on my G4 after my hardware router died, and I needed to get my Beige G3 on the net (I only have 1 IP address). It's a free tool that's easy to install and configure. I haven't had any problems with it.

I don't use PPoE, but I think it should still work on your system. It's just a software-based DHCP router.

[braveheart]

Thanks for the ideas. I'll check them out when I get home (at work at the moment). And I'll keep you guys posted


nonhuman: I got my idea from
http://homepage.mac.com/gdif/masqfirewall.html with no joy. sure hope I imbedded that URL right.

theonlyfrizzo: i've thought about just using a hardware router, but wouldn't be worth my money, since this is only for when my tower is in use.

schwa: haven't tried that app yet, i'll let you know.

for tor all the help!!

[braveheart]

ok guys...had a chance to check out geeRouter again with no joy.

any more ideas? anybody care to contact me and we can work this out step by step, maybe I missed something really simple. which i'm famous for forgetting.

Again, I thank you all for all the help, it means a lot

[theonlyfrizzo]

I would do a search in the OS X forums, it seems to me after looking at your script that it seems considerably short. When I was looking for info on NAT on this forum there was a HUGE post about NAT and DHCP a number of months ago, and the script he had was a lot bigger...oh wait, I think I actually copied it...let me see and paste it in:

<font color = red>
#!/bin/sh

. /etc/rc.common

# name the appropriate variables for your set-up
INTERFACE=en0
IPFW=/sbin/ipfw
NATD=/usr/sbin/natd
NETMASK=255.255.255.252
DHCP=yes # "yes" or "no"

# arbitrary IP for router...client TCP settings will have to be on the
# same subnet. I put "81" in there at random...you can choose your own
# value
ROUTER=209.98.10.222

# starting up the NAT daemon
ConsoleMessage "Configuring NAT daemon"

# starting natd
if [ ${DHCP} = yes ]; then ${NATD} -dynamic -interface ${INTERFACE}; fi
if [ ${DHCP} = no ]; then ${NATD} -interface ${INTERFACE}; fi

# setting up ipfw to use natd
${IPFW} -f flush
${IPFW} add divert natd all from any to any via ${INTERFACE}
${IPFW} add pass all from any to any

# set up the correct addresses to listen to
ifconfig en0 inet ${ROUTER} netmask ${NETMASK} alias
</font>

This was taken directly from that post...if you need explanation you will probably have to search for the original post as I have had a little trouble interpreting this. Also, I have a .tar file called NAT that I got form somewhere and would be able to email it to you to see if it would help. Just let me know. Hopefully this gives you some new insight!!! Good Luck

P.S. It seems to me after looking back at my post that you might be missing the last command line. That might be a good place to start...again...Good Luck.

[ 10-17-2001: Message edited by: theonlyfrizzo ]

[ 10-17-2001: Message edited by: theonlyfrizzo ]

[ 10-17-2001: Message edited by: theonlyfrizzo ]

[Chris Toppan]

I was having the same problem as Braveheart. What I did instead of changing the IPFORWARDING statement in /etc/hostconfig was to add <font color = red> sysctl -w net.inet.ip.forwarding=1</font> to the begining of my script to enable nat and ipfw. I got all the syntax/commands from the man page on natd for my script. Here is what my nat script looks like:

<font color = red>
#!/bin/sh
sysctl -w net.inet.ip.forwarding=1
/usr/sbin/natd -dynamic -interface ppp0
/sbin/ipfw -f flush
/sbin/ipfw add divert natd all from any to any via ppp0
/sbin/ipfw add pass all from any to any
</font>

I am not sure why setting IPFORWARDING to YES in /etc/hostconfig did not work while adding sysctl -w net.inet.ip.forwarding=1 to my script worked.

The one thing I had to do after changing IPFORWARDING to NO was to turn off my Built-in Ethernet port via the Network panel, apply the changes, then turn it back on. But after that I was able to restart my computer, launch a terminal, type sudo -s NATd, then my password and NAT was up and running and my Windows machine had Internet access.

[braveheart]

ok, i'm back at this..yet again.
I'm starting over from scratch. have reset /etc/hostconfig IPFORWARD -NO-

am using gNAT with no joy currently
here is my gNAT config:
Subnet Mask: 255.255.255.0
Router Address: 10.0.1.1
Preserve Ports: Yes
Use Sockets: Yes
Create Aliasing Log: Yes
Deny Incoming Requests: No
Create Denial Log: No
External Interface: Ethernet Card
Internal Interface: Airport Card
Dynamic IP Binding: Yes
Local Caching Name Server: Yes

On this host comp in NETWORK under airport
Configure: Manually
IP Address: 10.0.1.1
Subnet: 255.255.255.0
Router: BLANK
DNS: BLANK

On the PB in NETWORK under airport
Configure: Manually
IP Address: 10.0.1.2
Subnet: 255.255.255.0
Router: 10.0.1.1
DNS: 10.0.1.1

they are in a comp to comp airport network, appletake does work between them, but is OFF when i try for TCP

help me......please

thanks

PS: when filesharing the HOST over TCP, can see 3 possable IP's. just saw this not 2 mins ago

[ 10-21-2001: Message edited by: braveheart ]

[Brazuca]

I have almost the same setup as you do, except that my dsl has a fixed IP, so I don't have to "dial" it with PPPoe.

I did basically what you did in the beginning, and I couldn't surf from the PB with airport. I don't remember if I could share files or not.

I finally noticed one things that fixed my problems. My firewall was blocking the ip traffic. I simply opened Brickhouse and set it to allow the PB to lookup an address and other minor stuff. I don't remember exactly and I'm not in front of it now (I'm actually writting this on the PB )

Take a look at your firewall if you haven't done so already.

[braveheart]

I know I was playing with brickhouse as the first app I tried to work this, and I thought I opened it up before I dumped it, just trying to get Sharing to work. So i'm all but 100% sure that my firewall is open (yeah i know, bad idea). So I don't think that's it. But I'll give it a looky and see.

Anybody who wants a set up an e-mail correspondence is more than welcome.

[braveheart]

well my firewall is open, that I can be sure of. Installed Brickhouse...all rules are off. Still nothing. Installed Firewalk, again opened the firewall, and not sharing IP's.

ARGGGGGG. so close....yet so very far

i know it's got to be something so simple...and i'll hate myself for it when i find out

[braveheart]

anybody have any ideas....I'm still stuck at this. I hate to be pushy
If anybody has anyideas PLEASE shoot them my way.

sorry to be a pain, but I am honestly out of ideas

[braveheart]

FINALY got it up and running. The new version works. beta #9 i think.