Posiadaj\u0105c serwer ( nie router dla klient\u00f3w ), kt\u00f3ry posiada mo\u017cliwo\u015b\u0107 korzystania z wi\u0119cej jak jednego IP od r\u00f3\u017cnych dostawc\u00f3w natykamy si\u0119 na problem, i\u017c przy standardowej konfiguracji \u015bwiat widzi serwer tylko po IP z ustawionym gateway w \/etc\/networking\/ .<\/p>\n
\n
Podobnie jak w przypadku routera z wieloma dostawcami z pomoc\u0105 przychodzi iproute. Jednak\u017ce w tym przypadku znakowanie pakiet\u00f3w nie jest wykorzystywane .. bo nie zadzia\u0142a. Czemu to pewnie wiecie.<\/p>\n
\n
Poni\u017cej dzia\u0142aj\u0105ca rzeczywista konfiguracja jednej z moich maszyn, ten serwer to DNS posiadaj\u0105cy \u0142\u0105cza do debacom.pl oraz polsl.pl .<\/p>\n
\n
\ncat \/etc\/iproute2\/rt_tables<\/p>\n
\n
#<\/p>\n
# reserved values<\/p>\n
#<\/p>\n
255 local<\/p>\n
254 main<\/p>\n
253 default<\/p>\n
0 unspec<\/p>\n
#<\/p>\n
# local<\/p>\n
#<\/p>\n
#1 inr.ruhep<\/p>\n
200 t1<\/p>\n
201 t2<\/p>\n<\/blockquote>\n
\n
\n
\ncat routing<\/p>\n
\n
#!\/bin\/bash<\/p>\n
\n
\n
ip route add 213.227.125.0 dev eth0 src 213.227.125.129 table t1<\/p>\n
ip route add 178.212.43.0 dev eth1 src 178.212.43.101 table t2<\/p>\n
\n
ip route add default via 213.227.125.254 table t1<\/p>\n
ip route add default via 178.212.43.97 table t2<\/p>\n
\n
ip route add 213.227.125.0 dev eth0 src 213.227.125.254<\/p>\n
ip route add 178.212.43.0 dev eth1 src 178.212.43.97<\/p>\n
\n
ip route add default via 213.227.125.254<\/p>\n
\n
ip rule add from 213.227.125.129 table t1<\/p>\n
ip rule add from 178.212.43.101 table t2<\/p>\n
\n
ip route add 127.0.0.0\/8 dev lo table t1<\/p>\n
ip route add 127.0.0.0\/8 dev lo table t2<\/p>\n
\n
ip route add 213.227.125.0 dev eth0 table t2<\/p>\n
ip route add 178.212.43.0 dev eth1 table t1<\/p>\n<\/blockquote>\n
\n
\n
powodzonka!<\/p>\n","protected":false},"excerpt":{"rendered":"
Posiadaj\u0105c serwer ( nie router dla klient\u00f3w ), kt\u00f3ry posiada mo\u017cliwo\u015b\u0107 korzystania z wi\u0119cej jak jednego IP od r\u00f3\u017cnych dostawc\u00f3w natykamy si\u0119 na problem, i\u017c przy standardowej konfiguracji \u015bwiat widzi serwer tylko po IP z ustawionym gateway w \/etc\/networking\/ . Podobnie jak w przypadku routera z wieloma dostawcami z pomoc\u0105 przychodzi iproute. Jednak\u017ce w tym […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-444","post","type-post","status-publish","format-standard","hentry","category-sciaga-admina"],"_links":{"self":[{"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/posts\/444","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/comments?post=444"}],"version-history":[{"count":2,"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/posts\/444\/revisions"}],"predecessor-version":[{"id":446,"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/posts\/444\/revisions\/446"}],"wp:attachment":[{"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/media?parent=444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/categories?post=444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.antynet.pl\/index.php\/wp-json\/wp\/v2\/tags?post=444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}