How do i make two subnet talk to eachother?



  • I got two subnets right now. One with my WIFI AP attached to it, and one wired network with my dads computer, a printer, and two servers connected to it.

    I want to acess my servers and printer from my WIFI subnet, how do i do that?



  • Create a firewall rule on the interface allowing all traffic to go to/from it.



  • @tim.mcmanus:

    Create a firewall rule on the interface allowing all traffic to go to/from it.

    more specificlly, how do i do that?



  • Make a firewall rule that looks like the screen shot.  Mine has a specific gateway in this particular rule.  Yours will have an asterix in its place.

    http://doc.pfsense.org/index.php/Firewall_Rule_Basics

    ![Screen Shot 2013-03-23 at 5.13.46 PM.png](/public/imported_attachments/1/Screen Shot 2013-03-23 at 5.13.46 PM.png)
    ![Screen Shot 2013-03-23 at 5.13.46 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2013-03-23 at 5.13.46 PM.png_thumb)



  • Thanks - that's very helpful but it doesn't solve a problem that I have.  I have a Silicondust TV tuner connected on my LAN network with an address of 192.168.0.3 and while other systems on the LAN subnet can find the tuner, anything on the WLAN (192.168.1.*) subnet can not discover it.  I can browse to the HTTP server on the tuner from the wireless network but the tuner setup application does not find it when it scans … I assume that the tuner is only scanning the WLAN subnet.

    This will work if I bridge the two networks but I'm trying to get away from such a course solution as I want to be able to firewall the LAN separately from the WLAN.  Can anyone suggest a solution?



  • It might be using mDNS to scan the local subnet.

    If that's the case, you need to install avahi to extend mDNS across the two subnets.  It's a pfSense package.  Don't let the alpha label fool you, it works like a charm.



  • @tim.mcmanus:

    If that's the case, you need to install avahi to extend mDNS across the two subnets.  It's a pfSense package.  Don't let the alpha label fool you, it works like a charm.

    I installed it but it didn't help - it generates a lot of error messages in the system log - for example multiple "avahi-daemon[23377]: iface.c: avahi_server_add_service() failed: Not supported" messages and "avahi-daemon[23377]: Failed to add service 'pfsense' of type '_ssh._tcp', ignoring service group (/usr/local/etc/avahi/services/ssh.service): Not supported"



  • After talking to the support people at Silicondust, who make the HDhomerun tuner, they say that the device will only talk to devices on the same subnet so while it will work with LAN devices, it will not work on the WLAN unless I bridge the two networks.  Their setup does not store the device address but discovers it each time.



  • It's pretty surprising your TV tuner doesn't support defining a gateway O_o. Maybe throw in another NIC or use a VLAN and have all devices that need access to the TV-Tuner on the same interface.



  • I considered a VLAN but the wireless card doesn't support tagging so I've configured a separate wireless WPA network that bridges to the LAN and that seems to have solved the problems.



  • My SlingBox has the same issue.  Will only talk to the local subnet and won't route.

    I got around this by adding a NAT rule to hide all the traffic coming from other networks behind an address local to the slingbox.


Locked