[CUWiN] N00b Question
David Young
dyoung at pobox.com
Mon Aug 27 12:30:59 CDT 2007
On Sun, Aug 12, 2007 at 10:54:56PM -0500, David Young wrote:
> On Fri, Aug 10, 2007 at 04:35:58PM -0500, Jef Green wrote:
> > ----- Original Message -----
> > From: "David Young" <dyoung at pobox.com>
> > To: "Jef Green" <jefg at onshore.com>
> > Cc: <cu-wireless at lists.cuwireless.net>; <ryant at onshore.com>;
> > <stel at onshore.com>
> > Sent: Monday, August 06, 2007 11:48 AM
> > Subject: Re: [CUWiN] N00b Question
> >
> >
> > >On Mon, Aug 06, 2007 at 11:36:14AM -0500, Jef Green wrote:
> > >>Thanks for the reply, David.
> > >>
> > >>The other question I had was whether or not it is feasible to change the
> > >>private address subnets the radios will be using for user space/dhcp. We
> > >>have a rather large set of private NAT'd subnets internally already, and
> > >>I'd like to have the CuWin radios conform if possible. This way if we
> > >>wanted to use a common NAT router, their would be no overlap. We tried
> > >>changing subnet declarations in the config files and even tried disabling
> > >>ethip in the interface config files, but the radios rebooted with no
> > >>address instead of the addresses we had declared. Possibly their is an
> > >>easier solution for this as well. It seems the software is designed to
> > >>automatically choose IPs/subnetting based on MACs of the radios, but I'd
> > >>like to know if I can control or disable this function (within reason).
> > >
> > >I have never set up a node that way, myself. Give me some details about
> > >how you configured the node, and I will try to figure out what's gone
> > >wrong in the CUWiNware.
> > >
> > >Dave
> > >
> > >--
> > >David Young OJC Technologies
> > >dyoung at ojctech.com Urbana, IL * (217) 278-3933 ext 24
> > >
> >
> > David,
> > We finally got the desired IPs/design to stick after reboot. We
> > basically changed the ethip and wlanip to short scripts on each radio
> > (currently two radios for testing). The scripts return the desired IP info
> > when called. This seems an easier solution than bypassing ethip/wlanip
> > alltogether. The only problem we're having now is that packets headed for
> > the gateway stop at radio1(core radio) and are not routed out. You can
> > ping all radio1 interface IPs from your laptop while associated to radio2,
> > but no where beyond radio1. If the same laptop associates w/ radio1, it
> > gets out fine. Looks like we're missing something here. Attached is a
> > network a simple design layout. I pasted copies of the replacement dummy
> > scripts below.
>
> BTW, the reason your desired IPs did not stick was that the files
> /etc/ifconfig.* do not use the configuration stored in /etc/cuw_config,
> but they use wlanip, et cetera, instead. A template such as
> /etc/ifconfig.ap.tmpl ought to have lines like
>
> inet alias $(/sbin/get_config_val $int ipv4_address)
>
> instead of
>
> inet alias $(/sbin/ethip $int)
>
> as it has, now. I haven't made the change and tested it, myself.
I have made this change in the source, now. I have not tested with a
custom config, but I don't see any regression with a default config.
See if you can set custom IPs and netmasks by adding to /etc/cuw_config,
for example,
if_ath0_ipv4_address=10.0.1.2
if_ath0_ipv4_netmask=255.255.0.0
Dave
--
David Young OJC Technologies
dyoung at ojctech.com Urbana, IL * (217) 278-3933 ext 24
More information about the CU-Wireless
mailing list