Menu

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.

Show posts Menu

Messages - dergroddi

#1
Thank you both for your feedback.

Packet Capture is what I did, but I did not see anything being blocked in there... So I still do not know why the printer insisted on not having internet connection.

But after reading the article, I decided to stay in LAN only mode. I really do not need the mobile app anyway and the timelapse is accessible via FTPS.

I did add the necessary rules (in my LAN network) for the ports and the printer is now connected in local mode.

PS: It might have been something with the DNS (Pi-Hole in main network, no rule for IOT devices to let port 53 pass), I will maybe check it out later
#2
General Discussion / How do I log "blocked" traffic?
January 03, 2024, 11:12:03 PM
Hi there,

I have two networks (main + iot). Now, I have a new device (Bambu Labs 3D Printer) which refuses to "connect to Internet" while being in iot network (other devices do not have those problems).

My question is: how can I figure out what is being blocked / not allowed in the firewall? I switched on every log option (especially for the automatically generated rules) but I do not see ANY red (blocked / not allowed) traffic in my logs.

How can I do that or what other options do I have to monitor every traffic for this device?
#3
Perfect, I ssh-ed into my opnsense and from there to the birdcam.

Thank you for this valuable advice, I learned something useful  :)
#4
Hi,

in my setup I have two networks (192.168.1.x for main, 10.10.10.x for IOT devices). I also have a Raspi Pi Zero W with a camera mounted inside my birdhouse (which - at the moment - is filled with eggs about to hatch, so no physical access possible as not to disturb or drive away the bird parents).

Normally this birdhouse device is on DHCP with IP 10.10.10.10, gateway 10.10.10.1 and DNS 192.168.1.2 (which is my Pi-Hole). Since I had connection issues with the birdhouse I wanted to see if a static IP address instead of DHCP would solve my problem.

So I went in and changed the static IP to 10.10.10.10, the DNS to 192.168.1.2 and THE GATEWAY to 192.168.1.1 (instead of 10.10.10.1). And now I cannot connect AT ALL.

Is there any way I can fix this without being able to access the SD card from the Zero W?
#5
You are right, the connection happens over the cloud.

My openHAB server is connected to their cloud interface (myopenhab.org) and this is working fine. Also, I have to enable to Skill in the Alexa App, which correctly connects to my account on myopenhab.org.

#6
Hi,

i have three networks in my installation:
- WAN, 192.168.178.x, connected to my Fritzbox Router on Lan1 of opnsense
- LAN, 192.168.10.x
- IOT, 10.10.10.x, both connected on Lan2 of opnsense

My openHAB3 server is in the LAN network, my Alexa devices are in the IOT network.

Now I want some items from my openHAB3 server to be discovered by Alexa (the items all have the correct metadata) but Alexa doesn't find anything.

Any ideas how to go about this problem? I tried to look in the live logs but i could not find blocked traffic between the networks.

Thanks for advice