Skip to content

ispunity setup error - Error: an inet prefix is expected rather than "equalize". #15

@rtdp

Description

@rtdp

This is on openSuse 12.1 machine.
I was trying to connect with two of the ISPs. Below is ispunity setup command log -


linux-vai9:~ # cat /var/log/ispunity.log 
2012-06-01 20:17:45 INFO Configuration file successfully read
2012-06-01 20:17:45 INFO Isp Object succesfully created!
2012-06-01 20:17:45 INFO Routing Rable file successfully read!
2012-06-01 20:17:45 INFO Isp Object succesfully created!
2012-06-01 20:17:45 INFO Isp Object succesfully created!
2012-06-01 20:17:45 INFO New Isp's successfully added  to rt_table
2012-06-01 20:17:45 INFO Route commands successfully built
2012-06-01 20:17:45 DEBUG Route Command: ["/sbin/ip route add 115.242.67.0/24 dev ppp0 src 115.242.67.32 table reliance", "/sbin/ip route add default via 220.224.141.129 table reliance", "/sbin/ip route add 192.168.1.0/24 dev wlan0 src 192.168.1.137 table josh", "/sbin/ip route add default via 192.168.1.1 table josh"]
2012-06-01 20:17:45 INFO Successfully created routes
2012-06-01 20:17:45 INFO Rule commands successfully built
2012-06-01 20:17:45 DEBUG Rule Command: ["/sbin/ip rule add from 115.242.67.32 table reliance", "/sbin/ip rule add from 192.168.1.137 table josh"]
2012-06-01 20:17:45 INFO Successfully created rules
2012-06-01 20:17:47 INFO 0% packet loss for reliance
2012-06-01 20:17:47 INFO reliance is online
2012-06-01 20:17:49 INFO 0% packet loss for josh
2012-06-01 20:17:49 INFO josh is online
2012-06-01 20:17:49 INFO Multiple isps are alive
2012-06-01 20:17:49 INFO Load Balancing commands successfully built
2012-06-01 20:17:49 DEBUG Load Balance Command: ["/sbin/ip route replace equalize default  nexthop via 220.224.141.129 dev ppp0 weight 1  nexthop via 192.168.1.1 dev wlan0 weight 1 "]
2012-06-01 20:17:49 INFO Successfully load balancing done
2012-06-01 20:23:02 INFO Configuration file successfully read
2012-06-01 20:23:02 INFO Isp Object succesfully created!
2012-06-01 20:23:02 INFO Routing Rable file successfully read!
2012-06-01 20:23:02 INFO Isp Object succesfully created!
2012-06-01 20:23:02 INFO Isp Object succesfully created!
2012-06-01 20:23:02 INFO New Isp's successfully added  to rt_table
2012-06-01 20:23:02 INFO Route commands successfully built
2012-06-01 20:23:02 DEBUG Route Command: ["/sbin/ip route add 115.242.67.0/24 dev ppp0 src 115.242.67.32 table reliance", "/sbin/ip route add default via 220.224.141.129 table reliance", "/sbin/ip route add 192.168.1.0/24 dev wlan0 src 192.168.1.137 table josh", "/sbin/ip route add default via 192.168.1.1 table josh"]
2012-06-01 20:23:02 INFO Successfully created routes
2012-06-01 20:23:02 INFO Rule commands successfully built
2012-06-01 20:23:02 DEBUG Rule Command: []
2012-06-01 20:23:02 INFO Successfully created rules
2012-06-01 20:23:04 INFO 0% packet loss for reliance
2012-06-01 20:23:04 INFO reliance is online
2012-06-01 20:23:06 INFO 0% packet loss for josh
2012-06-01 20:23:06 INFO josh is online
2012-06-01 20:23:06 INFO Multiple isps are alive
2012-06-01 20:23:06 INFO Load Balancing commands successfully built
2012-06-01 20:23:06 DEBUG Load Balance Command: ["/sbin/ip route replace equalize default  nexthop via 220.224.141.129 dev ppp0 weight 1  nexthop via 192.168.1.1 dev wlan0 weight 1 "]
2012-06-01 20:23:06 INFO Successfully load balancing done

Command that can reproduce this error -

linux-vai9:~ # /sbin/ip route replace equalize default  nexthop via 220.224.141.129 dev ppp0 weight 1  nexthop via 192.168.1.1 dev wlan0 weight 1
Error: an inet prefix is expected rather than "equalize".

Command that can make it work -

linux-vai9:~ # /sbin/ip route replace default scope global  nexthop via 220.224.141.129 dev ppp0 weight 1  nexthop via 192.168.1.1 dev wlan0 weight 1
linux-vai9:~ # ip route show
default 
nexthop via 220.224.141.129  dev ppp0 weight 1
nexthop via 192.168.1.1  dev wlan0 weight 1
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.137  metric 2 
220.224.141.129 dev ppp0  proto kernel  scope link  src 115.242.67.32 

Let me know if some other details required.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions