Messages

[cuaU0.0]

Hi!

So I got a Huawei E3372 connected but I can't get it to work after updating from 18.7.

Error in dashbord is: "4G - None, No Service Mode".

When setting it up on 18.7 I used CU to determine what modem port to use (cuaU0.0) and get correct reply when verifying that SIM card does not have PIN enabled (I have screenshots of this).

On 19.7 I ran CU again and now I only get "OK" and "READY" responses from cuaU0.1(!).

I've tried both for connection and I get the following error responses in Point-to-point -> Log File:

cuaU0.0: ppp: [opt2_link0] CHAT: The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1" at ModemCmd: label.

cuaU0.1: ppp: [opt2_link0] CHAT: The modem is not responding to any ATI[1,3-5,8] commands.

I've done some googling and also tested different Init string to no avail.

I would greatly appreciate any help with resolving this issue.

Cheers
-- Paranoid Android

Thanks a lot for your comprehensive answer! I have been very busy the last few days so I haven't been able to test reverse route yet. Will look into it and (hopefully) figure it out.

Thanks again!

Thank you for responding hbc - I appreciate it :)

I am doing "real routing" in router2 (Dual NAT?), and I don't believe that I am having a reverse route configured on OPNsense. How can I verify this? Sorry; I am just an amateur so I don't have much experience with networking.

I attached a network topology map to ensure that you know what I am talking about. The issues is that the "light blue" clients on the left hand side cannot reach the "light green" ones to the far right.

I've seen others on here upload their OPNsense network configuration. is that something which would be beneficial? If so, how should I do it without exposing any personal information? :)

Hi!

So I have a (hopefully) simple question.

I have my system configured like this:
- OPNsense (with clients on range 192.168.0.2-100).
- One of those IP's is another router; "Router2", which has additional clients connected in the range 10.0.0.2->10.0.0.100).

From clients connected to Router2 I can hit my OPNsense-router control-panel/SSH, but I cannot SSH into any clients connected to OPNsense (example: 192.168.1.50) via LAN.

If I hit my WAN-IP (from my Router2-client) on a forwarded port to 192.168.1.50 I can get it... But that's pretty inconvenient.

Is there a simple FW-LAN rule to add to allow LAN-traffic coming from Router2 (10.0.0.x-range) to OPNsense clients (192.168.1.x?).


PS: I set the system up with two subnets like this to disallow traffic from 192.168.1.x being able to see clients connected to Router2 (10.0.0.x). I.e I can ping 192.168.1.50 from 10.0.0.3 but not the other way around.

Would greatly appreciate any input :)

Ok. I have started working on this.

I have completed steps 1,2,3 and 5 (not 4!) in the Multiple-WAN wiki...

As I mention I run a webserver (using port 443 on a local machine), and when I do step 4 (amend IPv4 "Default allow LAN to any rule" to use the new gateway access to the webserver from the outside is suspended (immediately).

I.e trying to navigate to the page just times out. The second I revert to "default" gateway the problem is alleviated.

Any ideas? :)

Hi everyone!

I've been using OPNsense now for.... almost a day, and so far I am very impressed!

To put all the cards on the table starting out; I'm not an IT-professional and have not really spent a lot of time setting up networks and stuff. I have gotten the initial setup done, but setting up WAN-failover to my 4G-USB-dongle seems like a tall order right now.

I have previously successfully used this with an ASUS home router, so I know the basics, but after reading the Multi-WAN wiki I'm not really that keen on trying this myself (it seems like there are many ways to get this wrong)...

What complicates this slightly is that I run a few web servers behind this router, so downtime in excess of a few minutes is not... Desirable...

I have connected the 4G dongle and it seems to be working fine.


What I would like to do is this:
- Set up failover from WAN to 4G if WAN-connection is lost.
- Switch back to WAN from 4G when WAN-connection is reestablished.
- Not use any kind of load balancing; 4G is metered while WAN is unlimited and much faster
- Set up some kind of DNS-service(?) which routes traffic to either WAN or 4G based on which connection is up (I have a website that points to my current IP. During a failover scenario my external IP would change to the 4G-IP-address (dynamic), and my website(s) should route the traffic accordingly.


The current setup looks like this:

Interfaces:
LAN
WAN
4G

Gateways:
- Single (WAN_DHCP)
- Group (NONE)

Firewall:
- LAN (IPv4 - Source: LAN net - "Default allow LAN to any rule)
- WAN (Port-forwarding rules associated with the web-servers)
- NAT: Outbound ("Automatic outbound NAT rule generation)
- Settings: Advanced (Reflection for port forwards ON, Automatic outbound NAT for reflection ON)

Services:
- DHCPv4 server on (192.168.1.0 / 255.255.255.0)
- Static mapping for 4 servers and my "home-router" (Ubiquity HD, providing networking for the family).
- Unbound DNS (DNSSEC ON, DHCP registration ON, DHCP Static Mappings ON)


Could someone please provide me with a step by step solution, keeping in mind that I'm not that knowledgeable in regards to networking? Again; I did take a look at the Multi-WAN wiki, but I'm not feeling too comfortable trying it out without some guidance.

Any help would be highly appreciated :)