30 Sep
2022
30 Sep
'22
9:59 p.m.
+1 on Vyos. I have it running on a VM as a VPN server and router. If
you are used to EdgeOS, you will be comfortable with Vyos as EdgeOS
forked from it some years ago. Very Junos-like.
Tim
On 9/30/22 7:18 AM, Barry Bahrami via 44net wrote:
If you go the bridge mode option then look at putting
VyOS behind it.
It's a great open source router, full featured, and as fast as the
hardware you put it on. It runs on regular x86 hardware. I've used it
for years. It's a fork of Vyatta before it went private. VyOS.io
Thank you,
Barry Bahrami
KN6MVB
On Fri, Sep 30, 2022 at 6:26 AM KI5PGJ via 44net <44net(a)mailman.ampr.org
<mailto:44net@mailman.ampr.org>> wrote:
Some broadband providers also support some form of bridge mode where
their CPE only provides transport layer, passing through all traffic
to your device. I know Windstream supports that in my area of the US.
diana
KI5PGJ
On September 28, 2022 2:08:01 PM MDT, Lee D Bengston via 44net
<44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote:
Not sure if that will work if the router is also a cable-modem
or DSL-modem.
On Wed, Sep 28, 2022, 2:49 PM Boudewijn (Bob) Tenty via 44net
<44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote:
Just flash your router with dd-wrt if it can't pass ipip and
the problem is solved.
Bob
On 2022-09-28 14:33, Rob PE1CHL via 44net wrote:
<mailto:44net@mailman.ampr.org>
There is nothing special to do, except that you
need to
make sure that incoming protocol-4
traffic on your internet connection arrives at
your
gateway system. And with modern internet
routers as supplied by providers that is often
impossible. You often can forward TCP and UDP
ports only, not protocols. And when there is a
"DMZ"
setting that promises to forward all
unsolicited incoming traffic to a specified host,
more
and more often it handles only TCP and UDP
traffic.
It can be deceiving that the router often passes replies
to outgoing
protocol-4 traffic as part
of its standard NAT function. That is not
enough. It
needs to pass unsolicited incoming traffic
or else you will not see the RIP packets.
Rob
On 9/28/22 20:24, David Ranch via 44net wrote:
> Hey Chris, Marius,
>
> Ok, thank you for the correction though I clearly
remember that
"something" additional was required before RIP
updates would start flowing over the IPIP tunnel other than
the user just defining their gateway IP address for the IPIP
tunnel endpoint. What is "that".
--David
KI6ZHD
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to
44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>
--
There is nothing permanent except change
-Heraclitus
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
<mailto:44net@mailman.ampr.org>
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
<mailto:44net@mailman.ampr.org>
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org