Franklin U 600, drxvi314.ko, bcm_wimax on Linux, Part IV

After my encouraging results described in Part III of these notes, I suffered a disappointing setback.
Attempting to search for a Wimax base station this time with an external antenna attached, I was once again confronted with the error "Device NOT present".
Yet I am looking at the device, lit up green for 3G and red for power to the 4G modem part.
Using drxvi312.ko the correct driver, usbbcm, is reported by 'usb-devices'.

Back to work. Using information found in this thread
http://ubuntuforums.org/showthread.php?t=2100982
I did:
lshw -C network:
 *-network
       description: Ethernet interface
       physical id: 2
       logical name: eth1
       serial: f4:63:49:xx:xx:xx
       capabilities: ethernet physical
       configuration: broadcast=yes multicast=yes

 The network is there, the driver working.

sudo dhcpd
Internet Systems Consortium DHCP Server 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Wrote 0 leases to leases file.

No subnet declaration for wlan0 (10.0.0.171).
** Ignoring requests on wlan0.  If this is not what
   you want, please write a subnet declaration
   in your dhcpd.conf file for the network segment
   to which interface wlan0 is attached. **
Not configured to listen on any interfaces!

My 'interfaces' file has the standard entry for linux/Kubuntu. Adding any additional information to it results in a slow start of the system and an error. system no longer usable. changed back to original.
That is not the solution!

Using command 'ifconfig -a' a number of interfaces are displayed, including eth1.
eth1 however has only the inet6 address. Conversion to inet4 failed so far.

Code:
ifconfig -a | egrep 'inet|inet6'
results in:

inet6 addr: fe80::f663:49ff:xxxx:xxxx/64 Scope:Link
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          inet addr:10.0.0.171  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::290:96ff:xxxx:xxxx/64 Scope:Link

 But which is which? I do not know.
 10.0.0.1 is wlan0, I guess.
 127.0.01 local loop.

 The first inet6 is my eth1.

 Entering the info into Network Manager for the eth1 setup does not do anything.

 Code:
 route -n
  Result:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.0.0.1        0.0.0.0         UG    0      0        0 wlan0
0.0.0.0         10.0.0.1        0.0.0.0         UG    303    0        0 wlan0
According to
10.0.0.0        0.0.0.0         255.255.255.0   U     303    0        0 wlan0
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 wlan0

That still does not mean a lot to me but I know the Flags code. what is 169.254.0.0 with Gateway o.o.o.o and Genmask 255.255.0.0? It is up and shown as wlan0????

Looking for an easier way and hopefully a shortcut I found the following interesting suggestion in one of the many threads I read:
Code;
$ sudo ifconfig eth1 down
followed by:
Code:
$ sudo ifconfig eth1 192.168.0.1 up.

Thereafter my ifconfig -a looks like this (excerpt):

eth1      Link encap:Ethernet  HWaddr f4:63:49:xx:xx:xx
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1400  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 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Note that ipv6 is replaced by a inet4 address. At least I got some IPv4 address, a submask and a BCast number.
Note that the broadcast address is similar to
                  '192.168.1.100'
which is shown in wimaxd as RADIUSIPAddress.

Entering the data into the screen for my second 'wired connection' in Network Manager still does not result in any connection, but the information stays and does not disappear when NM is closed.

Instead I went back to attempting a connection the standard way. Get the modem powered on, open wimaxd and wimaxc in terminals.

For my first attempt I used the driver bcm_wimax.ko instead of drxvi314.ko.
The result?

          wimaxd -D -c /etc/wimaxd.conf
********** CSCM Server Started ********** 08/22/13 17:10:42

Processing configuration file
=============================
Reading CM Server options file '/etc/wimaxd.conf'


Option Values In Effect
=======================

(details not shown here)
end of wimaxd evaluation says:

"Message queue initialized.
Process messages thread started successfully.
Changed state to: Library initialized
FATAL ERROR: Listen socket bind failed			<----------
Timer Periodic Action thread has started.
Timer Check Timeouts thread has started."

Now I need to find out what that error means.
End of my test.

Next test. Again with bcm_wimax driver.
Turning on 4Gmodem with picocom. lsusb shows Beceem modem (4G), usb-devices has driver usbbcm in effect.
Code:
ifconfig -a
result:
eth1      Link encap:Ethernet  HWaddr f4:63:49:07:27:9d
          UP BROADCAST NOARP MULTICAST  MTU:1400  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 txqueuelen:5
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

No inet address shown. Also NOARP.
fix:
ifconfig eth1 arp

Result:
eth1      Link encap:Ethernet  HWaddr f4:63:49:07:27:9d
          UP BROADCAST MULTICAST  MTU:1400  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 txqueuelen:5
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


Never paid attention to this interface:

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:4703 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4703 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:893111 (893.1 KB)  TX bytes:893111 (893.1 KB)


End of tests today.

08/24/13

Same setup as before but drxvi314.ko used.


Result:

Message queue initialized.
Process messages thread started successfully.
Changed state to: Library initialized
FATAL ERROR: Listen socket bind failed		<-----------------
Timer Periodic Action thread has started.
Timer Check Timeouts thread has started.


$ wimaxc -i
Beceem CM Server Version 1.1.7.0

> search
Beceem WiMAX device is NOT present



And picocom has: (excerpt)

ATZ E0 V1 X4 &C
ERROR

22, 99

OK

22, 99

OK

22, 99

OK

22, 99

OK

18, 99

OK

Conclusion: I am getting nowhere and wasting time.
What to do next but to give up, which is out of the question.

Following identical procedures before I managed to get the wimax driver to search for a base station.
What changed to make a repeat impossible?
Frustrating. No wonder Virgin Mobile claims that the modem does not work on Linux installations. Sprint says it does and gives detailed instructions. Many of them outdated or hard to understand.

A question to everyone: What does the characters/numbers shown by picocom mean? 18,99, 22,99 and so?
Important to know?
To be continued.