Well here is some info that you might be inerested in:
Note that the way I set this up is by following the
mini-dhcpcd howto. It claimed Debian would configure
everything out of dpkg, so maybe I had somethin messed
up earlier, I never configured the computer for inet
use on install, but I don't know if that even matters.
kernal is 2.2
I used to be able to ping lo and it worked fine, now I
get:
ping: sendto: Operation not permitted
ping:wrote erdos 64 chars, ret=-1
etc, etc ...
when I ping my address ( ping 24.217.273.166 ) I get
56 data byes
neighbour table overflow
ping:sendto: No buffer space available
ping:wrote 24.217.12.166 64 chars ret=-1
neighbour table overflow
etc, etc ...
when I say: "ping erdos" (erdos is the i386's name )
it is the same as "ping lo".
I was getting other ping errors but right now I can't
recreate them. Are you supposed to be able to do a
ping eth0 ??? b/c I can't.
route -n yields:
Kernel IP routing table
Destination Gateway Genmask Flasgs Metric Ref
Use Iface
24.217.160.0 0.0.0.0 255.255.240.0 U 0
0 0 eth0
0.0.0.0 24.217.160.1 0.0.0.0 UG 0
0 0 eth0
ifconfig yields:
eth0 Link encap:Ethernet HWaddr 00:A0:24:74:4B:F8
inet addr:24.217.273.166 Bcast:255.5\255.255.255 Mask:255.255.240.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:101 error:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txquiuelen:100
Interrupt:10 Base adress:0x300
Some other files:
/etc/resolv.conf -> /etc/dhcpcd/resolv.conf
domain
nameserver 24.217.0.3
nameserver 24.217.0.4
/etc/network/interfaces
iface lo inet loopback
/etc/modules
alias eth0 3c509
options th0 io=0x300 irq=10
Maybe I assigned wrong io ports and/or irq for card, but
don't think this is the case...
At the end of dmesg there is
eth0: 3c509 at 0x300 tag 1, 10baseTport, address 00a024 74 4b f8, IRQ 10.
3c509.c:1.16 (2.2) 2/3/98 [EMAIL PROTECTED]
...<some other stuff> ...
Packet log:input DENY eth0 PROTO=17 10.1.160.1:67 24.217.172.166:68 L=336
S=x00 I=25954 F=0x0000 T=255 (#3)
eth0: Setting Rx mode to 1 addresses.
these last three lines are repeated about 50 times with different values for
I, PROTO, and L. With I going to 0 PROTO cycling btw 1 and 17. and L cycling
btw 53 and 84.
Hope this is sufficient to hammer something out.
Perhaps what might help me most is something like
linuxconf. Does such a package exist for Debian?
You may have noticed that I obviosly don't get the
big picture as to what is supposed to be in place
for all this to work. I have been cutting & pasting
config files for a while and with that not working
I must consult a higher authority.
It almost seems correct, any help would be greatly
appreciated.
-----Andrew's First Response-----
Robert Matijasec writes:
> and it keeps trying until it times out. Where could the
> problem be ? It seems the system reconizes my
> ethernet card, and it even seems I get a connection to
> my provider.
Can you ping your ethernet card? How about your gateway? What does
% route -n
tell you?
> pump came w/Debian install, but after putting on
> dhcpcd I assumed it would have been neatly removed.
You can always check to see if pump is still there, using dselect or
dpkg.
Andrew.
-----Original Message-----
I just installed the dhcpcd package on my i386 and
everything seems fine right up to the point where I
want to test the connection.
I type: telnet ritix.slu.edu
I get: Host name lookup failure
I type: telnet 165.134.123.3
I get: Trying 165.134.123.3...
and it keeps trying until it times out. Where could the
problem be ? It seems the system reconizes my
ethernet card, and it even seems I get a connection to
my provider.
pump came w/Debian install, but after putting on
dhcpcd I assumed it would have been neatly removed.
Any ideas where the problem is ?
