> Try this tip clipped from an email to the list in July:
>
> " Try entering a valid command: tc qdisc add dev eth0 root handle 1: htb
> default 30 "
>
> (Courtesy Tom Eastep)
>
> regards,
>
> Mike
>
>
> - Original Message -
> From: "michiel" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
On Wed, 7 Jan 2004 [EMAIL PROTECTED] wrote:
> I realize that this might be a little general, or even a bit
> off-topic, but I figured that there must be SOMEone who has run into
> this problem at least once. I'm currently running
> Bering-uClibc-2.0_rc2 in a single-floppy arrangement, and it's be
Hi,
I tried these steps, and the connection works. I will attach the output from
the ipchains -L FORWARD -v.
What do I need to do next?
Thanks,
Matthew
-Original Message-
From: Huy Bui [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 6:55 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PRO
[EMAIL PROTECTED] wrote:
All,
# uname -a
Linux firewall 2.2.19-3-LEAF-RAID #4 Sat Dec 1 17:27:59 CST 2001 i386
unknown
# ip addr show
1: lo: mtu 3924 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
2: ipsec0: mtu
I'm just getting started with Leaf Bering.
I've built a new 2.4.20 kernel using the woody environment and have
iptables built statically and all is well as far as that goes.
Freeswan is a it of a mystery though. I'm using super-freeswan-1.99.6.2.
Pluto whack and other utilities are linked to
This site has some info on CF and Bering
http://pigtail.net/LRP/hd/index.html
>
> Joe,
>
> Try to check different CF cards.
> It looks like that not all CF cards are created equal. ;-)
> A lot of the CF cards i have tried from smaller OEM manufacturers (i.e not
> Sandisk) do not support the ful
> I am "debugging" a wireless AP router based on Bering 1.2 and
> since there is
> a lot of logging going on, the /var/log runs our of space very fast.
> # df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/root 131072 10040121032 8% /
> tmpfs
In your INPUT chain you have this
152 6372 DENY all l- 0xFF 0x00 eth0
anywhere anywhere n/a
Which mean you deny anything that you don't ACCEPT explicitely on eth0
(which i assume your internet facing nic)
To trouble shoot temporarily flush the INPUT chain with
>I am getting this error on Bering-uClibc 2.0.1 release.
>cp11837-a# tc qdisc add dev eth0 root
>RTNETLINK answers: Invalid argument
>I find in the oficial website:
>http://luxik.cdi.cz/~devik/qos/htb/htbfaq.htm this:
>"RTNETLINK answers: Invalid argument" and tc parameters are correct
There are
It look like IP protocol 47 (GRE) is block on eth0.
How many nic do you have? how do you connect to the internet? ADSL or Cable
modem?
Try this at the command prompt and then try to connect.
ipchains -P INPUT ACCEPT
Check you INPUT and OUTPUT for any DENY
ipchains -L INPUT -v
ipchains -L OUTPUT -v
Am Donnerstag, 8. Januar 2004 09:24 schrieb Neil Schneider:
> I'm trying to follow the instructions at
> http://leaf.sourceforge.net/doc/guide/buc-buildtool.html because I want to
> create a kernel with support for the Hi/fn 7951 card. I'm running into a
> problem because uClib has upgraded the ver
I'm trying to follow the instructions at
http://leaf.sourceforge.net/doc/guide/buc-buildtool.html because I want to
create a kernel with support for the Hi/fn 7951 card. I'm running into a
problem because uClib has upgraded the version number to 0.9.26. and
0.9.20 isn't on the server anymore. "./bu
12 matches
Mail list logo
