1
General Discussion / Re: Firewall configuration and gotify android application
« on: January 06, 2023, 10:54:56 am »
Any ideas ? 
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
General Discussion / Firewall configuration and gotify android application
« on: January 05, 2023, 12:05:50 am »
Hi
I have a gotify application configured in a docker with OPNSense on a router.
I've added a port forwarding (in attachment)
and rule was automatically created on WAN interface (in attachment)
I'm using WAN IP, because I need it usually outside of my local network.
but I'm still getting errors in application:
Caused by: java.net.SocketTimeoutException. failed to connecto to /myWanIP (port appPort) from /phoneIp (port 37344)
I've noticed that port 37344 is generated - sometimes is different.
I'm having problem with connectivity - it takes few seconds, but the most irritating is pushing mesages. I have to try few times till it sends because "Oops something went wrong" appears.
Can you provide what should be additionally configured in firewall? Some additional ports has to be opened?
Thanks in advance.
I have a gotify application configured in a docker with OPNSense on a router.
I've added a port forwarding (in attachment)
and rule was automatically created on WAN interface (in attachment)
I'm using WAN IP, because I need it usually outside of my local network.
but I'm still getting errors in application:
Caused by: java.net.SocketTimeoutException. failed to connecto to /myWanIP (port appPort) from /phoneIp (port 37344)
I've noticed that port 37344 is generated - sometimes is different.
I'm having problem with connectivity - it takes few seconds, but the most irritating is pushing mesages. I have to try few times till it sends because "Oops something went wrong" appears.
Can you provide what should be additionally configured in firewall? Some additional ports has to be opened?
Thanks in advance.
3
22.1 Legacy Series / Re: Issue with Suricata and interface
« on: July 06, 2022, 10:39:47 pm »
Hi,
Is this issue solved?
Is this issue solved?
4
22.1 Legacy Series / Re: Issue with Suricata and interface
« on: May 12, 2022, 09:19:48 pm »
Hi,
I have such issue on 22.1.7_1
Updated from version 21.7.8
When suricata is is activated "link state changed to down/up" and "arpresolver: cannot allocate llinfo for xxx.xxx.xxx.xxx on em0" is constantly occuring, it's not a problem.
But the strangest thing - router became unstable, GUI unaccessible because computer is loosing wifi connection when intrusion detection is enabled.
Everything disappear when suricata is disabled.
Is it possible that IDS cause such problems?
I have such issue on 22.1.7_1
Updated from version 21.7.8
When suricata is is activated "link state changed to down/up" and "arpresolver: cannot allocate llinfo for xxx.xxx.xxx.xxx on em0" is constantly occuring, it's not a problem.
But the strangest thing - router became unstable, GUI unaccessible because computer is loosing wifi connection when intrusion detection is enabled.
Everything disappear when suricata is disabled.
Is it possible that IDS cause such problems?
5
22.1 Legacy Series / Re: 22.1 Clean Install Console Output
« on: May 12, 2022, 09:06:16 pm »
Hello,
Any updates?
Issue exists on 22.1.7_1
Updated from version 21.7.8
The same issue and fix - when MAC address for WAN is changed - "link state changed to down/up" and "arpresolver: cannot allocate llinfo for xxx.xxx.xxx.xxx on em0" stops occuring and router became stable and accessible when intrusion detection is disabled.
GUI is unusable when IDS is active - I had to turn it off from /conf/config.xml.
Any updates?
Issue exists on 22.1.7_1
Updated from version 21.7.8
The same issue and fix - when MAC address for WAN is changed - "link state changed to down/up" and "arpresolver: cannot allocate llinfo for xxx.xxx.xxx.xxx on em0" stops occuring and router became stable and accessible when intrusion detection is disabled.
GUI is unusable when IDS is active - I had to turn it off from /conf/config.xml.
6
19.7 Legacy Series / Re: 4G (PPP) - Not working after update from 18.7
« on: September 05, 2019, 11:11:23 pm »
I started digging manually with commands and I've noticed interesting behavior:
- first I've disabled interface with modem to unlock cuaU0.1
- run command cu -l /dev/cuaU0.1
- run command: AT+CGACT=1,1
and then a light on modem stop blinking and start shining.
Unfortunately I don't know how to check if it's really connected.
- first I've disabled interface with modem to unlock cuaU0.1
- run command cu -l /dev/cuaU0.1
- run command: AT+CGACT=1,1
and then a light on modem stop blinking and start shining.
Unfortunately I don't know how to check if it's really connected.
7
19.7 Legacy Series / Re: 4G (PPP) - Not working after update from 18.7
« on: September 05, 2019, 05:35:44 pm »
Hi,
I have the same issue with the same modem on 19.7.3.
It responses properly on commands:
root@OPNsense:~ # cu -l /dev/cuaU0.1
Connected
+CFUN: 1
OK
+CPIN: READY
but it doesn't connect
About modem:
Manufacturer: huawei
Model: E3372
Revision: 21.200.07.00.805
IMEI: 86***
+GCAP: +CGSM,+DS,+ES
I have the same issue with the same modem on 19.7.3.
It responses properly on commands:
root@OPNsense:~ # cu -l /dev/cuaU0.1
Connected
+CFUN: 1
OK
+CPIN: READY
but it doesn't connect
About modem:
Manufacturer: huawei
Model: E3372
Revision: 21.200.07.00.805
IMEI: 86***
+GCAP: +CGSM,+DS,+ES
8
19.1 Legacy Series / Modem Huawei E3372H
« on: July 09, 2019, 05:44:38 pm »
Has anyone started Huawei e3372h in OPNsense 19.1.4-amd64?
I'm still getting:
Code: [Select]
CHAT: The modem is not responding to "AT" at ModemCmd: label.
I have modem in "stick" mode.
I've updated init string with: "&F&C1&D2E0S0=0", also "Z", "F" or empty.
It looks like init string wasn't changed and used in new configuration.
I've changed init string in PFSense with "&F&C1&D2E0S0=0" and it started working.
Any ideas what should be additionaly changed/checked in OpnSense?
I'm still getting:
Code: [Select]
CHAT: The modem is not responding to "AT" at ModemCmd: label.
I have modem in "stick" mode.
I've updated init string with: "&F&C1&D2E0S0=0", also "Z", "F" or empty.
It looks like init string wasn't changed and used in new configuration.
I've changed init string in PFSense with "&F&C1&D2E0S0=0" and it started working.
Any ideas what should be additionaly changed/checked in OpnSense?
9
19.1 Legacy Series / Re: USB LTE modem - E3372
« on: July 07, 2019, 12:10:47 pm »
Anybody had similar problem?
10
19.1 Legacy Series / Re: USB LTE modem - E3372
« on: July 05, 2019, 03:17:52 pm »
Hi,
I don't want to create new topic, so I put it here.
I have similar problem with Huawei e3372h in OPNsense 19.1.4-amd64
I'm still getting:
I've updated init string with: "&F&C1&D2E0S0=0", also "Z", "F" or empty.
It looks like init string wasn't changed and used in new configuration.
I've changed init string in PFSense with "&F&C1&D2E0S0=0" and it started working.
Any ideas?
I don't want to create new topic, so I put it here.
I have similar problem with Huawei e3372h in OPNsense 19.1.4-amd64
I'm still getting:
Code: [Select]
CHAT: The modem is not responding to "AT" at ModemCmd: label.
I have modem in "stick" mode.I've updated init string with: "&F&C1&D2E0S0=0", also "Z", "F" or empty.
It looks like init string wasn't changed and used in new configuration.
I've changed init string in PFSense with "&F&C1&D2E0S0=0" and it started working.
Any ideas?
Pages: [1]