auscom
asked on
RIP WAN Advertising Default Route BSD/Unix
We're trying to implement a RIP WAN where Site A is the only internet facing site.
We use pfSense firewalls across all sites which are BSD based, the standard BSD RIP Daemon 'routed' is install and enabled.
Site A is advertising all of its routes correctly except for the default route and I'm completely stumped on how to get this to work correctly.
I've tried things such as
root@localhost: routed -g
~ routed -F 0/0,1
Adding fake_default=1 to /etc/gateways
If I try to do something like adding this to /etc/gateways
net 0.0.0.0 gateway 172.22.0.14 metric 1 active
I get a bad net message saying I can't have that as the default route which is confusing as I can find a few people that have used something like that as an example or in lab scenarios.
Cisco routers have the "default-originate" command which takes care of this function and from reading the routed(8) article on the BSD page it would appear that "routed -g" SHOULD do the same but using this option seems to do nothing.
Am I missing something here? Or are there more hoops to jump through to get this default route to go out?
We use pfSense firewalls across all sites which are BSD based, the standard BSD RIP Daemon 'routed' is install and enabled.
Site A is advertising all of its routes correctly except for the default route and I'm completely stumped on how to get this to work correctly.
I've tried things such as
root@localhost: routed -g
~ routed -F 0/0,1
Adding fake_default=1 to /etc/gateways
If I try to do something like adding this to /etc/gateways
net 0.0.0.0 gateway 172.22.0.14 metric 1 active
I get a bad net message saying I can't have that as the default route which is confusing as I can find a few people that have used something like that as an example or in lab scenarios.
Cisco routers have the "default-originate" command which takes care of this function and from reading the routed(8) article on the BSD page it would appear that "routed -g" SHOULD do the same but using this option seems to do nothing.
Am I missing something here? Or are there more hoops to jump through to get this default route to go out?
ASKER
Example from BSD page
net Nname[/mask] gateway Gname metric value <passive | active | extern>
Have tried
net 0.0.0.0/0.0.0.0 gateway 172.22.0.14 metric 1 active
net 0.0.0.0 mask 0.0.0.0 gateway 172.22.0.14 metric 1 active
Also tried playing with the subnet parameter: subnet=nname[/mask][,metri c]
subnet=0.0.0.0/0.0.0.0,1
subnet=0.0.0.0/0,1
All with no luck when starting up the routed daemon it reports there is a bad line in /etc/gateways
If I add to Site B's /etc/gateways
net 0/0 gateway 172.22.0.5 metric 1 active
This seems to be the correct format as it accepts the line but then reports
bad net "0/0" in /etc/gateways entry "net 0/0 gateway 172.22.0.5 metric 1 active"--cannot be default
net Nname[/mask] gateway Gname metric value <passive | active | extern>
Have tried
net 0.0.0.0/0.0.0.0 gateway 172.22.0.14 metric 1 active
net 0.0.0.0 mask 0.0.0.0 gateway 172.22.0.14 metric 1 active
Also tried playing with the subnet parameter: subnet=nname[/mask][,metri
subnet=0.0.0.0/0.0.0.0,1
subnet=0.0.0.0/0,1
All with no luck when starting up the routed daemon it reports there is a bad line in /etc/gateways
If I add to Site B's /etc/gateways
net 0/0 gateway 172.22.0.5 metric 1 active
This seems to be the correct format as it accepts the line but then reports
bad net "0/0" in /etc/gateways entry "net 0/0 gateway 172.22.0.5 metric 1 active"--cannot be default
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ah I was thrown off a little bit from the manual, the description of pm_rdisc refers to broadcasting a default route for RIPv1 and I did not try playing with this switch.
This with a combination of an outbound NAT entry and internet traffic is now flowing as it should.
Thanks
This with a combination of an outbound NAT entry and internet traffic is now flowing as it should.
Thanks
Not sure whether CIDR notation 0.0.0.0/0 will be accepted.