{"action":"created","issue":{"url":"https://api.github.com/repos/troglobit/smcroute/issues/36","repository_url":"https://api.github.com/repos/troglobit/smcroute","labels_url":"https://api.github.com/repos/troglobit/smcroute/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/troglobit/smcroute/issues/36/comments","events_url":"https://api.github.com/repos/troglobit/smcroute/issues/36/events","html_url":"https://github.com/troglobit/smcroute/issues/36","id":156482960,"number":36,"title":"Daemon error: Failed adding VIF for iface eth1: Cannot assign the requested address","user":{"login":"spyhunter99","id":1975321,"avatar_url":"https://avatars.githubusercontent.com/u/1975321?v=3","gravatar_id":"","url":"https://api.github.com/users/spyhunter99","html_url":"https://github.com/spyhunter99","followers_url":"https://api.github.com/users/spyhunter99/followers","following_url":"https://api.github.com/users/spyhunter99/following{/other_user}","gists_url":"https://api.github.com/users/spyhunter99/gists{/gist_id}","starred_url":"https://api.github.com/users/spyhunter99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spyhunter99/subscriptions","organizations_url":"https://api.github.com/users/spyhunter99/orgs","repos_url":"https://api.github.com/users/spyhunter99/repos","events_url":"https://api.github.com/users/spyhunter99/events{/privacy}","received_events_url":"https://api.github.com/users/spyhunter99/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-24T11:23:32Z","updated_at":"2016-05-24T17:23:13Z","closed_at":null,"body":"Not sure what's going on here. I have a centos machine with 2 network cards on 2 different networks and my goal is to use this computer as a router between the 2 networks (network A 192.168.1.0/24 and network B 10.1.1.0/24). The machines are connected via a simple unmanaged switch (there's no router in the picture besides the cenos machine with 2 nics). I've already setup and have basic routing (ping, udp, tcp, etc) between the 2 networks. \r\n\r\nI think smcroute is the right solution to route multicast traffic produced from network A to network B. (is it?)\r\n\r\niptables is cleared and stopped on all 3 machines in the picture\r\n\r\nLong story short, my smcroute.conf look like this\r\n````\r\nphyint eth0 enable ttl-threshold 11\r\nphyint eth1 enable ttl-threshold 11\r\n\r\nmgroup from eth0 group 224.0.1.1\r\nmroute from eth0 group 224.0.1.1 to eth1\r\n\r\nmgroup from eth1 group 224.0.1.1\r\nmroute from eth1 group 224.0.1.1 to eth0\r\n````\r\n\r\nAfter saving and starting the daemon, I don't get any errors to stdout. At this point multicast traffic is still not being routed. So I issued the following command\r\n````\r\nsmcroute -j eth0 224.0.1.1\r\nSending commands....Daemon error: Failed adding VIF for iface eth1: Cannot assign the requested address\r\n````\r\nwhich is where i get the error message on the subject line.\r\n\r\nQuestion, is smcroute the right tool for what I'm trying to accomplish? if so, what am I doing wrong (in terms the error message) and what else do i need to do in order to get this setup working?"},"comment":{"url":"https://api.github.com/repos/troglobit/smcroute/issues/comments/221343260","html_url":"https://github.com/troglobit/smcroute/issues/36#issuecomment-221343260","issue_url":"https://api.github.com/repos/troglobit/smcroute/issues/36","id":221343260,"user":{"login":"troglobit","id":183517,"avatar_url":"https://avatars.githubusercontent.com/u/183517?v=3","gravatar_id":"","url":"https://api.github.com/users/troglobit","html_url":"https://github.com/troglobit","followers_url":"https://api.github.com/users/troglobit/followers","following_url":"https://api.github.com/users/troglobit/following{/other_user}","gists_url":"https://api.github.com/users/troglobit/gists{/gist_id}","starred_url":"https://api.github.com/users/troglobit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/troglobit/subscriptions","organizations_url":"https://api.github.com/users/troglobit/orgs","repos_url":"https://api.github.com/users/troglobit/repos","events_url":"https://api.github.com/users/troglobit/events{/privacy}","received_events_url":"https://api.github.com/users/troglobit/received_events","type":"User","site_admin":false},"created_at":"2016-05-24T17:23:13Z","updated_at":"2016-05-24T17:23:13Z","body":"But yes, from the few data points you've provided with your use-case, I do believe SMCRoute is what you are looking for.\r\n\r\nAlso, unlike unicast multicast does not have to be bi-directional. So if data is generated in network A and only destined for B, you only need one mroute rule.  You can see SMCRoute as a proxy, or repeater, of your multicast source in A, on B."}}
{"actor":{"display_login":"troglobit"}}