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

[David Ashburner]

>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