[MLB-WIRELESS] Minitar Problem......try again?

[Steven Haigh]

The default netmask of your minitar will probably be 255.255.255.0 - which
means it's sending out data to the default gateway if you're not in it's
subnet (apparently 192.168.2.x).

Change your PCs IP to somewhere in the 192.168.2.x range, and it should
work. 


--
Steven Haigh

Email: netwiz at crc.id.au
Phone: (03) 9909 0493 - 0412 935 897

-----Original Message-----
From: owner-melbwireless at wireless.org.au
[mailto:owner-melbwireless at wireless.org.au] On Behalf Of Mark Aitken
Sent: Wednesday, 16 March 2005 5:31 PM
To: David Ashburner
Cc: melbwireless at wireless.org.au
Subject: Re: [MLB-WIRELESS] Minitar Problem......try again?

Hi i David & others.

My windows box has 192.168.0.11 (netmask 255.255.0.0) which covers the
eventuality of a 192 168.2.1 address requiring access from it.

I have tried everything I can think of, the console sessin maybe my last
hope as re-configuring the minitar mod.  Not sure on the version, didnt take
note initally, now can get access to find out.  The wierd thing is that the
Minitar has performed faultlessly as my in-house AP for about a year now.  I
only turned it off a few weeks ago to play with the senaio I got, oh well,
dems der breaks.

Thanks for your assistance. 

Regards

Mark



David Ashburner wrote:

>
>> From: Mark Aitken <vk3jma at wia.org.au>
>
>
>>> I had a similiar thing happen and gateway setting seemed to fix it. 
>>> ie set the machine youre using to http into the AP to use the ap as 
>>> the gateway.
>>>
>>
>> How do I accomplish this?  I do not know the ip address of the 
>> AP.........this is my problem.
>>
>
> If you have now  reset the Minitar to factory defaults then you should 
> be able to get to it on 192.168.2.1 . I think Horace is suggesting 
> that the machine you are running the browser on may be multi-homed, in 
> which case if it does not have an explicit route for 192.168.2.0 it 
> will send packets down the interface with the default route.  Check 
> the routing table, if you have no entry for 192.168.2.0 and the 
> Minitar is not on the same  interface as "default" then  it's not 
> getting the requests.
>
> You can add a route for the minitar: route  add -host 192.168.2.1 
> netmask 255.255.255.0 eth0 replace eth0 with the interface you have it 
> connected to.
>
> Just a guess. If you add a serial port you are going directly to the 
> console and it will work regardless of the network interface running 
> or not. The problem with the console is that unless you  relitively 
> old firmware (like 2.32) the console password is unknown. There is a 
> hack - check the Minitar mods forum.
>
>
>
> To unsubscribe: send mail to majordomo at wireless.org.au with 
> "unsubscribe melbwireless" in the body of the message
>
>
>



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.7.3 - Release Date: 15/03/2005


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message