New User
John Seth
johnseth at phoenixwing.com
Sun Jun 29 00:06:18 EDT 2003
as root, run "ifconfig". You should see all available network
interfaces. 127.0.0.1, Ethernet (Eth0, Eth1, and/or any others) as well
as any PPP interfaces. If all you see is a reference to 127.0.0.1, then
only localhost (or localhost.localdomain) is active. Also Look for "UP"
on the interface under the line that starts with "inet addr". If any
says "DOWN" then the IP is not active on that device/interface.
I'm not sure if this will do you any good. But at least it'll let you
know if your ethernet is up and running and with an actual IP or not.
Without it, no matter what you type, you won't get out.
Example of my system:
eth0 Link encap:Ethernet HWaddr 00:04:5A:74:4D:55
inet addr:192.168.1.61 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7154 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:5724 dropped:0 overruns:0 carrier:11448
collisions:0 txqueuelen:100
RX bytes:656372 (640.9 Kb) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xe800
eth1 Link encap:Ethernet HWaddr 00:A0:CC:28:50:76
inet addr:2x.2x.2x.2x Bcast:2x.2x.2x.2x ask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:147846 errors:1 dropped:0 overruns:0 frame:0
TX packets:112206 errors:951 dropped:0 overruns:4 carrier:947
collisions:90 txqueuelen:100
RX bytes:22583161 (21.5 Mb) TX bytes:90833983 (86.6 Mb)
Interrupt:12 Base address:0xec00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:18237 errors:0 dropped:0 overruns:0 frame:0
TX packets:18237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2269375 (2.1 Mb) TX bytes:2269375 (2.1 Mb)
Another idea, make sure "named" is not running. An inability to resolve
hostnames, comes from bad DNS servers being listed in /etc/resolv.conf
or named (BIND) running with an invalid configuration, as well as a lack
of a connection to the internet.
I understand you may have a few issues, so my suggestions are for dns
resolution at this point. First, verify you have an IP address from
your ISP active on your system using "ifconfig". Second, ensure
"iptables" and "named" are not running using "service <iptables|named>
stop" as root. Thirdly, you'll need to verify with your ISP your DNS
server addresses, or anyone else using the same ISP in the same area as
you. In a case such as Adelphia, I've noticed Dunkirk area IP's and DNS
is different than that of Buffalo areas, hence my suggestion. Edit
/etc/resolv.conf to suit your needs, typically as follows:
domain buf.adelphia.net
search buf.adelphia.net
nameserver 0.0.0.0
nameserver 0.0.0.0
Replacing the last two nameserver entries with the primary and secondary
DNS IP addresses for your ISP. Make sure to copy it for backup
purposes. On reboot, or during DHCP IP address releases/renewals it may
be overwritten. Lastly, attempt a connection to a named host, such as
www.yahoo.com, maps.yahoo.com or something similar. If it does not
work, try the IP address of one of the hosts. One of the IP's for
www.yahoo.com is 216.109.125.75. If that works, but the first does not.
It's a matter of improper DNS. If the IP does not work, and all
ethernet/PPP connections work, it's a matter of routing. Check your
gateway and netmask addresses using "ifconfig" for the external IP
address. You may need to confer with a Technical Support rep at your
ISP (preferrably an intelligent one who's willing to listen to you and
not just spew "well in windows ..." or some unintelligble thing. If
your settings are correct, check where your kernel is routing through...
[root at system root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
localnet * 255.255.255.128 U 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default gateway.someisp 0.0.0.0 UG 1 0 0 eth1
The above shows default routing going through my ISP's gateway using
interface eth1, which is my external ethernet interface.
If this helps the slightest, cool. If not, feel free to disregard it.
- Tony
> Wheeeew. Where do I start.
>
> I tried eliminating any references to eth0 in my /etc/modules.conf
> file and rebooting as Peter suggested. It didn't ask to configure. I
> ended up reinstalling the ethernet without any prompting from the
> system, and it never asked about migrating the existing networking.
> After I
> reinstall the ethernet and then go back to /etc/modules.conf, "alias
> eth0 CDC Ethernet Class" has been put back in as the last line.
>
> When I was in the /etc/module.conf file, I noticed right under it in
> the directory listing, a module.conf~ file, and then a module.conf~~
> file. The contents of each looked the same. I'm assuming the ones
> with the tildes at the end are backup copies? But the fact they are
> being made doesn't seem good. I changed them so they all look the
> same. I
> apologize for not having a better sense of what's what regarding these
> various files.
>
> No matter what I do with the /etc/hosts file, I still get the "Could
> not look up internet address . . ." message. I noticed sometimes
> between these various changes and boots, I see at the login
> localhost.localdomain and at other times localhostlocaldomain (without
> the period). I'm not sure what that means.
>
> I entered the BIOS and disabled the onboard IDE controller, booted
> again, and all it did was say something like "invalid boot disk A:" I
> then disabled the floppy drive as a bootable device, and I still got
> the same response.
>
> Right now, if I have to live with booting from a floppy, I could think
> of worse things to complain about.
>
> I'm beginning to think my onboard NIC simply isn't compatible with
> this distribution. I was looking at
> http://www.redhat.com/mirrors/LDP/HOWTO/Cable-Modem/ethernet.html
> which offers how-to advice on setting up an ethernet card. It says I
> should see something like the following when I type dmesg:
>
> eth0: 3c509 at 0x300 tag 1, 10baseT port, address 00 20 af ee 01 23,
> IRQ 10.
> 3c509.c:1.07 6/15/95 becker at cesdis.gsfc.nasa.gov
>
> When I run dmesg, I get pages of the following:
>
> CDCEther.c: d: a1
> CDCEther.c: got intr callback
> CDCEther.c: intr status -75
> CDCEther.c: d: a1
> CDCEther.c: got intr callback
> CDCEther.c: intr status -75
> CDCEther.c: d: a1
> CDCEther.c: got intr callback
> CDCEther.c: intr status -75
> CDCEther.c: d: a1
> CDCEther.c: got intr callback
> CDCEther.c: intr status -75
> CDCEther.c: d: a1
> CDCEther.c: got intr callback
> CDCEther.c: intr status -75
> CDCEther.c: d: a1
> CDCEther.c: got intr callback
> CDCEther.c: intr status -75
> CDCEther.c: d: a1
>
> So obviously, I got some problems there. The documentation with my
> Dell lists the following info under NIC:
>
> "Integrated Intel 10/100 Ethernet Controller Driver (Intel 8256ET chip
> set)" Is there some way to manually configure for that?
>
> No, making the changes you suggested to iptables didn't do anything.
>
> My drive is a Western Digital model WD1600JBRTL 160 GB. It's EIDE,
> not SCSI.
>
> I ran cat /var/log/messages |grep hda and got nothing. I then ran
> /sbin/lsmod and got the info I've pasted in below:
>
> [root at localhostlocaldomain root]# cat /var/log/messages |grep hda
> [root at localhostlocaldomain root]# /sbin/lsmod
> Module Size Used by Not tainted
> cs46xx 62832 0 (autoclean)
> ac97_codec 13640 0 (autoclean) [cs46xx]
> soundcore 6404 3 (autoclean) [cs46xx]
> parport_pc 19076 1 (autoclean)
> lp 8996 0 (autoclean)
> parport 37056 1 (autoclean) [parport_pc lp]
> autofs 13268 0 (autoclean) (unused)
> iptable_filter 2412 0 (autoclean) (unused)
> ip_tables 15096 1 [iptable_filter]
> sg 36524 0 (autoclean)
> sr_mod 18136 0 (autoclean)
> ide-scsi 12208 0
> scsi_mod 107160 3 [sg sr_mod ide-scsi]
> ide-cd 35708 0
> cdrom 33728 0 [sr_mod ide-cd]
> CDCEther 14332 1
> acm 7840 0 (unused)
> keybdev 2944 0 (unused)
> mousedev 5492 1
> hid 22148 0 (unused)
> input 5856 0 [keybdev mousedev hid]
> usb-uhci 26348 0 (unused)
> usbcore 78784 1 [CDCEther acm hid usb-uhci]
> ext3 70784 2
> jbd 51892 2 [ext3]
> [root at localhostlocaldomain root]#
>
> Thanks again, everyone, for all your help.
>
> Joe
>
> On Sat, 2003-06-28 at 11:46, vlok stone wrote:
>> I think we need to evaluate what has and hasn't
>> worked.
>> We know that you're able to ping out, so connectivity
>> is there.
>> 1. Did shutting down iptables help (able to surf)
>> #/sbin/service iptables stop
>> if yes, then it's a firewall issue and can be
>> resolved easily.
>> 2. What is the name brand and model of your harddrive
>> Is it a scsi or reg drive
>> we'll be able to check linux compatible to see
>> if it should work. And if so how to get it working.
>> 3. post these messsages to the lug
>> #dmesg (this will give boot messages)
>> #cat /var/log/messages |grep sda (or hda for a reg
>>
>> drive)
>> #/sbin/lsmod (for which modules are loading)
>>
>> That should give us enough info for now. Hopefully,
>> putting our heads together we'll reolve these issues.
>>
>>
>>
>> -- John Seth <johnseth at phoenixwing.com> wrote:
>> > As Pete said, it looks like you have multiple
>> > problems. To remove your
>> > firewall altogether, as root, use "rpm -e iptables",
>> > provided your using
>> > the default 2.4.x kernel. If you are using an older
>> > 2.2.x kernel,
>> > you'll need to use "rpm -e ipchains" instead.
>> >
>> > --
>> >
>> >
>> > > Oooohhhhhhhooo this is frustrating. When I read
>> > your comment about
>> > > setting the BIOS for SCSI, I thought to myself,
>> > "Why of course!" I
>> > > was all excited, but then when I got into my BIOS,
>> > believe it or not,
>> > > there is no setting to account for a SCSI device.
>> > And it's not as if
>> > > I have an old computer. This is a Dell Dimension
>> > 4100 with an 800mHz
>> > > Pentium. Before I started monkeying around with
>> > this project I did
>> > > flash my BIOS with the latest version available --
>> > A11.
>> > >
>> > > Also, I deleted the existing device profile in
>> > network configurations
>> > > and reinstalled my ethernet device, making sure I
>> > set the host name as
>> > > localhost.localdomain. This brings up another
>> > issue. When I launch
>> > > neat, I get a warning message (yellow triangle
>> > w/exclamation point)
>> > > that states:
>> > >
>> > > "eth0 has an alias to module CDC in modules.conf,
>> > > instead of currently loaded module CDC Ethernet
>> > Class!"
>> > >
>> > > What's this telling me?
>> > >
>> > > But I was getting this all along since my first
>> > installation attempt.
>> > > (This makes about the 5th time I've deleted and
>> > reinstalled my
>> > > ethernet settings, hoping to get things right.)
>> > >
>> > > I'm still getting the "Could not look up internet
>> > address for . . ."
>> > > when I log in, except that "dhcp-124-6" has been
>> > replaced by
>> > > "localhost.localdomain"
>> > >
>> > > Also, I believe it was Mike that mentioned that I
>> > should delete the
>> > > firewall from RedHat. Since I can't seem to
>> > change the firewall
>> > > settings from "High security," deleting the entire
>> > firewall sounds
>> > > good right now. How do I do that?
>> > >
>> > > You know, I just had to have this 160 GB drive I
>> > found at Sams to
>> > > replace the original equipment 20 GB drive running
>> > Windows ME. But I
>> > > never thought to check to see if it was compatible
>> > with my existing
>> > > BIOS. I thought I was going to be able to install
>> > it alongside my 20
>> > > GB drive using the onboard IDE channels, and then
>> > copy over whatever
>> > > files I wanted to keep -- even have a dual boot
>> > system! But then,
>> > > after I got it home, that's when I learned why
>> > that nice 48-bit LBA
>> > > supported
>> > > controller card was included. I wish now that I
>> > had a <137 GB drive.
>> > >
>> > > Again, thank you for taking your time to try and
>> > help me figure this
>> > > out. I really appreciate it.
>> > >
>> > > Joe Isom
>> > >
>> > >
>> > > On Thu, 2003-06-26 at 23:18, Cyber Source wrote:
>> > >> Ok, I other thing, lol. Check the boot order in
>> > your BIOS and there
>> > >> should be a selection for SCSI, put that before
>> > any reference to the
>> > >> onboard IDE controller, this will tell the BIOS
>> > that it needs to
>> > >> look beyond it's own controller(s) for a boot
>> > record.
>> > >> On Thu, 2003-06-26 at 23:08, Cyber Source wrote:
>> > >> > One other note on that, take a look at the
>> > example of my lilo.conf
>> > >> file, lilo will always want to write to the first
>> > hard drive,
>> > >> > usually /dev/hda but if that is not possible,
>> > like in your case or
>> > >> in mine below, you need to tell it what drive is
>> > first, hence, the
>> > >> bios=0x80 reference, that tells lilo that that is
>> > the first hard
>> > >> drive and where to write the master boot record
>> > too. In my case, I
>> > >> wanted it on my scsi hard drive, so I put that
>> > first and the put
>> > >> my windows drive (/dev/hdb) and told lilo that it
>> > is my second
>> > >> drive but not 0x81 instead at 0x82 because
>> > /dev/hda is actually on
>> > >> the system but I only mount it when needed. Hope
>> > this helps....
>> > >> >
>> > >> > On Thu, 2003-06-26 at 22:56, Cyber Source
>> > wrote:
>> > >> > > OK, sounds like you've got a few problems.
>> > First, from a command
>> > >> prompt, run the command neat, then adjust your
>> > network settings
>> > >> accordingly. Your 127.0.0.1 address should not be
>> > hosting to
>> > >> adelphia so remove the adelphia stuff and put in
>> > >> > > localhost.localdomain .
>> > >> > > You need to see how your harddrive is being
>> > recognized, run the
>> > >> command dmesg and see what your hard drive is, it
>> > is probably
>> > >> something like /dev/hde since it's on a seperate
>> > controller.
>> > >> There are a bunch of options that can be put in
>> > the lilo.conf
>> > >> file, most importantly the map-drive= line, to
>> > give you an idea
>> > >> of the
>> > >> > > seperate commands on a dual boot/multi hard
>> > drive system, I will
>> > >> include a copy of my /etc/lilo.conf file, if you
>> > change that,
>> > >> run the lilo command again and you can probably
>> > do away with the
>> > >> floppy, One other VERY important note, some
>> > systems cant handle
>> > >> the linear geometry, change that to lba32 if so,
>> > >> > >
>> > >> > > prompt
>> > >> > > timeout=50
>> > >> > > default=RedHat
>> > >> > > boot=/dev/sda
>> > >> > > disk=/dev/sda bios=0x80
>> > >> > > disk=/dev/hdb bios=0x82
>> > >> > > map=/boot/map
>> > >> > > install=/boot/boot.b
>> > >> > > message=/boot/message
>> > >> > > linear
>> > >> > >
>> > >> > > image=/boot/vmlinuz-2.4.18-14
>> > >> > > label=RedHat
>> > >> > > initrd=/boot/initrd-2.4.18-14.img
>> > >> > > read-only
>> > >> > > append="hdc=ide-scsi root=LABEL=/"
>> > >> > > other=/dev/hdb1
>> > >> > > label=Windows
>> > >> > > table=/dev/hdb
>> > >> > > map-drive=0x80
>> > >> > > to=0x82
>> > >> > > map-drive=0x82
>> > >> > > to=0x80
>> > >> > >
>> > >> > > On Thu, 2003-06-26 at 22:32, Joe Isom wrote:
>> > >> > > > I used the command Mark gave me, and the
>> > settings for iptables
>> > >> look as you say it should. But nothing changed
>> > with respect
>> > >> to my inability to go anywhere but Redhat.com.
>> > And it is the
>> > >> Redhat.com site as opposed to any built-in help
>> > files. For
>> > >> example, I was able to sign up for the demo RHN
>> > account and
>> > >> have it query my system for available updates.
>> > >> > > >
>> > >> > > > Also, I attempted to edit my etc/hosts
>> > file. It now looks
>> > >> like this:
>> > >> > > >
>> > >> > > > # Do not remove the following line, or
>> > various programs
>> > >> > > > # that require network functionality will
>> > fail.
>> > >> > > > 127.0.0.1 GCPL301.buf.adelphia.net
>> > localhost
>> > >> > > >
>> > >> > > > That host name above is what I got from the
>> > Host Name field in
>> > >> ipconfig when I was running Windows. I'm not
>> > sure about that
>> >
>> === message truncated ===
>>
>>
>> =====
>> Free Good
>> Fire Bad
>>
>> __________________________________
>> Do you Yahoo!?
>> SBC Yahoo! DSL - Now only $29.95 per month!
>> http://sbc.yahoo.com
More information about the nflug
mailing list