Satellite Internet via Dreambox.
Satellite Internet via Dreambox
The Dreambox satellite receiver in the right hands fully lives up to its name. The Linux operating system used in it enables almost any programmer to write their applications expanding the capabilities of the device. Among the interfaces that the receiver is equipped with are USB 1.2 and 10/100 MBit Ethernet, which makes it possible to connect it to a local network.
Naturally, inquisitive users have a question - is it possible to use the Dreambox to receive data? The hardware receiver is ready for this. However, for a long time these functions were not implemented. Then the situation began to change. Using the DreamData plugin from the German programmer Mechatron, the problem of receiving multicast streams from Casablanka services (Sat @ once), Filiago, EasyNet, AliceSat, etc. was solved. For grabbing (fishing) Internet streams, the receiver began to work as a premiere for the most popular SkyNet program .
And finally this summer at the forum allrussian.info the joint work of several people led to a positive result. The methodology for using the Dreambox DM-7000S receiver as a receiver for a full asymmetric Internet has been developed. To clarify - the connection with the terrestrial and satellite providers is made on the computer using a modem, GPRS, local network, ADSL, etc. The Dreambox itself works as a satellite receiver and DVB / IP router.
So, we give the floor to visitors to the forum allrussian.info.
We have a receiver Dreambox DM-7000S. Please note that the image is not very ancient, dvbnet support has been built in since March 2005.
. We use the operator SpaceGate, the satellite Express AM22 (53 East).
We configure Dreambox on the channel with SpaceGate data: fr = 10969 s / r = 24128 fec = 7/8 pol = V
We connect to the receiver, go to telnet and give these commands:
~> dvbnet 1B58
(created a new network interface that listens for PID 7000 (1B58 - hex) - PID of the provider
You can create several such interfaces for your PID and MACs (for example, for different subscriptions).
To remove an unnecessary interface: dvbnet -X (dvb0_X - interface number)
For example, dvbnet -2 removes dvb0_2.
~> ifconfig dvb0_0 192.168.3.1 netmask 255.255.255.0 hw ether 00: xx: xx: xx: xx: xx mtu 1500
192.168.3.1 - IP address for the newly created dvb0_0 (you can substitute another one). Do not substitute the gray IP assigned to you by the satellite operator.
00: xx: xx: xx: xx: xx - MAC address of your subscription
further we configure routing
~> echo 1> / proc / sys / net / ipv4 / ip_forward
(allow packet forwarding, i.e. makes a router from dream)
~> echo 0> / proc / sys / net / ipv4 / conf / all / rp_filter
(reset the filter responsible for sending the packet only from the interface from which it came. rp_filter - reverse path filtering)
~> echo 0> / proc / sys / net / ipv4 / conf / dvb0_0 / rp_filter
(same, but for our new dvb0_0 interface - reverse path filtering)
~> route del default
(delete the old defaul gateway)
~> route add 0.0.0.0 gw 192.168.XX.XX dev eth0
(direct the entire stream to the gateway 192.168.XX.XX (i.e., to the computer)
where: 192.168.XX.XX - IP network card in the computer to which Dream is connected.
In the Manual transponder menu, we tune to the frequency with the parameters at which SpaceGate works, the signal should be locked. (crosses should appear in Lock and Synch).
We connect to the terrestrial Internet (modem, gprs), turn on the VPN and try - everything should work
It is possible to work with the satellite accelerator GlobaX. The first option is through a bunch of GlobaX + loopback adapters, in which the IP issued by SpaceGate is registered. The second option is without VPN and without loopback. We put on the network card in the computer the IP address that the provider issued. In this case, neither VPN nor loopback are needed. GlobaX also works fine in this configuration. (Note - all IP protocols go through a VPN. Through Globax, and it is a local HTTP proxy - a limited number).
Later, there were reports of successful work on the DreamBox 500 receiver, Gemini 2.10 firmware.
Well, now all that is left is to automate it. The first step to automating this process is a script that you need to put in /var/bin/sat_inet.sh, give it execute rights (755), write it in Expert Setup -> Scripts Autoexec Setup (it is in the ruDREAM command image).
#! / bin / sh
ifconfig dvb0_0 192.168.3.1 netmask 255.255.255.0 hw ether 00: d0: d7: XX: XX: XX mtu 1500
echo 1> / proc / sys / net / ipv4 / ip_forward
echo 0> / proc / sys / net / ipv4 / conf / all / rp_filter
echo 0> / proc / sys / net / ipv4 / conf / dvb0_0 / rp_filter
route del default
route add 0.0.0.0 gw 192.168.XX.XX dev eth0
DreamBox and SatGate.
In continuation of the topic of using DreamBox as a DVB / IP router, the following scheme was assembled:
Equipment: We have Internet access through D-Link DSL-G604T (Router, ADSL, 4 port switch, Wi-Fi 802.11g), satellite Internet subscription on SatGate (Sirius 5E). We work on VPN, Dreambox DM-7000S with a hard drive.
Task: "sharing" satellite Internet for home, downloading files at night during cheap tariffs for the Dreambox hard drive on a schedule without a PC.
To do this, you need to raise the VPN on D-Link e and use the Dreambox as a DVB / IP router.
First, I had to install an alternative firmware from mcmcc on D-Link (since Linux is there) in order to run pptp (the “native” firmware does not have such an opportunity).
So, Dreambox is configured and "drives" packages by default gw from satellite to D-Link. We raise the VPN to D-Link - everything works, satellite Internet is distributed everywhere, and on Wi-Fi too.
But periodically there is a hemorrhage with a VPN connection, and then terrible packet loss begins. But at the same time, if the VPN starts under Windows, everything is stable and works with the Dreambox as DVP / IP for hours.