Hi there,
On the Bering installation guide page:
http://leaf.sourceforge.net/devel/jnilo/bipackages.html
In the pcmcia section, the following link is broken:
http://leaf.sourceforge.net/devel/jnilo/bering/latest/packages/pcmcia_full.lrp
Anyone know where this file exists? If so, does it
contain
Hi David
At 03:15 18.07.2002, you wrote:
Hi. Me again!
By way of a reminder, I am the bloke who has a perfectly functional
Eigerstein box who wants to upgrade to Dachstein or Bering but found
that Dachstein would recognise the NICs and run the tulip driver as
required, find a good 10baseT link
Ok , problem resolved..
It works perfectly with the new packages (bering update, ipsec version 1.98)
The problem is in the config of the interface eth0 (external network)...
under interface config i never set the brodcast address and it seems that
IPsec wants to know the
Hi again
I have setup a new bering box using isdn for external and 3com nic for
internal.
on this box i get the same error as on a adsl box
**console output while trying to restart ipsec**
isdnvpn: -root-
# ipsec setup restart
ipsec_setup: Stopping FreeS/WAN IPsec...
ipsec_setup: stop
Cass,
On the Bering installation guide page:
http://leaf.sourceforge.net/devel/jnilo/bipackages.html
In the pcmcia section, the following link is broken:
http://leaf.sourceforge.net/devel/jnilo/bering/latest/packages/pcmcia_full.lrp
Yeah, I think I noticed this too. At one point or
On 18 Jul 2002 15:18:09 +0200
Ronny Aasen [EMAIL PROTECTED] wrote:
Hi again
I have setup a new bering box using isdn for external and 3com nic for
internal.
on this box i get the same error as on a adsl box
**console output while trying to restart ipsec**
isdnvpn: -root-
#
I have just realised that shorewall is not loading fully. I added the common file to
/etc/shorewall which is part of the three-interfaces files. Now when shorewall is
coming up it stops on:
Adding common files..
:. Can't open /etc/shorewall/common.def
What permissions should
After wrestling with firewall rules and routing tables, I finally
managed to set up Bering with three outbound gateways with multipath
routing, port forwarding to the inside on all three interfaces, and
incoming connections working nicely. So far, it seems to be working OK,
but I've noticed that
Jay Klesitz wrote about [leaf-user] WISP-Dist + Linksys (prism2 )wireless card:
Hello,
The WISP-Dist clearly states it has support for prism2-based wireless cards.
I have a linksys wmp-11 (prism2 based) How do I use this card in WISP??
That's a broad question, so you get a general
Vladimir,
I don't see how its a broad question. I have a linksys WMP-11 wireless card,
it is based on the prism2 chipset. It is a PCI interface.
When the PCMCIA module loads, it loads the i82365.o module. I believe this
is for the orinoco, which I do not have. Where is the prism2.o module? How
On Thu, 18 Jul 2002 10:11:47 CDT Russ Price wrote:
I've noticed that gzip doesn't work as a filter. This
results in /usr/bin/savelog compressing old log files to zero bytes. :-)
Does anyone have a working gzip?
Seems to work okay with the busybox gzip in Bering RC2. (See below.)
What
--- Mark A Nordstrand [EMAIL PROTECTED] wrote:
[snip]
I grabbed pcmcia.lrp and what I needed from:
http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/pcmcia/
Although I've been going through fits with the
wireless card I have, the 3c589 has been working
extremely well on the
Brad Fritz wrote:
Seems to work okay with the busybox gzip in Bering RC2. (See below.)
What version of Bering and busybox (gzip --help) are you using?
# gzip --help
BusyBox v0.60.2 (2002.04.04-20:23+) multi-call binary
I'm using RC3. Here's what I get:
# gzip --help
BusyBox
--- Cass Tolken [EMAIL PROTECTED] wrote:
[snip]
Ah, excellent! I got the 3c589_cs loading but still
having problems with the pcnet_cs card. Time to do
more investigating ;). Thanks, Mark!
Cool, this was a quick one. Taking a clue from the
/etc/pcmcia/config file, it seems that pcnet_cs.o
On Thu, 18 Jul 2002 11:13:48 CDT Russ Price wrote:
Brad Fritz wrote:
I'm using RC3. Here's what I get:
# gzip --help
BusyBox v0.60.3 (2002.06.08-17:56+) multi-call binary
# gzip foo.txt bar.txt.gz
# ls -l bar.txt.gz
-rw-r--r--1 root root0 Jul 18 11:09
On Thu, 2002-07-18 at 08:43, Jay Klesitz wrote:
Vladimir,
I don't see how its a broad question. I have a linksys WMP-11 wireless card,
it is based on the prism2 chipset. It is a PCI interface.
When the PCMCIA module loads, it loads the i82365.o module. I believe this
is for the orinoco,
Hello Marco and all others !
Sure, I am intersted by your script and may be other readers too ;-)
I have few colleagues to connect as this before I start my vacations at
end of this month, and you can help me to win time to do other things.
You are GREAT, thanks in advance.
Best Regards,
Le Jeudi 18 Juillet 2002 18:32, Brad Fritz a écrit :
On Thu, 18 Jul 2002 11:13:48 CDT Russ Price wrote:
Brad Fritz wrote:
I'm using RC3. Here's what I get:
# gzip --help
BusyBox v0.60.3 (2002.06.08-17:56+) multi-call binary
# gzip foo.txt bar.txt.gz
# ls -l bar.txt.gz
Thanks Tom. I did that but it made no difference.
Can you tell me how I can turn Shorewall off? That would prove whether
Shorewall is blocking my DHCP incoming packets, or not.
Thanks.
David Pitts
IT Services Manager
Reid Library
University of Western Australia
Ph: 61 (08) 9380 3492
On Fri, 19 Jul 2002, David Pitts wrote:
Thanks Tom. I did that but it made no difference.
Can you tell me how I can turn Shorewall off? That would prove whether
Shorewall is blocking my DHCP incoming packets, or not.
shorewall clear
-Tom
--
Tom Eastep\ Shorewall - iptables made
20 matches
Mail list logo