[Tyler McAdams]

Is there a way to route file sharing exclusively through firewire and turn off file sharing on the nics?

[P]

You could configure the firewall to disable those ports for the NICs while leaving them open for firewire. Brickhouse can do it, but it's working so-so on Tiger (at least for me) so if you've got Tiger you could be forced to edit the ruleset manually. Probably best to take questions related to that to either the Networking or UNIX fora if you have problems.

[Tyler McAdams]

P! Happy Holidays! I have not seen you around much Anyway, I'm looking for a way to disable the *service* on the interface... not just block it. This can be done in Xp by click on the properties menu on the interface and unchecking file sharing on that nic. There should be some way to do this... but i can't find it on OS X.

[P]

Oh, I'm around. I don't always post so much, because I work a lot at the moment and it's hard to find the time. I do check in to read reasonably often, though, when I need a break from work. I don't want to hide completely.

You'd think that it would be easy to make the service listen only on one network interface, right? Well, the setup doesn't seem to work like that - it assumes that you control this in the firewall. But what is wrong with just blocking incoming 548/tcp on that interface?

[Tyler McAdams]

Nothing really... it's jsut a less elegant way to create the same solution. I was just hoping for a way to do it more "correctly". Correctly meaning that if you don't need the service on that port I feel there should be a way to cut it off... especially on a server where you have more than 1 or 2 nics.

[P]

I don't really think that there is a difference in this case. The only case where it would be relevant is if you want to run something else on port 548 on one NIC, and this case, correctly is in the eyes of the beholder...

Happy holidays, Tyler.