Administrace komentářů

Po prihlaseni na ssh BusyBoxu to na me vyhodi toto:

BusyBox v0.61.pre (2007.05.10-01:41+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

#
IGMPProxy       \[              arp             ash
atmarp          atmarpd         br2684ctl       brctl
busybox         cat             chgrp           chmod
chown           cm_cli          cm_klogd        cm_logic
cm_pc           cp              date            dd
ddnsd           df              dhcp-fwd        diap
dproxy          dropbear        echo            false
flashwrite      free            grep            hostname
id              ifconfig        init            insmod
ip              iptables        kill            ledapp
ledcfg          ln              login           ls
lsmod           mkdir           modprobe        mount
msntp           mv              passwd          ping
pppd            ps              pwd             reboot
rm              rmmod           route           routed
sh              sleep           snmpd           sync
tar             tc              test            tftp
thttpd          touch           true            tty
udhcpc          udhcpd          umount          upgrade
upnpd           utelnetd        wget            whoami
yes

Takze je patrne, ze to zakladni utility obsahuje. Nastaveni sitovych rozhrani v BusyBoxu:

# ifconfig
br0       Link encap:Ethernet  HWaddr 00:1C:F0:0E:05:D9
          inet addr:10.0.0.138  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1  ASYMMTU:1500
          RX packets:32234 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29985 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3082501 (2.9 Mb)  TX bytes:8260056 (7.8 Mb)

br1       Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1  ASYMMTU:1500
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet  HWaddr 00:1C:F0:0E:05:D9
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1  ASYMMTU:1500
          RX packets:418512 errors:0 dropped:0 overruns:0 frame:0
          TX packets:511739 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:58916090 (56.1 Mb)  TX bytes:552635395 (527.0 Mb)
          Base address:0x2800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1  ASYMMTU:0
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5040 (4.9 kb)  TX bytes:5040 (4.9 kb)

nas0      Link encap:Ethernet  HWaddr 00:AA:BB:CC:DD:10
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1  ASYMMTU:1500
          RX packets:481762 errors:0 dropped:0 overruns:0 frame:0
          TX packets:386867 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:544376082 (519.1 Mb)  TX bytes:59835794 (57.0 Mb)

Jeste to vysvetlim lepe: Zapojeni je takoveto:

HTS -> splitter -> Dlink 584T (BusyBox) br0 -> (eth0) Linux server (eth1, eth2, wlan0)

Na br0 v BusyBoxu je 10.0.0.138/32 v siti 10.0.0.0/24
Na eth0 v Linuxu je 10.0.0.1/32 v siti 10.0.0.0/24
Zadne dalsi zarizeni v 10.0.0.0/24 neni pripojeno.

V BusyBoxu na 10.0.0.138 jsou otevreny tyto porty:

# nmap 10.0.0.138

Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2008-10-16 11:47 CEST
Interesting ports on 10.0.0.138:
(The 1655 ports scanned but not shown below are in state: closed)
PORT   STATE SERVICE
21/tcp open  ftp
22/tcp open  ssh
23/tcp open  telnet
80/tcp open  http

Nmap run completed -- 1 IP address (1 host up) scanned in 1.751 seconds

Problem je v tom, ze se pouze ze site 10.0.0.0/24 da na tyto porty na 10.0.0.138 dostat, z ostatnich ne. Routovani mam z vnitrnich sitich (eth1, eth2, wlan0) nastavene spravne a NAT z internetu pres eth0 na linuxu take. Ostatne jsem na zacatku psal, ze kdyz se pokousim prihlasit z jine IP nez v 10.0.0.0/24, tak na d-linku problikne dioda indikujici aktivitu na LAN portu br0, takze to spojeni proste zahodi. Kdyz jsem tam umistil jine zarizeni, na kterem jsem nastavil IP 10.0.0.138 a masku 255.255.255.0, tak jsem se do nej ze vsech jinych subnetu (wlan0, eth1 a eth2) normalne dostal, takze tady broblem nebude, ten je urcite v tom BusyBoxu.