Telegram bot not returning interaction for internal machine
-
Where are you testing from? A client on the same subnet?
Do you see states created for the traffic?
Are you policy routing, have gateways set on the rules?
The rules shown in your screen show show 0 state and 0 bytes on the counters so have never matched anything.
-
@stephenw10 thanks for reply.
Where are you testing from? A client on the same subnet?
Sorry, but I dont know if I understood the question, but the computer is in the LAN and my cellphone also, but the telegram server is on the Internet.Do you see states created for the traffic?
Yes.
Are you policy routing, have gateways set on the rules?
The gateway is the default. I have only one gateway. Should I change anything here?The rules shown in your screen show show 0 state and 0 bytes on the counters so have never matched anything.
Exactly -
Which of those is to the Telegram server?
I see one connection to a different local subnet.
Does it work if the cellphone using cellular data instead of local wifi?
Do you have port forwards setup to the bot machine?
Nothing there really nooks like an issue. I'd expect this to work fine as long as outbound traffic allowed.
-
@stephenw10
Which of those is to the Telegram server?
The Telegram server is 149.154.167.220I see one connection to a different local subnet.
Yes, to my IoT devices.Does it work if the cellphone using cellular data instead of local wifi?
No. Same issue.Do you have port forwards setup to the bot machine?
Yes, but not 443, another high port. Why, pls? -
I wouldn't expect to need any port forwards but was interested to if you had any. If the previous setup used them for example.
If Telegram somehow relies on open ports for reply traffic you might need to setup a static outbound NAT rule for the server. That seems unlikely though.
-
@stephenw10 I never neeeded static outbound NAT rule before and I didnt find anything from Telegram asking to do so. :-(
I see communication from both sides but not working
:
-
What was your setup before pfSense?
Could be simply a coincidence that this stopped when you put pfSense in.
I have no idea what sort of logging or debugging the bot machine might be able to provide but I would check for any errors there.
-
@stephenw10 I was using a UDM-PRO (Ubiquiti Gateway)
-
And you don't see any blocked packets on WAN from 149.154.167.220?
If it was a source port randomisation issue you would expect to see blocked traffic.
-
@stephenw10 Nothing. Thats why I am so lost...
-
Well I'd be checking it works still when behind something else because it doesn't look like anything special should be required in pfSense.
