Re: [CUWiN] N00b Question

On Fri, Aug 10, 2007 at 04:35:58PM -0500, Jef Green wrote:
> ----- Original Message ----- 
> From: "David Young" <[email protected]>
> To: "Jef Green" <[email protected]>
> Cc: <[email protected]>; <[email protected]>; 
> <[email protected]>
> 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
> >[email protected]      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.
> 
> 
> We changed to KornShell, BTW.
> 
> RADIO1 (CORE):
> ethip
> #!/bin/ksh
> if [[ $1 == "ath1" ]]; then echo 10.41.1.254/24; fi
> if [[ $1 == "sip0" ]]; then echo 10.10.104.254/24; fi
> 
> wlanip
> #!/bin/ksh
> if [[ $1 == "ath0" ]]; then echo 10.41.0.1/32; fi
> if [[ $1 == "-a" ]]; then echo 10.41.0.1; fi
> if [[ $1 == "-n" ]]; then echo /32; fi
> 
> RADIO2:
> ethip
> #!/bin/ksh
> if [[ $1 == "ath1" ]]; then echo 10.41.2.254/24; fi
> if [[ $1 == "sip0" ]]; then echo 10.10.104.254/24; fi
> 
> wlanip
> #!/bin/ksh
> if [[ $1 == "ath0" ]]; then echo 10.41.0.2/32; fi
> if [[ $1 == "-a" ]]; then echo 10.41.0.2; fi
> if [[ $1 == "-n" ]]; then echo /32; fi 

Have you assigned the same IP number to sip0 on both radios?  That will
cause problems.

Can 10.41.1.253 ping 10.41.2.253, and vice versa?

Dave

-- 
David Young             OJC Technologies
[email protected]      Urbana, IL * (217) 278-3933 ext 24
_______________________________________________
CU-Wireless mailing list
[email protected]
http://lists.chambana.net/cgi-bin/listinfo/cu-wireless
Project Page: http://cuwireless.ucimc.org