Thanks for the response.
I only have "up" in /etc/hostname.tun1
The rest of the config is dictated by npppd.
I have these statements in the file:
authentication LOCAL type local {
users-file "/etc/npppd/npppd-users"
}
tunnel L2TP protocol l2tp {
listen on <address>
}
ipcp IPCP {
options
}
interface tun1 address <address> ipcp IPCP
bind tunnel from L2TP authenticated by LOCAL to tun1
but that's it... nothing more.
Regards,
Kaya
On 05/06/2014 12:26 PM, Martin Pieuchot wrote:
Hello Kaya,
On 30/04/14(Wed) 23:38, Kaya Saman wrote:
Hi,
I've been having an issue with Igmpproxy after upgrading from 5.4-snapshot
to 5.5-CURRENT.
Before the upgrade Igmpproxy used to work fine with my current config file
and services such as upnp which need Igmpproxy to work were performing fine.
Currently running tcpdump -eni vlan(x) host 239.255.255.250 shows packets
being sent to the multicast address on the specified vlan so there is
actually multicast traffic appearing in the network.
# tcpdump -eni vlan192 host 239.255.255.250
tcpdump: listening on vlan192, link-type EN10MB
tcpdump: WARNING: compensating for unaligned libpcap packets
23:36:08.652520 00:25:90:e3:5d:a8 01:00:5e:7f:ff:fa 0800 215:
192.168.1.80.57831 > 239.255.255.250.1900: udp 173 [ttl 1]
23:36:08.652525 00:25:90:e3:5d:a8 01:00:5e:7f:ff:fa 0800 215:
192.168.1.80.57831 > 239.255.255.250.1900: udp 173 [ttl 1]
23:36:09.141167 00:25:90:e3:5d:a8 01:00:5e:7f:ff:fa 0800 215:
192.168.1.80.5282 > 239.255.255.250.1900: udp 173
23:36:09.141289 00:25:90:e3:5d:a8 01:00:5e:7f:ff:fa 0800 215:
192.168.1.80.5282 > 239.255.255.250.1900: udp 173
The exact issue is that Igmpproxy will not start. Using the rc script the
output is:
# /etc/rc.d/igmpproxy restart
igmpproxy(failed)
/var/log/messages output:
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 0 Fl 0x0 IP
0x010210ac vlan10, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 1 Fl 0x0 IP
0x0101a8c0 vlan192, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 2 Fl 0x0 IP
0x0100a8c0 vlan2, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 3 Fl 0x0 IP
0x0114a8c0 vlan20, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 4 Fl 0x0 IP
0x0102a8c0 vlan3, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 5 Fl 0x0 IP
0x010110ac vlan30, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 6 Fl 0x0 IP
0x018ca8c0 vlan50, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 7 Fl 0x0 IP
0x0137a8c0 vlan55, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 8 Fl 0x0 IP
0x7602b251 pppoe0, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 9 Fl 0x0 IP
0x01c8c80a tun0, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: Note: adding VIF, Ix 10 Fl 0x0 IP
0x01c9c90a tun1, Threshold: 1, Ratelimit: 0
Apr 30 23:23:04 Gamma-Ray igmpproxy: ERRO: MRT_ADD_VIF; Errno(45): Operation
not supported
How is your tun1 interface configured? If it is doing layer 3 tunneling
is won't support multicast and it is normal for MRT_ADD_VIF to fail
here.
Martin
