Hello!
Wow! Thanks. But Im starting to think that it wasnt the router, but
possibly the AP in between... Im watching this closely, and I will let you
all know how it turns out. After making a switch (of routers) it took
awhile, but it seems like this morning the same thing had recurred, (or so
it seems, but nobody called, so I dont know for sure). Have to wait and
see.
Where can I get that kernel? Ill put it in. and check things out, is there
a way I can get the kernel source too? so I can make custom drivers.
Thanks!!
Jerryf
Jerry,
I am not sure, one thing I know is that the voyage kernel is compiled to
use in-kernel arp cache. There is the kernel option to enlarge the arp
cache and to use userland arpd daemon to manage arp things.
I am not very good at router level, are you sure the problem is on arp
side? If so, I can built a custom kernel for you to test.
Punky
Jerry wrote:
Hello!
I recently put Voyage on a wrap board which I put in use as a router
(feed) for a wireless network. The wireless interface (2511mp) was as a
client, using an AP1000 as the broadcast. The device was doing routing
not nat, and the performance (speed/bandwidth) was good, and the
stability was good too.
The problems I had was with arp and/or dhcpd. I know that it comes with
'dnsmask' installed, but in my testing, a client behind a CB3 wouldnt get
an IP using dnsmask, so I used a statically compiled dhcpd binary which I
had been using in several other places (in wisp-dist) with great success.
Well, it worked, at first... after a day or two dhcpd would crash, and
the only way to make things work "correctly" was to restart the machine,
this was a temprorary solution, as by the next day (or less) the support
calls would return.
I believe the problem is arp, in that 'arp-a' would show the CB3 mac and
not the device behind it (im convinced it had something to do with this).
The CB3s were mostly default settings (I didnt give any special addresses
to them, just left them at default IP address, 192.168.1.1). If I gave a
local (192.168.1.13) secondary address to the wrap, I could NOT ping
192.168.1.1 at all. In all my other places 192.168.1.1 would respond,
and after replacing the wrap with a wisp-dist device, it would too.
I was really excited about voyage, as it has the features I have been
wanting in a device, and is tuned to the wrap boards. But alas I cannot
use it if it acts this way. Im really not sure what the problem is
directly, but I am convinced it has something to do with arp (or lack
thereof). Has anyone else had issues like this? I could accept the
issues better if this was a big pop, but there was maybe 10 customers at
the most, and it couldnt handle that. :(
any ideas?
Thanks
rryf ------------------------------------------------------------------------
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
--
Regards,
Punky
P U N K N ! X . c o m
Technology + Lifestyle
(http://www.punknix.com)
Voyage Linux
(http://www.voyage.hk/software/voyage.html)
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
