miniupnp.tuxfamily.org Forum Index miniupnp.tuxfamily.org
The forum about miniupnp and libnatpmp
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

peer/packet sender not from LAN - interface not identified?

 
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Compilation/Installation
View previous topic :: View next topic  
Author Message
chtaube



Joined: 24 Apr 2013
Posts: 3
Location: Germany

PostPosted: Wed Apr 24, 2013 11:34 am    Post subject: peer/packet sender not from LAN - interface not identified? Reply with quote

I am trying to get miniupnpd 1.8 running on FreeBSD 9.1. Problem is, miniupnpd keeps complaining about clients not being on the LAN.

This is from the syslog:

Code:
Apr 24 13:02:37 nibbler miniupnpd[15432]: HTTP listening on port 5555
Apr 24 13:02:37 nibbler miniupnpd[15432]: Listening for NAT-PMP traffic on port 5351
Apr 24 13:03:08 nibbler miniupnpd[15432]: HTTP peer 172.23.1.2:43392 is not from a LAN, closing the connection
Apr 24 13:04:35 nibbler miniupnpd[15432]: SSDP packet sender 172.23.2.23:37475 not from a LAN, ignoring
Apr 24 13:04:42 nibbler last message repeated 3 times
Apr 24 13:04:47 nibbler miniupnpd[15432]: SSDP packet sender 172.23.2.23:44131 not from a LAN, ignoring
Apr 24 13:04:53 nibbler last message repeated 3 times
Apr 24 13:06:08 nibbler miniupnpd[15432]: SSDP packet sender 172.23.2.23:45862 not from a LAN, ignoring


Configuration file (not complete):
Code:

ext_ifname=tun0
listening_ip=172.23.0.1
listening_ip=172.23.4.1
listening_ip=172.23.16.1
port=5555
enable_natpmp=yes
secure_mode=yes
system_uptime=yes
clean_ruleset_interval=600

allow 1024-65535 172.23.0.0/22 1024-65535
allow 1024-65535 172.23.4.0/22 1024-65535
allow 1024-65535 172.23.16.0/22 1024-65535

deny 70 0.0.0.0/0 70
deny 80 0.0.0.0/0 80
deny 1194 0.0.0.0/0 1194
deny 8080 0.0.0.0/0 8080


The FreeBSD machine is acting as an Internet gateway for three subnets:

    172.23.0.1/22 (Interface re0)
    172.23.4.1/22 (Interface re0.3)
    172.23.16.1/22 (Interface re0.2)


External IPv4 interface is called tun0.


Output of ifconfig (IPv6 prefixes have been obscured):

Code:

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:0f:c9:04:fc:c0
        inet 172.23.0.1 netmask 0xfffffc00 broadcast 172.23.3.255
        inet6 fe80::20f:c9ff:fe04:fcc0%re0 prefixlen 64 scopeid 0x1
        inet6 2001:db8:309:1::1 prefixlen 64
        inet 172.23.0.2 netmask 0xffffffff broadcast 172.23.0.2
        inet 172.23.0.3 netmask 0xffffffff broadcast 172.23.0.3
        inet 172.23.0.5 netmask 0xffffffff broadcast 172.23.0.5
        inet 172.23.0.8 netmask 0xffffffff broadcast 172.23.0.8
        inet6 2001:db8:309:1::2 prefixlen 128
        inet6 2001:db8:309:1::3 prefixlen 128
        inet6 2001:db8:309:1::5 prefixlen 128
        inet6 2001:db8:309:1::8 prefixlen 128
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
re1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:0f:c9:04:fc:c1
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10baseT/UTP <half-duplex>)
        status: no carrier
re2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether 00:0f:c9:04:fc:c2
        inet6 fe80::20f:c9ff:fe04:fcc2%re2 prefixlen 64 scopeid 0x3
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
re0.2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 00:0f:c9:04:fc:c0
        inet 172.23.16.1 netmask 0xfffffe00 broadcast 172.23.17.255
        inet6 fe80::20f:c9ff:fe04:fcc0%re0.2 prefixlen 64 scopeid 0xb
        inet6 2001:db8:309:10::1 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        vlan: 2 parent interface: re0
re0.3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 00:0f:c9:04:fc:c0
        inet 172.23.4.1 netmask 0xfffffc00 broadcast 172.23.7.255
        inet6 fe80::20f:c9ff:fe04:fcc0%re0.3 prefixlen 64 scopeid 0xc
        inet6 2001:db8:309:4::1 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
        vlan: 3 parent interface: re0
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1452
        options=80000<LINKSTATE>
        inet 88.130.71.6 --> 62.214.64.97 netmask 0xffffffff
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        Opened by PID 1228
Back to top
View user's profile Send private message
chtaube



Joined: 24 Apr 2013
Posts: 3
Location: Germany

PostPosted: Wed Apr 24, 2013 1:53 pm    Post subject: Reply with quote

Solved it by trial-and-error.

Added the CIDR suffix to the IP addresses in the listeining_ip configuration:

Code:
listening_ip=172.23.0.1/22
listening_ip=172.23.4.1/22
listening_ip=172.23.16.1/22


Probably the man-page and configuration example should indicate that CIDR notation is ok here.
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1391

PostPosted: Wed Apr 24, 2013 4:58 pm    Post subject: Reply with quote

the example .conf file already tells it :
# LAN network interfaces IPs / networks
# there can be multiple listening ips for SSDP traffic.
# should be under the form nnn.nnn.nnn.nnn/nn
# It can also be the network interface name (ie "eth0")
[...]

_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
chtaube



Joined: 24 Apr 2013
Posts: 3
Location: Germany

PostPosted: Wed Apr 24, 2013 8:54 pm    Post subject: Reply with quote

Just checked the example configuration and didn't find the text you've quoted.

Probably the example configuration from the FreeBSD ports still has an older version.

Anyway, MiniUPnPd seems to be doing a fine job. Thank you for that very helpful software! Smile
Back to top
View user's profile Send private message
miniupnp
Site Admin


Joined: 14 Apr 2007
Posts: 1391

PostPosted: Thu Apr 25, 2013 9:07 am    Post subject: Reply with quote

See https://github.com/miniupnp/miniupnp/blob/master/miniupnpd/miniupnpd.conf
and ask FreeBSD port maintainer to update Wink
_________________
Main miniUPnP author.
http://miniupnp.tuxfamily.org/
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    miniupnp.tuxfamily.org Forum Index -> miniupnpd Compilation/Installation All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
Protected by Anti-Spam ACP
© 2007 Thomas Bernard, author of MiniUPNP.