hello Radek,
You can do the route add command as part of bringing up a network interface
We often put a separate loopback address on an interface to make an
address available
via OSPF on our network...
if you add in a loopback interface with the /32 route and then add the
loopback interface to
Hello Bradley,
> It will look silly but maybe it works?
It looks silly, but it works well, thank you.
[10.109.3.15] $ cat /etc/hostname.vr0
-inet
inet 10.109.3.15 255.255.255.0
[10.109.3.15] $ cat /etc/hostname.vr3
inet 10.1.111.1 255.255.255.0
!route add 10.1.111.11 10.1.111.11
!route add
Hello
Maybe try doing the IP of the host you want to go to?
It will look silly but maybe it works?
Aka
!route add 10.1.111.11 10.1.111.11
That worked on my attempt even without sleeping
See if that helps.
On Thu, 9 Feb 2023, 22:59 Radek, wrote:
> Hello Bradley,
> if I add that route to
Hello Bradley,
if I add that route to /etc/hostname.vr3 I have no access to 10.1.111.11, even
from the local router.
After reboot I have to delete and add that route again by hand to make
everything work (sometimes I have to repeat delete/add few times to make it
work). It's 7.2/i386.
Any idea?
Hi,
I see a small mistake
You need to add that route to vr3 interface when you bring it up, vr0 will
most likely be up before vr3 so that is why your route adding in the
hostname.vr0 is wrong.
Cheers
On Thu, 9 Feb 2023, 01:36 Radek, wrote:
> Hello Bradley,
> thank you, your setup works the
Hello Bradley,
thank you, your setup works the way I need.
I can't deal with adding the static route permanently. I have to add the static
route by hand (route add 10.1.111.11/32 10.1.111.1) after reboot.
Did I missed something?
[10.109.3.15] $ cat /etc/hostname.vr0
-inet
dhcp
#inet
Hi all,
I have done an experiment.
If your interface is part of an area, it will be advertised always.
If you wanted to advertise only /32 this is how I got mine to work.
Ensure your interface vr3 is not in your ospf area
Add a static route to the one you wish to advertise, it appears that
Hello,
> I’d check the databases on both sides.
> And flush/reload the config and fibs.
I reloaded and restarted OSPFd on both sides - nothing changes. Then, I
rebooted routers on both sides - nothing changes.
I still can see/ping the whole 10.1.111.0/24 subnet from the far end.
[10.109.3.15]$
Hello,
I’d check the databases on both sides.
And flush/reload the config and fibs.
Then check again which link state advertisements are in the database.
To make sure you now get the /32 advertised.
Sent from my iPhone
> On 5 Feb 2023, at 21:15, Radek wrote:
>
> Hello Diederik, hello Tom,
>
Hello Diederik, hello Tom,
this is a simple lab/testing configuration, that's why there is no "passive"
and other...
The purpose of this configuration is to allow access to certain IP address and
restrict access to the rest of the subnet.
I can use PF to block/pass what I need... but I'm trying
Hi Radek,
it is better practice to add ospf network statements to ospfd.conf
(if you dont want to send / recieve ospf messages on an interface set the
interface to passive in ospfd.conf
avoid redistribute connected
(add the network you want to be added to your ospf network) and leave the
other
Hello Radek,
Rather than using “redistribute connected” use “redistribute ”
ospfd.conf
redistribute 10.1.111.20/32
redistribute 10.1.111.16/30
Greetings,
Diederik
Sent from my iPhone
> On 4 Feb 2023, at 20:55, Radek wrote:
>
> Hello,
> is it possible to announce over OSPF only one
Hello,
is it possible to announce over OSPF only one (or a few specific) IP address
instead of the whole subnet?
If yes.. an ospfd.conf example would be appreciated.
$ cat /etc/hostname.vr3
inet 10.1.111.1 255.255.255.0
$ cat /etc/ospfd.conf
router-id 10.109.3.15
redistribute connected
area
13 matches
Mail list logo
