RIP $100 {awarded}
-
I haven't the time to personally test this any time soon. If anyone interested could test this pfSense RIP with even your home router (assuming it has RIP), I can go ahead and award this bounty.
Thanks, -pc -
Do other devs count? I would love to help Bill get some loving, too ;)
-
Of course!
Thanks, -pc -
Of course!
Thanks, -pcThanks, I'll work on wrapping this up this weekend then. Just been waiting for you to have time to be able to test ;)
–Bill
-
Of course!
Thanks, -pcThanks, I'll work on wrapping this up this weekend then. Just been waiting for you to have time to be able to test ;)
–Bill
OK, routed package posted. It has the following features:
Supports RIP v1 and RIP v2
Allows you to choose which interface to run RIP on (the version is global, can't choose per interface)
Allows you to set a RIP v2 password (this will apply to all RIP enabled interfaces)Some of the items I wanted to add (individual settings per interface) weren't an option with our current package code. It was my understanding this wasn't a requirement. If the package is considered acceptable, I'd be willing to create a patch to enable this functionality on an embedded install (packages only work on full installs).
–Bill
-
this a nice package!
-
-
it installs and starts for me.
root 77143 0.0 0.8 1356 956 ?? Ss 11:54PM 0:00.30 /sbin/routedI also see packets on the wire:
[buraglio@precious:~ ] sudo tcpdump -i en1 -vvv -s 1500 port 520 <3045>
tcpdump: listening on en1, link-type EN10MB (Ethernet), capture size 1500 bytes
00:00:48.897769 IP (tos 0x0, ttl 1, id 11754, offset 0, flags [none], length: 92) 192.168.209.1.router > rip2-routers.mcast.net.router: [udp sum ok]
RIPv2, Response, length: 64, routes: 3
Simple Text Authentication data: password
AFI: IPv4: 192.168.209.0/27, tag 0x0000, metric: 1, next-hop: self
AFI: IPv4: dhcp-74-136-192-0.insightbb.com/19, tag 0x0000, metric: 1, next-hop: self
0x0000: 0202 0000 ffff 0002 7061 7373 776f 7264
0x0010: 0000 0000 0000 0000 0002 0000 c0a8 d100
0x0020: ffff ffe0 0000 0000 0000 0001 0002 0000
0x0030: 4a88 c000 ffff e000 0000 0000 0000 0001
00:01:18.899978 IP (tos 0x0, ttl 1, id 725, offset 0, flags [none], length: 92) 192.168.209.1.router > rip2-routers.mcast.net.router: [udp sum ok]
RIPv2, Response, length: 64, routes: 3
Simple Text Authentication data: password
AFI: IPv4: 192.168.209.0/27, tag 0x0000, metric: 1, next-hop: self
AFI: IPv4: dhcp-74-136-192-0.insightbb.com/19, tag 0x0000, metric: 1, next-hop: self
0x0000: 0202 0000 ffff 0002 7061 7373 776f 7264
0x0010: 0000 0000 0000 0000 0002 0000 c0a8 d100
0x0020: ffff ffe0 0000 0000 0000 0001 0002 0000
0x0030: 4a88 c000 ffff e000 0000 0000 0000 0001It starts and stops from the gui.
I'll bounce the box and hopefully get another RIP enabled device on tomorrow.nb
-
Ship it!
j/k
-
Sorry for the delay, I finally got around to bouncing this box that's running routed and found that it was not running after a restart. /usr/local/etc/rc.d/ did not have a startup script for routed which would pobably explain it. I reinstalled the pkg which of course restarted the service but there was still no startup script so I don't expect it to be running after a restart.
So if it operates as I'm reading it should a simple startup script should start it and begin forwarding packets among the connected nets (since the box is acting as a router). I don't have anything else that runs rip close by that I can test with to see but as I saw before it's at least talking as I'd expect it to.This worked at the most basic level (starting and stopping the service) on my box:
–snip
#!/bin/sh
rc_start() {
/sbin/routed
}rc_stop() {
/usr/bin/killall routed
}case $1 in
start)
rc_start
;;
stop)
rc_stop
;;
restart)
rc_stop
rc_start
;;
esac---snip
--nb
-
Gah, thanks, I'll get that added.
–Bill
-
Gah, thanks, I'll get that added.
–Bill
Bah, this showed a bug in package startup, thanks, fixed now in HEAD. Waiting on Scott to sync the change back to RELENG_1 (although now we've gotta check the known working packages to make sure I didn't just break them…doh!)
--Bill
-
Has anyone verifed RIP as working and communicating routes with other RIP devices yet?
Thanks, -pc -
Has anyone verifed RIP as working and communicating routes with other RIP devices yet?
Thanks, -pcNot that I'm aware of.
–Bill
-
Can someone please verify that this pacakge works so we can close out this bounty? Thanks!
-
Since nobody is interested in providing feedback on this package, I've pulled it from RELENG_1. If there's not feedback on it during our next beta cycle it won't make it into 1.1 either.
–Bill
-
Hi all
have installed this package in 3 pf in my test lab, and configured with RIP v2, all the pfs work in routing mode, without NAT, But when i go to Diagnostics -> Routes, there is nothing. I have to do something else, to get this package working?
-
Hi all
have installed this package in 3 pf in my test lab, and configured with RIP v2, all the pfs work in routing mode, without NAT, But when i go to Diagnostics -> Routes, there is nothing. I have to do something else, to get this package working?
I bet Diagnostics->Routes only shows static routes (as it's part of core). I'll check that out tonight and see if it makes sense to modify that screen to show dynamic routes (probably) or if it's something that needs to be added to the package specifically.
–Bill
-
Works fine here between a RELENG_1 (1.0RC3) and a HEAD box (CVS current). I see the advertised routes from each box under Diagnostics->Routes
–Bill
-
Works fine here between a RELENG_1 (1.0RC3) and a HEAD box (CVS current). I see the advertised routes from each box under Diagnostics->Routes
–Bill
OK, wild guess here, you probably are using RIP v1 not v2. dsh@ and I did find some more bugs in this package and I spent some time reworking it tonight. Please reinstall the package and re-save and let me know how it works. If we can get this package tested and confirmed in the next couple days, I'll mark it stable and include it in 1.0. Thanks
–Bill