Re: [44net] ipencap routing question

Roland, * I tested on a Ubuntu system, so the 'sudo modprobe -r ipip' command worked as tested. I gleaned to use it '-r' from the Startampr wiki (I developed the script with PE1CHL and others on the mailing group here). Therefore, I cannot speak specifically to why Debian automatically pre-loads the Kernel module. Can you explain the issue this presents for you? Could a firewall rule fix it? You only have a single /32 IP - this shouldn't cause a major issue to your setup. * Can you show the Wiki URL you're referencing that tells you to make a route for 44.0.0.0/9 and 44.128.0.0/10 - so it may be corrected? I know the routes to be invalid; because they do not specify where those subnets in the /9 and /10 are exactly located (e.g. your IP 86.5x.x.42 to reach 44.130.240.3/32). That's what ampr-ripd or rip44d does. You should now be able to see valid routes by running the command 'ip route show table 44' * You noted you're running ampr-ripd...but answered no....that confused me, but nonetheless I see it's running successfully; perhaps it was semantics or a language barrier. - KB3VWG :-) I was, but not more The modules is available by default in stock debian. Ok, why do you think so? These are not my invention, I copied them from templates in the ampr wiki. AFAIK they refelct the fact of the sold upper quater of the addresses, no? No, I am using ampr-ripd.