MiamiDX and Airport Base

[bbond007]

I knew that every device on the network needs to have a unique IP address but I believed that you have to use the same IP address that the Router assign to your device otherwise it will not work.
Anyway I tried using IP 192.168.1.200 and it didn't work too

ok, thats good... now that you have assigned a static IP, try and issue the command

ping 192.168.1.1 (or whatever your router is)

if you get a response then you'll need to also manually set your DNS to your router, or openDNS 8.8.8.8 (i think) and you are good to go...

If you don't get a response (and you have done everything correctly) then I guess you'll need to get a different router because nobody is going to fix MIAMI's flaky DHCP at this point....

good luck

[bbond007]

I'm not that Dumb.

Nobody is saying you are... you see a little defensive.

Do you know how many times people come in here and have a problem with HD toolbox not saving the max transfer or something because they simply neglected to press ENTER before saving? Its just checking the obvious stuff first.

[bbond007]

oops double posted...

[bbond007]

I think you should be able to use static ip for amiga. Even if DHCP is enabled on router. Give Amiga an IP address that is outside of routers IP pool (not sure if absolutely necessary), but on the same subnet. Use same subnet mask and default gateway that you mac is using so you know they are correct.

100% correct. The only downside to not using DHCP is that when using DHCP if I issue the command.

ping (or ftp) amiga1200 then I'll get a response as the router will have added me to its DNS tables. Without using DHCP the router won't resolve amiga1200 to an IP address but I could still FTP to the machine by specifying the IP address.

[bbond007]

100% correct. The only downside to not using DHCP is that when using DHCP if I issue the command.

ping (or ftp) amiga1200 then I'll get a response as the router will have added me to its DNS tables. Without using DHCP the router won't resolve amiga1200 to an IP address but I could still FTP to the machine by specifying the IP address.

The DNS thing will only work if you enable some esoteric option that not enabled by default anyway.

I should probably switch my 1200 to static. Miami fails to get an IP address occasionally and but always works the second time...

[Daedalus]

You'll probably find that most routers these days allow IP address reservation, so the router will assign a specific IP address to a specific MAC address. On my setup anyway, this works with both static and DHCP machines, and allows the router to resolve names for all machines, regardless of whether they used DHCP or not.

[Reflex]

ok, thats good... now that you have assigned a static IP, try and issue the command

ping 192.168.1.1 (or whatever your router is)

if you get a response then you'll need to also manually set your DNS to your router, or openDNS 8.8.8.8 (i think) and you are good to go...

If you don't get a response (and you have done everything correctly) then I guess you'll need to get a different router because nobody is going to fix MIAMI's flaky DHCP at this point....

good luck

I'm really sorry to have been misunderstaken. When I only used Amiga i was quite expert on miami, after 10 years I forgot almost everything, I wanted to try the solution you suggested to me, I really appreciated it.

Then I didn't configure a manual route, i put the static IP address 192.168.1.200 and pinged it, this is the result:

ping wrote 192.168.1.1 64 chars, ret=-1

[Reflex]

I'm really sorry to have been misunderstaken. When I only used Amiga i was quite expert on miami, after 10 years I forgot almost everything, I wanted to try the solution you suggested to me, I really appreciated it.

Then I didn't configure a manual route, i put the static IP address 192.168.1.200 and pinged it, this is the result:

ping wrote 192.168.1.1 64 chars, ret=-1

these are 2 pics of the Network utility I run from My macbook.

the second one has been shot when I sent a ping from the amiga to the macbook, as you can see the macbook sees the ip of my amiga (192.168.1.201).
Otherwise the amiga is not seen on the connection.

[bbond007]

I'm really sorry to have been misunderstaken. When I only used Amiga i was quite expert on miami, after 10 years I forgot almost everything, I wanted to try the solution you suggested to me, I really appreciated it.

Then I didn't configure a manual route, i put the static IP address 192.168.1.200 and pinged it, this is the result:

ping wrote 192.168.1.1 64 chars, ret=-1

thats a bummer. Ideally what you wan to see is a response in milliseconds.

well, you have manually put in your subnet mask 255.255.255.0 and your router in as the gateway then I don't think you should have to do anything else as MIAMI will add the gateway as the necessary default route.

I'm not sure if your issue is that you are behind a double NAT and you need to specify a different subnet for your IP (ideally you really want your airport to act as a bridge, but save that for a different day) if I understand your setup correctly.

Meaning your primary router is DHCP server and provides NAT
192.168.100.1
then your secondary router is 192.168.100.100 or something and it also does NAT
computers under that would then be 192.168..

plug in your macbook and determine its DHCP address... then remove it completely and then  put the Amiga on the exact same address. If that works then you'll pick a slightly different address(not in DHCP range) for your Amiga... If that does not work you might be out of luck. I don't see why it won't work though. Apple airports are quality hardware...

[bbond007]

these are 2 pics of the Network utility I run from My macbook.

the second one has been shot when I sent a ping from the amiga to the macbook, as you can see the macbook sees the ip of my amiga (192.168.1.201).
Otherwise the amiga is not seen on the connection.

Humm... maybe it is working. the ping response does not seem right. I'll try to see what it should look like on my 1200..

Humm, it should definately say "time=xxxms" if its working right. But it is "MiamiPing" you are using, right? I totally forgot its not simply ping.

Also you can attempt to ping the amiga from the mac or ping the mac vs the router, or ping the router from the mac... all useful info.

Under databases/DNS maske sure to put in 192.168.1.1 and 8.8.8.8 (as a backup) maybe with DNS it will all magically start working

Oh edit:

I was reading up on the airport base station, to see how it works because that's the part of your setup I'm not familiar with(if that would be a double NAT, etc) . Anyway I see it supports 100mb and gigabit Ethernet, no mention of 10MB...

[Reflex]

Humm... maybe it is working. the ping response does not seem right. I'll try to see what it should look like on my 1200..

Humm, it should definately say "time=xxxms" if its working right. But it is "MiamiPing" you are using, right? I totally forgot its not simply ping.

Also you can attempt to ping the amiga from the mac or ping the mac vs the router, or ping the router from the mac... all useful info.

Under databases/DNS maske sure to put in 192.168.1.1 and 8.8.8.8 (as a backup) maybe with DNS it will all magically start working

Oh edit:

I was reading up on the airport base station, to see how it works because that's the part of your setup I'm not familiar with(if that would be a double NAT, etc) . Anyway I see it supports 100mb and gigabit Ethernet, no mention of 10MB...

today after work I'll try the solution you suggested me, anyway I have a 100MB ethernet board on my mediator... a Realtek RT8139 board...
Anyway yesterday I tried to put another IP address, 192.168.1.33 and it worked!!! I goy response from router!
But when I tried a second ping test is was not working again


ok I did it, I put a static IP address using the macbook one, 192.168.1.104 and the result is the same. But I noticed that if the interface is offline the ping behaves like before (ret=-1), when I put the interface online the shell freezes up...

[Reflex]

Humm... maybe it is working. the ping response does not seem right. I'll try to see what it should look like on my 1200..

Humm, it should definately say "time=xxxms" if its working right. But it is "MiamiPing" you are using, right? I totally forgot its not simply ping.

Also you can attempt to ping the amiga from the mac or ping the mac vs the router, or ping the router from the mac... all useful info.

Under databases/DNS maske sure to put in 192.168.1.1 and 8.8.8.8 (as a backup) maybe with DNS it will all magically start working

Oh edit:

I was reading up on the airport base station, to see how it works because that's the part of your setup I'm not familiar with(if that would be a double NAT, etc) . Anyway I see it supports 100mb and gigabit Ethernet, no mention of 10MB...

Update, today I tried to ping the aiport base.
Well pinging worked from mac, but from amiga I had the real same repli (ret=-1)
so it seems that the amiga is no able to talk with airport base too

what does it mean?

[bbond007]

what does it mean?

I don't recall you mentioning if you were getting an ethernet link LED(s). Check that.. When you attempt to ping do you see any activity on the 8139's LEDs?

Double check that your Amiga network board is still working by hooking it up however you had it before. Perhaps the card died or something with Miami has has gotten messed up or maybe its as simple as a bad network cable.

Finally, I guess guess it means that the 8139 and the airport base are not compatible. Seems unlikely though...

good luck

[magnetic]

Reflex

You may be wasting your time, i told you mac airports are notorious for problems. Just google it.  I couldnt even connect my gf's pc laptop to my old airport express with WPA!

[Reflex]

Reflex

You may be wasting your time, i told you mac airports are notorious for problems. Just google it.  I couldnt even connect my gf's pc laptop to my old airport express with WPA!

so the only problem is WPA password of the airport base?
It looks strange though...

[Reflex]

I don't recall you mentioning if you were getting an ethernet link LED(s). Check that.. When you attempt to ping do you see any activity on the 8139's LEDs?

Double check that your Amiga network board is still working by hooking it up however you had it before. Perhaps the card died or something with Miami has has gotten messed up or maybe its as simple as a bad network cable.

Finally, I guess guess it means that the 8139 and the airport base are not compatible. Seems unlikely though...

good luck

When I turn on the amiga I get green led on the Amiga 100/ACT and green on the Airport base.
When I ping or when I try to use a browser and the interface is online, the green led flashes just once on the amiga side then nothing more happens