Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Temporary or permanent solution to "listen socket bind failure"?
- After getting stuck at the above error and without external input, I read more manuals than one would ever want to do. Linux man are not the easiest and most entertaining pieces to read and understand.
- However, before getting into modifying certain files mentioned in the manuals, I tried another approach because I had seen an inet address in one of my lsof -i results that looked very similar to the inet address shown in the Sprint4GDeveloperPackxxx.
- In my uncuccessful attempts to connect to wimax I had used the inet address 192.168.1.100 and related sub-addresses.
- Today I replaced it with:
- 169.254.0.0.
- (That is similar to the inet address shown in the above Sprint instructions and a connection address revealed by lsof -i earlier today while the 3G part of U600 was running)
- It gives eth1:
- eth1 Link encap:Ethernet HWaddr f4:63:49:xx:xx:
- inet addr:169.254.0.0 Bcast:169.254.255.255 Mask:255.255.0.0 <-----------------
- inet6 addr: fe80::f663:49ff:fe07:279d/64 Scope:Link
- 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)
- Thereafter:
- wimaxd server started.
- Then: wimaxc -i, which results in > search
- Search returns:
- Network search returned 0 base stations. <-----------------------------------
- So far, so good.
- CLI sudo lsof -i gives among many others:
- wimaxd 27428 root 5u IPv4 141276 0t0 TCP localhost:5200 (LISTEN) <-------------
- This time there is even the correct port 5200.
- We will see what happens when I connect the external antenna sometimes this weekend.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement