networking - How to use CLEAR USB WiMax in Ubuntu (host) and Windows XP (guest) using VirtualBox

25
2013-09
  • Questioner

    I'm trying to use CLEAR Motorola WiMax USB in Ubuntu as there is no support for Linux as yet. I've installed Windows XP as guest in Ubuntu and the version I'm using is 3.2.2. USB is connecting fine in Windows XP but I can't use internet in Ubuntu. Can you please tell me how to do it. Here is the configuration that could help you guys. Thanks in advance.

    I'm using Two Network Adapters.

    Network
Adapter 1:
PCnet-FAST III (NAT)
Adapter 2:
PCnet-FAST III (Host-only adapter, 'vboxnet0')

    ipconfig [on Guest windowsXP]

    Windows IP Configuration
Ethernet adapter Local Area Connection:  PCnet-FAST III (NAT)

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 10.0.2.15
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.2.2

Ethernet adapter Local Area Connection 3: PCnet-FAST III (Host-only adapter, 'vboxnet0')

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 192.168.56.101
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 2: 

        Connection-specific DNS Suffix  . : CLEAR Motorola USB
        IP Address. . . . . . . . . . . . : 10.168.242.33
        Subnet Mask . . . . . . . . . . . : 255.255.192.0
        Default Gateway . . . . . . . . . : 10.168.192.2

    IFCONFIG [on Host Ubuntu]

    (Ethernet) eth0      Link encap:Ethernet  HWaddr 00:14:22:b9:9d:76  
          UP BROADCAST MULTICAST  MTU:1500  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)
          Interrupt:16 

eth1    (Wireless) Link encap:Ethernet  HWaddr 00:13:ce:f0:9b:0d  
          inet6 addr: fe80::213:ceff:fef0:9b0d/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:5 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:84 (84.0 B)
          Interrupt:17 Base address:0xe000 Memory:dfcff000-dfcfffff 

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:16436  Metric:1
          RX packets:2292 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:171952 (171.9 KB)  TX bytes:171952 (171.9 KB)

vboxnet0  Link encap:Ethernet  HWaddr 0a:00:27:00:00:00  
          inet addr:192.168.56.1  Bcast:192.168.56.255  Mask:255.255.255.0
          inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:21174 (21.1 KB)
    • Answers
  • ta.speot.is

    You should enable ICS on the Windows XP box and set the network adapter for vboxnet0 to DHCP.

    The Windows XP guest has a DHCP server built-in for ICS. When your vboxnet0 adapter sends a DHCP request the guest should return the necessary configuration information (specifically default gateway) to allow Ubuntu to route traffic through it.

    I don't know why you have two adapters for the guest.


    • Related Question

    networking - Command-line connect to wired network for Ubuntu
  • Tim

    I like to know how to use command-line to connect to a wired network in general for Ubuntu 8.10?

    In my case, I connect a cable to my laptop but it doesn't work with my WICD. So I like to try command-line method.

    Here is the ifconfig of my network adapters:

    $ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:c0:9f:8d:23:74  
          UP BROADCAST MULTICAST  MTU:1500  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)
          Interrupt:19 Base address:0x1800 

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:16436  Metric:1
          RX packets:4457 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4457 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:493002 (493.0 KB)  TX bytes:493002 (493.0 KB)

wlan0     Link encap:Ethernet  HWaddr 00:0e:9b:ab:56:19  
          UP BROADCAST NOTRAILERS PROMISC ALLMULTI  MTU:576  Metric:1
          RX packets:1508929 errors:0 dropped:0 overruns:0 frame:0
          TX packets:768144 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:806027375 (806.0 MB)  TX bytes:78834873 (78.8 MB)

wlan0:avahi Link encap:Ethernet  HWaddr 00:0e:9b:ab:56:19  
          inet addr:169.254.5.92  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST NOTRAILERS PROMISC ALLMULTI  MTU:576  Metric:1

wmaster0  Link encap:UNSPEC  HWaddr 00-0E-9B-AB-56-19-00-00-00-00-00-00-00-00-00-00  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  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)

    UPDATE:

    Tried what oyvindio suggested. Here is the failing message:

    $ sudo dhclient3 eth0
There is already a pid file /var/run/dhclient.pid with pid 18279
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

mon0: unknown hardware address type 803
wmaster0: unknown hardware address type 801
mon0: unknown hardware address type 803
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:c0:9f:8d:23:74
Sending on   LPF/eth0/00:c0:9f:8d:23:74
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

    • Related Answers
  • oyvindio

    If your router is set up to serve IP addresses via dhcp, run sudo dhclient3 eth0 to ask for an IP address for the eth0 interface.

  • Cry Havok

    The No DHCPOFFERS received. means that you're not reaching, and getting a response, from the DHCP server.

    There may be a number of reasons for this, but having your wireless in monitor mode isn't one I'd put on the list. It could be that the DHCP server only serves a limited set of MAC addresses (each network card has a unique MAC address), or that there is no DHCP server. It could also be a security feature of the switch restricting access only to certain MAC addresses.

    The other thing to check is hardware - does the network cable work with another computer and does your computer work with another wired network.

    The easy way to test your theory is to take wlan0 out of monitor mode.