Hi Florin,
I installed the dhcp-3* from contrib like you can see below from the
init-msg's
and removed the pump-rpm. Result was that dhcp was used to get the IP-address
but after got the IP nothing works anymore.
There was NOTHING else changed on the config-files.
This are the outputs when I used pump:
[root@mumpel RPMS]# ifconfig tr0
tr0 Link encap:16/4 Mbps Token Ring HWaddr 00:20:35:C0:DA:1D
inet addr:9.165.175.103 Bcast:9.165.175.255 Mask:255.255.240.0
UP BROADCAST RUNNING MTU:2000 Metric:1
RX packets:326889 errors:0 dropped:0 overruns:0 frame:0
TX packets:431563 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0xa20 Memory:d4000-d7fff
[root@mumpel RPMS]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
9.165.160.0 0.0.0.0 255.255.240.0 U 0 0 0 tr0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 9.165.160.1 0.0.0.0 UG 0 0 0 tr0
And here in add. the netstat -rn for dhcp:
[root@mumpel contrib]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
9.165.160.0 0.0.0.0 255.255.240.0 U 0 0 0 tr0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 9.165.160.1 0.0.0.0 UG 0 0 0 tr0
-> exactly the same but did not work.
I know that I can ignore the error-msg regarding eth0
additional info: with the dhcp-2* rpm's the dhcp-client don't works at all.
Udo
Florin Grad wrote:
> Hi there,
>
> except some error messages comming from the eth0 network card (indeed in
> most cases, this is the checked interface), if I understand correctly, you
> managed to get an IP: 9.165.172.28 and to ping it correctly. What about
> the routes ? do you manage to use alright this network ?
>
> about the dhcpd initscript:
> The /etc/init.d/dhcpd script detects eth0 so you should replace eth0 in
> that script with tr0 in your case in order to setup your dhcp server
> listening to that interface.
>
> are my assumptions correct ?
>
> I'm asking this because I cannot test this in here.
>
> and, one last question: are you using the dhcp*3*pl11 package from the
> contrib (you mentionned something about that) or dhcp-2*, the stable
> version, from cooker/main ? (some people have tested both and they seem to
> have prb with dhcp-3* but it works ok with dhcp-2*).
>
> Thanks for your answer
> --
> Florin http://www.linux-mandrake.com
>
> >[EMAIL PROTECTED] (Udo Weber) writes:
>
> > Florin Grad wrote:
> >
> > > Hi there,
> > >
> > > anyone managed to install/use the dhcp-3* packages with a token ring
> > > network ?
> > > --
> > > Florin http://www.linux-mandrake.com
> >
> > Hi Florin,
> > maybe you can remember on my discussion about dhcp and TR a few weeks
> > ago.
> > I just tryed the dhcp-3* from contrib now and here my experiences:
> >
> > from init:
> >
> > Bringing up interface eth0: cardmgr[3217]: + Determining
> > IP information for tr0 via dhclient...Internet Software
> > Consortium DHCP Client V3.0b2pl11
> > cardmgr[3217]: + All rights reserved.
> > cardmgr[3217]: +
> > tr0: Initial interrupt : 16 Mbps, shared RAM base 000d4000.
> > tr0: Opend adapter: Xmit bfrs: 2 X 2048, Rcv bfrs: 16 X 1032
> > tr0: Adapter initialized and opened.
> > tr0: Setting functional address: 00 00 00 00
> > tr0: Setting functional address: 00 00 00 00
> >
> > from syslog:
> >
> > Dec 6 11:42:36 mumpel network: Setting network parameters: succeeded
> > Dec 6 11:42:36 mumpel cardmgr[3217]: initializing socket 0 <30>Dec
> > 6 11:42:36 cardmgr[3217]: socket 0: IBM Token Ring Adapter
> > Dec 6 11:42:36 mumpel cardmgr[3217]: executing: './network start tr0'
> > Dec 6 11:42:36 mumpel ifup: SIOCADDRT: Network is unreachable
> > Dec 6 11:42:36 mumpel network: Bringing up interface lo: succeeded
> > Dec 6 11:42:36 mumpel dhclient: Internet Software Consortium DHCP
> > Client V3.0b2
> > pl11
> > Dec 6 11:42:36 mumpel cardmgr[3217]: + Copyright 1995-2000 Internet
> > Software Co
> > nsortium.
> > Dec 6 11:42:36 mumpel dhclient: All rights reserved.
> > Dec 6 11:42:36 mumpel cardmgr[3217]: + For info, please visit
> > http://www.isc.or
> > g/products/DHCP
> > Dec 6 11:42:36 mumpel dhclient:
> > Dec 6 11:42:36 mumpel modprobe: modprobe: Can't locate module
> > Dec 6 11:42:40 mumpel ifup: Delaying eth0 initialization.
> > Dec 6 11:42:40 mumpel network: Bringing up interface eth0: failed
> > Dec 6 11:42:41 mumpel modprobe: modprobe: Can't locate module
> > Dec 6 11:42:41 mumpel cardmgr[3217]: + Listening on
> > LPF/tr0/00:20:35:c0:da:1d
> > Dec 6 11:42:41 mumpel dhclient: Sending on LPF/tr0/00:20:35:c0:da:1d
> > Dec 6 11:42:41 mumpel cardmgr[3217]: + Sending on Socket/fallback
> > Dec 6 11:42:41 mumpel dhclient: DHCPREQUEST on tr0 to 255.255.255.255
> > port 67
> > Dec 6 11:42:41 mumpel cardmgr[3217]: + DHCPACK from 9.165.160.2
> > Dec 6 11:42:41 mumpel dhclient: bound to 9.165.172.28 -- renewal in
> > 34050 secon
> > ds.
> > Dec 6 11:42:41 mumpel cardmgr[3217]: + done.
> > Dec 6 11:42:43 mumpel portmap: portmap startup succeeded
> >
> > [root@mumpel /root]# ifconfig
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > UP LOOPBACK RUNNING MTU:3924 Metric:1
> > RX packets:112 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:112 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > tr0 Link encap:16/4 Mbps Token Ring HWaddr 00:20:35:C0:DA:1D
> > inet addr:9.165.172.28 Bcast:9.165.175.255
> > Mask:255.255.240.0
> > UP BROADCAST RUNNING MULTICAST MTU:2000 Metric:1
> > RX packets:665 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:9 Base address:0xa20 Memory:d4000-d7fff
> >
> > [root@mumpel /root]# ping 9.165.172.28
> > PING 9.165.172.28 (9.165.172.28): 56 octets data
> > 64 octets from 9.165.172.28: icmp_seq=0 ttl=255 time=0.2 ms
> > 64 octets from 9.165.172.28: icmp_seq=1 ttl=255 time=0.0 ms
> > 64 octets from 9.165.172.28: icmp_seq=2 ttl=255 time=0.0 ms
> >
> > --- 9.165.172.28 ping statistics ---
> > 3 packets transmitted, 3 packets received, 0% packet loss
> > round-trip min/avg/max = 0.0/0.0/0.2 ms
> > [root@mumpel /root]# ping 9.165.160.93
> > PING 9.165.160.93 (9.165.160.93): 56 octets data
> >
> > --- 9.165.160.93 ping statistics ---
> > 35 packets transmitted, 0 packets received, 100% packet loss
> >
> > ***********************************************************
> > Always the old already discussed problem with dhcp.
> > Result: I go back to pump, this works without problems (currently).
> > ***********************************************************
> >
> > Udo
