On Nov 17, 2011, at 10:31 AM, Andrzej Odyniec wrote: > Dears > > I have a problem with 4.4.22.3 on kernel 3.0.4 and with two providers. > Problem > was revealed when the next to the LAN segment (eth0) I connected the new WLAN > segment (eth4). When I add eth4 after eth0 to COPY column of both providers, > Shorewall crashes, and when there is no eth4 interface in COPY column, the > new > segment has no flow via any of the providers. > > Crash is because of try add duplicate route to providers routing tables. In > main table there are originally the following routes for connected segments: > >> 255.255.255.255 dev eth0 scope link >> 255.255.255.255 dev eth1 scope link >> 255.255.255.255 dev eth4 scope link > > When Shorewall is trying to copy routes for eth0 as for eth4 to provider > table, obtains from netlink error: > >> RTNETLINK answers: File exists > > and crashes. > > Ofcourse, workaround is simple: copying routes manually in started script. > But > it is not elegant. > > Anyone know other solution?
Right after I hit 'send', I realized that the first patch was incorrect. Here's a corrected copy. -Tom
PROVIDER2.patch
Description: Binary data
Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
