Satellite Internet via Dreambox.
Satellite Internet via Dreambox
The satellite receiver Dreambox in able hands fully justifies its name. The Linux operating system used in it makes it possible for almost any programmer to write applications expanding the capabilities of the device. Among the interfaces provided with the receiver, there are USB 1.2 and 10/100 MBit Ethernet, which makes it possible to connect it to the local network.
Naturally, inquisitive users have a question: is it possible to use Dreambox to receive data? The receiver is ready for this. However, these functions have not been implemented for a long time. Then the situation began to change. With the help of the DreamData plug-in from the German programmer Mechatron, the task was to receive multicast streams of Casablanka (Sat @ once), Filiago, EasyNet, AliceSat, etc. To grab (fish) Internet streams, the receiver began working as a premiere for the popular SkyNet program .
And finally this summer at the allrussian.info forum the joint work of several people led to a positive result. The technique of using the Dreambox DM-7000S receiver as a receiver for a full-fledged asymmetric Internet has been worked out. Specifically, the connection to the terrestrial and satellite providers is done on the computer using a modem, GPRS, local area network, ADSL, etc. The Dreambox itself acts as a satellite receiver and a DVB / IP router.
So, we give the floor to the visitors of the forum allrussian.info.
We have a Dreambox DM-7000S receiver. Pay attention that the image was not very ancient, support for dvbnet was built in since March 2005.
. We use the operator SpaceGate, satellite Express AM22 (53 east).
Set Dreambox to a channel with SpaceGate data: fr = 10969 s / r = 24128 fec = 7/8 pol = V
We connect to the receiver, go into telnet and give these commands:
~> dvbnet 1B58
(created a new network interface that listens to PID 7000 (1B58 - hex) - PID provider
You can create such interfaces for your PIDs and MACs (for example, for different subscriptions).
To remove an unnecessary interface: dvbnet -X (dvb0_X is the 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 also substitute another). Do not substitute the gray IP assigned to you by the satellite operator.
00: xx: xx: xx: xx: xx - MAC address of your subscription
Next, configure the routing
~> echo 1> / proc / sys / net / ipv4 / ip_forward
(we allow the redirection of packets, ie it makes a router out of the drift)
~> echo 0> / proc / sys / net / ipv4 / conf / all / rp_filter
(reset the filter that is responsible for sending the packet only from the interface from which it came in. rp_filter - reverse path filtering)
~> echo 0> / proc / sys / net / ipv4 / conf / dvb0_0 / rp_filter
(the same, but for our new interface, dvb0_0 is reverse path filtering)
~> route del default
(delete the old defaul gateway)
~> route add 0.0.0.0 gw 192.168.XX.XX dev eth0
(we direct the entire flow to the gateway 192.168.XX.XX (ie on the computer)
where: 192.168.XX.XX - IP network card in the computer to which the Dream is connected.
In the menu Manual transponder we are tuned to the frequency with the parameters on which SpaceGate works, the signal should be set. (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 also possible to work with the satellite accelerator GlobaX. The first option is via the GlobaX + bundle loopback adapter, 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 IP address, which issued by the provider. In this case, neither VPN nor loopback is needed. GlobaX works fine in this configuration. (Note - all IP protocols go through the 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 this has to be automated. The first step to automating this process is the script, which should be placed in /var/bin/sat_inet.sh, give it the right to execute (755), write it in Expert Setup -> Scripts Autoexec Setup (there are in the ruDREAM image files).
#! / 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 add 0.0.0.0 gw 192.168.XX.XX dev eth0
DreamBox and SatGate.
In continuation of the theme of using DreamBox, as a DVB / IP router, the following scheme was assembled:
Equipment: We have access to the Internet through D-Link DSL-G604T (Router, ADSL, 4-port switch, Wi-Fi 802.11g), subscription to satellite Internet on SatGate (Sirius 5E). We work on VPN, Dreambox DM-7000S with a hard drive.
The task: "rassharka" satellite internet for home, download files at night during the cheap tariffs on the Dreambox on a schedule without the participation of PC.
To do this, you need to raise the VPN to D-Link and use Dreambox as a DVB / IP router.
First, I had to install an alternative firmware from mcmcc on D-Link (good for Linux there) in order to run pptp ("Native" firmware does not have this capability).
So, Dreambox is configured and "chases" packets for default gw from satellite to D-Link. We raise the VPN on D-Link - everything works, the satellite Internet is distributed everywhere, and on Wi-Fi too.
But periodically there is a hemorrhoid with a VPN connection, and then terrible packet losses begin. But at the same time, if the VPN runs under Windows, everything is stable and with the Dreambox as DVP / IP it works for hours.