N1URO wants me to let you folks know what his site is offline for a few days because construction work cut his network link. His email is similarly affected. - Brian
Thanks Brian.. I will eagerly look for his return.. Thanks for passing along!!!
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Wednesday, January 15, 2014 8:24 PM To: 44net@hamradio.ucsd.edu Subject: [44net] n1uro offline
(Please trim inclusions from previous messages) _______________________________________________ N1URO wants me to let you folks know what his site is offline for a few days because construction work cut his network link. His email is similarly affected. - Brian _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
What? No uber wideband RF link to the ISP?
Your slipping Brian!! :)
On Thu, Jan 16, 2014 at 9:09 AM, Jerry n9lya@blueriver.net wrote:
(Please trim inclusions from previous messages) _______________________________________________ Thanks Brian.. I will eagerly look for his return.. Thanks for passing along!!!
-----Original Message----- From: 44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu [mailto:44net-bounces+n9lya=blueriver.net@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Wednesday, January 15, 2014 8:24 PM To: 44net@hamradio.ucsd.edu Subject: [44net] n1uro offline
(Please trim inclusions from previous messages) _______________________________________________ N1URO wants me to let you folks know what his site is offline for a few days because construction work cut his network link. His email is similarly affected. - Brian _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
please give me a report on my new system 44net BELGIUM the access is 44.144.11.136 I installed a OpenBCM BBS
the next port are accessible only via 44net:
telnet port 23 http port 80 FTP Port 8021 SMTP Port 8025 pop3 Port 8110 nntp Port 8119
login: GUEST password: test
of course have used the OM login: your call and your personal password
Thanks in advance for a report André ON4HU on4hu.ampr.org
Andre,
Your 44.144.11.136 IP address is not present in latest encap.txt file, therefore is not accessible and not pingable from my own IP 44.165.2.2
OpenBCM is accessible on: http://on4hu.dyndns.org:81
Best regards. Tom - sp2lob
The entire 44.144.0.0/16 should be in the encap file and André's subnet should be reachable trough our local routing on our network.
On Thu, Jan 16, 2014 at 5:04 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Andre,
Your 44.144.11.136 IP address is not present in latest encap.txt file, therefore is not accessible and not pingable from my own IP 44.165.2.2 OpenBCM is accessible on: http://on4hu.dyndns.org:81
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Robbie,
That's correct, there is 44.144.0.0/16 via 141.75.245.225 but it not helps at all - 44.144.11.136 is not accessible. IP address itself 141.75.245.225 responds to pings.
There's also another subnet registered: 44.144.11.192/28 via 91.180.159.115 but not even one host responds at the moment.
Best regards. Tom - sp2lob
Btw Tom, your system is not reachable from the german hamnet either...
Marius,
Thank you for that info. I'm not ruling the other side, apparently...
Best regards. Tom - sp2lob
Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
1) The gateway for rule 0 should be 44.144.4.1 and not your local router ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16 dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connection new-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpn
So since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and I do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local router ip.
- You have disabled rule 0, meaning that all your outbound traffic is
being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16 dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connection new-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpn
So since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Dear Andre,
I have fixed the configuration for you:
[robbie@on4hu] /ip route> set 0 gateway=44.144.4.1 [robbie@on4hu] /ip route> enable 0 [robbie@on4hu] /ip route> pr detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 A S dst-address=0.0.0.0/0 gateway=44.144.4.1 gateway-status=44.144.4.1 reachable via ovpn-adc distance=1 scope=30 target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-gateway distance=1 scope=30 target-scope=10 vrf-interface=ether1-gateway
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gateway=ovpn-adc gateway-status=ovpn-adc reachable distance=0 scope=10
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.129 gateway=bridge-local gateway-status=bridge-local reachable distance=0 scope=10
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway=ether1-gateway gateway-status=ether1-gateway reachable distance=0 scope=10
I am now able to ping your router on 44.144.11.129 and 44.144.4.2 However still not able to ping or access 44.144.11.136
Are you sure you have set the default gateway on this machine to 44.144.11.129 ?
73s Robbie
On Thu, Jan 16, 2014 at 7:44 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and I do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local router
ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16 dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connection new-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpn
So since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44.144.11.129 and 44.144.4.2 is reachable now. One step solved :-)
Marius & Andre,
I confirm the same... Both IP's reachable.
Tom - sp2lob
Robies below my table wheel, what should I do to make as gateway 44.144.11.129
http://www.google.com/url?source=transpromo&rs=rsmf&q=http://translate.google.com/globalmarketfinder/%3Flocale%3Dfr [root@localhost on4hu]# route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth1 44.144.11.128 0.0.0.0 255.255.255.240 U 10 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth1 [root@localhost on4hu]# [root@localhost on4hu]# arp -n Address HWtype HWaddress Flags Mask Iface 44.144.11.129 ether d4:ca:6d:b6:c6:87 C eth0 192.168.1.1 ether 1c:df:0f:e5:10:d6 C eth1 192.168.1.4 ether 00:26:2d:2b:7e:62 C eth1 192.168.1.2 ether 00:24:21:52:81:22 C eth1 [root@localhost on4hu]#
André ON4HU
Le 16/01/14 20:08, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
I have fixed the configuration for you:
[robbie@on4hu] /ip route> set 0 gateway=44.144.4.1 [robbie@on4hu] /ip route> enable 0 [robbie@on4hu] /ip route> pr detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 A S dst-address=0.0.0.0/0 gateway=44.144.4.1 gateway-status=44.144.4.1 reachable via ovpn-adc distance=1 scope=30 target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-gateway distance=1 scope=30 target-scope=10 vrf-interface=ether1-gateway
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gateway=ovpn-adc gateway-status=ovpn-adc reachable distance=0 scope=10
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.129 gateway=bridge-local gateway-status=bridge-local reachable distance=0 scope=10
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway=ether1-gateway gateway-status=ether1-gateway reachable distance=0 scope=10
I am now able to ping your router on 44.144.11.129 and 44.144.4.2 However still not able to ping or access 44.144.11.136
Are you sure you have set the default gateway on this machine to 44.144.11.129 ?
73s Robbie
On Thu, Jan 16, 2014 at 7:44 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and I do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local router
ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16 dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connection new-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpn
So since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hello André,
You currently have your default route set to your VDSL router. Since this router does not know amprnet the outbound traffic is still send and blackholed to the internet.
You have 2 options:
1) If you only want to make the box reachable from amprnet (44.x.x.x) you can add a static route: Destination: 44.0.0.0/8 Gateway: 44.144.11.129
This can be done with eg the command:
route add -net 44.0.0.0/8 gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to add persistent static routes.
2) If you want the make the box reachable from amprnet and the public internet on its 44.144.11.136 address, you need to change the default gateway. Since we advertise 44.144 via BGP to the internet you can then use the 44.144.11.136 address instead of on4hu.dyndns.org for access from the internet. BEWARE: As stated before you are advised to put a firewall in place to only open needed ports to the public internet !!!!
This can be done with eg the commands:
route del default route add default gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to change the default gateway.
73s Robbie ON4SAX
On Thu, Jan 16, 2014 at 9:04 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Robies below my table wheel, what should I do to make as gateway 44.144.11.129
http://www.google.com/url?source=transpromo&rs=rsmf&q=http://translate.google.com/globalmarketfinder/%3Flocale%3Dfr [root@localhost on4hu]# route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth1 44.144.11.128 0.0.0.0 255.255.255.240 U 10 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth1 [root@localhost on4hu]# [root@localhost on4hu]# arp -n Address HWtype HWaddress Flags Mask Iface 44.144.11.129 ether d4:ca:6d:b6:c6:87 C eth0 192.168.1.1 ether 1c:df:0f:e5:10:d6 C eth1 192.168.1.4 ether 00:26:2d:2b:7e:62 C eth1 192.168.1.2 ether 00:24:21:52:81:22 C eth1 [root@localhost on4hu]#
André ON4HU
Le 16/01/14 20:08, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
I have fixed the configuration for you:
[robbie@on4hu] /ip route> set 0 gateway=44.144.4.1 [robbie@on4hu] /ip route> enable 0 [robbie@on4hu] /ip route> pr detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 A S dst-address=0.0.0.0/0 gateway=44.144.4.1 gateway-status=44.144.4.1 reachable via ovpn-adc distance=1 scope=30 target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-gateway distance=1 scope=30 target-scope=10 vrf-interface=ether1-gateway
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gateway=ovpn-adc gateway-status=ovpn-adc reachable distance=0 scope=10
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.129 gateway=bridge-local gateway-status=bridge-local reachable distance=0 scope=10
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway=ether1-gateway gateway-status=ether1-gateway reachable distance=0 scope=10
I am now able to ping your router on 44.144.11.129 and 44.144.4.2 However still not able to ping or access 44.144.11.136
Are you sure you have set the default gateway on this machine to 44.144.11.129 ?
73s Robbie
On Thu, Jan 16, 2014 at 7:44 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and I do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local router
ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16 dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connection new-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpn
So since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
thank you Robbie, this time it is understandable that you send me example. I will apply myself to make sure it works I am sorry to disturb you while you have a lot of work 73s André ON4HU
Le 17/01/14 10:10, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Hello André,
You currently have your default route set to your VDSL router. Since this router does not know amprnet the outbound traffic is still send and blackholed to the internet.
You have 2 options:
- If you only want to make the box reachable from amprnet (44.x.x.x)
you can add a static route: Destination: 44.0.0.0/8 Gateway: 44.144.11.129
This can be done with eg the command:
route add -net 44.0.0.0/8 gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to add persistent static routes.
- If you want the make the box reachable from amprnet and the public
internet on its 44.144.11.136 address, you need to change the default gateway. Since we advertise 44.144 via BGP to the internet you can then use the 44.144.11.136 address instead of on4hu.dyndns.org for access from the internet. BEWARE: As stated before you are advised to put a firewall in place to only open needed ports to the public internet !!!!
This can be done with eg the commands:
route del default route add default gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to change the default gateway.
73s Robbie ON4SAX
On Thu, Jan 16, 2014 at 9:04 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Robies below my table wheel, what should I do to make as gateway 44.144.11.129
http://www.google.com/url?source=transpromo&rs=rsmf&q=http://translate.google.com/globalmarketfinder/%3Flocale%3Dfr [root@localhost on4hu]# route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth1 44.144.11.128 0.0.0.0 255.255.255.240 U 10 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth1 [root@localhost on4hu]# [root@localhost on4hu]# arp -n Address HWtype HWaddress Flags Mask Iface 44.144.11.129 ether d4:ca:6d:b6:c6:87 C eth0 192.168.1.1 ether 1c:df:0f:e5:10:d6 C eth1 192.168.1.4 ether 00:26:2d:2b:7e:62 C eth1 192.168.1.2 ether 00:24:21:52:81:22 C eth1 [root@localhost on4hu]#
André ON4HU
Le 16/01/14 20:08, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
I have fixed the configuration for you:
[robbie@on4hu] /ip route> set 0 gateway=44.144.4.1 [robbie@on4hu] /ip route> enable 0 [robbie@on4hu] /ip route> pr detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 A S dst-address=0.0.0.0/0 gateway=44.144.4.1 gateway-status=44.144.4.1 reachable via ovpn-adc distance=1 scope=30 target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-gateway distance=1 scope=30 target-scope=10 vrf-interface=ether1-gateway
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gateway=ovpn-adc gateway-status=ovpn-adc reachable distance=0 scope=10
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.129 gateway=bridge-local gateway-status=bridge-local reachable distance=0 scope=10
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway=ether1-gateway gateway-status=ether1-gateway reachable distance=0 scope=10
I am now able to ping your router on 44.144.11.129 and 44.144.4.2 However still not able to ping or access 44.144.11.136
Are you sure you have set the default gateway on this machine to 44.144.11.129 ?
73s Robbie
On Thu, Jan 16, 2014 at 7:44 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and I do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate 2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope 3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s 4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local router
ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connectionnew-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpnSo since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
hello Robie some prble i ipted for the option 2
route del default route add default gw 44.144.11.129
from PC wher is the connction with the RouterBOARD or from any LAN PC i am connecterd to the routerBOARD never to the bbs ??????
André ON4HU
Le 17/01/14 10:10, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Hello André,
You currently have your default route set to your VDSL router. Since this router does not know amprnet the outbound traffic is still send and blackholed to the internet.
You have 2 options:
- If you only want to make the box reachable from amprnet (44.x.x.x)
you can add a static route: Destination: 44.0.0.0/8 Gateway: 44.144.11.129
This can be done with eg the command:
route add -net 44.0.0.0/8 gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to add persistent static routes.
- If you want the make the box reachable from amprnet and the public
internet on its 44.144.11.136 address, you need to change the default gateway. Since we advertise 44.144 via BGP to the internet you can then use the 44.144.11.136 address instead of on4hu.dyndns.org for access from the internet. BEWARE: As stated before you are advised to put a firewall in place to only open needed ports to the public internet !!!!
This can be done with eg the commands:
route del default route add default gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to change the default gateway.
73s Robbie ON4SAX
On Thu, Jan 16, 2014 at 9:04 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Robies below my table wheel, what should I do to make as gateway 44.144.11.129
http://www.google.com/url?source=transpromo&rs=rsmf&q=http://translate.google.com/globalmarketfinder/%3Flocale%3Dfr [root@localhost on4hu]# route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth1 44.144.11.128 0.0.0.0 255.255.255.240 U 10 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth1 [root@localhost on4hu]# [root@localhost on4hu]# arp -n Address HWtype HWaddress Flags Mask Iface 44.144.11.129 ether d4:ca:6d:b6:c6:87 C eth0 192.168.1.1 ether 1c:df:0f:e5:10:d6 C eth1 192.168.1.4 ether 00:26:2d:2b:7e:62 C eth1 192.168.1.2 ether 00:24:21:52:81:22 C eth1 [root@localhost on4hu]#
André ON4HU
Le 16/01/14 20:08, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
I have fixed the configuration for you:
[robbie@on4hu] /ip route> set 0 gateway=44.144.4.1 [robbie@on4hu] /ip route> enable 0 [robbie@on4hu] /ip route> pr detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 A S dst-address=0.0.0.0/0 gateway=44.144.4.1 gateway-status=44.144.4.1 reachable via ovpn-adc distance=1 scope=30 target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-gateway distance=1 scope=30 target-scope=10 vrf-interface=ether1-gateway
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gateway=ovpn-adc gateway-status=ovpn-adc reachable distance=0 scope=10
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.129 gateway=bridge-local gateway-status=bridge-local reachable distance=0 scope=10
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway=ether1-gateway gateway-status=ether1-gateway reachable distance=0 scope=10
I am now able to ping your router on 44.144.11.129 and 44.144.4.2 However still not able to ping or access 44.144.11.136
Are you sure you have set the default gateway on this machine to 44.144.11.129 ?
73s Robbie
On Thu, Jan 16, 2014 at 7:44 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and I do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate 2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope 3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s 4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local router
ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes in-interface=bridge-local
1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connectionnew-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing new-routing-mark=via_amprnet passthrough=yes connection-mark=from_vpnSo since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via AMPRNet VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
Works now from my system. Ping www and telnet connections to 44.144.11.136 work.
Congrats. Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of on4hu Sent: Friday, January 17, 2014 12:00 To: AMPRNet working group Subject: Re: [44net] on4hu on line
(Please trim inclusions from previous messages) _______________________________________________ hello Robie some prble i ipted for the option 2
route del default route add default gw 44.144.11.129
from PC wher is the connction with the RouterBOARD or from any LAN PC i am connecterd to the routerBOARD never to the bbs ??????
André ON4HU
Le 17/01/14 10:10, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Hello André,
You currently have your default route set to your VDSL router. Since this router does not know amprnet the outbound traffic is still send and blackholed to the internet.
You have 2 options:
- If you only want to make the box reachable from amprnet (44.x.x.x)
you can add a static route: Destination: 44.0.0.0/8 Gateway: 44.144.11.129
This can be done with eg the command:
route add -net 44.0.0.0/8 gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to add persistent static routes.
- If you want the make the box reachable from amprnet and the public
internet on its 44.144.11.136 address, you need to change the default gateway. Since we advertise 44.144 via BGP to the internet you can then use the 44.144.11.136 address instead of on4hu.dyndns.org for access from the internet. BEWARE: As stated before you are advised to put a firewall in place to only open needed ports to the public internet !!!!
This can be done with eg the commands:
route del default route add default gw 44.144.11.129
Please beware that this command does not persist a reboot. Please consult the documentation of your linux distribution to find out how to change the default gateway.
73s Robbie ON4SAX
On Thu, Jan 16, 2014 at 9:04 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Robies below my table wheel, what should I do to make as gateway 44.144.11.129
[root@localhost on4hu]# route -n Table de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use
Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth1 44.144.11.128 0.0.0.0 255.255.255.240 U 10 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 10 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth1 [root@localhost on4hu]# [root@localhost on4hu]# arp -n Address HWtype HWaddress Flags Mask Iface 44.144.11.129 ether d4:ca:6d:b6:c6:87 C eth0 192.168.1.1 ether 1c:df:0f:e5:10:d6 C eth1 192.168.1.4 ether 00:26:2d:2b:7e:62 C eth1 192.168.1.2 ether 00:24:21:52:81:22 C eth1 [root@localhost on4hu]#
André ON4HU
Le 16/01/14 20:08, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
I have fixed the configuration for you:
[robbie@on4hu] /ip route> set 0 gateway=44.144.4.1 [robbie@on4hu] /ip route> enable 0 [robbie@on4hu] /ip route> pr detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit 0 A S dst-address=0.0.0.0/0 gateway=44.144.4.1 gateway-status=44.144.4.1 reachable via ovpn-adc distance=1 scope=30 target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-gateway distance=1 scope=30 target-scope=10
vrf-interface=ether1-gateway
2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gateway=ovpn-adc gateway-status=ovpn-adc reachable distance=0 scope=10
3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.129 gateway=bridge-local gateway-status=bridge-local reachable distance=0 scope=10
4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway=ether1-gateway gateway-status=ether1-gateway reachable distance=0 scope=10
I am now able to ping your router on 44.144.11.129 and 44.144.4.2 However still not able to ping or access 44.144.11.136
Are you sure you have set the default gateway on this machine to 44.144.11.129 ?
73s Robbie
On Thu, Jan 16, 2014 at 7:44 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ hello Robbie I did absolutely nothing changed, I sent you an email on this subject, which you probably have not answered for lack of time I feel that the restoration on this router does not restore anything, I'll still make a new backup for you as I had already report without documentation in my native language I am unable to change anything and
I
do not touch can you confirm me about the backup otherwise how?? is what I am connectable or not ... that is the question Robbies 73s André ON4HU
Le 16/01/14 19:20, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
You have disabled the route back to the network:
[robbie@on4hu] > ip route print detail Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - m B - blackhole, U - unreachable, P - prohibit 0 X S dst-address=0.0.0.0/0 gateway=44.144.11.129 gateway-status=44.144.11.129 inactive distance=1 s target-scope=10 routing-mark=via_amprnet
1 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable via ether1-g scope=30 target-scope=10 vrf-interface=ether1-gate 2 ADC dst-address=44.144.4.0/24 pref-src=44.144.4.2 gate gateway-status=ovpn-adc reachable distance=0 scope 3 ADC dst-address=44.144.11.128/28 pref-src=44.144.11.12 gateway-status=bridge-local reachable distance=0 s 4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.100 gateway-status=ether1-gateway reachable distance=0
- The gateway for rule 0 should be 44.144.4.1 and not your local
router
ip. 2) You have disabled rule 0, meaning that all your outbound traffic is being sent through your VDSL provider which does not know amprnet and thus the packets die a lonely death in a blackhole on the internet. 3) FYI: There is a mangle rule that uses rule 0, just to be clear;
[robbie@on4hu] > ip firewall mangle print Flags: X - disabled, I - invalid, D - dynamic 0 chain=prerouting action=mark-routing
new-routing-mark=via_amprnet
passthrough=yes in-interface=bridge-local 1 chain=output action=mark-routing new-routing-mark=via_amprnet passthrough=yes src-address=44.144.0.0/16dst-address=!44.144.11.128/28
2 chain=prerouting action=mark-connectionnew-connection-mark=from_vpn passthrough=yes in-interface=ovpn-adc
3 chain=prerouting action=mark-routing
new-routing-mark=via_amprnet
passthrough=yes connection-mark=from_vpnSo since this route is disabled and misconfigured, no traffic is flowing back through the VPN to amprnet.
73s Robbie
On Thu, Jan 16, 2014 at 7:05 PM, sp2lob@tlen.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Marius,
Besides, 44.144.11.136 reachability I checked additionally via
AMPRNet
VPN generously provided by OH7LZB.
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN
WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/
ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
Andre,
Confirm also from my side it works O.K. now!
thank you all for the reports received, we contunue this momentum forward a stroke to 44.xx.xx.xx vy73s André ON4HU
Le 18/01/14 01:24, sp2lob a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Andre,
Confirm also from my side it works O.K. now!
I'm sorry Tom, because I have absolutely no aid, what use an ip address if it is not connectable My administrator 44net gives me absolutely nothing as information, I'm really disappointed it is the same system as with http://on4hu.be:81 vy73 André
Le 16/01/14 17:04, sp2lob@tlen.pl a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Andre,
Your 44.144.11.136 IP address is not present in latest encap.txt file, therefore is not accessible and not pingable from my own IP 44.165.2.2 OpenBCM is accessible on: http://on4hu.dyndns.org:81
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Dear Andre,
We have exchanged over a 100 mails. You cannot say i give you no information.
Sadly I am very busy on my dayjob now and have limited time for HAMradio.
73s Robbie
On Thu, Jan 16, 2014 at 5:16 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
I'm sorry Tom, because I have absolutely no aid, what use an ip address if it is not connectable My administrator 44net gives me absolutely nothing as information, I'm really disappointed it is the same system as with http://on4hu.be:81 vy73 André
Le 16/01/14 17:04, sp2lob@tlen.pl a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Andre,
Your 44.144.11.136 IP address is not present in latest encap.txt file, therefore is not accessible and not pingable from my own IP 44.165.2.2 OpenBCM is accessible on: http://on4hu.dyndns.org:81
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Robbies yes I'm exaggerating a little, and I understand that you're busy but that is three months following that absolutely alone in my corner to not even be able to use 44net however it can serve this 44netsi I'm not connectable?? if no one can contact me on this network André ON4HU
Le 16/01/14 17:18, Robbie De Lise a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Dear Andre,
We have exchanged over a 100 mails. You cannot say i give you no information.
Sadly I am very busy on my dayjob now and have limited time for HAMradio.
73s Robbie
On Thu, Jan 16, 2014 at 5:16 PM, on4hu on4hu.0@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
I'm sorry Tom, because I have absolutely no aid, what use an ip address if it is not connectable My administrator 44net gives me absolutely nothing as information, I'm really disappointed it is the same system as with http://on4hu.be:81 vy73 André
Le 16/01/14 17:04, sp2lob@tlen.pl a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Andre,
Your 44.144.11.136 IP address is not present in latest encap.txt file, therefore is not accessible and not pingable from my own IP 44.165.2.2 OpenBCM is accessible on: http://on4hu.dyndns.org:81
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-- forum => http://on4hu.be/phpbb/ inscrivez vous? New MediaWiki => http://on4hu.be/MediaWiki http://on4hu.dyndns.org:81/ http://www.on4hu.be/ ftp://ftp.on4hu.be/ ou ftp://on4hu.dyndns.org/ COMPUTERS ARE LIKE AIR-CONDITIONERS THEY STOP WORKING PROPERLY AS SOON AS YOU OPEN WINDOWS.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Hi again Andre,
The last reachable router to your system on the network is 44.144.208.6. IMHO that's where you should start digging.
Marius, YO2LOJ
Hi Andre,
It seems that your GW is 44.224.12.238. If that is the case, that one is reachable, but no reply beyond that comes thru.
Marius, YO2LOJ
YO2LOJ Marius thank you, on my side I can not do anything to make it usable vy73s André
Le 16/01/14 17:41, Marius Petrescu a écrit :
(Please trim inclusions from previous messages) _______________________________________________ Hi Andre,
It seems that your GW is 44.224.12.238. If that is the case, that one is reachable, but no reply beyond that comes thru.
Marius, YO2LOJ
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Marius et al,
Yeah, but 44.224.12.238 is an MikroTik v6.7 router which itself responds to pings of course...
Best regards. Tom - sp2lob
Prolly got the same issue. On Jan 16, 2014 1:36 PM, "Bill Vodall" wa7nwp@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________
What? No uber wideband RF link to the ISP?
Or even better - the ham next door....
Bill _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Bill Vodall -
Brian Kantor -
Jerry -
Marius Petrescu -
Mark Phillips -
on4hu -
Robbie De Lise -
sp2lob -
sp2lob＠tlen.pl