Hello!
 
Reading your explanation this makes sense to a certain degree.
However, I have no issue when modifying the conguration:

root@pc4-svp:/etc/shorewall# cat providers 
#NAME           NUMBER  MARK    DUPLICATE       INTERFACE       GATEWAY         OPTIONS         COPY
um_business     1       0x10000 -               UMB_IF          detect          track,balance
um_private      2       0x20000 -               UMP_IF          192.168.1.1     loose

root@pc4-svp:/etc/shorewall# ip rule ls
0:      from all lookup local 
999:    from all lookup main 
1000:   from 217.8.50.86 lookup um_business 
1000:   from 192.168.1.14 lookup um_private 
10000:  from all fwmark 0x10000/0x30000 lookup um_business 
10001:  from all fwmark 0x20000/0x30000 lookup um_private 
11000:  from 10.1.0.1 lookup um_business 
20000:  from 217.8.50.86 lookup um_business 
32765:  from all lookup balance 
32767:  from all lookup default 

 
Based on this there's a relation to the configuration of options "track" and "loose" in /etc/shorewall/providers.
 
Gesendet: Mittwoch, 13. April 2016 um 09:01 Uhr
Von: "Simon Hobson" <[email protected]>
An: "Shorewall Users" <[email protected]>
Betreff: Re: [Shorewall-users] Multiple ISP: Issues running apt update - routing rules issue?
Tom Eastep <[email protected]> wrote:

>> I get this error when starting apt update:
>> W: Fehlschlag beim Holen von
>> http://repo.saltstack.com/apt/debian/8/amd64/latest/dists/jessie/Release.gpg
>> Verbindung mit repo.saltstack.com:80 kann nicht aufgebaut werden
>> (2604:a880:400:d0::2:e001). - connect (101: Das Netzwerk ist nicht
>> erreichbar) [IP: 2604:a880:400:d0::2:e001 80]
>
> It is trying to connect via IPv6 -- try disabling IPv6 on eth0 on the
> system that is seeing this error.

Sometimes feels like there's an echo in here !

When I looked this up a week or so ago, it's a "known issue" with APT that the message is misleading. It tries all addresses returned in order - so if the IPv4 addresses fail then it'll also try IPv6 even if the machine isn't configured with IPv6 (IMO this is wrong). When it runs out of addresses it spits out the above report which really means "I couldn't connect to any address".

So taking a step back, it suggests that apt couldn't connect to the IPv4 addresses.


------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to