ICS with Extenders

[aeblank]

I have spent HOURS on this, and failed.

I recently lost my isp when they went out of business. Losers. I still don't know my next move, as all options are crappy.

For now, I'm using foxfi (pdanet) and my Android phone. I have an unlimited plan, so it is ok.

I want to use my always on media center computer to be the router and it's normal media center (4 tuners, 2 extenders) duties..

I've failed. To get ics to work, the nic ends up without a default route, which makes an unidentified network, which fails the extenders. If i put in a default route, i get extenders and no internet sharing.

I tried two nics, one for internet and one for extenders. Can't get the extenders to work in that situation either (more details on request).

So i have my old slow desktop doing ics, but I'm convinced my speeds will suffer cause of how slow it is. Plus the $ of another computer on all the time. Plus, now it's war.

So had anyone had ics with extenders on the same machine?

Thanks,
Andy

[Crash2009]

Why don't you buy a router that supports USB modem, flip the switch, plug your phone into the USB, and be done with it. All your other stuff will not be effected. RT-N56U can be had for as little as $45, maybe less if you look around.

http://www.amazon.com/dp/B0049YQVHE/?ta ... 8bfg0ikr_e

[aeblank]

I will certainly read up on that router, but I don't think it's what I need.

I don't have a USB data card. I have an android phone with PDAnet. I've looked for a router that supports PDAnet.......that would be my DREAM. I even emailed pdanet to ask if there was such a router (no response yet, I think it was Friday).

I'm familiar with data cards and routers. I've had a cradlepoint router (multiples, even) and a data card. All have made their way to my parents, who use it all the time. The MBR1200 for at home, and the travel one for "camping".

So yeah.. Unless that router surprises me, any other ideas?


If you want to get complicated, I have a bandrich 4G router from Mispot, a now-defunct (GRRR) 4G internet provider. Since it is a high-gain panel antenna, I'd love to get a SIM and put it in there. I am considering at&t for that. Either getting a data card or getting a cheap android phone, pulling the SIM, etc. But the PDAnet fills the bill for the short term, till I figure out what/how to do the other stuff.

[Crash2009]

If it's of any use to you, here are the default 4 types of USB modems that an RT-N56U supports.

[Crash2009]

If you want to get complicated, I have a bandrich 4G router from Mispot, a now-defunct (GRRR) 4G internet provider. Since it is a high-gain panel antenna, I'd love to get a SIM and put it in there. I am considering at&t for that. Either getting a data card or getting a cheap android phone, pulling the SIM, etc.

Working on the Bandrich seems to be a more worthwhile project. PDAnet is nice bandaid, but it doesn't take the place of a cast.

[Crash2009]

I plugged my phone into the USB of the RT-N56U. Looks like if I had of left it alone for awhile, it might have negotiated a success or fingered the driver it needed. Our internet connection went down while Android and Asus were duke-ing it out. Wrong time of day for a test, so I removed it from the router. At first glance it looks like it will work.

The code below is from the Syslog of the router.

Code: Select all

Dec  7 17:13:27 kernel: usb 1-2: new high-speed USB device number 3 using rt3xxx-ehci
Dec  7 17:13:28 kernel: usb 1-2: New USB device found, idVendor=04e8, idProduct=6860
Dec  7 17:13:28 kernel: usb 1-2: Product: SAMSUNG_Android
Dec  7 17:13:28 kernel: usb 1-2: Manufacturer: SAMSUNG
Dec  7 17:13:28 kernel: usb 1-2: SerialNumber: ********
Dec  7 17:14:30 stop_wan(): raise DHCP release event
Dec  7 17:14:30 RT-N56U: wan down (eth3)
Dec  7 17:14:31 DHCP WAN Client: deconfig: lease is lost
Dec  7 17:14:31 kernel: eth3: ===> VirtualIF_close
Dec  7 17:14:31 kernel: cdc_acm 1-2:1.1: This device cannot do calls on its own. It is not a modem.
Dec  7 17:14:31 kernel: cdc_acm 1-2:1.1: ttyACM0: USB ACM device
Dec  7 17:14:31 kernel: usbcore: registered new interface driver cdc_acm
Dec  7 17:14:31 kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Dec  7 17:14:31 kernel: usbcore: registered new interface driver usbserial
Dec  7 17:14:31 kernel: usbcore: registered new interface driver usbserial_generic
Dec  7 17:14:31 kernel: USB Serial support registered for generic
Dec  7 17:14:31 kernel: usbserial: USB Serial Driver core
Dec  7 17:14:31 kernel: usbcore: registered new interface driver option
Dec  7 17:14:31 kernel: USB Serial support registered for GSM modem (1-port)
Dec  7 17:14:31 kernel: usbcore: registered new interface driver sierra
Dec  7 17:14:31 kernel: USB Serial support registered for Sierra USB modem
Dec  7 17:14:33 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload [WAN]<->[LAN]
Dec  7 17:14:33 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Dec  7 17:14:33 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Dec  7 17:14:33 kernel: eth3: ===> VirtualIF_open
Dec  7 17:14:33 RT-N56U: select RAS modem interface ttyACM0 to pppd
Dec  7 17:14:34 pppd[11568]: pppd 2.4.5 started by asus, uid 0
Dec  7 17:14:45 comgt: ERROR: CONNECT TIMEOUT!
Dec  7 17:14:45 pppd[11568]: Connect script failed
Dec  7 17:15:08 comgt: ERROR: CONNECT TIMEOUT!
Dec  7 17:15:08 pppd[11568]: Connect script failed
Dec  7 17:15:31 comgt: ERROR: CONNECT TIMEOUT!
Dec  7 17:15:31 pppd[11568]: Connect script failed
Dec  7 17:15:53 pppd[11568]: Child process /bin/comgt -d /dev/ttyACM0 -s /etc_ro/ppp/3g/Generic_conn.scr (pid 11745) terminated with signal 15
Dec  7 17:15:53 pppd[11568]: Connect script failed
Dec  7 17:15:54 pppd[11568]: Exit.
Dec  7 17:15:54 kernel: eth3: ===> VirtualIF_close
Dec  7 17:15:54 kernel: usbcore: deregistering interface driver cdc_acm
Dec  7 17:15:54 kernel: USB Serial deregistering driver Sierra USB modem
Dec  7 17:15:54 kernel: usbcore: deregistering interface driver sierra
Dec  7 17:15:54 kernel: USB Serial deregistering driver GSM modem (1-port)
Dec  7 17:15:54 kernel: usbcore: deregistering interface driver option
Dec  7 17:15:54 kernel: USB Serial deregistering driver generic
Dec  7 17:15:54 kernel: usbcore: deregistering interface driver usbserial_generic
Dec  7 17:15:54 kernel: usbcore: deregistering interface driver usbserial

[Crash2009]

Found it.

http://support.asus.com/Search/KDetail. ... FB48E4&t=2

How to share network of Android mobile phone to the router(USB 3G tethering)
--------------------------------------------------------------------------------
Page Tools Print this page
Email this page


Solution
Using 3G/4G Tethering allows sharing the Internet connection of Internet-connected mobile phone with other devices connect to the router. Insert the phone with router through USB cable, connection of other devices connected to the router with the phone can be done over wired LAN/wireless LAN (Wi-Fi). The combination of Internet-connected mobile phone and the router thus act as a portable wireless access point for devices connected to it. Noticed that if you connect both WAN and the mobile phone, the default is using WAN to Internet while failover is the mobile phone.


Step1. Mobile phone settings (Android)
Before continuing, you will need to set up your mobile phone;
1. Setting up USB PC connection as Media device (MTP) mode.
hspace=0
2. Enable USB Tethering: Settings→More settings→Tethering and portable hotspot→Enable USB tethering
hspace=0


Step2. Router settings
Connect the Android mobile to the router; you will need to set up:
A. Connect LAN to your computer.
B. Update the firmware to version 3.0.0.4.268 or later.
C. Connect mobile device and router via USB port. When use 4G/LTE, using the USB extension cable to have at least 50 cm distance between the router and the mobile for best performance.
hspace=0
D. Now using your Android mobile phone as 3G/4G USB modem is working. Launch the setting page http://192.168.1.1, Network Map status is changed.
hspace=0

[aeblank]

Yeah, I know. I just want to best it, at this point.

[aeblank]

Ooo, needed to refresh before replying. Off to read. Thanks!

[aeblank]

Aaah crap. I don't pay for a hotspot, so I can't enable that USB tether.

[aeblank]

That router seems awesome though. Not to familiar with Asus.....

[Crash2009]

That router seems awesome though. Not to familiar with Asus.....

It's a 2012 model, Ralink chip-so NO DD-WRT, when it first came out Asus had some trouble with their firmware so I've been using the Russian Firmware ever since-Padovan http://code.google.com/p/rt-n56u/

I'm not trying to sell router's or brag up Asus. Just suggesting a feature that you might want to get, when you look for something different. When you explained the problem you were having, my first thought was, ICS I haven't used that since 1998 and I think I had to use a hub, USB 3G tethering should work for you without having to tear down what you have built.

[aeblank]

I can't enable USB tethering though (Verizon unlimited plan). I wonder if it would work with easytether or foxfi/pdanet or similar. It seems SO SO close.

[Crash2009]

Just to let you know, I had to enable USB tethering and Hotspot. Hotspot is the one that acts like ICS and allows my entire list (27) of DHCP clients access. As soon as I saw the new IP for Crash2009.com I knew it was working, well at least from the router out. Still haven't had time to push one of the clients through the router, but that should be the easy part.

Code: Select all

Dec  8 14:56:08 detect_link: WAN link down detected!
Dec  8 15:02:12 stop_wan(): raise DHCP release event
Dec  8 15:02:12 RT-N56U: wan down (eth3)
Dec  8 15:02:12 DHCP WAN Client: deconfig: lease is lost
Dec  8 15:02:13 kernel: eth3: ===> VirtualIF_close
Dec  8 15:02:13 kernel: usbcore: deregistering interface driver cdc_acm
Dec  8 15:02:13 kernel: USB Serial deregistering driver GSM modem (1-port)
Dec  8 15:02:13 kernel: usbcore: deregistering interface driver option
Dec  8 15:02:14 kernel: usbcore: registered new interface driver cdc_ether
Dec  8 15:02:14 kernel: rndis_host 1-2:1.0: weth0: register 'rndis_host' at usb-rt3xxx-ehci-2, RNDIS device, 02:02:07:50:33:37
Dec  8 15:02:14 kernel: usbcore: registered new interface driver rndis_host
Dec  8 15:02:14 kernel: usbcore: registered new interface driver cdc_wdm
Dec  8 15:02:14 kernel: usbcore: registered new interface driver qmi_wwan
Dec  8 15:02:14 kernel: usbcore: registered new interface driver cdc_ncm
Dec  8 15:02:14 kernel: usbcore: registered new interface driver cdc_mbim
Dec  8 15:02:14 kernel: usbcore: registered new interface driver sierra_net
Dec  8 15:02:14 kernel: usbcore: registered new interface driver option
Dec  8 15:02:14 kernel: USB Serial support registered for GSM modem (1-port)
Dec  8 15:02:16 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload [WAN]<->[LAN]
Dec  8 15:02:16 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Dec  8 15:02:16 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Dec  8 15:02:16 kernel: eth3: ===> VirtualIF_open
Dec  8 15:02:16 DHCP WAN Client: starting on weth0 ...
Dec  8 15:02:18 RT-N56U: wan up (weth0)
Dec  8 15:02:19 dnsmasq[762]: read /etc/hosts - 27 addresses
Dec  8 15:02:19 dnsmasq[762]: read /etc/storage/dnsmasq/hosts - 0 addresses
Dec  8 15:02:19 dnsmasq-dhcp[762]: read /etc/ethers - 24 addresses
Dec  8 15:02:19 dnsmasq[762]: using nameserver 192.168.42.129#53
Dec  8 15:02:19 inadyn[14046]: Inadyn version 1.99.2 -- Dynamic DNS update client.
Dec  8 15:02:19 DHCP WAN Client: bound (weth0), IP: 192.168.42.201, GW: 192.168.42.129, lease time: 3600
Dec  8 15:02:19 inadyn[14046]: Resolving hostname Crash2009.XXX.com => IP# 71.XXX.XXX.XXX
Dec  8 15:02:19 inadyn[14046]: Checking for IP# change, connecting to checkip.dyndns.org(91.198.22.70)

Dec  8 15:11:15 stop_wan(): raise DHCP release event
Dec  8 15:11:16 kernel: eth3: ===> VirtualIF_close
Dec  8 15:11:16 kernel: usbcore: deregistering interface driver cdc_acm
Dec  8 15:11:16 kernel: USB Serial deregistering driver GSM modem (1-port)
Dec  8 15:11:16 kernel: usbcore: deregistering interface driver option
Dec  8 15:11:17 kernel: usbcore: registered new interface driver cdc_ether
Dec  8 15:11:17 kernel: rndis_host 1-2:1.0: weth0: register 'rndis_host' at usb-rt3xxx-ehci-2, RNDIS device, 02:02:07:50:33:37
Dec  8 15:11:17 kernel: usbcore: registered new interface driver rndis_host
Dec  8 15:11:17 kernel: usbcore: registered new interface driver cdc_wdm
Dec  8 15:11:17 kernel: usbcore: registered new interface driver qmi_wwan
Dec  8 15:11:17 kernel: usbcore: registered new interface driver cdc_ncm
Dec  8 15:11:17 kernel: usbcore: registered new interface driver cdc_mbim
Dec  8 15:11:17 kernel: usbcore: registered new interface driver sierra_net
Dec  8 15:11:17 kernel: usbcore: registered new interface driver option
Dec  8 15:11:17 kernel: USB Serial support registered for GSM modem (1-port)
Dec  8 15:11:19 RT-N56U: Hardware NAT/Routing: Enabled, IPoE/PPPoE offload [WAN]<->[LAN]
Dec  8 15:11:19 RT-N56U: Hardware NAT/Routing: IPv4 UDP flow offload - OFF
Dec  8 15:11:19 RT-N56U: Hardware NAT/Routing: IPv6 routes offload - OFF
Dec  8 15:11:19 kernel: eth3: ===> VirtualIF_open
Dec  8 15:11:19 dnsmasq[762]: read /etc/hosts - 27 addresses
Dec  8 15:11:19 dnsmasq[762]: read /etc/storage/dnsmasq/hosts - 0 addresses
Dec  8 15:11:19 dnsmasq-dhcp[762]: read /etc/ethers - 24 addresses
Dec  8 15:11:19 dnsmasq[762]: using nameserver 8.8.4.4#53
Dec  8 15:11:19 dnsmasq[762]: using nameserver 8.8.8.8#53
Dec  8 15:11:19 DHCP WAN Client: starting on weth0 ...
Dec  8 15:11:19 RT-N56U: wan up (weth0)
Dec  8 15:11:20 inadyn[14747]: Inadyn version 1.99.2 -- Dynamic DNS update client.
Dec  8 15:11:20 DHCP WAN Client: bound (weth0), IP: 192.168.42.201, GW: 192.168.42.129, lease time: 3600
Dec  8 15:11:20 inadyn[14747]: Resolving hostname Crash2009.XXX.com => IP# 71.XXX.XXX.XXX
Dec  8 15:11:20 inadyn[14747]: Checking for IP# change, connecting to checkip.dyndns.org(216.146.38.70)
Dec  8 15:11:20 inadyn[14747]: Update needed for alias Crash2009.XXX.com, new IP# 166.XXX.XXX.XXX
Dec  8 15:11:20 inadyn[14747]: Sending IP# update to DDNS server, connecting to ns1.XXX.com(103.10.4.108)
Dec  8 15:11:21 inadyn[14747]: Successful alias table update for Crash2009.XXX.com => new IP# 166.XXX.XXX.XXX
Dec  8 15:11:22 dnsmasq[762]: read /etc/hosts - 27 addresses
Dec  8 15:11:22 dnsmasq[762]: read /etc/storage/dnsmasq/hosts - 0 addresses
Dec  8 15:11:22 dnsmasq-dhcp[762]: read /etc/ethers - 24 addresses
Dec  8 15:11:22 dnsmasq[762]: using nameserver 8.8.4.4#53
Dec  8 15:11:22 dnsmasq[762]: using nameserver 8.8.8.8#53
Dec  8 15:11:28 NTP Scheduler: Synchronizing time to pool.ntp.org.

[aeblank]

It's just us, but I got the unlock codes from my old ISP for the bandrich. She said one other person was successful at doing this.

[Crash2009]

3rd place is better than last.....

[aeblank]

So, went to att, paid through my butt, and got a 10gig, data only plan. Dug out the ladders, swapped out the Sim in the bandrich. Seemed to connect after unlocking. Struggled at first, cause I had my own DNS set, and at doesn't seem to allow that (grrrrrr). That said, it's working and I have good signal, I think. -70db.

I'd still love to find a router that works with foxfi though. Maybe the Asus. Been going to email their customer support, just need time.