14 May
2018
14 May
'18
8:11 p.m.
http://supertos.free.fr/supertos.php?page=1688
Ceci explique tres bien comment configuré une freebox pour vos besoin, sans avoir a placé
un routeur entre votre freebox et un raspberr pi qui fera votre encapsulation ipip pour
votre segment amprnet.
This will explain how to settup a freebox for ip fowarding or dmz to have a raspberry pi
behind the freebox without needing a routeur.
Bien le bonsoir de Pierre VE2PF
Envoyé de mon iPad
Le 14 mai 2018 à 20:11, Tony Langdon
<vk3jed@vkradio.com<mailto:vk3jed@vkradio.com>> a écrit :
On 15/05/18 04:57, Lin Holcomb wrote:
The wonders of gmail translate make it English ;)
Shaky, but readable. :)
Hello,
I try to make the configuration of the gateway through my
Freebox in router mode.
I am currently "stuck" because it is not possible to add
additional roads.
Does the Freebox have a "DMZ" or "Default host" mode? This is an IP
address that all traffic not otherwise forwarded is sent to. Many
routers can only forward specific TCP or UDP ports. The IPIP
encapsulation uses neither, and the only way to forward these is to use
DMZ mode.
The transition to bridge mode would require me to put behind the Freebox is
a
router, or a small pc.
Ideas to solve the problem of the network 44 with a Freebox in
router mode?
If not
Is it a good idea to turn a raspberry into a router and server
web behind a Freebox in bridge mode?
A Raspberry Pi is good for AMPernet routing, but I wouldn't use one as
the primary router for Internet use, because the I/O performance of the
Pi will slow down your Internet connection - across the LAN here, I get
only a few Mbps transferring files from a Pi, compared to the full 100
Mbps for any other host on the LAN. As I'm on a 100/40 Mbps Internet
connection, that would be unacceptable!
So first thing I'd try on your network is to use DMZ forward incoming
traffic to a Pi running ampr-ripd and the other software necessary. If
that's not possible, then put the Freebox into bridge mode and get
another router to do all of your port forwarding.
One last thing to note, if you already have a machine in DMZ, then you
have a problem, as you can only have one DMZ host on your network, and
that will need to be the AMPRnet router (that Pi we mentioned before).
In this case, you have to either remove the other machine from the DMZ,
usually by doing specific port forwards for it, consolidate the
functions of that machine and AMPRnet routing into one (ideally Linux)
machine, or you need to obtain another public IP address from your ISP.
Failing that, the only other solution left is to organise AMPRnet access
via VPN.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
_________________________________________
44Net mailing list
44Net@mailman.ampr.org<mailto:44Net@mailman.ampr.org>
https://mailman.ampr.org/mailman/listinfo/44net