View previous topic :: View next topic |
Author |
Message |
unclerunkle
Joined: 24 Dec 2015 Posts: 2
|
Posted: Thu Dec 24, 2015 4:35 pm Post subject: Bug? "SSDP packet sender [ip:port] not from a LAN, igno |
|
|
Originally asked this on the pfSense form, but was directed here.
Stumped on this one even after searching the forums / Google. Here's the setup:
Client on 192.168.4.0/27 > pfSense2 firewall (no NAT) > pfSense1 firewall (NAT) > WAN
pfSense2 forwards the SSPD multicast to pfSense1. The client and pfSense1 are on different subnets.
pfSense1 has the following miniupnpd config in /var/etc/miniupnpd.conf:
Code: | ext_ifname=vmx0
port=2189
listening_ip=vmx1
packet_log=yes
presentation_url=https://192.168.1.1/
uuid=b74cb48c-6d13-48de-052e-ade3d61826d
serial=B74CB48C
model_number=2.2.6-RELEASE
allow 53-65535 192.168.4.0/27 53-65535
deny 0-65535 0.0.0.0/0 0-65535
enable_upnp=yes
enable_natpmp=yes |
However, these warnings keep showing up in the miniupnpd log:
SSDP packet sender 192.168.4.30:63177 not from a LAN, ignoring
Shouldn't this work? My allow range is specified but not working? I've tried an allow range of 192.168.0.0/16 with no success as well. How can I do this with multiple subnets?
Lastly, I'm unsure of how to tell my miniupnpd version. Some pfSense code appears to reference "20100712" however. |
|
Back to top |
|
 |
unclerunkle
Joined: 24 Dec 2015 Posts: 2
|
Posted: Thu Dec 24, 2015 4:38 pm Post subject: |
|
|
Also, can my username be edited to just unclerunkle or deleted? Seems I accidentally typed my email as the username. Sorry |
|
Back to top |
|
 |
miniupnp Site Admin
Joined: 14 Apr 2007 Posts: 1594
|
Posted: Wed Dec 30, 2015 9:10 pm Post subject: |
|
|
1 - username edited.
2 -
listening_ip=vmx1
I guess the IP/mask for vmx1 is 192.168.1.1/24 ?
so 192.168.4.30 doesn't match.
The trick would be to configure
listening_ip=192.168.1.1/16 _________________ Main miniUPnP author.
https://miniupnp.tuxfamily.org/ |
|
Back to top |
|
 |
|