ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: Alexandr Rakhmanin <community@rscenter.ru>
To: community@altlinux.ru
Subject: [Comm] Samba и броузинг между подсетями...
Date: Fri, 04 Mar 2005 17:04:37 +0600
Message-ID: <422840C5.1030208@rscenter.ru> (raw)

Привет.

Было:
Роутер АЛМ 2.2 на 2е подсетки 192.168.0.0 и 192.168.2.0, стояла 
samba-2.2.11-alt2.
Настройки:
[global]
   null passwords = yes
   workgroup = RSCDOMAIN
   netbios name = SkyGW
   server string =  Samba server on %h (v. %v)
   log file = /var/log/samba/log.%m
   max log size = 50
   guest account = nobody
   security = share
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   local master = yes
   os level = 79
   domain master = yes
   preferred master = yes
   domain logons = no
   name resolve order = wins lmhosts bcast
   wins support = yes
   wins proxy = yes
   dns proxy = no
   client code page = 866
   character set = KOI8-R
[public]
   path = /home/public
   public = yes
   only guest = yes
   writable = yes
   printable = no

Через Vtund соединение до филиала, он же роутер там АЛМ 2.4, samba-3.0.10.
eth1      Link encap:Ethernet  HWaddr 00:A9:40:0F:D5:D0
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
tun0      Link encap:Point-to-Point Protocol
          inet addr:192.168.240.3  P-t-P:192.168.240.1  Mask:255.255.255.255
Настройки:
[global]
   null passwords = yes
   workgroup = RSCDOMAIN
   netbios name = GW4
   server string =  Samba server on %h (v. %v)
   printcap name = cups
   load printers = no
   printing = cups
   log file = /var/log/samba/log.%m
   max log size = 50
   guest account = nobody
   security = share
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   socket options = TCP_NODELAY
   interfaces = 192.168.3.1/24
   local master = yes
   os level = 79
   preferred master = yes
   name resolve order = wins lmhosts bcast
   wins server = 192.168.0.101
   wins proxy = yes
   dns proxy = no
   dos charset = CP866
   unix charset = KOI8-R
   display charset = KOI8-R
   use sendfile = no
[Public]
    path = /home/public
    public = yes
    writable = yes
    guest ok = yes
    printable = no
    create mask = 0666
    directory mask = 0777
    block size = 65536
    write cache size = 262144
Всё работало замечательно, все компы во всех сегментах виделись и был 
доступ.

Обновил на роутере систему АЛМ 2.4 из-за wifi и вылезла следующая проблема.
Его конфиг:
[global]
   null passwords = yes
   workgroup = RSCDOMAIN
   netbios name = SkyGW
   server string =  Samba server on %h (v. %v)
   printcap name = cups
   load printers = no
   printing = cups
   log file = /var/log/samba/log.%m
   max log size = 50
   guest account = nobody
   security = share
   encrypt passwords = yes
   smb passwd file = /etc/samba/smbpasswd
   socket options = TCP_NODELAY
   interfaces = 192.168.0.101/24 192.168.2.1/24
   bind interfaces only = yes
   local master = yes
   os level = 79
   domain master = yes
   preferred master = yes
   name resolve order = wins lmhosts bcast
   wins support = yes
   wins proxy = yes
   dns proxy = no
   dos charset = CP866
   unix charset = KOI8-R
   display charset = KOI8-R
   use sendfile = no
[Public]
    path = /home/public
    public = yes
    writable = yes
    guest ok = yes
    printable = no
    create mask = 0666
    directory mask = 0777
    block size = 65536
    write cache size = 262144
Виндовые компа из сети 192.168.0.0 в сети 192.168.2.0 видны, но зайти на 
них невозможно (аналогично и с 192.168.3.0), пинги по имени не проходят, 
винс почемуто не отдает имена, хотя те компы где работает Самбы видны 
везде и всё нормально. На всех юзерских компах WINS IP прописан со 
стороны своего сегменты.
Конфиги на обоих сторонах менялись уже в разных конфигурациях, включал
remote browse sync и  remote announce на обоих сторонах, делал и там и 
там domain master = yes
Думал что дело в 3.0.10 самбе на роутере, поменял на 2.2.11, не помогло, 
даже завёл на нем старую карту wifi аналогично. :-(
Файрволла нигде нет, весь трафик разрешон, с маршрутизацией проблем нет.

Из-за чего такое может быть ? Может в настройках ядра для АЛМ 2.4 что 
кардинально изменилось?

-- 
Всего наилучшего.
СисАдмин ЗАО "Региональный сервисный центр".



                 reply	other threads:[~2005-03-04 11:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=422840C5.1030208@rscenter.ru \
    --to=community@rscenter.ru \
    --cc=community@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git