On Thu, 18 Nov 1999, Erasmus, M.C. wrote: > Three days ago I got cable internet at home installed in Lelystad, > Netherlands. I am subscribing to Telekabel/UPC (http://www.chello.nl) > operating in the province Flevoland and the cable provider uses DHCP. > Unfortunatley it looks like only Windoze networking is supported. > > Everything works just fine when using the Win98 networking with DHCP > activated, server assigned IP adress and manual entry of two DNS servers. > However, using an Amiga A1200 with Cnet ethernet card, MiamiDx 0.9m can not > find my IP adress. > > I tried to use MiamiInit to let it figure out the settings but there is no > luck. After specifying my network as ethernet/cable and selecting the > cnet.device driver MiamiInit tries to figure out whats going on. First it > does something with Rarp and after some operation I get a requestor from > MiamiInit asking me to enter my IP adress. Which in theory I do not know. > After entering bogus adress 10.0.0.1 and continued I was given the option to > save a log, whuch I did. When examining the MiamiInit logfile it did find > everything: Gateway, Netmask, MTU etc. etc. but NOT my IP adress. Certainly entering a bogus IP address won't give you any real communication. > I then went on to let Miami itself try figure out the aforementioned > details, but Miami itself also got the problem of not able to figure out my > IP adress. My network interface is ethernet and the IP adress, gateway and > Netmask was set to the DHCP option. In the TCP/IP panel I activated the > DHCP checkbox afterwhich I selected the online button in the main Interfaces > section. What happens is as explained earlier that after a while Miami > gives up when trying to find my IP adress and the interface does not go > online afterall. It's very often necessary to reset or power-cycle the cable modem when switching machines, since it remembers the MAC address (Ethernet address) of the machine it's talking to. However, you mentioned below that you tried this. You don't say whether you tried the non-MiamiInit method with the modem reset, though. It sounds like some compatibility problem with DHCP. Unfortunately, you can't trace the initial DHCP with MiamiTCPDump, so probably setting PACKETDEBUG=10 or PACKETDEBUG=20 in the MiamiDx tooltypes is the only way to get a useful log. If you have a hub, so that you can connect the PC and the Amiga at the same time, then you could configure a dummy static IP on the Amiga and put the interface online (uselessly for real traffic), so that you can trace the PC's traffic with MiamiTCPDump (this only works with the MNI driver). > Just some extra note, using the Win98 box I noted my current IP address down > and switched my cable modem off and then on again, and according to > windoze98 WinIPcfg program my IP adress did not change. I read in some > other postings that it looks like the "lease" can expire and miami must > obtain a new IP adress. Can Miami handle this? Also, after the switchoff > and on I first connected the cable modem to my Amiga and tried MiamiInit but > without success, the same things happened as I explained earlier. It is > for me a big disappointment that MiamiDx -- which is a superior of Windoze Some cable ISPs really assign IP addresses statically, although they don't guarantee that, and prefer that you use DHCP to track any changes in the assigned address. The purpose of the DHCP lease is to guarantee that the address does *not* change during the lease, not to guarantee that it *does* change when the lease expires. If your ISP is like this, you may be able to get around the DHCP problem by configuring the IP assigned to the PC as a static IP in MiamiDx. You may still need to reset or power-cycle the modem when switching machines to reset its knowledge of the MAC address. Fred Wright -- To unsubscribe send "unsubscribe miamidx-talk-ml" to "[EMAIL PROTECTED]". For help on list commands send "help" to "[EMAIL PROTECTED]".
