In the Ap manager, the signal level is about 55-60%
In the wisp, thats the output of iwconfig:
netcs0IEEE 802.11-DS ESSID:ESSID Nickname:NICK
Mode:Managed Frequency:2.462GHz Access Point: 00:02:2D:XX:XX:XX
Bit Rate:1Mb/s Tx-Power=15 dBm Sensitivity:1/3
I am using a linux rescue disk to copy over a bering distribution to the
disk-on-chip device.
Both the fdisk utility and syslinux seem to recognize /dev/hda1 as the IDE
drive.
Any way, I'll try to create a bering disk for which I have incorporated the
ide drivers into initrd.lrp. I didn't do
On Monday 02 June 2003 02:03 pm, Steve Wright wrote:
Gurus,
I have built a script that configures iproute2 on my LEAF box. I tried
placing this script in /etc/network/if-up.d/ and then backing up - which
saves my script quite nicely.
When I restart networking from the menu I notice this
Does anyone know if the latest stable bering release has a module to
handle this piece of hardware. If there is no module for it in the
default modules directory, has anyone tried to implement this piece of
hardware and if so how?
Here is the link to the hardware that I am trying to get up and
I made more tests here, and i find one thing strange! When the wisp-dist is sending a
file in direction of ap1000 (To a station behind the ap1000), the signal in AP Manager
goes to 40%, and i get some packet loss, when i stop the transmission, the signal back
to 60%!
In the other station if i
Hi Marc
Marc E. Fiuczynski wrote the following at 19:27 03.06.2003:
I am using a linux rescue disk to copy over a bering distribution to the
disk-on-chip device.
If the system reconizes the disk as an IDE device, I would believe it. Some
time ago I had difficulties running syslinux on my bering
On Saturday 31 May 2003 11:35 am, Fisher, Brian wrote:
I am currently trying to setup a VPN via pptp. My understanding is that I
need to do three things on my Dachstein firewall first. They are: 1) load
the ip_masq_pptp module
2) open protocol 47
3) open port 1723
You don't need to load
First of all let me apologize for double posting on the same issue.
I just picked up 10 Iwill G300 Security systems. Nine of them have the
Broadcom BCM5802 Macro Processor built in, and the other one (which my
boss is looking at really hard as our new hardware platform for the LVS
cluster) has
sigh this isn't working. What am I missing ?
# grep pppd /var/log/messages
[...]
pppd[2591]: Couldn't set tty to PPP discipline: Invalid argument
Kernel mode doesn't work. ppp_deflate won't load.
wisprouter: -root-
# modprobe ppp_deflate
insmod: /lib/modules/2.4.20: No such file or directory
On Tuesday 03 June 2003 09:18 pm, Steve Wright wrote:
sigh this isn't working. What am I missing ?
[...]
wisprouter: -root-
# modprobe ppp_deflate
insmod: /lib/modules/2.4.20: No such file or directory
Using /modules/ppp_deflate.o
insmod: unresolved symbol zlib_deflateInit2_
insmod:
On Monday 02 June 2003 08:02 pm, Nicolas Riendeau wrote:
I was wondering if there is any known issues in Bering (V1.1) and/or the
Shorewall that came with (1.3.?) that might cause it to temporarily stop
forwarding a port...
Not that I am aware of.
--
~Lynn Avants
Linux Embedded Appliance
On Wednesday 28 May 2003 06:37 pm, Steve Wright wrote:
Heyas All,
fishing
Anyone else out there thinking about LEAF, IPV6, bigger networks, and
policy routing ?
/fishing
I belive someone got a LEAF ipv6 box up and running after jumping through
many hoops. LEAF is running on several very
On Tuesday 03 June 2003 02:05 pm, Charles Holbrook wrote:
Does anyone know if the latest stable bering release has a module to
handle this piece of hardware. If there is no module for it in the
default modules directory, has anyone tried to implement this piece of
hardware and if so how?
I
On Tue, 3 Jun 2003, Lynn Avants wrote:
On Monday 02 June 2003 08:02 pm, Nicolas Riendeau wrote:
I was wondering if there is any known issues in Bering (V1.1) and/or the
Shorewall that came with (1.3.?) that might cause it to temporarily stop
forwarding a port...
Not that I am aware of.
Le Mercredi 4 Juin 2003 03:59, Lynn Avants a écrit :
On Tuesday 03 June 2003 09:18 pm, Steve Wright wrote:
sigh this isn't working. What am I missing ?
[...]
wisprouter: -root-
# modprobe ppp_deflate
insmod: /lib/modules/2.4.20: No such file or directory
Using
From [EMAIL PROTECTED] Tue Jun 3 23:06:08 2003
Date: Wed, 04 Jun 2003 09:05:59 +1200
From: Steve Wright [EMAIL PROTECTED]
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
X-Accept-Language: en-us, en
To: Erich Titl [EMAIL PROTECTED]
Subject: Re: [leaf-user] syslinux
Charles,
On the basis that there is some distance involved ; (an assumption)
My understanding is that some of the cheaper (dlink in particular)
wireless gear has 'timing issues' when the A/Ps are physically far apart.
In the extreme, you will have to go to a proprietry fix, viz turbocell,
or
17 matches
Mail list logo
