44net-request(a)hamradio.ucsd.edu wrote:
> Subject:
> [44net] LinFBB patch
> From:
> Brian <n1uro(a)n1uro.ampr.org>
> Date:
> 09/10/2014 02:05 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> For those who run LinFBB 7.05f on the amprnet, I have a patch for it
> that I released last night. All it does is adds a (Q)uit command which
> parallels the existing (B)ye command. Considering with FlexNet and Xnet,
> and other softwares leaning more towards Quit than Bye for an "exit
> application" command, this patch will make FBB more user friendly.
In the old days, everyone had an FBB BBS (or maybe RLI or 4RE) and used B for Bye,
except the Germans who had "DIEBOX" where B meant "Bell (alert the sysop)"!
Always fun.
>
> You may find it at:
> ftp://n1uro.ampr.org/packet/xfbb/fbbquit.patch
>
> if interested.
The system is not reachable from here (44.137)
Rob
Hello,
i am coord offrench network 44.151.
I want to make gateways :
For example, i want ping 44.151.29.1 and i would like to have an
answer from my localIP 78.241.81.29.
What is the command to the server.
I knows these command
f5pbg add a 78.241.xxx.xxx
etc...
but i don't know the command to make gateways...
Thank's a lot for the answer.
All the best
Ludovic - F5PBG.
For those who run LinFBB 7.05f on the amprnet, I have a patch for it
that I released last night. All it does is adds a (Q)uit command which
parallels the existing (B)ye command. Considering with FlexNet and Xnet,
and other softwares leaning more towards Quit than Bye for an "exit
application" command, this patch will make FBB more user friendly.
You may find it at:
ftp://n1uro.ampr.org/packet/xfbb/fbbquit.patch
if interested.
--
73 de Brian Rogers - N1URO
email: <n1uro(a)n1uro.ampr.org>
Web: http://www.n1uro.net/
Ampr1: http://n1uro.ampr.org/
Ampr2: http://nos.n1uro.ampr.org
Linux Amateur Radio Services
axMail-Fax & URONode
AmprNet coordinator for:
Connecticut, Delaware, Maine,
Maryland, Massachusetts,
New Hampshire, Pennsylvania,
Rhode Island, and Vermont.
Are we anywhere close to being able to support an RF-based mesh network?
Or is it just simplest to have backhaul to a single tunnel device?
I'm thinking the RF network side would be using OSLR or some other
routing protocol, providing it with the information it needs, but for
the tunnel announcing a single IP makes the most sense. Otherwise, the
large network would show up with multiple diverse routes, but may in
reality be partitioned.
--
Kris Kirby, KE4AHR
Disinformation Architect
To anyone that reported the “Please select your country” bug when editing an IP request allocation.
This has now been fixed.
Please let me know if anyone finds anymore bugs.
Thanks,
Chris
Jean ve2pkt asked me to setup a axip link between our gateways.
ve2pkt 44.135.49.2
and
ve2uqh 44.135.52.33
When trying to ping ve2pkt I get no response, a few hours later it works
fine.
The next day again no response.
Same results from n1uro.
Route to ve2pkt is via n1uro.
I can ping other gateways fine.
Could this be a firewall problem ?
I run jnos2.0j on Debian wheezy with rip44d.
thanks,
Michel
ve2bcw
sysop ve2uqh.ampr.org
Gatineau/Ottawa
