Re: Newbie networking
[EMAIL PROTECTED] (Martin Bialasinski) writes: Maybe some interrupt conflict or such? Check /proc/interrupts Already done. I hesitated to provide too much or irrelevant information initially, so I'll give a more complete picture now. The box is as basic as possible: 486/33, 16mb RAM, plain all-isa mobo, trident s3 w/mono VGA, the ne2000 clone (at a very plain-jane IRQ and IO base, 3-300), 3.5 floppy and 250Mb hard drive. All the /proc stuff checks out okay AFA possible hardware conflicts. Did you try to ping or telnet to your box from some other host in the net? Does the RX line in ifconfig show received packages? Yes, and no. As before, the ping works fine under LOAF. Wish I had more time and energy to compare a few different distros on this box; this is truly a weird beast. Right now I'm booted to LOAF, in fact, so I can telnet downstairs and compose this message... Pinging your own IP won't use the interface, so this should always work and is no indicator for a proper setup. Thanks for clearing that up; I had been under the assumption that using the loopback interface (127.0.0.1) would not use eth0, but that using the real local address would at least use that interface, if not go out over the wire. Maybe it's time to try reading the RFC's again, after a few years of getting familiar with the basic concepts of TCP and actually slogging my way through some books on the subject; the 30th anniversary one, as well as 2196 (determining security policy for Internet hosts) reminded me that there's nothing like the original source. -i -- I let go of the law, and people become honest / I let go of economics, and people become prosperous / I let go of religion, and people become serene / I let go of all desire for the common good, and the good becomes common as grass..oOo.[Tao Te Ching, Chapter 57, Stephen Mitchell translation]
Re: setting up DNS
Lev Lvovsky [EMAIL PROTECTED] writes: At Sunday 05:03 PM 4/11/99 , dyer wrote: Lev Lvovsky wrote: my ADSL provider is mminternet.com, and my address is silver168.mminternet.com (the IP is listed above). You've answered your own question here mminternet.com _is_ the domain, silver168 is only a machine on the domain. You don't register each machine. hrm, maybe there's still something that i'm missing...let's say I want to register www.linuxnewbie.com (just an example), and have it point to my machine (silver168). The ADSL provider provides me with a static IP, so I figured this'd be possible (plus a friend of mine with the same setup did it)... I've been recently tackling this whole issue in preparation for registering a domain. So as always, may others gently correct my errors. To register a domain, you need two things: a static IP address, and two nameservers. Virtual host providers give you a static IP on their machine, and if you have a high-speed connection you may use your own. Generally the host provider runs the required nameservers; you *can* run your own if you need/want to, but if you have to ask why you want it, you probably don't need it. So for most people, the pair of nameservers you give are whatever names your provider tells you to use. (Naturally, any high-speed connection you run personally should be protected by at *least* a simple firewall. A tool called Mason can help the novice user with firewall configuration. Good passwords that aren't trivially guessable should be used and changed regularly on the firewall machine. Fast connections are a rich target for enterprising script kiddies and the (very) occasional malicious attacker. See www.opensec.net/tools.html for lots of powerful tools which may be used for good or ill. Those interested in the security issues are encouraged to spawn this message to a separate thread.) -i -- they're gonna tell you where to walk, when to smile and just what to say | they say have your own fun, make your own mind but don't make no waves | but i got it made in my mind, don't waste my time it's not gonna change | so say what you want, spit it out loud, into my face... ...and i'll pay no attention!
Re: Newbie networking
Wayne Topa [EMAIL PROTECTED] writes: See man resolv.conf. You need your nameserver addresses in there. If it works with the IP # then that your problem. BTW I would thing RH also had the same file. Yes, even with resolv.conf properly configured DNS lookups don't work under LOAF, although all the rest of the networking does; and none of it works under the Debian setup, despite the identical config. The only IP address slinky (the debian name) can ping is itself (and yes, it's the LAN number and not the loopback alias). Bad craziness. -- I let go of the law, and people become honest / I let go of economics, and people become prosperous / I let go of religion, and people become serene / I let go of all desire for the common good, and the good becomes common as grass..oOo.[Tao Te Ching, Chapter 57, Stephen Mitchell translation]
Re: Newbie networking
(LOAF recognizes NIC and networks, Debian recognizes NIC but doesn't despite identical configuration) [EMAIL PROTECTED] (Martin Bialasinski) writes: ifconfig eth0 reports the right values? Correct. It does take many seconds to report back after hitting ENTER, which goes against my experience. Install tcpdump and check the networktraffic for more hints. Done. I'm still poking and will report back; for now, the only traffic that shows up is ARP who-has requests for whatever IP numbers I try to reach. The only real difference between the two setups I've been able to think of is that under LOAF the NE2000 driver is compiled into the kernel, and Debian loads it as a module. -i -- Write your representatives and complain. Demand that they institute the death penalty for all crimes, including jaywalking, tearing the tags off mattresses and thinking about possibly contemplating an action which may be considered a crime at some point in the future. ['TruthMonger', on the cypherpunks list]
Newbie networking
As a relatively veteran user of other distributions (Redhat mainly, but also many of the single-floppy ones), I feel astoundingly stupid for presenting this problem, but here goes. Just installed Debian 2.1 base, and everything is working fine except for one glaring exception. The module for NIC (ne2000) loads successfully, all the network routes are configured correctly, and yet it's unable to ping anyone except itself. What makes this a real hair-puller: This box works perfectly when booted with the latest LOAF floppy. Same kernel (2.0.36), identical routing information, with the exception that it works (except for DNS lookups). Any ideas? I'm already enjoying the cleaner feel of Debian over Redhat, and would like to eventually switch over to it entirely if I can resolve this little issue. (apt-get was one of the things that got me interested initially.) -ian -- [EMAIL PROTECTED] | hempseed.com | geocities.com ] ICQ #859-0985 this is my stop excuse me...if i'm wrong please correct got to get off excuse me...you're standing on my neck... i might go pop i've got to be direct...la la LA la la...
