Ok hang on. I think i have the answer. Give me a min to find it. Is that the original mbim.sh or the modified one?
The SECOND modified one. The one you linked to earlier today (not the first modified version in that other forum thread.)
Should I overwrite the current mbim.sh with the one included in that attachment? Or just add the files that are missing and reporting errors?
Going AFK for a few, got to make some lunch for the kids and then put them down for a nap.
I’m not really sure. It seems its only getting hung up on that one file so you might keep the same mbim for now. There are so many modified mbim.sh that I can’t keep track anymore. I would just trying all of them till one works. I think this is the latest one.
Ok directly from one of the people that put this all together.
The best “last” variant! Insert /lc/netifd/proto/mbim.sh the command “/etc/init.d/sessionhold.sh start”!
Attached /etc/init.d/sessionhold.sh, /home/reconn.sh, /home/loopback.sh and /lib/netifd/proto/mbim.sh
The mbim.sh You can also use. Clean up and contains all necessary calls.
For loopback.sh, adapt the forwarding to your server.
Important: Set all scripts to “executable” 775 or 777.
lteforum.at/attachments/reconnect-zip.6000/
Here is the link to his post lteforum.at/mobilfunk/cat-6- … te-65.html
Or if you want just use this mbim and it hasn’t been over modified. And i dont think you need all that other stuff with it
Wow…came back to a large amount of scripts to try.
Working my way down the list for a little while.
Sorry haha. I’m learning too myself.
Really wanted to try this one, but it seems like a dead link. Keeps timing out on me.
Strange. It works for me.
Go to this page. Do not translate it to english it will mess it up. The mbim.sh can be copy and pasted onto your mbim file.
Your right. It’s dead now. I asked them to update their stuff to the latest newest working setup. They may be in there doing it now.
Alrighty then…
The best mbim.sh for the Pi2B running OpenWRT 15.05.1 appears to be the first “try this mbim.sh” you sent a link over for today, combined with the rest of the scripts from:
I just keep getting the no servers found in /tmp/resolv.conf.auto error.
Drinking some rum now, because that always helps me not break things with my fists while troubleshooting. Still continuing to work on this… Going to do some internet research on this error…
Try Lede. Kernel 3.18 (from OpenWrt 15.05) does not have the latest fixes for the MC7455.
Runs on Pi 2 or 3?
in “/etc/config/network” section " config Interface ‘lan’ " enter or modify the following line:
Code:
option dns ‘8.8.8.8 8.8.4.4’
in “/etc/config/dhcp” in section “dnsmasq” enter or modify the following lines:
Code:
list server=8.8.8.8
list server=8.8.4.4
Remove lines with “option resolvfile” !!
It will look like this with a # in front of the resolving
config dnsmasq
option domainneeded ‘1’
option boguspriv ‘1’
option localise_queries ‘1’
option rebind_protection ‘1’
option rebind_localhost ‘1’
option local ‘/ lan /’
option domain ‘lan’
option expand hosts ‘1’
option authoritative ‘1’
option readethers ‘1’
option lease file ‘/tmp/dhcp.leases’
# option resolvfile ‘/tmp/resolv.conf.auto’
option local service ‘1’
list server ‘8.8.8.8’
list server ‘8.8.4.4’
option nonwildcard ‘0’ [/ CODE]
This will change the server to google 8.8.8.8 and 8.8.4.4 instead of looking for what the network wants it to be. Google dns servers are better anyway
I bet you a dollar this fixes it!
Lede is the better choice. If the above doesn’t work You might do a lede firmware. That’s what I’ve had the best luck with.
But he did connect and it was all running except for the dns server so I think with the fix i just posted it will work.
But im not to smart with this stuff and the only reason I kinda know is i have asked all these questions before and im just repeating the answers from them.
Fs1 knows this stuff way better than I do.
F*CK YEAH! WORKING!
I ended up flashing the LEDE 4.4 Kernel on the Pi3. Added the modified mbim.sh script through SSH, and theother scripts packaged along with it AND…
It is peak usage time here right now (week night between 7-12p), so a little slower than normal, and I need to knock down the SNR on the cellular amplifier a little bit.
But ho-lee-phuck… it is done. Now, just to make an image of this SD card, just in case anything goes sideways while trying to change the Pi3 over to a ‘gateway-only’ interface to feed the WAN port on the router. Right now, the router is only serving as a repeater, with the Pi handling WAN access and DHCP.
Tears of joy, you guys…tears of joy.
Hmmm… although network wide, everything on port 80 is getting 4-5Mbs/s, any other port or protocol is getting throttled down to 60Kbs/s again, just like Windows 10 ICS set up. I’m thinking that T-Mobile is identifying networked components as “tethered” devices to their “registered” device (the MC7455.)
I’m thinking that adding an .OVPN tunnel config to LEDE to funnel all data through 256-bit AES over port 80 using UDP to an AirVPN server. That should prevent ANY throttling based upon protocol, and any deep packet inspection. More testing tomorrow on that front…
Tonight, I am taking a well diserved break. Thank you for all of your efforts WESTREM and FS1, I couldn’t have done this without you guys. I will be posting a thorough walk-through/how-to guide tomorrow, under a separate thread.