Wimax connection problem (Solved)

Message

poe503 · #1 Post by **poe503** » Sat 14 Dec 2013, 01:38

[The solution to no browsing with the Ubee stick is to change the stick configuration to NAT and leave it at the suggested IP values. The Ubee stick will restart. Rerun the network wizard and auto DHCP. That's it!]

Dell Inspiron 1100
Precise Puppy Retro 5.7.1
Ubee Wimax Stick PXU1964

This a USB stick that hooks up with the Freedom POP Wimax network which is also, I believe, the Clear network.

The stick works with Ubuntu 10.04 with no problem.

With Puppy, a prompt comes up that I am hooked up via Eth1 and shows an IP address.

Neither SeaMonkey nor Opera can browse. Interesting to note that Opera initially brought up a webpage but then refused to load any page at all.

Any help would be appreciated.

BTW, I am delighted to find that Puppy works with my old Linksys wifi card which Ubuntu fails to recognize.

RetroTechGuy · #2 Post by **RetroTechGuy** » Sat 14 Dec 2013, 02:37

poe503 wrote:Dell Inspiron 1100
Precise Puppy Retro 5.7.1
Ubee Wimax Stick PXU1964

This a USB stick that hooks up with the Freedom POP Wimax network which is also, I believe, the Clear network.

The stick works with Ubuntu 10.04 with no problem.

With Puppy, a prompt comes up that I am hooked up via Eth1 and shows an IP address.

Neither SeaMonkey nor Opera can browse. Interesting to note that Opera initially brought up a webpage but then refused to load any page at all.

Any help would be appreciated.

BTW, I am delighted to find that Puppy works with my old Linksys wifi card which Ubuntu fails to recognize.

Did you try going through the connect network tool? I've seen cases where the configuration wasn't right (or changed) and it dropped out.

I also had a USB stick that would overheat and shut itself down... (or was sucking too much power from the USB port, which would shut it down)

That might be the first thing, and then some of the real network experts can come in and help...

poe503 · #3 Post by **poe503** » Sat 14 Dec 2013, 03:01

Thanks for the reply.

I checked it out with the network tool. If there needs to be a config change, I don't know what it would be.

There is no other network connection, just the Wimax stick. I removed the wifi card before using it.

The stick works fine with Ubuntu and XP. No overheating.

RetroTechGuy · #4 Post by **RetroTechGuy** » Sat 14 Dec 2013, 03:26

poe503 wrote:Thanks for the reply.

I checked it out with the network tool. If there needs to be a config change, I don't know what it would be.

There is no other network connection, just the Wimax stick. I removed the wifi card before using it.

The stick works fine with Ubuntu and XP. No overheating.

Very weird... The fact that it worked, and then didn't...

Perhaps try 5.28 -- I've had good luck with it on a wide range of machines (I have an old 1.6 GHz Dell Latitude and it works fine).

Or perhaps 5.25 Retro... This runs on my old 333 MHz PII...

5.25 Retro:

http://www.murga-linux.com/puppy/viewto ... 627#521627

Edit: BTW, congrats! You seem to be the first person trying to run this stick...

poe503 · #5 Post by **poe503** » Sat 14 Dec 2013, 06:35

Ugh, I would gladly decline the honor of being the first in any hardware or software venture.

I downloaded the Puppy 525 version but get the same situation. The eth1 is noted as active but no browser or download. I used
the Firefox browser in this instance.

Interesting to note that the initial installation of the Ubee stick in Windows had the same situation: a connection is recognized but the browser doesn't work. Restarted Windows and then everything worked fine.

RetroTechGuy · #6 Post by **RetroTechGuy** » Sat 14 Dec 2013, 07:04

poe503 wrote:Ugh, I would gladly decline the honor of being the first in any hardware or software venture.

I downloaded the Puppy 525 version but get the same situation. The eth1 is noted as active but no browser or download. I used
the Firefox browser in this instance.

Interesting to note that the initial installation of the Ubee stick in Windows had the same situation: a connection is recognized but the browser doesn't work. Restarted Windows and then everything worked fine.

Well, I was looking to see if anyone else had luck in Linux:

http://askubuntu.com/questions/251072/i ... ith-ubuntu

http://www.indigent-networks.com/freedo ... usb-stick/

RetroTechGuy · #7 Post by **RetroTechGuy** » Sat 14 Dec 2013, 07:08

I'm going to tell you, I'm out of my depth (not an expert at networking issues). So I'm going to flail around a bit...

Ubee says that it is supported by Linux...

I would start by going through here:

http://www.ubeeinteractive.com/support/consumers/faq

If they support Linux, I would expect that they provide a driver (or otherwise tell you what chipset your device uses).

They claim that this is the driver (looks like Windows crud):

http://www.ubeeinteractive.com/support/ ... d-driver-0

poe503 · #8 Post by **poe503** » Sat 14 Dec 2013, 19:38

Thanks for your kind efforts.

After sleeping on it, I decided to compare the working Ubuntu network config file(s) with Puppy's. Don't have the time to do that right now but will get back and report on how it goes.

If someone could list the appropriate files to check, that would be helpful. Thanks.

poe503 · #9 Post by **poe503** » Tue 17 Dec 2013, 00:19

Up to now, the only difference I have found between Ubuntu and Puppy that is the apparent lack of IPv6 in Puppy. I don't have a clue if this would make a difference in the functioning of the Wimax connection.

I have disabled the firewall and shutdown the onboard LAN in the laptop's BIOS. Nothing has helped.

The only clue is that sometimes I get a small amount of data to load into a browser or able to do a small download 40 kb (?) before the connection stops working. The computer continues to show that I am connected but nothing flows.

ardvark · #10 Post by **ardvark** » Tue 17 Dec 2013, 01:38

Hi..

Out of curiosity, what is the chipset on this device? Please post the output of the command below...

Code: Select all

lsusb

Regards...

poe503 · #11 Post by **poe503** » Tue 17 Dec 2013, 03:24

Thank you for your reply.

Here are the results of lsusb -v :

Bus 001 Device 004: ID 198f:8160 Beceem Communications Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x198f Beceem Communications Inc.
idProduct 0x8160
bcdDevice 3.24
iManufacturer 2 Beceem Communications
iProduct 3 UBEE Stick
iSerial 4 USB Serial No *
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 80
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 8 CDC Ethernet Control Model (ECM)
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress *
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 9 CDC Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x09 EP 9 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
#

poe503 · #12 Post by **poe503** » Tue 17 Dec 2013, 04:00

I forgot that this unit has its own webpage.

It says:

Baseband Chip: bece3522

RF Chip: 4400

Does Puppy have RNDIS 'out of the box' ?

ardvark · #13 Post by **ardvark** » Wed 18 Dec 2013, 00:43

poe503 wrote:Does Puppy have RNDIS 'out of the box' ?

Hi....

With the version you're running, I'm not sure. However, I found this thread in which the OP claims that RNDIS can be found in Puppy 4.3.1. If you want to see if this version works for you, you can download it here (pup-431.iso) or here. Or you could try any of the other more recent versions to see if they will natively support your device. If it works fine in Ubuntu 10.04 and your system can run it efficiently, that might be a better option or you can give Lubuntu a try.

Like RetroTechGuy, I too am at a loss why your version of Puppy is having problems with your device.

Regards...

poe503 · #14 Post by **poe503** » Wed 18 Dec 2013, 02:57

I guess it does have RNDIS. Syslog shows it recognizing the usb stick as a CDC device and seems to be OK with that. I think that I will post a copy of both Ubuntu and Puppy logs regarding the Ubee stick for a comparison. Will try to make it as short as possible. Perhaps someone will have a bright idea.

I tried Lubuntu before trying Puppy. It was too buggy, at least in regards to my laptop. Regular Ubuntu is too bloated.

RetroTechGuy · #15 Post by **RetroTechGuy** » Wed 18 Dec 2013, 05:02

ardvark wrote:With the version you're running, I'm not sure. However, I found this thread in which the OP claims that RNDIS can be found in Puppy 4.3.1. If you want to see if this version works for you, you can download it here (pup-431.iso)

My recollection was that the driver bundle from 4.31 was migrated into the 5.2X family. But it might be worth a try.

I was thinking that the network was a fairly new device, so I'm really not sure...

Like RetroTechGuy, I too am at a loss why your version of Puppy is having problems with your device.

I keep hoping that Tempestuous, Playdayz or rcrsn51 will jump in... (and/or a few others...)

Ardvark, who is the main dev on Precise? Maybe poe503 can PM one of them...

I'm my reading was correct, the device isn't just a network card, but provides a direct wireless internet link (a 4G device). I wonder if that is part of the issue... The device would have to be recognized locally, then the network would have to be recognized, then the security would have to be negotiated... I wonder in there's a problem at the last...

ardvark · #16 Post by **ardvark** » Wed 18 Dec 2013, 06:48

RetroTechGuy wrote: Ardvark, who is the main dev on Precise? Maybe poe503 can PM one of them...

I'm my reading was correct, the device isn't just a network card, but provides a direct wireless internet link (a 4G device). I wonder if that is part of the issue... The device would have to be recognized locally, then the network would have to be recognized, then the security would have to be negotiated... I wonder in there's a problem at the last...

I have no idea but Barry should know, he can be PM'd at this thread.

It's entirely possible that Poe's device operates in this manner. What I find interesting, too, is that his (or her) connection shows up as "Eth1." I'm not a network expert either but I don't think wireless connections in Linux show up as that.

Regards...

poe503 · #17 Post by **poe503** » Wed 18 Dec 2013, 18:31

Thanks for putting on the thinking cap, guys.

Ubuntu also recognizes this connection as Eth1.

I shut off the onboard LAN in the Inspiron because Puppy seemed to be juggling between Eth0 and Eth1 when booting up the connection.

Didn't help.

Security issues could possibly explain why the data flow gets throttled to death in the infancy of the connection.

I am built with a male connector, BTW.

ardvark · #18 Post by **ardvark** » Wed 18 Dec 2013, 18:43

Hi Poe...

Give Barry a jingle (PM) at the thread I linked to above, he might know of something or at least the Dev who takes care of your version.

Regards...

poe503 · #19 Post by **poe503** » Thu 19 Dec 2013, 00:45

(Here is the Ubuntu syslog for the Ubee stick. 192.168.14.1 is the ip for the stick and 71.20.10.155 is the ip for Clear network. I put a space where I disconnected the stick.)

Dec 18 16:19:38 paul-laptop kernel: [ 476.996236] usb 2-1: new high speed USB device using ehci_hcd and address 4
Dec 18 16:19:38 paul-laptop kernel: [ 477.130190] usb 2-1: configuration #2 chosen from 1 choice
Dec 18 16:19:38 paul-laptop kernel: [ 477.134013] usb 2-1: USB disconnect, address 4
Dec 18 16:19:38 paul-laptop kernel: [ 477.161779] Initializing USB Mass Storage driver...
Dec 18 16:19:38 paul-laptop kernel: [ 477.163039] usbcore: registered new interface driver usb-storage
Dec 18 16:19:38 paul-laptop kernel: [ 477.163045] USB Mass Storage support registered.
Dec 18 16:19:39 paul-laptop kernel: [ 478.076202] usb 2-1: new high speed USB device using ehci_hcd and address 5
Dec 18 16:19:39 paul-laptop kernel: [ 478.220994] usb 2-1: config 1 has 2 interfaces, different from the descriptor's value: 3
Dec 18 16:19:39 paul-laptop kernel: [ 478.222232] usb 2-1: configuration #1 chosen from 1 choice
Dec 18 16:19:40 paul-laptop kernel: [ 478.261613] eth1: register 'cdc_ether' at usb-0000:00:1d.7-1, CDC Ethernet Device, xxxx
Dec 18 16:19:40 paul-laptop kernel: [ 478.261637] usbcore: registered new interface driver cdc_ether
Dec 18 16:19:40 paul-laptop NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/net/eth1, iface: eth1)
Dec 18 16:19:40 paul-laptop NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/net/eth1, iface: eth1): no ifupdown configuration found.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): carrier is OFF
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): new Ethernet device (driver: 'cdc_ether')
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/2
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): now managed
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): device state change: 1 -> 2 (reason 2)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): bringing up device.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): preparing device.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): deactivating device (reason: 2).
Dec 18 16:19:40 paul-laptop NetworkManager: Added default wired connection 'Auto eth1' for /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/net/eth1
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): carrier now ON (device state 2)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): device state change: 2 -> 3 (reason 40)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) starting connection 'Auto eth1'
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) successful.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): device state change: 5 -> 7 (reason 0)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Beginning DHCP transaction (timeout in 45 seconds)
Dec 18 16:19:40 paul-laptop NetworkManager: <info> dhclient started with pid 1680
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) scheduled...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) started...
Dec 18 16:19:40 paul-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP6 Configure Get) complete.
Dec 18 16:19:40 paul-laptop dhclient: Internet Systems Consortium DHCP Client V3.1.3
Dec 18 16:19:40 paul-laptop dhclient: Copyright 2004-2009 Internet Systems Consortium.
Dec 18 16:19:40 paul-laptop dhclient: All rights reserved.
Dec 18 16:19:40 paul-laptop dhclient: For info, please visit https://www.isc.org/software/dhcp/
Dec 18 16:19:40 paul-laptop dhclient:
Dec 18 16:19:40 paul-laptop NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): carrier now OFF (device state 7, deferring action for 4 seconds)
Dec 18 16:19:40 paul-laptop dhclient: Listening on LPF/eth1/xxxx
Dec 18 16:19:40 paul-laptop dhclient: Sending on LPF/eth1/xxxx
Dec 18 16:19:40 paul-laptop dhclient: Sending on Socket/fallback
Dec 18 16:19:40 paul-laptop NetworkManager: <info> (eth1): carrier now ON (device state 7)
Dec 18 16:19:41 paul-laptop avahi-daemon[750]: Registering new address record for xxxx on eth1.*.
Dec 18 16:19:44 paul-laptop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Dec 18 16:19:46 paul-laptop dhclient: DHCPOFFER of 192.168.14.2 from 192.168.14.1
Dec 18 16:19:46 paul-laptop dhclient: DHCPREQUEST of 192.168.14.2 on eth1 to 255.255.255.255 port 67
Dec 18 16:19:46 paul-laptop dhclient: DHCPACK of 192.168.14.2 from 192.168.14.1
Dec 18 16:19:46 paul-laptop dhclient: bound to 192.168.14.2 -- renewal in 10 seconds.
Dec 18 16:19:46 paul-laptop NetworkManager: <info> DHCP: device eth1 state changed preinit -> bound
Dec 18 16:19:46 paul-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) scheduled...
Dec 18 16:19:46 paul-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) started...
Dec 18 16:19:46 paul-laptop NetworkManager: <info> address 192.168.14.2
Dec 18 16:19:46 paul-laptop NetworkManager: <info> prefix 24 (255.255.255.0)
Dec 18 16:19:46 paul-laptop NetworkManager: <info> gateway 192.168.14.1
Dec 18 16:19:46 paul-laptop NetworkManager: <info> nameserver '192.168.14.1'
Dec 18 16:19:46 paul-laptop NetworkManager: <info> domain name 'clearwire-wmx.net'
Dec 18 16:19:46 paul-laptop NetworkManager: <info> wins '192.168.14.1'
Dec 18 16:19:46 paul-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 18 16:19:46 paul-laptop NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Get) complete.
Dec 18 16:19:46 paul-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Dec 18 16:19:46 paul-laptop avahi-daemon[750]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.14.2.
Dec 18 16:19:46 paul-laptop avahi-daemon[750]: New relevant interface eth1.IPv4 for mDNS.
Dec 18 16:19:46 paul-laptop avahi-daemon[750]: Registering new address record for 192.168.14.2 on eth1.IPv4.
Dec 18 16:19:47 paul-laptop NetworkManager: <info> (eth1): device state change: 7 -> 8 (reason 0)
Dec 18 16:19:47 paul-laptop NetworkManager: <info> Policy set 'Auto eth1' (eth1) as default for routing and DNS.
Dec 18 16:19:47 paul-laptop NetworkManager: <info> Activation (eth1) successful, device activated.
Dec 18 16:19:47 paul-laptop NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Dec 18 16:19:47 paul-laptop ntpdate[1734]: can't find host ntp.ubuntu.com
Dec 18 16:19:47 paul-laptop ntpdate[1734]: no servers can be used, exiting
Dec 18 16:19:50 paul-laptop kernel: [ 488.864088] eth1: no IPv6 routers present
Dec 18 16:19:56 paul-laptop dhclient: DHCPREQUEST of 192.168.14.2 on eth1 to 192.168.14.1 port 67
Dec 18 16:19:56 paul-laptop dhclient: DHCPACK of 192.168.14.2 from 192.168.14.1
Dec 18 16:19:56 paul-laptop dhclient: bound to 192.168.14.2 -- renewal in 10 seconds.
Dec 18 16:19:56 paul-laptop NetworkManager: <info> DHCP: device eth1 state changed bound -> renew
Dec 18 16:19:56 paul-laptop NetworkManager: <info> address 192.168.14.2
Dec 18 16:19:56 paul-laptop NetworkManager: <info> prefix 24 (255.255.255.0)
Dec 18 16:19:56 paul-laptop NetworkManager: <info> gateway 192.168.14.1
Dec 18 16:19:56 paul-laptop NetworkManager: <info> nameserver '192.168.14.1'
Dec 18 16:19:56 paul-laptop NetworkManager: <info> domain name 'clearwire-wmx.net'
Dec 18 16:19:56 paul-laptop NetworkManager: <info> wins '192.168.14.1'
Dec 18 16:20:06 paul-laptop dhclient: DHCPREQUEST of 192.168.14.2 on eth1 to 192.168.14.1 port 67
Dec 18 16:20:06 paul-laptop dhclient: DHCPACK of 192.168.14.2 from 192.168.14.1
Dec 18 16:20:06 paul-laptop dhclient: bound to 192.168.14.2 -- renewal in 10 seconds.
Dec 18 16:20:16 paul-laptop dhclient: DHCPREQUEST of 192.168.14.2 on eth1 to 192.168.14.1 port 67
Dec 18 16:20:16 paul-laptop dhclient: DHCPNAK from 192.168.14.1
Dec 18 16:20:16 paul-laptop NetworkManager: <info> DHCP: device eth1 state changed renew -> expire
Dec 18 16:20:16 paul-laptop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Dec 18 16:20:16 paul-laptop NetworkManager: <info> DHCP: device eth1 state changed expire -> preinit
Dec 18 16:20:18 paul-laptop dhclient: DHCPOFFER of 71.20.10.155 from 192.168.14.1
Dec 18 16:20:18 paul-laptop dhclient: DHCPREQUEST of 71.20.10.155 on eth1 to 255.255.255.255 port 67
Dec 18 16:20:18 paul-laptop dhclient: DHCPACK of 71.20.10.155 from 192.168.14.1
Dec 18 16:20:18 paul-laptop dhclient: bound to 71.20.10.155 -- renewal in 30 seconds.
Dec 18 16:20:18 paul-laptop NetworkManager: <info> DHCP: device eth1 state changed preinit -> bound
Dec 18 16:20:18 paul-laptop NetworkManager: <info> address 71.20.10.155
Dec 18 16:20:18 paul-laptop NetworkManager: <info> prefix 18 (255.255.192.0)
Dec 18 16:20:18 paul-laptop NetworkManager: <info> static route 192.168.14.1 gw 71.20.10.155
Dec 18 16:20:18 paul-laptop NetworkManager: <info> gateway 71.20.0.1
Dec 18 16:20:18 paul-laptop NetworkManager: <info> nameserver '192.168.14.1'
Dec 18 16:20:18 paul-laptop NetworkManager: <info> nameserver '64.13.115.12'
Dec 18 16:20:18 paul-laptop NetworkManager: <info> domain name 'clearwire-wmx.net'
Dec 18 16:20:18 paul-laptop NetworkManager: <info> wins '192.168.14.1'
Dec 18 16:20:18 paul-laptop avahi-daemon[750]: Withdrawing address record for 192.168.14.2 on eth1.
Dec 18 16:20:18 paul-laptop avahi-daemon[750]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.14.2.
Dec 18 16:20:18 paul-laptop avahi-daemon[750]: Interface eth1.IPv4 no longer relevant for mDNS.
Dec 18 16:20:18 paul-laptop avahi-daemon[750]: Joining mDNS multicast group on interface eth1.IPv4 with address 71.20.10.155.
Dec 18 16:20:18 paul-laptop avahi-daemon[750]: New relevant interface eth1.IPv4 for mDNS.
Dec 18 16:20:18 paul-laptop avahi-daemon[750]: Registering new address record for 71.20.10.155 on eth1.IPv4.
Dec 18 16:20:19 paul-laptop NetworkManager: <info> Policy set 'Auto eth1' (eth1) as default for routing and DNS.

Dec 18 16:20:43 paul-laptop kernel: [ 541.589590] usb 2-1: USB disconnect, address 5
Dec 18 16:20:43 paul-laptop kernel: [ 541.589807] eth1: unregister 'cdc_ether' usb-0000:00:1d.7-1, CDC Ethernet Device
Dec 18 16:20:43 paul-laptop NetworkManager: <info> (eth1): carrier now OFF (device state 8, deferring action for 4 seconds)
Dec 18 16:20:43 paul-laptop avahi-daemon[750]: Interface eth1.IPv4 no longer relevant for mDNS.
Dec 18 16:20:43 paul-laptop avahi-daemon[750]: Leaving mDNS multicast group on interface eth1.IPv4 with address 71.20.10.155.
Dec 18 16:20:43 paul-laptop dhclient: receive_packet failed on eth1: Network is down
Dec 18 16:20:43 paul-laptop NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/net/eth1, iface: eth1)
Dec 18 16:20:43 paul-laptop NetworkManager: <info> (eth1): now unmanaged
Dec 18 16:20:43 paul-laptop NetworkManager: <info> (eth1): device state change: 8 -> 1 (reason 36)
Dec 18 16:20:43 paul-laptop NetworkManager: <info> (eth1): deactivating device (reason: 36).
Dec 18 16:20:43 paul-laptop avahi-daemon[750]: Withdrawing address record for fe80::21d:88ff:fe53:2223 on eth1.
Dec 18 16:20:43 paul-laptop avahi-daemon[750]: Withdrawing address record for 71.20.10.155 on eth1.
Dec 18 16:20:43 paul-laptop NetworkManager: <info> (eth1): canceled DHCP transaction, dhcp client pid 1680
Dec 18 16:20:43 paul-laptop NetworkManager: <info> (eth1): cleaning up...

poe503 · #20 Post by **poe503** » Thu 19 Dec 2013, 00:57

(Here is the syslog from Puppy)

Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.223212] usb 1-1: new high-speed USB device number 3 using ehci_hcd
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.347416] usb 1-1: New USB device found, idVendor=198f, idProduct=e160
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.347425] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.347431] usb 1-1: Product: Beceem CDR
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.347435] usb 1-1: Manufacturer: Beceem Communications
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.347440] usb 1-1: SerialNumber: xxxx
Dec 18 16:38:43 puppypc1249 user.debug kernel: [ 1580.353611] usb-storage: device found at 3
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.353648] scsi2 : usb-storage 1-1:2.0
Dec 18 16:38:43 puppypc1249 user.debug kernel: [ 1580.353764] usb-storage: waiting for device to settle before scanning
Dec 18 16:38:43 puppypc1249 user.info kernel: [ 1580.353880] usb 1-1: USB disconnect, device number 3
Dec 18 16:38:44 puppypc1249 user.info kernel: [ 1581.279879] usb 1-1: new high-speed USB device number 4 using ehci_hcd
Dec 18 16:38:44 puppypc1249 user.warn kernel: [ 1581.423612] usb 1-1: config 1 has 2 interfaces, different from the descriptor's value: 3
Dec 18 16:38:44 puppypc1249 user.info kernel: [ 1581.424101] usb 1-1: New USB device found, idVendor=198f, idProduct=8160
Dec 18 16:38:44 puppypc1249 user.info kernel: [ 1581.424108] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Dec 18 16:38:44 puppypc1249 user.info kernel: [ 1581.424114] usb 1-1: Product: UBEE Stick
Dec 18 16:38:44 puppypc1249 user.info kernel: [ 1581.424118] usb 1-1: Manufacturer: Beceem Communications
Dec 18 16:38:44 puppypc1249 user.info kernel: [ 1581.424122] usb 1-1: SerialNumber: USB Serial No xxxx
Dec 18 16:38:45 puppypc1249 daemon.debug dhcpcd[8305]: eth0: using hwaddr xxxx
Dec 18 16:38:45 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
Dec 18 16:38:45 puppypc1249 user.info kernel: [ 1581.951849] cdc_ether 1-1:1.0: eth0: register 'cdc_ether' at usb-0000:00:1d.7-1, CDC Ethernet Device, xxxx
Dec 18 16:38:45 puppypc1249 user.info kernel: [ 1581.953896] usbcore: registered new interface driver cdc_ether
Dec 18 16:38:45 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Dec 18 16:38:49 puppypc1249 daemon.info dhcpcd[8305]: eth0: carrier acquired
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: using hwaddr xxxx
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: discarding expired lease
Dec 18 16:38:49 puppypc1249 daemon.info dhcpcd[8305]: eth0: broadcasting for a lease
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending DISCOVER (xid 0xf3773f6c), next in 4.41 seconds
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: discarding expired lease
Dec 18 16:38:49 puppypc1249 daemon.info dhcpcd[8305]: eth0: broadcasting for a lease
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending DISCOVER (xid 0x1f4bb67a), next in 8.77 seconds
Dec 18 16:38:49 puppypc1249 daemon.info dhcpcd[8305]: eth0: carrier lost
Dec 18 16:38:49 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Dec 18 16:38:53 puppypc1249 daemon.info dhcpcd[8305]: eth0: carrier acquired
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: using hwaddr xxxx
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: discarding expired lease
Dec 18 16:38:53 puppypc1249 daemon.info dhcpcd[8305]: eth0: broadcasting for a lease
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending DISCOVER (xid 0x214caecd), next in 3.59 seconds
Dec 18 16:38:53 puppypc1249 daemon.info dhcpcd[8305]: eth0: offered 192.168.14.2 from 192.168.14.1
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending REQUEST (xid 0x214caecd), next in 4.20 seconds
Dec 18 16:38:53 puppypc1249 daemon.info dhcpcd[8305]: eth0: acknowledged 192.168.14.2 from 192.168.14.1
Dec 18 16:38:53 puppypc1249 daemon.info dhcpcd[8305]: eth0: checking for 192.168.14.2
Dec 18 16:38:53 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP probe (1 of 3), next in 1.88 seconds
Dec 18 16:38:55 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP probe (2 of 3), next in 1.73 seconds
Dec 18 16:38:57 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
Dec 18 16:38:59 puppypc1249 daemon.info dhcpcd[8305]: eth0: leased 192.168.14.2 for 20 seconds
Dec 18 16:38:59 puppypc1249 daemon.debug dhcpcd[8305]: eth0: renew in 10 seconds, rebind in 17 seconds
Dec 18 16:38:59 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding IP address 192.168.14.2/24
Dec 18 16:38:59 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding route to 192.168.14.0/24
Dec 18 16:38:59 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding default route via 192.168.14.1
Dec 18 16:38:59 puppypc1249 daemon.debug dhcpcd[8305]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:38:59 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Dec 18 16:39:03 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
Dec 18 16:39:05 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (2 of 2)
Dec 18 16:39:09 puppypc1249 daemon.info dhcpcd[8305]: eth0: renewing lease of 192.168.14.2
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: rebind in 7 seconds, expire in 10 seconds
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending REQUEST (xid 0xc62bd61), next in 4.86 seconds
Dec 18 16:39:09 puppypc1249 daemon.info dhcpcd[8305]: eth0: acknowledged 192.168.14.2 from 192.168.14.1
Dec 18 16:39:09 puppypc1249 daemon.info dhcpcd[8305]: eth0: leased 192.168.14.2 for 20 seconds
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: renew in 10 seconds, rebind in 17 seconds
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding IP address 192.168.14.2/24
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason RENEW
Dec 18 16:39:09 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
Dec 18 16:39:11 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (2 of 2)
Dec 18 16:39:19 puppypc1249 daemon.info dhcpcd[8305]: eth0: renewing lease of 192.168.14.2
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: rebind in 7 seconds, expire in 10 seconds
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending REQUEST (xid 0x4d251a63), next in 3.44 seconds
Dec 18 16:39:19 puppypc1249 daemon.warn dhcpcd[8305]: eth0: NAK: from 192.168.14.1
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: deleting default route via 192.168.14.1
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: deleting route to 192.168.14.0/24
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: deleting IP address 192.168.14.2/24
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason NAK
Dec 18 16:39:19 puppypc1249 daemon.info dhcpcd[8305]: eth0: broadcasting for a lease
Dec 18 16:39:19 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending DISCOVER (xid 0x7ba70bbb), next in 4.28 seconds
Dec 18 16:39:21 puppypc1249 daemon.info dhcpcd[8305]: eth0: offered 71.20.10.155 from 192.168.14.1
Dec 18 16:39:21 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending REQUEST (xid 0x7ba70bbb), next in 4.81 seconds
Dec 18 16:39:21 puppypc1249 daemon.info dhcpcd[8305]: eth0: acknowledged 71.20.10.155 from 192.168.14.1
Dec 18 16:39:21 puppypc1249 daemon.info dhcpcd[8305]: eth0: checking for 71.20.10.155
Dec 18 16:39:21 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP probe (1 of 3), next in 1.23 seconds
Dec 18 16:39:22 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP probe (2 of 3), next in 1.29 seconds
Dec 18 16:39:24 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
Dec 18 16:39:26 puppypc1249 daemon.info dhcpcd[8305]: eth0: leased 71.20.10.155 for 60 seconds
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: renew in 30 seconds, rebind in 52 seconds
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding IP address 71.20.10.155/18
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: using Classless Static Routes
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding route to 71.20.0.0/18
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding route to 192.168.14.0/24
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:39:26 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Dec 18 16:39:30 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
Dec 18 16:39:32 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (2 of 2)
Dec 18 16:39:56 puppypc1249 daemon.info dhcpcd[8305]: eth0: renewing lease of 71.20.10.155
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: rebind in 22 seconds, expire in 30 seconds
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending REQUEST (xid 0x975d6e67), next in 3.54 seconds
Dec 18 16:39:56 puppypc1249 daemon.info dhcpcd[8305]: eth0: acknowledged 71.20.10.155 from 192.168.14.1
Dec 18 16:39:56 puppypc1249 daemon.info dhcpcd[8305]: eth0: leased 71.20.10.155 for 60 seconds
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: renew in 30 seconds, rebind in 52 seconds
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: adding IP address 71.20.10.155/18
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: using Classless Static Routes
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason RENEW
Dec 18 16:39:56 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (1 of 2), next in 2.00 seconds
Dec 18 16:39:58 puppypc1249 daemon.debug dhcpcd[8305]: eth0: sending ARP announce (2 of 2)

Dec 18 16:40:15 puppypc1249 user.info kernel: [ 1671.996439] usb 1-1: USB disconnect, device number 4
Dec 18 16:40:15 puppypc1249 user.info kernel: [ 1671.996621] cdc_ether 1-1:1.0: eth0: unregister 'cdc_ether' usb-0000:00:1d.7-1, CDC Ethernet Device
Dec 18 16:40:15 puppypc1249 daemon.info dhcpcd[8305]: eth0: carrier lost
Dec 18 16:40:15 puppypc1249 daemon.debug dhcpcd[8305]: eth0: deleting route to 192.168.14.0/24
Dec 18 16:40:15 puppypc1249 daemon.debug dhcpcd[8305]: eth0: deleting route to 71.20.0.0/18
Dec 18 16:40:15 puppypc1249 daemon.debug dhcpcd[8305]: eth0: deleting IP address 71.20.10.155/18
Dec 18 16:40:15 puppypc1249 daemon.err dhcpcd[8305]: del_address: No such device
Dec 18 16:40:15 puppypc1249 daemon.debug dhcpcd[8305]: eth0: executing `/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Dec 18 16:40:15 puppypc1249 user.err kernel: [ 1672.065903] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev-eth0 instead
Dec 18 16:40:19 puppypc1249 daemon.err dhcpcd[8305]: manage_link: No such device or address
Dec 18 16:40:19 puppypc1249 daemon.info dhcpcd[8305]: eth0: removing interface

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Wimax connection problem (Solved)

Wimax connection problem (Solved)

Re: Wimax connection problem