It has been a long time since I have done any serious networking so am
still struggling with getting my head around the instructions for the
Edgerouter even after reading Marius's Microtik wiki.
Does anyone have a Dummies Guide version of building a new gateway on the
Edgerouter X?
I have a HamServerPi and HamNet node (Ubiquiti Bullet M2) ready to go and a
large group of hams waiting for my setup before they start active
involvement in the development of our local HamNet - something we really
need in the middle of tornado alley.
My thanks in advance.
Andy KA5BBC
> We were wondering if it would be possible to tunnel in the AMPRNet from
> UCSD into the exchange over BGP for the weekend of the event. If so what is
> the best way to go about this? I'm more than happen to land it on a VM
> elsewhere (Likely in London) then deal with getting it to the field myself
> if need be.
The standard way to have traffic tunneled to you, in the absence of a regional
gateway that is BGP-routed, would be to register a subnet at the portal and
setup an IPIP gateway for it, if desired using a VM somewhere to do the tunneling
and a further tunnel (VPN) to the site to forward the traffic.
Of course it would be possible to setup BGP routing to your VM, but would it be
worth it for a 3-day event only? Maybe you could setup something more permanent
that can be used by local amateurs after the event has ended.
Rob
Hi,
There is an upcoming event here in the UK, EMF Camp (
https://www.emfcamp.org/). There are a bunch of villages doing various
things, included is an amateur radio village (
https://wiki.emfcamp.org/wiki/Village:Amateur_Radio) as well as an internet
exchange (https://wiki.emfcamp.org/wiki/Village:EMF-IX).
We were wondering if it would be possible to tunnel in the AMPRNet from
UCSD into the exchange over BGP for the weekend of the event. If so what is
the best way to go about this? I'm more than happen to land it on a VM
elsewhere (Likely in London) then deal with getting it to the field myself
if need be.
Thanks,
Alistair
Hello All,
Have you noticed if you do a "C port Call" connect via a com port from Linux
JNOS window with your own (JNOS) call sign to BPQ, BPQ32 or XROUTER that the
connection is established but there is no further response in the connection
and seems to not respond any more.
However if you use another call sign via say Telnet or TNC via JNOS com
port, all works fine and the connection across the com port is established
and proceeds normally.
It makes it hard to test the configuration and have not gotten to the bottom
of it yet.
This has happened thru several versions of JNOS, but I am using similar
autoexec, etc files.
Any Ideas please?
Secondly, why does McAfee keep quarantining my WIN10 BPQ32.EXE file and also
the contents of downloaded BPQ32 EXE ZIP file from the official web site?
Thanks
Rob
Vk1kw
If -- for example -- one has a /24 delegated, are the .0 and .255
blocked at gw.ampr.org?
I haven't tried this, just figured I'd ask.
--
Kris Kirby, KE4AHR
Disinformation Architect, Systems Mangler, & Network Mismanager
> Before, or as soon as you attach a piece of equipment to our network
> (or anywhere else, for that matter) IMMEDIATELY CHANGE THE PASSWORD.
> Oh, and be careful when upgrading firmware: in far too many devices
> when you flash new firmware into it, the password gets reset to the
> factory default. Be sure to check it afterwards!
But, do not see this as a reason to not upgrade firmware!
It is really important to keep firmware uptodate, as e.g. was seen in the recent
case of MikroTik routers being compromised because they were running firmware
before version 6.42.1 which has a vulnerability that allows a remote user to
retrieve the correct password from the router! This was fixed some time ago
(current version is 6.42.6) but people didn't upgrade, and their router became
infected with a botnet that essentially allows it do do anything.
In this case, it is also important to change the password after the upgrade,
not because it would be reset, but because it could be known to an attacker who
retrieved it before the upgrade. In that case they can still login after upgrade!
(more details on how to avoid such things can be found on the MikroTik forum, but
even the "cannot do! too difficult for me!" type of operator still can upgrade the
software as this is only a matter of two clicks in the user interface)
Rob
Most network equipment comes from the manufacturer with a common
default password. The bad guys know what these are.
Before, or as soon as you attach a piece of equipment to our network
(or anywhere else, for that matter) IMMEDIATELY CHANGE THE PASSWORD.
If you don't, your device will be hacked in a matter of seconds and
you may lose control of it. It might be used to launch attacks on
other systems, and may become part of an evil botnet spreading
badness across the Internet.
Hardly a week goes by that I don't get an official complaint from
somewhere that a device on our network has been compromised and is
being used to attack other devices.
The root cause is almost always that someone attached their shiny
new computer/router/accesspoint/camera/toy to the network and
it got taken over because they forgot to CHANGE THE PASSWORD.
Oh, and be careful when upgrading firmware: in far too many devices
when you flash new firmware into it, the password gets reset to the
factory default. Be sure to check it afterwards!
Thank you.
- Brian
