Bir Ubuntu sunucusunda birden fazla a\u011f arayüzü (örne\u011fin biri internete, di\u011feri iç a\u011fa ba\u011fl\u0131) bulundu\u011funda, do\u011fru yap\u0131land\u0131rma yap\u0131lmad\u0131\u011f\u0131nda ba\u011flant\u0131 sorunlar\u0131, gecikmeler veya çak\u0131\u015fmalar ya\u015fanabilir.
Bu yaz\u0131da \u015fu konular\u0131 ele alaca\u011f\u0131z:<\/p>\r\n
Ubuntu’da mevcut a\u011f arayüzlerini görmek için en modern yöntem:<\/p>\r\n
ya da k\u0131sa haliyle:<\/p>\r\n Örnek ç\u0131kt\u0131:<\/p>\r\n Burada:<\/p>\r\n * `lo` → localhost (loopback) Belirli bir interface’in detaylar\u0131n\u0131 görmek için:<\/p>\r\n Bir a\u011f arayüzüne geçici olarak IP atamak için (yeniden ba\u015flat\u0131nca kaybolur):<\/p>\r\n Kontrol etmek için:<\/p>\r\n Netplan ile Kal\u0131c\u0131 Statik IP Yap\u0131land\u0131rmas\u0131<\/p>\r\n<\/blockquote>\r\n Ubuntu 18.04 ve sonras\u0131nda a\u011f ayarlar\u0131 **Netplan** ile yap\u0131l\u0131r. Örne\u011fin mevcut sistemde `ens160` için a\u015fa\u011f\u0131daki yap\u0131 varsa:<\/p>\r\n Bunu bozmada, ikinci arayüz (**ens192**) için yeni bir IP tan\u0131mlayabiliriz:<\/p>\r\n Dosyay\u0131 kaydettikten sonra de\u011fi\u015fiklikleri uygulay\u0131n:<\/p>\r\n E\u011fer iki arayüzün de **gateway** sat\u0131r\u0131 varsa, Ubuntu hangi yolu kullanaca\u011f\u0131n\u0131 kar\u0131\u015ft\u0131rabilir. Örne\u011fin:<\/p>\r\n Do\u011fru yap\u0131land\u0131rma \u015föyle olmal\u0131d\u0131r:<\/p>\r\n * `ens160` sistemin ana a\u011f geçidi (internet bu yoldan ç\u0131kar).<\/span> <\/p>\r\n Kontrol ve Do\u011frulama<\/p>\r\n Ayarlar\u0131 uygulad\u0131ktan sonra do\u011frulamak için:<\/p>\r\n Örnek ç\u0131kt\u0131:<\/p>\r\n Ping testi:<\/p>\r\n Do\u011fru route ayarlar\u0131 sayesinde sistemin hem <\/p>","excerpt":"Bir Ubuntu sunucusunda birden fazla a\u011f aray\u00fcz\u00fc (\u00f6rne\u011fin biri internete, di\u011feri i\u00e7 a\u011fa ba\u011fl\u0131) bulundu\u011funda, do\u011fru yap\u0131land\u0131rma yap\u0131lmad\u0131\u011f\u0131nda ba\u011flant\u0131 sorunlar\u0131, gecikmeler veya \u00e7ak\u0131\u015fmalar ya\u015fanabilir.","created_at":"2025-10-30 14:41:01","updated_at":"2026-09-06 14:49:08","category_id":6,"view_count":620,"reading_time":3,"status":"published","editor_choice":1,"is_editor_choice":0,"published_at":"2025-10-30 14:41:00","featured_image":"api_pixabay_1762013995_6906332b4597e.jpg","slug":"ubuntu-statik-ip-ile-route","category_name":"Sistem","category_slug":"sistem"}ip link show<\/code>
<\/p>\r\nip a<\/code>
<\/p>\r\n1: lo: mtu 65536 ...<\/code>2: ens160: mtu 1500 ...<\/code>3: ens192: mtu 1500 ...<\/code>
<\/p>\r\n
* `ens160` → aktif Ethernet arayüzü
* `ens192` → ikinci Ethernet arayüzü (örne\u011fin iç a\u011f ba\u011flant\u0131s\u0131)<\/p>\r\nip addr show dev ens160<\/code><\/p>\r\nGeçici IP Atama (Test Amaçl\u0131)<\/h2>\r\n
sudo ip link set ens192 up<\/code>sudo ip addr add 10.100.0.111\/23 dev ens192<\/code>
<\/p>\r\nip a show dev ens192<\/code><\/p>\r\n\r\n
Netplan dosyas\u0131 genellikle `\/etc\/netplan\/00-installer-config.yaml` konumundad\u0131r.<\/p>\r\nyaml<\/code>network:<\/code> ethernets:<\/code> ens160:<\/code> addresses:<\/code> - 10.50.10.111\/24<\/code> gateway4: 10.50.10.1<\/code> nameservers:<\/code> addresses:<\/code> - 10.50.10.1<\/code> search: []<\/code> version: 2<\/code><\/p>\r\nyaml<\/code>network:<\/code> version: 2<\/code> ethernets:<\/code> ens160:<\/code> addresses:<\/code> - 10.50.10.111\/24<\/code> gateway4: 10.50.10.1<\/code> nameservers:<\/code> addresses:<\/code> - 10.50.10.1<\/code> search: []<\/code> ens192:<\/code> addresses:<\/code> - 10.100.0.111\/23<\/code>
<\/p>\r\nsudo netplan apply<\/code><\/p>\r\nRoute (Yönlendirme) Ayarlar\u0131n\u0131 Optimize Etme<\/h2>\r\n
Bu durumda biri ana ç\u0131k\u0131\u015f (örne\u011fin internete giden), di\u011feri sadece belirli bir a\u011fa ba\u011fl\u0131 olmal\u0131d\u0131r.<\/p>\r\n`ens160` → \u0130nternet ç\u0131k\u0131\u015f\u0131 (10.5.10.0\/24)<\/code>`ens192` → \u0130ç a\u011f (10.100.0.0\/23)<\/code><\/p>\r\nyaml<\/code>network:<\/code> version: 2<\/code> ethernets:<\/code> ens160:<\/code> addresses:<\/code> - 10.50.10.111\/24<\/code> gateway4: 10.50.10.1<\/code> nameservers:<\/code> addresses:<\/code> - 10.50.10.1<\/code> search: []<\/code> ens192:<\/code> addresses:<\/code> - 10.100.0.111\/23<\/code> routes:<\/code> - to: 10.100.0.0\/23<\/code> via: 10.100.0.1<\/code>
<\/p>\r\nAç\u0131klama<\/h2>\r\n
* `ens192` sadece 10.100.0.0\/23 alt a\u011f\u0131ndaki cihazlarla ileti\u015fim kurar.<\/span><\/p>\r\nip route<\/code><\/p>\r\ndefault via 10.50.10.1 dev ens160<\/code>10.100.0.0\/23 via 10.100.0.1 dev ens192<\/code>10.5.10.0\/24 dev ens160 proto kernel scope link src 10.50.10.111<\/code>
<\/p>\r\nping -c 4 10.100.0.1<\/code><\/p>\r\n\r\n
internet ba\u011flant\u0131s\u0131n\u0131<\/code> hem de lokal a\u011f ileti\u015fimini<\/code> sorunsuz bir \u015fekilde sürdürebilir.<\/p>\r\n