44net

44net@mailman.ampr.org

3196 discussions

Lost my subnet...
by jerome schatten 19 Jul '17

19 Jul '17

Yesterday I lost all the folks I had links with… Today after much head scratching I decided to look at my gateway on the ampr portal. The gateway addy is 174.6.225.73 and the subnet I had WAS 44.135.172.0/29 My 44 addy is 44.135.172.128 So at the portal it says: 'network not found' I don’t find this block of four addresses in the available networks list to add it back in. Help please. Confused in Vancouver jerome - ve7ass

3 5

MikroTik Routers
by Marc Williams 18 Jul '17

18 Jul '17

Good afternoon all, Unfortunately I made little progress with my home setup due to the joys of work and real life demands.Anyway sob story aside I have a little spare time again so I am looking to get a MikroTik router ordered.So my question is do I need to adhere to a minimum spec? The memory and processor specs seem to very greatly. Thanks in advance. Marc (2W0PNT)

4 7

Lost my subnet... Still More
by jerome schatten 18 Jul '17

18 Jul '17

And also, none of the folks I’m linked to can connect to me if they are using the rip broadcasts or the list. I’m probably not the only one that has this problem. I seem to remember a cleansing of the gateways that are inactive, maybe you can fix this so that those whose CPE no longer allows rip to function (the ‘bitten’) can still make use of the system. j. ve7ass ----------------- And of course I’m no longer in the gateways list… If this is because I don’t reply to pings, unfortunately I can no longer receive gateway broadcasts so that would be expected, no? jerome _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

2 1

Lost my subnet... More
by jerome schatten 18 Jul '17

18 Jul '17

And of course I’m no longer in the gateways list… If this is because I don’t reply to pings, unfortunately I can no longer receive gateway broadcasts so that would be expected, no? jerome

2 1

Re: [44net] MikroTik Routers
by Rob Janssen 18 Jul '17

18 Jul '17

> In my case, where we run a BGP session with Internet and publish our assigned segment, we use a CCR1036 having in memory the full BGP routing table, but even so, this is not a compulsory requirement for you. Indeed for doing BGP on internet you need such a router. To do BGP on AMPRnet (i.e. internal routes only) the RB750Gr3 is good enough. > In example, you can configure a less expensive router with only a default gateway to your ISP and/or to the ISP that runs the BGP session for you (if that would be the case). This is what we do at our gateway as well. The ISP advertises our network and routes the traffic to our system. > If you want to launch a traceroute from public Internet, just to demonstrate above setup, you can use 44.133.233.8 It does not answer to us. First hop is 88.26.246.131 via IPIP tunnel. > Being said that, and nonetheless, I don’t think a Mikrotik RB750 is a good idea as it quite skimpy to have many things running at the same time. > A Mikrotik RB2011 (no Wi-Fi) and above will be, for sue, very good platforms to play with. Remember the suggestion was not the RB750 but the RB750Gr3. This is an entirely different thing. It is more powerful than the RB2011. (but has less ports of course) Rob

1 0

Re: [44net] MikroTik Routers
by Rob Janssen 14 Jul '17

14 Jul '17

> Thanks Rob, so I can ignore all the wiki instructions then and follow the script and read me? Yes > I assume I don't want to use a dmz but put my vdsl router into dumb bridged modem mode? Well that is usually better (when you don't want to be bitten by DMZ bugs), however that complicates things a little bit. Maybe it is better to make that your second experiment :-) When you want to put the VDSL router in bridged mode, you probably also want the MikroTik to double-up as a NAT router for your normal internet use. In itself that is not a problem, it can do that. But it requires a little more study of the matter, especially when you want to be able to talk from AMPRnet to internet (no NAT) and at the same time want to talk from your RFC1918 LAN to internet using NAT. This involves using "policy routing", i.e. two route tables, one for each usage, and "IP Route Rule" settings to select the proper routing table based on source address. Like this: /ip route rule add src-address=44.x.x.x/28 table=ampr then put all AMPRnet routes in the table "ampr". the normal table "main" has the "internet" routes. Traffic from your normal LAN (e.g. 192.168.88.x) to normal internet addresses is routed via the "main" table where there is a default route to your ISP, traffic from your AMPRnet network 44.x.x.x/28 is routed to the "ampr" table where there are the 600 or so tunnel routes and a default route pointing to amprgw. You may also want to separate the LAN side in two different networks, either by reserving physical ports for each network or by using a tagged VLAN for one of the networks. Can be done as well. Almost anything can be done using these routers. However, trying to do it all at once and finding out everything with your network lying in shambles because you re-configured your VDSL router to bridge mode at the same time is not the easiest way forward :-) So, first experiment a bit with the modem in DMZ mode and the MikroTik behind it, find out how things operate, lock yourself out and find out how to recover, etc. Then you can more easily move on to a more complex configuration by adding the above mentioned things. Rob

1 0

Re: [44net] MikroTik Routers
by Rob Janssen 14 Jul '17

14 Jul '17

> Excellent thank you I now have one on order. > Does anyone know if the setup on the wiki is still current or given recent changes is there a new one? Well, the text about MikroTik router setup on the wiki is not something you would want to do, as it only installs a single tunnel to UCSD, but at the bottom it refers to the YO2LOJ site and the script you can find there (get the latest version) and the directions for installing it are the way to go to get it on the IPIP mesh. Of course you can use it in a lot of other ways (also at the same time), depending on the local radio network available. We use these routers (from their availability mostly RB750Gr3, before that some RB2011 and RB750 versions) as routers in our radio network as well, each running a couple of links to neighbors and using BGP as an autorouting protocol. In some areas it is also possible to setup a VPN to some nearby gateway that is on the mesh and/or is directly routed on Internet. Rob

2 1

Re: [44net] MikroTik Routers
by Rob Janssen 14 Jul '17

14 Jul '17

> I think the RB750GR3 is the best bang for your buck if you don't need > POE or SFP.https://routerboard.com/RB750Gr3 It sure is! Make sure you get the r3 version, not the earlier ones. It is much more powerful than the RB750 (no G) and RB2011. (of course it has only 5 ports and no WiFi) Rob

2 1

Re: [44net] gw.ampr.org from tunnel system
by Rob Janssen 13 Jul '17

13 Jul '17

> Try turning off RPF (return path filtering at the kernel level) if it goes out on one interface and comes in the other, then RPF is almost always at fault as it will by default drop the connection I expect it is something invisible and nasty like that, but rp_filter is not active on that system. (I never enable this because it is so difficult to monitor what it does... on gw-44-137 I use packet marking using the "rpfilter" matcher in mangle and drop of the marked packets with logging in the filter) Rob

1 0

Re: [44net] gw.ampr.org from tunnel system
by Rob Janssen 13 Jul '17

13 Jul '17

> The strange thing is that ping works ok when TCP doesn't connect. > My first suspicion would be a stateful firewall, but I'm sure you > checked that. Could it be a TTL problem? I'm just guessing here. The TTL of the inside IP packet is 63. I first traced on the external interface and saw the encapsulated packet, then I traced on the tunl0 interface and saw the decapsulated packet (same without the outer IP header), and it all looks OK. I see the SYN going out,the SYN ACK coming in, but nothing more (ACK should go out). The firewall is stateful but I added an explicit accept for -s 44.0.0.1 at the top of all the rules to make sure it is not that. Also, I reset the firewall and watched the counters, did not see any packets being dropped. And indeed, ping works OK. It is strange. Maybe something is wrong due to the gateway external address change, although I would not know what could produce the above scenario. The system is up for about a year, maybe I should try rebooting it. (usually this brings nothing when I try it... it isn't Windows :-) Of course sometime it will become clear how this can be explained. Rob

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net