mozilla package dumps core

Anyone noticed the mozilla-0.8.1 package core dumping on 4.2-RELEASE and have a fix for it? Here's the gdb output: Program received signal SIGSEGV, Segmentation fault. 0x48158f9a in nsThreadPoolRunnable::Run () from /usr/X11R6/lib/mozilla/./libxpcom.so cheers, -Ian -- Ian Kallen &l

Re: accessing an outside IP from inside a NAT net

e internal net should be in the example rc.firewall and/or in the /usr/share/examples/etc examples. cheers, -Ian -- Ian Kallen <[EMAIL PROTECTED]> | AIM: iankallen | efax: (415) 354-3326 On Fri, 19 Jan 2001, Ian Kallen wrote: > > I'd like a hand figuring out how to access res

Re: accessing an outside IP from inside a NAT net

pass all from any to any So if you can suss the incantation that allows 10.0.0.0/25 hosts to access 10.0.0.130 via 206.169.18.10, I think I'd be all set! thanks, -Ian -- Ian Kallen <[EMAIL PROTECTED]> | AIM: iankallen | efax: (415) 354-3326 On Sat, 20 Jan 2001, Nick Rogness wrote: &

Re: accessing an outside IP from inside a NAT net

ve been reading the ipfw man page and the archives, yet even though the two nets can access each other directly, I haven't been able to get the clients to access any server resources via the 206.169.18.10 nat. Further suggestions? thanks, -Ian -- Ian Kallen <[EMAIL PROTECTED]> | AIM: i

Re: accessing an outside IP from inside a NAT net

clients all have proper subnetmasks, so they shouldn't be talking to each other directly but only through the router/natd machine. Any other ideas? thanks, -Ian -- Ian Kallen <[EMAIL PROTECTED]> | AIM: iankallen | efax: (415) 354-3326 On Fri, 19 Jan 2001, Gordon Tetlow wrote: > On Fr

accessing an outside IP from inside a NAT net

the connction never succeeds). Is there a nice way to handle this case without running a dummy DNS just for the 10.0.0.0 internal net? thanks, -Ian -- Ian Kallen <[EMAIL PROTECTED]> | AIM: iankallen | efax: (415) 354-3326 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscri