What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ASUS AC66U + Huawei e3272 connection problems

Shadovv

New Around Here
ASUS AC66U + Huawei e3272 conflicting IP problems

Hi everyone,

First time posting here but I'm in desperate need of help! :(
Namely I'm having serious problems to configure either ASUS RT AC66U or ASUS DSL-N55U (own both of them) with my USB dongle: hi-link version Hauwei E3272 (firmware version: 22.436.07.04.1202)

Both the router and USB dongle share the same IP address 192.168.1.1. Dongle on its own works perfectly but if I plug it into the asus router it does not connect to 4G network automatically.

I have tried various settings for the router to utilize the USB dongle but nothing works (ISP: Orange Poland) and only workaround I could find is using an older firmware version for the ASUS DSL-N55U - 3.0.0.4.374_4422-gc83c78f, which frees up 192.168.1.1 after I move my LAN network and router IPs to 192.168.3.x. It's not perfect but at least this way I'm able to access the dongle web interface via browser and can input the needed PIN manually.

Now when I use either ASUS RT AC66U or ASUS DSL-N55U with a newer firmware version IP: 192.168.1.1 is always reserved by the router and takes me to a separate page informing me that the ASUS Router IP has changed and I need to use the proper one in order to connect.

Question: any ideas how to make the E3272 connect automatically to 4g network via an ASUS Router or at least stop the router from hijacking 192.168.1.1 so I can access the dongle web-ui manually?

Device name: E3272
Hardware version: CH1E3272SM
Software version: 22.436.07.04.1202
Web UI version: 13.100.04.06.1202
WAN IP Address: 10.234.95.160
IP address: 192.168.1.1
Subnet mask: 255.255.255.0
RSSI: -65dBm
RSRP: -89dBm
NetWork: LTE

Thank you in advance for your help since I spent countless hours trying out different settings with no success.
 
Last edited:
Anyone have some guidance on this?

I would be very happy if I could finally use my ASUS AC66U + Huawei e3272 an be able to access the dongle web interface on 192.168.1.1 without the router intercepting it and informing me that the router IP has been changed.
 
Last edited:
...without the router intercepting it and informing me that the router IP has been changed.

Did you try to clear the cache of your browser? Perhaps that could help...

Ciao
Gerald
 
Did you try to clear the cache of your browser? Perhaps that could help...

Ciao
Gerald

Thanks for the replay Gerald.

Yes, I have tried doing that and it only happens with the new firmware where I'm taken to an "error page" informing me of the new IP configuration.

It seems that although the router is 192.168.3.1 it is not "letting go" of the standard 192.168.1.1, which again would allow me to get through to my usb dongle manually. Doh!
 
Thanks for the replay Gerald.

Yes, I have tried doing that and it only happens with the new firmware where I'm taken to an "error page" informing me of the new IP configuration.

It seems that although the router is 192.168.3.1 it is not "letting go" of the standard 192.168.1.1, which again would allow me to get through to my usb dongle manually. Doh!

By the way I'm getting this message every time on 192.168.1.1, although the router has been reconfigured to 192.168.3.1:

http://jdrch.wordpress.com/2013/10/...n-the-asus-rt-n66u-how-to-fix-it-if-you-have/

rt-n66u-2013-10-01-18-40-41.png
 
By the way I'm getting this message every time on 192.168.1.1, although the router has been reconfigured to 192.168.3.1:

http://jdrch.wordpress.com/2013/10/...n-the-asus-rt-n66u-how-to-fix-it-if-you-have/

rt-n66u-2013-10-01-18-40-41.png

That's because the offline data for 192.168.1.1 is still cached by your router. Search the forums on how to erase offline data (that's different from your browser cache), there has been a few posts over the months showing how to do it with various browsers.

I have no idea what this blogger is talking about, because https does work fine. My first guess is that he forgot to specify the port when connecting over https, so he got the offline cached error page. That's not a router issue, that's an end-user issue.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top