| |
GM4UPX > SYSOP 29.01.20 13:20l 37 Lines 1512 Bytes #999 (0) @ WW
MID : 20008_GB7JED
Read: GAST
Subj: Node to Node
Path: DB0FFL<OE5XBL<F1OYP<ON0AR<OZ5BBS<CX2SA<ZL2BAU<NA7KR<GB7JED
Sent: 200129/1047Z @:GB7JED.#71.GBR.EURO #:20008 [ScottishBorders] $:20008_GB7J
From: GM4UPX@GB7JED.#71.GBR.EURO
To : SYSOP@WW
Hello,
Here's my problem :
I'm looking to provide a reliable RF to remote Internet link, so far I have the RF node(s) working
fine, it's the Internet node that's not working consistently.
The remote Internet node is running on a router with a connection to 4G network and I have " ping " set
every 4 minutes between it and its Internet neighbour.
Almost all of the time I can connect from one Internet node to the 4G remote Internet node, other
times I cannot, even when the 4G node has been recently heard.
Sometimes a " ping " followed by a " fping " from one Internet node to the 4G remote Internet node
will bring it " back to life ", other times it will not.
As you can see this doesn't make for a reliable link in one direction.
When I am at the remote 4G Internet node I can connect from it 100% to its Internet neighbour node.
I'm hoping someone reading this has had a similiar experience and can advise me.
I also have an additional problem regarding connections via 44net; with " my " settings using the
" traceroute " cmd gives the expected result in most cases; when using the " examples " settings
using " traceroute " shows all the public ip addresses in the route.
Is that correct ? Does it show that not all 44net addresses are routed the same ?
Again, if someone reading this is at a similiar stage as myself I would be interested to exchange
notes/settings in an effort to better understand what I am attempting.
Regards,
Ian..
Lese vorherige Mail | Lese naechste Mail
| |
