![]() I've tried to activate it for Port 53 and bind interfaces LAN, VLAN100 and VLAN101.Īlso I set a floating rule from any to any.We'd strongly recommend users to use Google Cast only on Chromebook, Google Pixel phone via wePresent WiCS-2100. I've already installed the mdns-responder package into box and restarted. On the LAN interface where the printers are? On which interface did you setup this Any-Any Rule? ![]() I'm looking nearly for the same solution to a printer problem.I want to discover printers from Windows and Mac Clients and also mobile devices (smartphones and tablets).Īt my environment the printers are on the LAN subnet.įrom print-server over SMB connected printers can print and be managed inter VLAN.ġxLAN (local subnet with servers, desktops and printers)ġx WIFI (Management-Interface for Access Points, Switches)ġx VLAN200 subinterface of WIFI (not allowed for printing)ġx VLAN300 subinterface of WIFI (not allowed for printing) Quote from: Julien on July 25, 2016, 10:51:17 am Hi Guys, When creating a group of interfaces, does the rules on the interface side apply as first than the group firewall rules ? I am ready to provide any log/informatie needed to help you guys understand the idea behind. and no 5353 UDP is open or NAT to the printer It's working now thank you guys for your support. I dont know if it does works out of the box or mdns-rep package does the job. So checked the firewall rules and found out that the Productions interface doesn't have a Allow Any to Any, just on each interface.īecause on Pfsense it does Works and OPNSENSE not, so i compared the configuration and i noticed the different between the setup of Pfsense and Opnsense is the group of the Interfaces.Īfter i created any to any rules on the productions interface printers shows up on the iPads/iPhone.Įven the bonjour services is working now. I've traced the Airprint package using wireshark and figured out there was deny rule. I have created a group of the productions LAN and VLANS. So having the users and the printers on the same VLAN would makes this works ? I am willing to fix this without any package. Whenever I try the same with OPNsense it doesn't work, the firewall rules are the same as OPNsense, from the WAN and LAN side. IP is 192.168.1.100 and it detectable from VLANS and users can print. I've configured the printer IP to use the em1 subnet and not the VLANS subnet. I appreciate every support you guys provided. I am continuing asking on this forum to understand the way how OPNsense works to either decide continue with it or not. We been forced to take OPNsense firewall of the network. ![]() Its not about the design of the network, the design of the network is fine as it working fine with PFsense right now. ![]() As the test went fine, but we didn't think about the Mac users and their AirPrint. I believe we needed to think twice before migrating to OPNsense. edit the following lines in /etc/etc/avahi/nf:Īllow-interfaces=eth0,eth0.XX [add all interfaces here, separated by ",") Install vlan and avahi: sudo apt install vlan avahi-daemon Update and upgrade: sudo apt update & sudo apt upgradeħ. SSH into your PI (default setting is dhcp so you should be able to find the IP in your DHCP server listing}Ħ. Create a trunk port on your network switch with LAN and all VLANs that need mDNSĥ. Install Raspian as per use the raspbian-lite imageģ. Avahi needs a build environment and a lot of dependencies and is rather difficult to build if you don't do this all the time.Ģ. There's a pkg for pfsense but on OPNsense you need to build it from source from the ports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |