Gabriel Kerneis wrote:
> Hello,
>
> the following patch upgrades the babel package to 0.97.
>
> Babel has been renamed to babeld since 0.96 [1], but the name has not
> been changed in OpenWRT. The following patch changes every occurrence
> of babel to babeld (this is necessary because upstream c
Gabriel Kerneis wrote:
> Hello,
>
> the following patch fixes the ahcpd package. More precisely, it:
> - upgrades ahcpd to the latest release (0.50),
> - adds librt dependency to the Makefile,
> - removes the installation of the obsolete ahcp-dummy-config.sh file,
> - fixes the ahcpd.init file to
Set a list of addnhosts files.
e.g.
list 'addnhosts' '/var/etc/hosts.olsr'
list 'addnhosts' '/var/etc/hosts.olsrv6'
hosts.olsr for ipv4 and hosts.olsrv6 for ipv6 addresses.
Signed-off-by: Patrick Grimm
Index: package/dnsmasq/files/dnsmasq.init
==
Here's some more info: the diff between dmesgs of release and trunk :
--- release.log 2009-11-21 19:55:12.0 +0200
+++ trunk.log 2009-11-21 19:55:15.0 +0200
@@ -1,5 +1,5 @@
-Linux version 2.6.25.20 (a...@stable-sandbox) (gcc version 4.1.2) #4 Mon Jun 1
23:39:13 UTC 2009
+Linux
ard writes:
> It sounds like the switch in your wrt is configured wrongly.
> Can you try all other ports and see if you still get tagged
> traffic?
wrt54gl v1.1 physical port "Internet"
-
sends dhcp queries and does not reply to arp since it has no IP address.
On Sat, Nov 21, 2009 at 04:01:30PM +0200, Timo Juhani Lindfors wrote:
> but noticed that all arp replies come back prefixed with "vlan 0, p
> 0," according to tcpdump. After some googling I was able to figure
> out that with
It sounds like the switch in your wrt is configured wrongly.
Can you try
Hi,
I have r18259 on WRT54GL. I tried to connect my laptop to it with
ip link set eth0 up
ip addr add 192.168.1.5/24 dev eth0
ping 192.168.1.1
but noticed that all arp replies come back prefixed with "vlan 0, p
0," according to tcpdump. After some googling I was able to figure
out that with
mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I think this feature is incomplete in the current implementation. There
> are some updates in the madwifi-dfs branch on madwifi-project.org, but I
> don't know how reliable the feature is in that branch.
> Unfortunately, I
> don't have the equip
