Wireless - Was [Re: DSL]

[John Dangler]

On Mon, 2007-02-12 at 03:22 -0500, Matthew Flaschen wrote:
> John Dangler wrote:
> > On Mon, 2007-02-12 at 02:28 -0500, Matthew Flaschen wrote:
> >> John Dangler wrote:
> >>> -----------------
> >>> wireless config in System ->Networks:
> >>> (profile = office_wireless, which is eth0: inactive, eth1: active)
> >>>
> >>> Network Name: (ESSID): mgj_ventures
> >>> Key type: Hexadecimal
> >>> WEP Key:
> >>>
> >>> Connection Settings:
> >>> Configuration: Static IP Address
> >>> IP Address: 192.168.2.38
> >>> Subnet mask: 255.255.255.0
> >>> Gateway address: 192.168.2.1
> >>>
> >>> DSL Modem IP: 192.168.1.1
> >>> Router IP: 192.168.1.2
> >>> Wireless Router IP: 102.168.2.1
> >>>
> >>> The Router is enabled for Static IP addresses (I have an XP box with a
> >>> USB54G adapter that works fine, and is on static)
> >> That network's weird, I think.  You have a static IP of 192.168.2.38,
> >> and a subnet of 255.255.255.0 .  All good so far.  But then you say your
> >> wireless router has an IP of 102.168.2.1 .  Is that a typo, because
> >> that's not a standard internal address?  Anyway, your gateway address
> >> should match the wireless router IP.  If that really is your wireless
> >> router address, I think you should change the static IP to 102.168.2.38
> >> and the gateway to 102.168.2.1 .
> > Why 102?  The internal net is 192...
> 
> I know!  Your original posting has 102, which is what bewilders me.  I
> was recommending changes to make your network consistent (if strange and
> possibly vulnerable).
wow.. sorry about that... i must have fat-fingered the number... it's
definitely 192.
> >> Apparently:
> >>
> >> iwconfig eth1 essid mgj_ventures channel 6 key BADF00D
> >>
> >> (BADFOOD should be replaced with your key) does it though.
> > 
> > iwconfig eth1 essid mgj_ventures channel 6 - returns
> > Error for wireless request "Set Frequency (8B04)L
> > SET failed on device eth1; Operation not supported
> 
> I believe that's a limitation of the card or driver.  The man page says
> "All these parameters and statistics are device dependent. Each driver
> will provide only some of them depending on hardware support, and the
> range of values may change."
yikes!  I'll have to see if I can, in fact, change that channel with
ipw2100... If not, I'm doomed to only DHCP for wireless on this laptop.
So, the next step would be figuring out if I can setup my router to
handle both IP and dhcp at the same time (I saw some info somewhere on
the net to that effect, but my strong suit is application and database
architecture/design/development, not networking)...
> 
> Matthew Flaschen
>