>One more thing:
>While I can access ospfd thru quaggaadm no problem, I get a connection
>refused while trying to access zebra.
>Does the quaggaadm-accessebility for zebra need to be configured
>somewhere?
OK - at least, I solved this part.
While ospf was accessible via telnet from the start, zebra wasn't:
r...@kunde003-wan:/etc/inet# routeadm -l ospf:quagga
svc:/network/routing/ospf:quagga:
config_file =
group =
pid_file =
user =
value_authorization = solaris.smf.value.routing
vty_address = 127.0.0.1
vty_port = 2604
r...@kunde003-wan:/etc/inet# routeadm -l zebra:quagga
svc:/network/routing/zebra:quagga:
batch = false
config_file =
group =
pid_file =
stability = Evolving
user =
value_authorization = solaris.smf.value.routing
vty_address =
vty_port = 0
After a bit of googling, I found that zebra seems to like port 2602, so:
r...@kunde003-wan:/etc/inet# routeadm -m zebra:quagga
vty_address="127.0.0.1"
r...@kunde003-wan:/etc/inet# routeadm -m zebra:quagga vty_port="2602"
Followed by a reload of the service, this got me on the zebra / horse
with quaggaadm.
Cheers,
Kai
_______________________________________________
networking-discuss mailing list
[email protected]
