[ECOS] server_test vmware tribulation

["Vijai Krishnamurthy" <vijai at protosys dot com>]

Thanks for the vmware dhcp information, but I'm still facing this problem.

Here's my observation in detail supplemented by tcpdump trace on vmnet8
interface:
vmnet8 is configured for 192.168.2.1 with dns and router at 192.168.2.2

Redboot (configured for static ip 192.168.2.3) boots quite well.
tcpdump -
22:21:43.357008 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:44.379784 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:45.404087 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:46.505599 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
22:21:47.526022 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x55553412
[|bootp]
.
.
.

RedBoot defaults to the static IP address and on the screen I can see these
prints -
Can't get BOOTP info, using default IP address
Ethernet eth0: MAC address 27:39:08:00:00:8e
IP: 192.168.2.3/255.255.255.0, Gateway: 192.168.2.2
Default server: 0.0.0.0, DNS server IP: 192.168.2.2
.
.
.

As usual ping and telnets work fine.

At this point I'm little concerned about Redboot's default server being
0.0.0.0. Is this
OK? I couldn't locate a place in ecos.ecc to set this??!!

Now from the gdb via serial I load the server_test built on ecos configured
for BOOTP/DHCP.
I go step by step till I hit this line init_all_network_interfaces ->
do_dhcp -> bring_half_up.
I step over to see this in tcpdump
tcpdump -
22:40:24.400944 B arp who-has 0.0.0.0 tell 0.0.0.0

Is this arp query OK??

As I continue further I observe that a bootp message is being constructed
and broadcasted (sendto does not
fail, recvfrom fails) but I don't see anything in the tcpdump. Eventually it
just times out with the message
BOOT/DHCP failed on eth0.

I just feel I've missed out something trivial in the ecos configuration. Can
someone please help me.

Thanks,
Vijai


On Thursday 31 October 2002 15:47, Vijai Krishnamurthy wrote:
> Help solicited.
>
> I'm trying to run the server_test program in vmware 3.1 linux.
>
> Vmware is configured for NAT type connection (virtual vmnet adapter on
> 192.168.2.1).
>
> Target is booted on Redboot (configured for static ip 192.168.2.2).
> Everything is
> fine on the network side of the redboot target. I'm able to ping
> 192.168.2.2 from anywhere
> on the network and also able to telnet to 9000.

Since VMware nat device uses the xxx.xxx.xxx.2 ip as the default router and
nameserver for the target, You shouldn't have configured RedBoot to this ip
address. Use xxx.xxx.xxx.10 for instance.

Take a look at /etc/vmware/vmnet8/dhcp/dhcp.conf (vmnet8 is the NAT device).

You shoud perhaps configure RedBoot with a static IP (beetwen 3 and 127) and
let the eCos to be configured with dhcp. That works.

Regards
iz


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss