l interface
natdport1=8668 # port to use for nat on first interface
natdport2=8669 # port to use for nat on second interface
natd -port ${natdport1} -interface ${oif1} -f /etc/natd1.conf
natd -port ${natdport2} -interface ${oif2} -f /etc/natd2.conf
----
I hope this work out.
en it
should be safe (and correct I think) to add the -unregistered_only argument
to both of the natd commands above.
Please let me know how it goes....
Regards,
Patrick O'Reilly
---
"I do not feel obliged to believe that the same God who has endowed us with
sense, reason, and intellect h
Hi all!
I need to allow some M$ clients to access M$ shares on an NT server, the
clients and server being on opposite sides of a FreeBSD ipfw firewall. The
firewall is running fine (has been for 6 months) but I cannot get this D**N
Netbios stuff going.
In my desperation I have gone as far as ad
FIXED !!!
Thanks to you all (Bill, Blair and Johnny) for your help.
It turns out the problem was not at the transport level at all (seriously
red face now!)
The login and password was the issue - Since the clients and server are not
on the same windows NT domain, the NT server was validating th
Peter,
> My question is, why didn't routed or something figure this out on its own?
What? These are just computers, remember? Computers have a nasty habit of
doing what we tell them to do, not what we want them to do!
;-)
Seriously though, You do need to tell the firewall/nat box about the
1
the least.
So: is there anyone with any bright ideas for me whereby I can put voice
over IP, but still use FreeBSD for routing, and avoid buying those horribly
expensive router-based alternatives?
Thanks,
Patrick O'Reilly.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
