[ixp1200] Booting Intel ixp boards from tftp

[Brandewie, Dirk J]

Both the target and the host have the same IP address.  The
target should be 192.168.0.2 and the host 192.168.0.4.  The
exact IP addresses are not important but they need to be different :-)

Other comments inline

> -----Original Message-----
> From: Gregory Prier [mailto:greg at lever.cs.ucla.edu]
> Sent: Monday, April 22, 2002 1:33 PM
> To: ixp mailing list
> Subject: RE: [ixp1200] Booting Intel ixp boards from tftp
> 
> 
> Thank you all for the help.  I didn't understand how all of 
> this fit together
> and was taking a completely incorrect approach.
> 
> I was able to get the board to boot just fine with your 
> suggestions.  The PCI
> network drivers seemed to install successfully.  I am able to 
> ping from the 
> target from the host but I can't ping the host from the 
> target.  The network 
> interfaces are set up as follows:
> 
> Host:
> 
> 6 > ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:06:5B:2F:24:44  
>           inet addr:131.179.187.20  Bcast:131.179.187.255  
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:5239573 errors:0 dropped:0 overruns:161 frame:0
>           TX packets:1347440 errors:0 dropped:0 overruns:0 carrier:837
>           collisions:2858 txqueuelen:100 
>           Interrupt:11 Base address:0xe880 
> 
> eth1      Link encap:Ethernet  HWaddr AA:00:00:00:00:00  
>           inet addr:192.168.0.4  Bcast:192.168.0.255  
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:30 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100 
> 
> 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:46895 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:46895 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
> 
> -note: I removed the vmware interfaces-
> 
> and for the target:
> 
> [root at Linux /]$ifconfig -a
> eth0      Link encap:Ethernet  HWaddr AA:00:00:00:00:01  
>           inet addr:192.168.0.4  Bcast:192.168.0.255  
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100 
> 
> 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:24 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
> 
> Routing is setup as follows:
> 
> Host:
> 
> 7 > route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric 
> Ref    Use Iface
> 131.179.187.0   0.0.0.0         255.255.255.0   U     0      
> 0        0 eth0
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      
> 0        0 eth1
> 172.16.230.0    0.0.0.0         255.255.255.0   U     0      
> 0        0 vmnet8
> 192.168.139.0   0.0.0.0         255.255.255.0   U     0      
> 0        0 vmnet1
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      
> 0        0 lo
> 0.0.0.0         131.179.187.1   0.0.0.0         UG    0      
> 0        0 eth0
> 
> Target:
> 
> [root at Linux /]$route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric 
> Ref    Use Iface
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      
> 0        0 eth0
> 0.0.0.0         0.0.0.0         0.0.0.0         U     0      
> 0        0 eth0
> 
> Any suggestions what could the be problem?
> 
> Also, I wanted to clarify exactly how this system works.  The 
> host now has an 
> ethernet interface called eth1 that is really a link into the 
> pci bus.  This 
> interface talks to the target's interface (eth0) through the 
> pci bus.   These 
> packets never leave the network.
> 
> Why did intel and Radisys decide to have this communication 
> occur over ethernet 
> interfaces?  Is this to make communication between the host 
> and target easier?

We built it this way to mimic the way the SDK system is used 
with development described in the standard SDK documentation.

> 
> I assumed that ifconfig on the target would also show 
> interfaces for each of the
> four RJ-45 jacks that are on the card .  Since they didn't 
> show up I assume that
> I access these through the strong arm?  Do these ports get 
> interfaces in linux?
>

The IXP1200 card is not a NIC it is a self contained router on a card
for lack of a better term.  The eth1 interface is there to make it
easy for the tools to commuicate with the card.
 
> Thanks for the help.
> 
> GKP
> 
--Dirk