Re: Network Install won't connect
The information you get from ifconfig does not seem very coherent to me either. Josh already mentioned the incoherence about the broadcast address, and with the full addresses we see that it goes farther. The subnet mask, although unusual, is legal, and might have been selected by your ISP. However, I have some doubts on that:if we pick up again the computation that Manuel performed earlier without the full addresses, we note that the subnetwork address should be 24.218.248.0, which means that the four digits of the addresses on the same subnetwork must be in the ranges 24.218.248-255.0-255 (hope I'm not mistaken, it's getting into sleep time here in France :-). This assumes that your Inet address is 24.218.255.40, as per ifconfig output. Now the problem is that a gateway at 24.218.224.1 does not seem to belong on the same subnetwork as your machine ; this might explain why you can't ping it. BTW, where did you get your other "default gateway" id (66.31.248.1) ? My feeling over this is that your DHCP did not perform the initialisation correctly, perhaps even not at all. Seeing the number of errors for received packets might also indicate a malfunction of your Ethernet board, but you said that it worked perfectly with MacOs 9 so that would be ruled out. I see two ways out of this : 1) you can reboot your Linux machine, note all initialization performed on the network parameters, redo all the ifconfig/arp/route dance, and send the results to this list for suggestions (we should be able to tell whether DHCP really has been active) ; 2) or, you can reboot with Mac OS 9, go to the TCP/IP Control Panel, note down all the relevant parameters, and then kinda quickly (meanning : before the 12 strokes of midnight - and that's probably serious) reboot into Linux and insert the parameters into the routing tables - most importantly of course the id of your machine, of the gateway and of the subnet mask. Note that the gateway may be displayed under MacOs as a "router". I think the second way may be easier. In case you read up to this point ;-) do you suppose you could check on the existence and contents of a "dhclient.leases" file ? I can't tell you where it is because my Linux box is down, but the dhclient man page probably talks about it. If it's large, I think only the latest info would be useful. I do hope I didn't get too boring :-) Cheers, LMS == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant == Reçu de Colin Foran le 11/07/02 à 17:14 >The ifconfig output: >Link encap: Ethernet HWaddr: *** >inet addr:24.218.255.40bcast:255.255.255.255mask:255.255.248.0 >UP BROADCAST RUNNING MTU 1500 Metric 1 >RX pakets:6 errors:3 dopped:0 frame 3 >TX packets: 3 errors:0 dropped:0 overruns:0 carrier:0 >colisions:0 txqueuelen:100 >interrupt:14 Base address: 0x1000 > > >and route -n:: >DestinationGateway Genmask Flags Metric Ref Use IFace >24.218.224.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0 >0.0.0.024.218.224.1 0.0.0.0 UG0 0 0 eth0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network Install won't connect
(Follow-up to my previous message) ATT Broadband does indeed provide the unusual subnet mask that I talked about, so my doubts about this specific point were not founded. Bye, LMS == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network Install won't connect
Hello again, -- Reçu de Colin Foran le 11/07/02 à 3:11 >> BTW, where did you get your other "default gateway" id (66.31.248.1) ? > >I've got another machine running RedHat (this one). I had figured that sice we >really had no idea what was going on with the mac, it might prove wiser >to use a >valid address. In hindsight though, that doesnt really sound too plausable. Well actually it *is* a good idea, if the setup allows it. Does it ? What you have told us about your configuration up to now makes me think (this is sort of an educated guess, nothing more) that you have two computers, the one that wears a Red Hat and the one with Debian, which you can also boot under MacOs 9; that these computers can be connected to your service provider, ATT Broadband Internet, through a cable modem ; and finally, that the modem as well as the two machines are connected to a single Ethernet cable. Now could you tell me how close (or remote) this description is from the actual setup? That might be important because your Internet provider does not necessarily want you to connect several machines to the same modem - at least not without paying an extra fee. So trying to do that with a standard DHCP configuration might not work, just like what you're experiencing. If so, we could probably help you to setup your network so that it works, but I at least would need more information for that. == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network Install won't connect
As for me, nothing much, sorry ! I was going to suggest doing what you've just done, so if it doesn't work I am quite puzzled, especially since it worked on the MacOs. One caveat though : it is likely that the IP address that it gives to your RedHat machine is linked (by your provider) to the Ethernet address of that machine, and this address *will be different* on the Debian machine. In fact that's the reason why I suggested earlier to reboot under MacOs and gather a correct set of addresses : then you're sure not to have the problem since it is the same Ethernet board. By the way, it should be possible to fake the Ethernet address (using ifconfig) if it proved necessary. Still, if that doesn't work, you could try to setup (if your cabling permits) a LAN between the Red Hat machine, with static addresses, hostnames, etc. In fact that's basically my own setup, since I use a Titanium with MacOs X to connect to the ADSL (USB) modem and a PowerBook G3 with Linux connected to the Ti through Ethernet, so if you take this route I could give you the local addresses and the whole setup. However this is a bit more complex. OTOH, if you intend to do IP masquerading, that's a big part of what you'll have to do anyway. Be sure to tell us how it goes ! Good luck, Laurent Reçu de Colin Foran le 13/07/02 à 17:36 >Well i've tried a new method of manually configureing the network during >installation, using only numbers i know to be good. (from this machine, >bothing use >the same modem, etc) and that just gets me to the same spot i was before. Im >willing to try get myself to believe that this is one of my own mistakes >though, so >i'll try it a few more times. Anyone else have anything come to them in >the last >few days? >-Cheers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network Install won't connect
well you know, once you manage to get through ATT's gateway you're able to access the DNS servers, which should resolve the names for you. But I'm not sure I understood your previous message; have you been able to ping the gateway, or establish some kind of communication with anything ? I think the reason why you got a "hostname not resolved" is still because you haven't gone through the DNS servers. Cheers, Laurent --- Reçu de Colin Foran le 13/07/02 à 1:42 >Just a quick one: >Would it be possible to supply the ip address to the debian site in the arp >list ? once the system is sort of installed i mean. >It seems as though i could just pick most of the things i needed it it were >possible. >-Cheers > > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network Install won't connect
I remember that when I installed my Debian, a few weeks ago, I had some kind of trouble with a non-existent interface, which appeared nonetheless in ifconfig, and that messed up my configuration. Is it possible you'd have the same problem ? you can check on that by just doing an "ifconfig". I think the only interfaces that you should see are "eth0" and "lo". Same applies to "route". If you'd like me to look at your configuration parameters, I'm online for another half-hour or so. LMS == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: netatalk does not see a printer
Hello, I am able to print using netatalk trough an Asante bridge to my HP LaserJet. The following points might help you : - your ifconfig does not show that the Ethernet network is "UP", meaning that it's probably down :-) I suggest you perform an "ifconfig eth0 up" and see what happens. - my "getzones" command also times out, but that does not seem to have any impact on the printing ability. In particular, nbplkup works (so does printing) both before and after the getzones command. Let me know if you'd like more information. Good luck, LMS == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant == Reçu de Alessandro Ghigi le 18/07/02 à 23:24 >Hi. > >I have a potato on a laptop with a pcmcia ethernet card, and I am trying >to connect it to an Apple LaserWriter 4/600 PS, which has a LocalTalk >connector. I also have an Asantetalk adapter which bridges (or should >bridge) between ethernet and localtalk. > >I have a kernel with appletalk as a loadable module, and have installed >netatalk. When I start netatalk using the script (after loading >appletalk.o), it does not complain. Nevertheless the getzones command >does not work: > >root:/etc/init.d# getzones >atp_rresp: Connection timed out > > >With nbplkup I get the following: > >root:/etc/init.d# nbplkup >caspar:AFPServer >65280.226:128caspar:netatalk > 65280.226:4 >caspar:Workstation65280.226:4 > >With ifconfig I get: > >root:/home/ghigi# ifconfig eth0 >eth0 Link encap:Ethernet HWaddr 00:50:04:DF:B4:BF > EtherTalk Phase 2 addr:65280/226 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > Interrupt:11 Base address:0x200 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: netatalk does not see a printer
Hello Alessandro, I'm glad you managed to make it work. I can understand your happiness at being able to use the Asante bridge, I had the same feeling a few weeks ago :-) Cheers, Laurent == Laurent Steffan [EMAIL PROTECTED] eBusiness Technical Consultant == Reçu de [EMAIL PROTECTED] le 22/07/02 à 16:37 >Dear Laurent. > >I have removed the network.opts file in /etc/pcmcia, and I send the >"ifconfig eth0 up" before starting AppleTalk. It works!!! > >I am not on a network, so my network.opts file was a standard one which >I had not edited. I hope it is fine just removing it. I'll try learning >something about it, so I can configure it properly. > >Anyway now it works, so I am very happy, also because the Asante box >was quite expensive. > > Thank you very much for your advise > >Alessandro > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
