rc.firewall example?
arnee wrote:
> I have been wondering what the right answer to this scenario is. Here is
> the scenario:
>
> machine A -- outside ip (internet)
> machine B -- router, natd, registered ip and set to stop RFC1918 on the
> public interface
> machine C --
gistered ips? I would think that it would be aliased to like
this, "machine B's ip" --> machine C's ip" like a proxy? But this
would still break the rule "... from any ...".
2. If so, is it correct to not include the ipfw rule above when stopping
RFC1918? B
Bill Paul wrote:
> Of all the gin joints in all the towns in all the world, arnee had to walk
> into mine and say:
hehehhe... Oh no!! What did I walk into... a quicksand! :-)
> Ack...
> No, please...
> Stop, you're killing me...
> Aie!
>
> Oh for the love of
cause this isn't really in my court any more but maybe
> someone else in -current has some ideas.
>
> -Matt
> Matthew Dillon
> <[EMAIL PROTECTED]>
Thanks for the he
re of what is going on... but I now suspect, like what matt has mentioned, that
neither samba nor nfs are at fault. I simply have to do more experimenting and
running the system without the ultra66 controller.
arnee
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
afternoon, hoping things work, and yes I will add DEBUG-g option
next time I compile the kernel :-). Also, please let me know if I am writing any
redundant infos or if I should include any other infos from kgdb when posting a
panic message. Sorry for the ignorance but I am still familiarizing with how
thi
thing less than 15mgs.
System:
pcchips m571 with cyrix 6x86
promise ultra66
Anyone interested in more info let me know. Plus, is this kind of thread
encourage in this list? I'm simply wondering if this would help,
otherwise i could just follow cvs and hope things will work.
arnee
To U
