Linux-haladó

TCP port forward iptables-szel, azonos subnetre, azonos kártyán?

Fórumok

Sziasztok!

Adott egy helyi hálózat 172.16.16.x-es tartomány.
A szerver belső (eth0) IP-je 172.16.16.100 .
A problémám a következő: ez egy pentium3, 256 MB rammal, rengeteg használt szolgáltatással.
HTTP proxy-ként squid fut rajta, a 3128-as porton. Kicsit lassú a net, több gép van rá, mint amennyi indokolt lenne. Lenne egy másik gép, amit csak proxy-zásra be tudnék állítani a szerver helyett, ennek az IP-je 172.16.16.210. Azt szeretném megoldani, hogy a klienseken ne kelljen változtatni a beállításokon, és a szerver a 172.16.16.100:3128-ról IPTABLES-szel irányítsa át a kéréseket a 172.16.16.210:3128-ra. (TCP port ugye.) Túrtam a google-t, próbálkoztam, de nem jött össze. Hozzáteszem, annyira nagy IPTABLES mágus nem vagyok. Eddit nat táblával és DNAT destination-ökkel dolgoztam, de ez csak úgy működött, ha az egyik hálókártyáról a másikra küldtem a csomagokat.

(Nem parent proxy-ként szeretném berakni az új gépet.)

Megoldható ez IPTABLES-szel, vagy csak userspace alkalmazással?

Válaszotokat előre is köszi!

Üdv,
Szenti

Debian nem megy fel Fujitsu Siemens Primergy szerverre :(

Fórumok

A gondom az lenne, hogy van a cégnél egy Fujitsu Siemens Primergy TX150 S3 SATA-s szerver.
Debiant kellene rá feltennem. Netinstall CD-ről próbáltam, de nem megy fel rá.
Ugye végig megy a telepítő az első szakaszon, és ezután elméletileg újraindul a gép, hogy leszedje, és telepítse a csomagokat. Na újraindítás után azt írja ki, hogy nem talál operációs rendszert...

Tud erre valaki vmi megoldást? Jártmár így valaki közületek? Mi lehet a megoldás?

ndiswrapper problema - busrt jelleggel kuldi az adatot a kartya

Fórumok

sziasztok

Egy KTI Networks-os PCMCIA kartyat hasznalok netezeshez a laptopomon. Ndiswrapperhez meg is talaltam a kartya window-os inf file-jat. Mukodik is. A baj az, hogy szakaszosan kuldi az adatot a kartya. Ez foleg akkor gond, amikor beSSHzom valahova, es hiaba irok barmit nem laccik semmi a kepernyon, majd egyszercsak HUSS :) es bedaralja. Itt egy pelda pingelesre, ahol szinten lathato a problemam:

64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=1 ttl=57 time=36.3 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=2 ttl=57 time=4960 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=3 ttl=57 time=3961 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=4 ttl=57 time=2962 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=5 ttl=57 time=1964 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=6 ttl=57 time=965 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=7 ttl=57 time=15.9 ms
64 bytes from ldir-loopback.index.hu (217.20.131.2): icmp_seq=8 ttl=57 time=27.1 ms

Van otlet?

MSN sniffer

Fórumok

Sziasztok!

Nem tudtok valami jó, konzolos megoldást arra, hogy hogyan lehetne az MSN messenger beszélgetéseket lehallgatni egy routeren.

Találtam egy IMSniff nevű cuccot, megy daemon módban is, szépen logol, de nekem űgy tűnik, hogy az új messenger Live beszélgetésekkel meggyűlik a baja.

thx,
Dolphy

Suid redirect probléma...

Fórumok

Egy perl scripten szeretném elenőrizni az áfuttó web lapokat :P
Ehhez 1 egyszerü megoldást alkalmaztam squid.conf ba ...:

redirect_program /home/squid/script/script.pl
redirect_children 10

A script jelenleg:



#!/usr/bin/perl
while($_=<STDIN>) {
    chomp ($_);
    print"$_\n";
}

De a proxy azonnal meghal ha beadolom... a redirect sort...
Úgyanakkor a :
redirect_program /usr/bin/cat
redirect_children 10

működik ... na de nekem uye nem ez kell...

Már próbáltam ezt is :

redirect_program /usr/bin/perl /home/squid/script/script.pl
redirect_children 10

De a perl scriptel nem megy...
Mi lehett a baj ?

PCLINUXOS 0.94/2007 - Dokumentációs és fordítási projekt -

Fórumok

Sziasztok!

Hozzátok fordulok forumozók, s a segítségeteket kérem abban hogy a fenti nagyszerű operációs rendszernek magyar dokumentációja, és TELJES magyar fordítása szülessen. A jelenlegi állás szerint per pillanatban egyedül vagyok, remélem akad akit érdekel majd a dolog. A magyar fórumot elindítottam, bárki jöhet aki picit beszél angolul
Ha már elkezdtél valamit, de nem tudod, hogy hova fordulj vele keress meg itt:
hopparz@gmail.hu

vagy itt -

www.mypclinuxos.com, regisztrálj, és írj ide: Active Projects - Localizations - Hungarian

Zoltan

Nokia 3220 + CA-42 kábel vs. Fedora Core 6

Fórumok

Sikerült már valakinek a Nokia 3220 -as telefont kezelni linux alatt? (Fájlok fel - le töltése stb) CA-42 kábelem van hozzá, kernelbe bele van forgatva a CA-42 támogatás. Gnokii 0.6.14 van a gépemen. Mit kéne csinálnom, hogy működjön? (Xgnokii - vel próbáltam) Fedora Core 6-ot használok.

A dmesg fontos része:

Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver libusual
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for ark3116
usbcore: registered new interface driver ark3116
drivers/usb/serial/usb-serial.c: USB Serial support registered for cp2101
usbcore: registered new interface driver cp2101
drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.07
drivers/usb/serial/usb-serial.c: USB Serial support registered for DeLorme Earthmate USB
drivers/usb/serial/usb-serial.c: USB Serial support registered for HID->COM RS232 Adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for Nokia CA-42 V2 Adapter
usbcore: registered new interface driver cypress
drivers/usb/serial/cypress_m8.c: Cypress USB to Serial Driver v1.09
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
usbcore: registered new interface driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
drivers/usb/serial/usb-serial.c: USB Serial support registered for TI USB 3410 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for TI USB 5052 2 port adapter
usbcore: registered new interface driver ti_usb_3410_5052
drivers/usb/serial/ti_usb_3410_5052.c: TI USB 3410/5052 Serial Driver v0.9
usbcore: registered new interface driver uss720
drivers/usb/misc/uss720.c: v0.6:USB Parport Cable driver for Cables using the Lucent Technologies USS720 Chip
drivers/usb/misc/uss720.c: NOTE: this is a special purpose driver to allow nonstandard
drivers/usb/misc/uss720.c: protocols (eg. bitbang) over USS720 usb to parallel cables
drivers/usb/misc/uss720.c: If you just want to connect to a printer, use usblp instead

A dmesg vége:

usb 4-2: new full speed USB device using uhci_hcd and address 2
usb 4-2: configuration #1 chosen from 1 choice
ark3116 4-2:1.0: ark3116 converter detected
usb 4-2: ark3116 converter now attached to ttyUSB0
drivers/usb/serial/ark3116.c: can't set 0 baud, using 9600 instead
drivers/usb/serial/ark3116.c: can't set 0 baud, using 9600 instead
usb 4-2: USB disconnect, address 2
ark3116 ttyUSB0: ark3116 converter now disconnected from ttyUSB0
ark3116 4-2:1.0: device disconnected
usb 4-1: new full speed USB device using uhci_hcd and address 3
usb 4-1: configuration #1 chosen from 1 choice
ark3116 4-1:1.0: ark3116 converter detected
usb 4-1: ark3116 converter now attached to ttyUSB0
drivers/usb/serial/ark3116.c: can't set 0 baud, using 9600 instead

Az xgnokii kimenete:

[root@localhost ~]# xgnokii
Orphaned line: port = /dev/ttyUSB0
Orphaned line: model = 6510
LOG: debug mask is 0x1

(xgnokii:3108): Gtk-WARNING **: horizontal scrolling not implemented

(xgnokii:3108): Gtk-WARNING **: horizontal scrolling not implemented
phone instance config:
model: 6510
port_device: /dev/ttyUSB0
connection_type: 2
init_length: 0
serial_baudrate: 19200
serial_write_usleep: -1
hardware_handshake: 0
require_dcd: 0
smsc_timeout: 100
connect_script:
disconnect_script:
rfcomm_cn: 1
sm_retry: off
Connecting
Serial device: opening device /dev/ttyUSB0
Serial device: setting RTS to low and DTR to low
Serial device: setting RTS to high and DTR to high
Serial device: setting speed to 19200
Switching to FBUS mode
Serial device: setting speed to 115200
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Serial write: transmitter busy, waiting
Serial write: transmitter ready
Getting model...
Message sent: 0x1b / 0x0006
00 01 00 07 01 00 |
Serial write: transmitter busy, waiting
Serial write: transmitter ready
SM_Block: exiting the retry loop
Message sent: 0x1b / 0x0006
00 01 00 07 01 00 |
SM_Block: exiting the retry loop

A gnokiirc:

# This is a sample ~/.gnokiirc file. Copy it into your
# home directory and name it .gnokiirc.
# See http://wiki.gnokii.org/index.php/Config for working examples.
#

[global]

# Set port to the physical port used to connect to your phone.
# Linux version is:
port = /dev/ttyUSB0
#
# For MacOSX you will need something like:
# port = /dev/cu.USA28X1P1.1
#
# For Win32 you want to use:
# port = com1:
# or similiar.
#
# FreeBSD (probably NetBSD and OpenBSD too) use:
# port = /dev/cuaa0
#
# With Linux-IrDA you will want to use
# port = /dev/ircomm0
# or similiar.
#
# Use this setting also for the Bluetooth connection:
# port = aa:bb:cc:dd:ee:ff
# when using it with AT driver set it to:
# port = /dev/rfcomm0
# or similiar.
#
# For the Linux USB cables you will need one of the following settings (or
# similiar)
# port = /dev/ttyUSB0
# port = /dev/tts/USB0
# port = /dev/ttyACM0
# the last one will work only with AT driver. The correct setting should be
# given in the dmesg output.

# Set model to the model number of your phone. For the
# Symbian phones use:
# model = series60
# For other non-Nokia phones and when you want to use AT
# mode use:
# model = AT
# If you can't figure out what to put here read the FAQ.
# If it still doesn't help, consult gnokii-ml or #gnokii at freenode.
model = 6510
# There are few main models that should make use of the certain drivers.
# These are: 6110, 7110, 6510, 3110, 2110, 6160.

# Set IrDA device name.
# If you use irda connection you may want gnokii to autodetect the irda
# device it connects to. This is fine for most of the cases. if you have
# more than one device in range you may want to give manually the device
# name so gnokii correctly recognizes it. Use the name that you can see
# in the discovery log when the phone with infrared is in the range of
# your irda port.
# Note that you need to set this for each phone_ section separately. It
# isn't nested from the global section.
# irda_string = Nokia 6610i

# Initlength controls the number of characters sent to the
# phone during initialisation. You can either set it to
# the word "default" or a positive integer.
#
# You can try setting this value if you want to connect
# to the phone quicker. If you've never noticed the
# connection to be slow, it is suggested that you
# leave this alone. Read the initialisation code in fbus-xxxx
# to understand what this changes if you're curious.
initlength = default

# The type of the connection, for IR set this to infrared or irda.
# For the nk6110 driver only infrared is valid for the IrDA connection.
# See Docs/gnokii-ir-howto for more detailes on this.
# If you have 6210/6250/7110 phone and dau9p cable (the one you can
# use with 6100 series and cannot use hardware modem from the phone)
# you may want to use 'dau9p' value to get faster initialization.
# If you use dlr3 or dlr3p cable for nokia phones in FBUS mode (ie.
# you don't use model = AT) you may want to use 'dlr3p' value here.
# Note that it is recommended and currently the best way to use this
# cable with nk6510 driver.
connection = dlr3p
# With DKU-2 cable use the following setting if you want to libusb driver
# (recommended):
# connection = dku2libusb
# or the following setting if you want to use Linux kernel driver
# connection = dku2
# With DKU-5 cable use the following setting
# connection = dku5
# For Bluetooth and AT driver use the following setting
# connection = serial
# For other Bluetooth settings use
# connection = bluetooth
# For infrared connection with phones other than Nokia 6110/6130/6150 use
# connection = irda

# Set this to 'yes' if you want gnokii to set and check the lock file in
# /var/lock directory. It avoids potential conflicts with other serial
# port software (eg. minicom). If you have wrong permissions for the
# directory, a warning will be generated. If you don't want a lockfile, set
# it to 'no'.
use_locking = no

# Baudrate to use on serial port connections.
# Currently used only by models AT and BIP/CIMD. Defaults to 19200.
serial_baudrate = 19200

# Force waiting after each send character the specified usec time.
# Value -1 forces the fastest 'block' writing,
# value 0 writes each character separately without any explicite waiting,
# other positive values specify the appropriate 1/1000000 sec delaying.
# Siemens M20 requires at least "1"! FIXME: Model-driven autodetection
#serial_write_usleep = 10000

# Force serial port handshaking mode, useful primarily for "AT" model.
# Gnokii "AT" model uses software handshake by default.
# Possible values: hardware (RTS/CTS - 7 wires) or software (XON/XOFF - 3 wires)
#handshake = software

# If defined (not commented out by '#') it will quit Gnokii anytime
# when DCD line will drop.
#require_dcd = 1

# If you are using a bluetooth connection, you can specify the rfcomm
# channel number here. Default value is 1.
#rfcomm_channel = 1

# There may happen various timeouts during the communication with the phone.
# This parameter enables the retransmission policy. Ie. if the phone doesn't
# respond, we send the frame again. This happend mainly with the older
# phones. You may want to enable it when you see mysterious timeouts.
# Be very carefull with this option. It is suspected to cause phone breakage
# with new DCT4 phones (like Nokia 6100). By default it is switched off
# (sm_retry = 0)
#sm_retry = 1

# Run the specified script(s) right after opening and initializing the device
# and before any communication (right before closing for disconnect_script).
# You may find handy to use it to connect your modem to SMS Center
# when using BIP or CIMD protocols
# Non-absolute path is relative to the specific directory where gnokii is run!
#connect_script = /absolute/path/to/gnokii/Docs/sample/cimd-connect
#disconnect_script =

# When sending SMS you can experience timeouts. This is the feature of the
# overloaded SMSCs. The phones waits for the response from the SMSC confirming
# that it received the short message. When the SMSC is DoSed with many requests
# it will take more time to get the response. Adjust it to your needs. The
# value is given in seconds to wait. Defaults to 10 seconds. Set to 0 to wait
# forever.
smsc_timeout = 10

# Set bindir to point to the location of the various gnokiid binaries.
# In particular ensure that mgnokiidev is in this location, with
# permissions 4750, owned by root, group gnokii. Ensure you
# are in the gnokii group and that the group exists...
[gnokiid]
bindir = /usr/sbin/

# Any entries in the following two sections will be set as environment
# variables when running the scripts.
# Handy for use for $VAR substitutions in your chat(8) script.
[connect_script]
TELEPHONE = 12345678
[disconnect_script]

# The following parameters control how libgnokii handle the debugging messages.
# Currently there are three categories: "debug" controls the libgnokii
# normal debug output, "rlpdebug" controls the debug output of the RLP
# subsystem, and "xdebug" is used by the xgnokii or smsd.

[logging]

# where to log the debug output (on: stderr, off: /dev/null)
debug = on

# where to log the rlp debug output (on: stderr, off: /dev/null)
rlpdebug = off

# where to log X debug output (on: stderr, off: /dev/null)
xdebug = off

Köszönöm: Zsolt

RedHat, kernel modul install kozben

Fórumok

Hogyan lehet RedHat (Enterprise) install kozben kernel modult betolteni?
Addig oke, hogy konzolon ki tudom listazni a mar betoltott modulokat, sot torolni is tudok, de nem tudok egyet sem betolteni! Nem is latom hol kellene, hogy legyenek.

ui: kicsit meglepett, hogy sem Fedora sem RedHat csoport nincs a forumoldalak kozott... oda akartam eredetileg