Have a masquerade/nat iptable rule in your router what is
doing the encap tunneling.
If has already a 44 address binded and that address is used.
iptables -t nat -A POSTROUTING -s 192.168.1.20/32 -o eth0 -j MASQUERADE
or just a masq entry in your existing firewall software scripts like an
entry
in /etc/shorewall/masq if you are using shorewall.
Make sure that amprnet traffic is routed to that machine from
the computers at your lan.
73,
Bob VE3TOK
On 13-12-15 08:42 PM, kb9mwr(a)gmail.com wrote:
(Please trim inclusions from previous messages)
_______________________________________________
How does everyone handle servers that they have accessible via net 44?
(As well as their local network)
I typically use the 192.168.1.X private IP range on my home network.
A couple IPs on that network are servers (askerisk, samba etc). I
don't really want to change my internal network configuration. So I
was thinking some sort of one-to-one translation of IP addresses.
I have tried everything I have read thus far with no luck.
Lets say:
server: 192.168.1.20 that I'd like translated to 44.92.21.35
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net