At 12:32 AM 12/27/02 -0500, Omar D. Samuels wrote:
Hey all. Just setting up a LEAF box at home from scratch with my new
fixed wireless connection. For some strange reason I'm doing what I
always do same hardware and it just doesnt seem to work.
I was wondering... would the fact that by default
On Fri, 27 Dec 2002, Omar D. Samuels wrote:
> Hey all. Just setting up a LEAF box at home from scratch with my new
> fixed wireless connection. For some strange reason I'm doing what I
> always do same hardware and it just doesnt seem to work.
>
> I was wondering... would the fact that by def
Hey all. Just setting up a LEAF box at home from scratch with my new
fixed wireless connection. For some strange reason I'm doing what I
always do same hardware and it just doesnt seem to work.
I was wondering... would the fact that by default the internal network
is 192.168.1.x and my broadb
--On Thursday, December 26, 2002 5:22 PM -0800 Scott <[EMAIL PROTECTED]>
wrote:
Hi,
I have bering 1.0 firewall and I can't forward port 23 and 21 to a server
inside my network. I can connect internally on the network, so I'm sure
it's something with the firewall. I have no problem forwarding
Hi,
I have bering 1.0 firewall and I can't forward port 23 and 21 to a
server inside my network. I can connect internally on the network, so
I'm sure it's something with the firewall. I have no problem forwarding
a bunch of other ports (not sure of my method, but it's working):
/etc/shorewal
Lynn,
Thanks for weighing in on this. Unchecking the autodetect had no effect.
it seems some URLs are not a problem so I am getting used to checking my
mail pop prior to browsing and by the time I finish the mail the
browsers
work fine. I see some mention of appending dns suffixes in the TCP setup
Mike Hahn wrote about "RE: [Re: [leaf-user] Leaf wired<->wireless bridging. Is it
possible?]":
> Sure thing, I'll send the file up there today. I'll also try to roll it up
> into a .lrp file.
>
> It seems to report error messages when running /sbin/ip on the bering, saying
> the call was unsuc
Sure thing, I'll send the file up there today. I'll also try to roll it up
into a .lrp file.
It seems to report error messages when running /sbin/ip on the bering, saying
the call was unsuccessful. Regardless, the calls do succeed.
I'll also post the diffs so that parprouted can be built under
Hey all.
Thanks for a GREAT AND EASY PRODUCT with the Dachstein-CD Image! I have
an old Dell Optiplex GXL 5166 (486 DX2 66 with 32MB RAM and onboard NIC
(3Com 509c series) and Netgear FX310TX (PCI running with Tulip module).
I was really able to get this thing up and running in only a couple
hour
I eventually sorted out connecting Cisco VPN Client v3.6.1 (on Win98) to my
company VPN server via Dachstein. (The client is configured to use UDP, not
TCP).
I tried connecting with a direct connection to my cable modem, and realised
I was using the wrong ***£*"^+$** username - once I corrected th
10 matches
Mail list logo
