[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debian-users:13692] Re: bpf の代わり

むつみです。

 ISHIKAWA Mutsumi <ishikawa@xxxxxxxxx> さんは
   Subject: [debian-users:13691] Re: bpf の代わり
   Message-ID: <19990316124122F.ishikawa@xxxxxxxxx>
 において言いました

>> むつみです。

>> >> いのうえです。

>> >> 　すいません。条件を書き忘れていました。
>> >> 　パケット送受信の対象とするネットワークが閉じたネットワークで IP では
>> >> 無い独自のプロトコルを用いているのです。で、socket が使用できなくて困っ
>> >> てしまいました。同じ理由から、上記のデバイスは使用できないのではないで
>> >> しょうか？
>> 
>>  なんで? low パケットを拾えるんだから、その目的のプロトコルに対応した
>> ipchains tool 相当のプログラムを書くだけだと思うんですが。
>> 
>> ＃それとも NETLINKってそういうドライバではないの? ＞ all

 えーと、引用する場所を間違えてました ^^;; こっち。

----- ここから
Kernel/User network link driver
CONFIG_NETLINK
  This driver allows for two-way communication between certain parts
  of the kernel or modules and user processes; the user processes are
  able to read from and write to character special files in the /dev
  directory having major mode 36. So far, the kernel uses it to
  publish some network related information if you say Y to "Routing
  messages", below. It is also used by the firewall code to publish
  information about possible attacks if you say Y to "IP: firewall
  packet netlink device" further down. You also need to say Y here if
  you want to use arpd, a daemon that helps keep the internal ARP
  cache (a mapping between IP addresses and hardware addresses on the
  local network) small. The ethertap device, which lets user space
  programs read and write raw Ethernet frames, also needs the network
  link driver. If unsure, say Y.
----- ここまで

ついでに、これ

----- ここから
Ethertap network tap
CONFIG_ETHERTAP
  If you say Y here (and have said Y to "Kernel/User network link
  driver", above) and create a character special file /dev/tap0 with
  major number 36 and minor number 16 using mknod ("man mknod"), you
  will be able to have a user space program read and write raw
  Ethernet frames from/to that special file. tap0 can be configured
  with ifconfig and route like any other Ethernet device but it is not
  connected to any physical LAN; everything written by the user to
  /dev/tap0 is treated by the kernel as if it had come in from a LAN
  to the device tap0; everything the kernel wants to send out over the
  device tap0 can instead be read by the user from /dev/tap0: the user
  mode program replaces the LAN that would be attached to an ordinary
  Ethernet device. Please read the file
  Documentation/networking/ethertap.txt for more information. 

  This driver is also available as a module ( = code which can be
  inserted in and removed from the running kernel whenever you want).
  The module will be called ethertap.o. If you want to compile it as a
  module, say M here and read Documentation/modules.txt. If you don't
  know what to use this for, you don't need it.
----- ここまで

＃以上 kernel の Documentation/Configure.help から
-- 
 From Nagoya
  ishikawa@xxxxxxxxxxx, ishikawa@debian.or.jp,
   ishikawa@xxxxxxxxxxxxx,  ( mutsumi@xxxxxxxxxxx for PostPet only )
 ＊＊ 石川 睦％無意味な全文引用をする人は嫌い＠Japan Linux Users Group ＊＊
     My Debian JP NEWS  http://www.linux.or.jp/~ishikawa/linux/debian-jp/