OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of gliddie »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Messages - gliddie

Pages: 1 [2] 3
16
18.1 Legacy Series / Re: TFTP Proxy
« on: July 17, 2018, 07:01:29 pm »
Hey,

Did you ever get this to work?

Thank you

17
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 14, 2018, 07:39:46 am »
Hello Frank,

II did plugin the MR401 to a Telekom router and did let it grab the firmware that way.
After that I plugged it back to my Opnsense box.

FreeBSD  comes with a tftp proxy, which we would need to enable. So opnsense could proxy the tftp queries to Telekoms server. There is no plugin for that in opnsense.

I haven't figured out yet how to get that tftp proxy up and running. Am working on it.
For the moment you would need to use a Fritz Box or Telekom router for the very first start.
After that you can remove these and begin using Opnsense with the MR401.

I'll be back soon...

Gliddie

18
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 14, 2018, 01:08:14 am »
Ok,

besides the usual Firewall rules for IGMP, nothing special is required for the Media Receiver 401.
Mine was not starting, as I had an NTP server handed out by my DHCP server.
The MR401 doesnt seam to like NTP servers, other then the Telekom ones.
After disable option 42 and 4 on my dhcp, the MR401 is booting fine now.

Conclusion:
The Media Receiver 401, which requires IMGP V3 SSM, does work with the actual Opnsense version and the igmp proxy which does come with the last version.

Things to consider:

  • this igmp proxy version does not recognize virtual upstream interfaces.
    ==> If you have to tag your upstream interface with a VLAN, do that on the modem, infront of your opnsense box.
  • Somehow there might be a conflict with the OpenVPN Server. igmp proxy does not start, if you run an Open VPN Site to Site tunnel. I dont have that issue with my IPsec Tunnel.
  • The MR401 grabs his firmware files from an TFTP server at Telekom. ==> You will need to run a tftp proxy on Opnsense, if you like to be able to upgrade firmware. If you start your MR401 the first time, it will not boot up, if it cannot reach the TFTP server.

Ok. enough for today, Will give the box my wife for testing it a few days :-)


Have a nice weekend,
Gliddie


19
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 13, 2018, 08:28:08 pm »
Last update for today:
My Media Receiver 401 is working with the latest version from Opnsense and the igmp proxy from that version.
==> IGMP V3 SSM must be working with that version from IGMP proxy.
Am just wathc ZDF HD, since 10 Minute and the picture is clear and stable.
Zapping works well.
Will now test it over a longer time period and see, if it stays stable.

By the way, I still receive the old IGMP V2 and V3 streams. So far Telekom did not change anything on my circuit, since I had plugged in the Media Receiver 401.

Will be back in a few days after testing it a longer time.

Have a nice weekend,
Gliddie

20
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 13, 2018, 12:28:15 pm »
Ok, I will need a moment to get the box booting up.

1.) At the first start it is looking for an tftp server, to grab its firmware ==> We will need a tftp proxy on opnsense. Else a fresh unboxed MR401 will not start. Also future firmwareupgrades would not work .
2.) Then the box is trying to reach 4 different NTP Servers. And then it stops starting up with an error message stating it cannot contact the NTP servers.

Next step, if my wife gives me time to play: I'll connect the box to the Telekom Router and capture some sniffer traces from the boot process. I just like to see which traffic is running back and forth to build the required firewall rules.

Let's see, I'll be back later today or tomorrow.

Cheers,
Gliddie

21
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 12, 2018, 11:46:36 am »
Hi,

I have just received the Mediareceiveder 401 from Telekom and connected it.
Will begin testing now.

Lets see ....

Greetings,
Gliddie

22
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 10, 2018, 03:13:27 pm »
Hi, I wish I could.
Haven't received the kit yet.
Just checked the order status on Telekoms Webpage and it looks like delivery is due in July 14.

Can't wait to get it  :)

I'll let you know as soon as I have received the box.

Have a nice day,
Gliddie

23
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 03, 2018, 07:09:42 am »
No Problem,

Have ordered the Telekom MediaReceiver 401 yesterday.
Will give it a try  ;)

I'll report the result after testing.

24
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 02, 2018, 07:12:31 am »
rtp://87.141.215.251@232.0.20.35:10000 is "Das Erste HD".
It is from the new Entertain TV. I am just watching it through VLC on my Smartphone.
This would not work, if IGMP V3 would not be working with the recent IGMP Proxy in Opnsense.

25
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 01, 2018, 11:49:23 pm »
Interesting  ;) TVHeadend ist working with IGMP V3 and SSM.
Long time I had been using the old IGMP V2 Multicast Streams.
If I try the IGMP V3 stream with VLC it is working, as well as with TVHeadend.
I have no single IGMP V2 Address configured in my TVHeadend.

Am not using the Telekom Boxes, as I only watch a little bit TV.
And with TVHeadend and Kodi, I am a lot more flexible  :)

26
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 01, 2018, 11:54:20 am »
My Topology is:

Telekom Magenta L --> Draytek Vigor 130 acting as Modem --> APU 2C4 / Opnsense 18.1.10 --> LAN Switch TP-Link TL-SG108E with IGMP Snooping enebaled --> TVHeadend/Centos Linux on Intel NUC --> Kodi TVH Client on Rasperrry PI.

It is working like a charm.

27
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: July 01, 2018, 11:44:52 am »
Ok,

this is my igmpproxy.conf:

Code: [Select]
##------------------------------------------------------
## Enable Quickleave mode (Sends Leave instantly)
##------------------------------------------------------
quickleave
phyint pppoe1 upstream ratelimit 0 threshold 1
altnet 193.158.0.0/15
altnet 224.0.0.0/4
altnet 239.32.0.0/16
altnet 87.141.0.0/15

phyint igb1 downstream ratelimit 0 threshold 1
altnet 192.168.3.0/24

phyint igb2 disabled

28
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: June 30, 2018, 09:58:14 pm »
I am surprise about all the challanges here. For me it is working fine. I also watch the new Telekom IPTV with IGMP V3. My IGMP proxy starts without issues. I have a Vigor 130, I front of my Opnsense box, acting as the Modem.

29
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
« on: April 13, 2018, 01:54:26 pm »
Yep, same for me.

30
18.1 Legacy Series / Re: igmpproxy won't start after upgrade
« on: March 06, 2018, 09:44:30 am »
Regarding the VLAN, nothing should have changed.
If you set the VLAN on the modem, you musn't set it in Opnsense.
And when you set the VLAN in Opnsense, you have to remove it from the modem.
Either way does work for me.

@maldenvik: Do you have a VPN tunnel established?

With my box, I have to start igmpproxy, before starting the vpn server on opnsense.
If I start igmpproxy, after the vpn server has started and the tunnel is established, it fails for me with the same message as yours.

Pages: 1 [2] 3
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2