| |
HF1L > TCPIP 07.11.20 19:00l 38 Lines 1397 Bytes #999 (999) @ WW
BID : 7BUSR1BSZ00R
Read: GUEST IU4JRU
Subj: Re^2: How get encap.txt
Path: IZ3LSV<DB0ERF<DB0RES<ON0AR<SV1CMG<SR1BSZ
Sent: 201107/1759z @:SR1BSZ.SZ.POL.EU [Szczecin_PL JO73GK] obcm1.07b12 LT:999
From: HF1L @ SR1BSZ.SZ.POL.EU (Janusz)
To: TCPIP @ WW
X-Info: Sent with login password
From: N1URO@VE2PKT.#QBC.QC.CAN.NOAM
To : TCPIP@WW
>Janusz;
>G1FEF now is denying connections to both www.ampr.org and portal.ampr.org
>IF you use ipencap. 44-net is now basically useless.
>
G1EFE wrote to me that:
You probably have a routing error. Check your routing table to see what route
your server is taking for 44.190.255.16
Make sure you have the correct routes for 44/9 and 44.128/10 instead of 44/8
Unfortunately, I don't remember how to do it, now I have this:
This is how I currently have:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 62.69.192.1 0.0.0.0 UG 0 0 0 eth0
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 bcsf1
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ax0
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 ax1
44.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth1
44.0.0.1 169.228.34.84 255.255.255.255 UGH 0 0 0 tunl0
Should I enter this in the routing table ?:
/sbin/ip route add 44/9 via 169.228.66.251 dev tunl0 proto static onlink"
/sbin/ip route add 44.128/10 via 169.228.66.251 dev tunl0 proto static onlink"
73 de Janusz HF1L sysop SR1BSZ
Read previous mail | Read next mail
| |
