Have you remembered to stick
BPQPARAMS
ETH_ADDR FF:FF:FF:FF:FF:FF
in your net.cfg AND made sure that the odidrv that you execute reads that
net.cfg (and not some other one)?
Dirk G1TLH
On 23-May-99 Peter wrote:
> Hello,
>
> I'am trying to make a dos machine with BPQ to talk with linux via ax25
> and ethernet.
> By reading ax25-howto the bpq device is associated with eth0
> With "# /sbin/ifconfig bpq0 hw ax25 pi4cc-7 comment" I do config the
> eth0 device.
>
> When I start calling pi4cc-7 at the dos machine the packets a received
> at eth0. The rx pactkets is counting. But there will be no link. The
> bpq0 doen't receive any packet.
>
> My question: whats wrong?
>
> Here is a copy of ifconfig:
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:1657 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1657 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> eth0 Link encap:Ethernet HWaddr 52:54:4C:02:EB:50
> inet addr:10.0.0.0 Bcast:10.255.255.255 Mask:255.0.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:30 errors:0 dropped:0 overruns:0 frame:0
> TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Interrupt:5 Base address:0x300
>
> bpq0 Link encap:AMPR AX.25 HWaddr PI4CC-7
> inet addr:192.168.0.1 Mask:255.255.255.0
> UP RUNNING MTU:256 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> ax0 Link encap:AMPR AX.25 HWaddr PI4CC
> inet addr:192.168.0.1 Mask:255.255.255.0
> UP RUNNING MTU:255 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
>
> 73 peter
> PB0AIU
---
Dirk-Jan Koopman, Tobit Computer Co Ltd
At the source of every error which is blamed on the computer you will find
at least two human errors, including the error of blaming it on the computer.
