Pit

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 37 total)
  • Author
    Posts
  • in reply to: Heinzelmännchen Problem #50221

    Pit
    Member

    Sorry, the main too.

    root@zeroshell root> ip route list table main
    213.191.64.45 dev ppp1 proto kernel scope link src 78.51.19.196
    213.191.64.52 dev ppp2 proto kernel scope link src 78.52.122.111
    213.191.64.48 dev ppp0 proto kernel scope link src 78.51.125.38
    87.234.250.0/29 dev ETH01 proto kernel scope link src 87.234.250.3
    192.168.7.0/24 dev ETH00 proto kernel scope link src 192.168.7.75
    192.168.250.0/24 dev VPN99 proto kernel scope link src 192.168.250.254
    default
    nexthop via 87.234.250.1 dev ETH01 weight 1
    nexthop dev ppp0 weight 1

    in reply to: Heinzelmännchen Problem #50220

    Pit
    Member

    Meanwhile i found a working configuration with default gateway + one pppoe line
    balanced.

    iptables -t mangle -L -vn :

    Chain PREROUTING (policy ACCEPT 697 packets, 119K bytes)
    pkts bytes target prot opt in out source destination
    789 135K CONNMARK all — * * 0.0.0.0/0 0.0.0.0/0 CONNMARK restore
    789 135K NetBalancer all — * * 0.0.0.0/0 0.0.0.0/0

    Chain INPUT (policy ACCEPT 399 packets, 42348 bytes)
    pkts bytes target prot opt in out source destination
    489 57946 NetBalancer all — * * 0.0.0.0/0 0.0.0.0/0

    Chain FORWARD (policy ACCEPT 300 packets, 76696 bytes)
    pkts bytes target prot opt in out source destination

    Chain OUTPUT (policy ACCEPT 507 packets, 125K bytes)
    pkts bytes target prot opt in out source destination
    507 125K NetBalancer all — * * 0.0.0.0/0 0.0.0.0/0
    507 125K OpenVPN all — * * 0.0.0.0/0 0.0.0.0/0

    Chain POSTROUTING (policy ACCEPT 807 packets, 201K bytes)
    pkts bytes target prot opt in out source destination
    115 8517 NB_CT_POST all — * * 0.0.0.0/0 0.0.0.0/0 state NEW
    807 201K NB_STAT all — * * 0.0.0.0/0 0.0.0.0/0

    Chain NB_CT_POST (1 references)
    pkts bytes target prot opt in out source destination
    30 2236 MARK all — * * 0.0.0.0/0 0.0.0.0/0 realm 0x66 MARK set 0x66
    50 3875 MARK all — * * 0.0.0.0/0 0.0.0.0/0 realm 0x64 MARK set 0x64
    115 8517 CONNMARK all — * * 0.0.0.0/0 0.0.0.0/0 CONNMARK save

    Chain NB_STAT (1 references)
    pkts bytes target prot opt in out source destination
    31 2312 all — * * 0.0.0.0/0 0.0.0.0/0 MARK match 0x66
    51 3986 all — * * 0.0.0.0/0 0.0.0.0/0 MARK match 0x64

    Chain NetBalancer (3 references)
    pkts bytes target prot opt in out source destination
    0 0 LOG all — ETH00 * 192.168.7.201 62.75.202.23 state NEW,RELATED,ESTABLISHED limit: avg 10/min burst 15 LOG flags 0 level 4 prefix `NetBalancer/001′
    0 0 MARK all — ETH00 * 192.168.7.201 62.75.202.23 state NEW,RELATED,ESTABLISHED MARK set 0x64
    182 31383 ACCEPT all — * * 0.0.0.0/0 0.0.0.0/0 MARK match !0x0
    0 0 LOG tcp — ETH00 * 192.168.7.201 85.25.135.90 state RELATED,ESTABLISHED limit: avg 10/sec burst 15 LOG flags 0 level 4 prefix `NetBalancer/002′
    0 0 MARK tcp — ETH00 * 192.168.7.201 85.25.135.90 state RELATED,ESTABLISHED MARK set 0x64
    0 0 ACCEPT all — * * 0.0.0.0/0 0.0.0.0/0 MARK match !0x0
    0 0 LOG all — ETH00 * 10.0.0.0/24 0.0.0.0/0 state NEW,RELATED,ESTABLISHED limit: avg 10/min burst 15 LOG flags 0 level 4 prefix `NetBalancer/003′
    0 0 MARK all — ETH00 * 10.0.0.0/24 0.0.0.0/0 state NEW,RELATED,ESTABLISHED MARK set 0x66
    0 0 ACCEPT all — * * 0.0.0.0/0 0.0.0.0/0 MARK match !0x0

    Chain OpenVPN (1 references)
    pkts bytes target prot opt in out source destination

    root@zeroshell root> ip rule list
    0: from all lookup local
    32764: from all fwmark 0x66 lookup 102
    32765: from all fwmark 0x64 lookup 100
    32766: from all lookup main
    32767: from all lookup default

    root@zeroshell root> ip route list table 102
    213.191.64.45 dev ppp1 proto kernel scope link src 78.51.19.196
    213.191.64.52 dev ppp2 proto kernel scope link src 78.52.122.111
    213.191.64.48 dev ppp0 proto kernel scope link src 78.51.125.38
    87.234.250.0/29 dev ETH01 proto kernel scope link src 87.234.250.3
    192.168.7.0/24 dev ETH00 proto kernel scope link src 192.168.7.75
    192.168.250.0/24 dev VPN99 proto kernel scope link src 192.168.250.254
    default dev ppp0 scope link
    unreachable default metric 99

    root@zeroshell root> ip route list table 100
    213.191.64.45 dev ppp1 proto kernel scope link src 78.51.19.196
    213.191.64.52 dev ppp2 proto kernel scope link src 78.52.122.111
    213.191.64.48 dev ppp0 proto kernel scope link src 78.51.125.38
    87.234.250.0/29 dev ETH01 proto kernel scope link src 87.234.250.3
    192.168.7.0/24 dev ETH00 proto kernel scope link src 192.168.7.75
    192.168.250.0/24 dev VPN99 proto kernel scope link src 192.168.250.254
    default via 87.234.250.1 dev ETH01
    unreachable default metric 99

    in reply to: Heinzelmännchen Problem #50218

    Pit
    Member

    Further testing:

    The idea: creating a balancing rule that sends answer packages to a host through the gateway they come from.

    It’s a funny thing. The log’s show that those packages are handled but only sometimes.

    Bye the way the ZS experiment is very expensive meanwhile.

    Is there somebody outsite who can configure the machine for us the right way?
    Please make an offer.

    Regards
    Pit

    in reply to: Heinzelmännchen Problem #50217

    Pit
    Member

    Well, the patch is ok. Don’t know why the patch command failed.
    I patched the rejected parts handish and saved the patched files
    in /Database/custom.
    Then under the “Startup/cron” tab under “SYSTEM” “Setup”, I have put the following into the “pre-boot” script:

    for file in /Database/custom/*
    do
    cp ${file} /root/kerbynet.cgi/scripts/
    done

    All works fine with balancing disabled. Even vpn99 works well. All virtual servers behind ZS are reachable. No need for virtual servers to reach ZS from the outsite. No need for NAT on the only default gateway.

    But the crux is: If i enable balancing the hole ZS is unreachable from the outsite and no virtual services are reachable.
    Enabeling NAT on the balanced devices has no effect.

    My point of view is outsite. I have to manage ZS and the servers behind ZS remote.
    I tried ZS for balancing traffic to the outsite additionally.

    Any idea?

    in reply to: Heinzelmännchen Problem #50216

    Pit
    Member

    Z e r o S h e l l – Net Services 1.0.beta12 May 11, 2010 – 19:13

    I have done so. May be you did not show me the latest patch.

    in reply to: Heinzelmännchen Problem #50214

    Pit
    Member

    nb_fw.rej:

    ***************
    *** 1,24 ****
    #!/bin/sh
    . /etc/kerbynet.conf
    iptables -t mangle -D PREROUTING -j CONNMARK –restore-mark 2>/dev/null
    – iptables -t mangle -D PREROUTING -j NetBalancer 2>/dev/null
    – iptables -t mangle -D INPUT -j NetBalancer 2>/dev/null
    – iptables -t mangle -D OUTPUT -j NetBalancer 2>/dev/null
    iptables -t mangle -D OUTPUT -j OpenVPN 2>/dev/null
    iptables -t mangle -D POSTROUTING -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -D POSTROUTING -j NB_STAT 2>/dev/null
    if [ “`cat $REGISTER/system/net/nb/Enabled 2>/dev/null`” = yes ] ; then
    iptables -t mangle -I PREROUTING 1 -j CONNMARK –restore-mark
    – iptables -t mangle -I PREROUTING 2 -j NetBalancer
    iptables -t mangle -I POSTROUTING 1 -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -I POSTROUTING 2 -j NB_STAT 2>/dev/null
    – iptables -t mangle -I INPUT 1 -j NetBalancer
    – iptables -t mangle -I OUTPUT 1 -j NetBalancer
    – iptables -t mangle -I OUTPUT 2 -j OpenVPN
    fi
    $SCRIPTS/nb_vpn 2> /dev/null
    $SCRIPTS/nb_setautomarking 2>/dev/null


    — 1,35 —-
    #!/bin/sh
    . /etc/kerbynet.conf
    iptables -t mangle -D PREROUTING -j CONNMARK –restore-mark 2>/dev/null
    + iptables -t mangle -D PREROUTING -m state –state NEW -j NB_CT_PRE 2>/dev/null
    + iptables -t mangle -D PREROUTING -m state –state NEW -j NetBalancer 2>/dev/null
    + iptables -t mangle -D INPUT -m state –state NEW -j NB_CT_POST 2>/dev/null
    + iptables -t mangle -D OUTPUT -j CONNMARK –restore-mark 2>/dev/null
    + iptables -t mangle -D OUTPUT -m state –state NEW -j NB_FO_PRE 2>/dev/null
    + iptables -t mangle -D OUTPUT -m state –state NEW -j NetBalancer 2>/dev/null
    iptables -t mangle -D OUTPUT -j OpenVPN 2>/dev/null
    iptables -t mangle -D POSTROUTING -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -D POSTROUTING -j NB_STAT 2>/dev/null
    + # Need QoS to be done in mangle POSTROUTING. Note that if NetBalance
    + # is enabled then we will insert those rules/chains first. So any
    + # routing marks will be handled before we blow them away with QoS
    + # marks.
    + iptables -t mangle -D POSTROUTING -j QoS 2>/dev/null
    + iptables -t mangle -I POSTROUTING 1 -j QoS 2>/dev/null
    if [ “`cat $REGISTER/system/net/nb/Enabled 2>/dev/null`” = yes ] ; then
    iptables -t mangle -I PREROUTING 1 -j CONNMARK –restore-mark
    + iptables -t mangle -I PREROUTING 2 -m state –state NEW -j NB_CT_PRE 2>/dev/null
    + iptables -t mangle -I PREROUTING 3 -m state –state NEW -j NetBalancer
    + iptables -t mangle -I INPUT 1 -m state –state NEW -j NB_CT_POST 2>/dev/null
    + iptables -t mangle -I OUTPUT 1 -j CONNMARK –restore-mark
    + iptables -t mangle -I OUTPUT 2 -m state –state NEW -j NB_FO_PRE
    + iptables -t mangle -I OUTPUT 3 -m state –state NEW -j NetBalancer
    + iptables -t mangle -I OUTPUT 4 -j OpenVPN
    iptables -t mangle -I POSTROUTING 1 -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -I POSTROUTING 2 -j NB_STAT 2>/dev/null
    fi
    $SCRIPTS/nb_vpn 2> /dev/null
    $SCRIPTS/nb_setautomarking 2>/dev/null
    + echo 300 > /proc/sys/net/ipv4/route/gc_min_interval
    + echo 360 > /proc/sys/net/ipv4/route/gc_timeout

    in reply to: Heinzelmännchen Problem #50213

    Pit
    Member

    Oops! something went wrong.

    The patch may be not compatible:

    root@zeroshell scripts> patch -p0 < zeroshell-3.patch
    patching file failoverd
    patching file fw_initrules
    Hunk #2 FAILED at 23.
    1 out of 2 hunks FAILED — saving rejects to file fw_initrules.rej
    patching file fw_makerule
    patching file fw_start
    Hunk #1 succeeded at 10 with fuzz 1.
    patching file fw_viewchain
    patching file nb_fw
    Hunk #1 FAILED at 1.
    1 out of 1 hunk FAILED — saving rejects to file nb_fw.rej
    patching file nb_setautomarking

    fw_initrules.rej:

    ***************
    *** 23,34 ****
    iptables -A INPUT -j SYS_INPUT
    iptables -A INPUT -p tcp –dport 80 -j SYS_HTTPS
    iptables -A INPUT -p tcp –dport 443 -j SYS_HTTPS
    iptables -A INPUT -p tcp –dport 22 -j SYS_SSH
    fi
    [ “$CHAIN” == OUTPUT ] && iptables -A OUTPUT -j SYS_OUTPUT
    if [ -d $CONFIG/Chains/$CHAIN/Rules ] ; then
    cd $CONFIG/Chains/$CHAIN/Rules
    RULES=`ls`
    for RULE in $RULES ; do
    ENABLED=”`cat $RULE/Enabled 2>/dev/null`”
    if [ “$ENABLED” == yes ] ; then
    — 23,38 —-
    iptables -A INPUT -j SYS_INPUT
    iptables -A INPUT -p tcp –dport 80 -j SYS_HTTPS
    iptables -A INPUT -p tcp –dport 443 -j SYS_HTTPS
    iptables -A INPUT -p tcp –dport 22 -j SYS_SSH
    fi
    [ “$CHAIN” == OUTPUT ] && iptables -A OUTPUT -j SYS_OUTPUT
    + # If we are doing the QoS chain, thenlear any marks left over from
    + # Netbalancing/failover routing. The QoS chain is applied after
    + # routing so there is no conflict.
    + [ “$CHAIN” == “QoS” ] && iptables $TABLE -A $CH -j MARK –set-mark 0x0
    if [ -d $CONFIG/Chains/$CHAIN/Rules ] ; then
    cd $CONFIG/Chains/$CHAIN/Rules
    RULES=`ls`
    for RULE in $RULES ; do
    ENABLED=”`cat $RULE/Enabled 2>/dev/null`”
    if [ “$ENABLED” == yes ] ; then

    in reply to: Heinzelmännchen Problem #50212

    Pit
    Member

    Thank you for the hint.

    The patch may be not compatible:

    root@zeroshell scripts> patch -p0 /dev/null
    – iptables -t mangle -D PREROUTING -j NetBalancer 2>/dev/null
    – iptables -t mangle -D INPUT -j NetBalancer 2>/dev/null
    – iptables -t mangle -D OUTPUT -j NetBalancer 2>/dev/null
    iptables -t mangle -D OUTPUT -j OpenVPN 2>/dev/null
    iptables -t mangle -D POSTROUTING -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -D POSTROUTING -j NB_STAT 2>/dev/null
    if [ “`cat $REGISTER/system/net/nb/Enabled 2>/dev/null`” = yes ] ; then
    iptables -t mangle -I PREROUTING 1 -j CONNMARK –restore-mark
    – iptables -t mangle -I PREROUTING 2 -j NetBalancer
    iptables -t mangle -I POSTROUTING 1 -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -I POSTROUTING 2 -j NB_STAT 2>/dev/null
    – iptables -t mangle -I INPUT 1 -j NetBalancer
    – iptables -t mangle -I OUTPUT 1 -j NetBalancer
    – iptables -t mangle -I OUTPUT 2 -j OpenVPN
    fi
    $SCRIPTS/nb_vpn 2> /dev/null
    $SCRIPTS/nb_setautomarking 2>/dev/null


    — 1,35 —-
    #!/bin/sh
    . /etc/kerbynet.conf
    iptables -t mangle -D PREROUTING -j CONNMARK –restore-mark 2>/dev/null
    + iptables -t mangle -D PREROUTING -m state –state NEW -j NB_CT_PRE 2>/dev/null
    + iptables -t mangle -D PREROUTING -m state –state NEW -j NetBalancer 2>/dev/null
    + iptables -t mangle -D INPUT -m state –state NEW -j NB_CT_POST 2>/dev/null
    + iptables -t mangle -D OUTPUT -j CONNMARK –restore-mark 2>/dev/null
    + iptables -t mangle -D OUTPUT -m state –state NEW -j NB_FO_PRE 2>/dev/null
    + iptables -t mangle -D OUTPUT -m state –state NEW -j NetBalancer 2>/dev/null
    iptables -t mangle -D OUTPUT -j OpenVPN 2>/dev/null
    iptables -t mangle -D POSTROUTING -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -D POSTROUTING -j NB_STAT 2>/dev/null
    + # Need QoS to be done in mangle POSTROUTING. Note that if NetBalance
    + # is enabled then we will insert those rules/chains first. So any
    + # routing marks will be handled before we blow them away with QoS
    + # marks.
    + iptables -t mangle -D POSTROUTING -j QoS 2>/dev/null
    + iptables -t mangle -I POSTROUTING 1 -j QoS 2>/dev/null
    if [ “`cat $REGISTER/system/net/nb/Enabled 2>/dev/null`” = yes ] ; then
    iptables -t mangle -I PREROUTING 1 -j CONNMARK –restore-mark
    + iptables -t mangle -I PREROUTING 2 -m state –state NEW -j NB_CT_PRE 2>/dev/null
    + iptables -t mangle -I PREROUTING 3 -m state –state NEW -j NetBalancer
    + iptables -t mangle -I INPUT 1 -m state –state NEW -j NB_CT_POST 2>/dev/null
    + iptables -t mangle -I OUTPUT 1 -j CONNMARK –restore-mark
    + iptables -t mangle -I OUTPUT 2 -m state –state NEW -j NB_FO_PRE
    + iptables -t mangle -I OUTPUT 3 -m state –state NEW -j NetBalancer
    + iptables -t mangle -I OUTPUT 4 -j OpenVPN
    iptables -t mangle -I POSTROUTING 1 -m state –state NEW -j NB_CT_POST 2>/dev/null
    iptables -t mangle -I POSTROUTING 2 -j NB_STAT 2>/dev/null
    fi
    $SCRIPTS/nb_vpn 2> /dev/null
    $SCRIPTS/nb_setautomarking 2>/dev/null
    + echo 300 > /proc/sys/net/ipv4/route/gc_min_interval
    + echo 360 > /proc/sys/net/ipv4/route/gc_timeout

    Are there any further ideas?

    in reply to: Heinzelmännchen Problem #50210

    Pit
    Member

    At the production location the ZS balancer works fine over four ADSL lines.

    Does somebody know the trick to administer the machine and virtual servers from remote?

    VPN99 does not connect. Vitual server at :443 works only one time. After connecting to the other virtual server behind ZS the machines is no more reachable.

    I guess that the answer packages are balanced to the nirwana.

    Is there a way to solve this problem?

    Thanks in advance

    Pit

    in reply to: Heinzelmännchen Problem #50209

    Pit
    Member

    OK. I got the idea of ZS GUI.
    Thanks again for your help.

    Regards
    Pit

    in reply to: Heinzelmännchen Problem #50207

    Pit
    Member

    … changing the default gateway to a balancer gateway….
    Irefer to the first picture at ZS landingpage: Thre is the default gateway disabled and the balancer gateway Infostrada ADSL used instead.

    in reply to: Heinzelmännchen Problem #50205

    Pit
    Member

    In this environment ZS works now as expected.

    Now i ask before my next mismatch causes trouble:

    Next step are three another lines (pppoe) balanced with the default one.

    Am i right to enable NAT on this devices?

    Am i right to change the default gateway to a balancer gateway?

    Am i right to point the traffic to a special server with a balancer rule to a dedicated gateway?

    Is it a good idea to enable rip-v.2 on all devices?

    Thanks in advance

    Pit

    in reply to: Heinzelmännchen Problem #50203

    Pit
    Member

    The public IP at ETH04 is from the former/later location. There is a range of pulic IP’s.
    The private IP is at my home where i troubleshoot the balancer.

    ETH03 is my lan with one gateway machine. This machine and the balancer itself should be reachable over the virtual servers.

    My perception of the GUI Router/NAT was, that one has to point to the both devices between NAT is supposed to be. This was obviously wrong. Additionally behind the curtain works MASQUERADING and not NAT. This is confusing too.

    After some testing MASQUERADING only on device ETH04 solves the Problem.
    In virtual servers also the IP wich is supposed to be used has to be configured explicitly.
    Configuring the device only does not work.

    I thank you for your effort and the hint about MASQUERADING.

    Regards
    PIT

    in reply to: Heinzelmännchen Problem #50201

    Pit
    Member

    Hello ppalias,
    here are the results:

    root@zeroshell root> iptables -L -v
    Chain INPUT (policy ACCEPT 13 packets, 708 bytes)
    pkts bytes target prot opt in out source destination
    405 70508 SYS_INPUT all — any any anywhere anywhere
    0 0 SYS_HTTPS tcp — any any anywhere anywhere tcp dpt:http
    258 35718 SYS_HTTPS tcp — any any anywhere anywhere tcp dpt:https
    40 4172 SYS_SSH tcp — any any anywhere anywhere tcp dpt:ssh

    Chain FORWARD (policy ACCEPT 218 packets, 52580 bytes)
    pkts bytes target prot opt in out source destination

    Chain OUTPUT (policy ACCEPT 317 packets, 171K bytes)
    pkts bytes target prot opt in out source destination
    412 179K SYS_OUTPUT all — any any anywhere anywhere

    Chain NetBalancer (0 references)
    pkts bytes target prot opt in out source destination

    Chain SYS_HTTPS (2 references)
    pkts bytes target prot opt in out source destination
    0 0 ACCEPT all — lo any anywhere anywhere
    258 35718 ACCEPT all — any any anywhere anywhere

    Chain SYS_INPUT (1 references)
    pkts bytes target prot opt in out source destination
    30 3966 ACCEPT all — lo any anywhere anywhere
    20 6488 ACCEPT udp — any any anywhere anywhere udp spt:domain state ESTABLISHED
    15 17252 ACCEPT tcp — any any anywhere anywhere tcp spt:http state ESTABLISHED
    0 0 ACCEPT tcp — any any anywhere anywhere tcp spt:8245 state ESTABLISHED
    29 2204 ACCEPT udp — any any anywhere anywhere udp spt:ntp state ESTABLISHED
    311 40598 RETURN all — any any anywhere anywhere

    Chain SYS_OUTPUT (1 references)
    pkts bytes target prot opt in out source destination
    30 3966 ACCEPT all — any lo anywhere anywhere
    21 1593 ACCEPT udp — any any anywhere anywhere udp dpt:domain
    15 908 ACCEPT tcp — any any anywhere anywhere tcp dpt:http
    0 0 ACCEPT tcp — any any anywhere anywhere tcp dpt:8245
    29 2204 ACCEPT udp — any any anywhere anywhere udp dpt:ntp
    317 171K RETURN all — any any anywhere anywhere
    Chain SYS_SSH (1 references)
    pkts bytes target prot opt in out source destination
    0 0 ACCEPT all — lo any anywhere anywhere
    40 4172 ACCEPT all — ETH04 any anywhere anywhere
    0 0 DROP all — any any anywhere anywhere

    root@zeroshell root> iptables -t nat -L -v
    Chain PREROUTING (policy ACCEPT 40 packets, 4069 bytes)
    pkts bytes target prot opt in out source destination
    0 0 DNAT tcp — ETH04 any anywhere 192.168.0.199 tcp dpt:http to:192.168.7.201:80
    15 900 DNAT tcp — ETH04 any anywhere 192.168.0.199 tcp dpts:snpp:commplex-main to:192.168.7.201:444-5000
    11 660 DNAT tcp — ETH04 any anywhere anywhere tcp dpt:https to:192.168.7.75:443
    1 60 DNAT tcp — ETH04 any anywhere anywhere tcp dpt:ssh to:192.168.7.75:22

    Chain POSTROUTING (policy ACCEPT 11 packets, 923 bytes)
    pkts bytes target prot opt in out source destination
    92 6629 SNATVS all — any any anywhere anywhere
    15 900 MASQUERADE all — any ETH03 anywhere anywhere
    66 4806 MASQUERADE all — any ETH04 anywhere anywhere

    Chain OUTPUT (policy ACCEPT 64 packets, 4932 bytes)
    pkts bytes target prot opt in out source destination

    Chain SNATVS (1 references)
    pkts bytes target prot opt in out source destination

    root@zeroshell root> ifconfig
    ETH00 Link encap:Ethernet HWaddr 00:30:18:AA:BE:73
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    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:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:18 Base address:0xe000

    ETH01 Link encap:Ethernet HWaddr 00:30:18:AA:BE:74
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    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:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:19

    ETH02 Link encap:Ethernet HWaddr 00:30:18:AA:BE:75
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    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:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:16 Base address:0x2000

    ETH03 Link encap:Ethernet HWaddr 00:30:18:A1:71:5B
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:112 errors:0 dropped:0 overruns:0 frame:0
    TX packets:131 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:16099 (15.7 Kb) TX bytes:41353 (40.3 Kb)
    Interrupt:23 Base address:0x6000

    ETH03:00 Link encap:Ethernet HWaddr 00:30:18:A1:71:5B
    inet addr:192.168.7.75 Bcast:192.168.7.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    Interrupt:23 Base address:0x6000

    ETH04 Link encap:Ethernet HWaddr 00:1B:21:56:DE:97
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:607 errors:0 dropped:0 overruns:0 frame:0
    TX packets:600 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:100
    RX bytes:122933 (120.0 Kb) TX bytes:210159 (205.2 Kb)

    ETH04:00 Link encap:Ethernet HWaddr 00:1B:21:56:DE:97
    inet addr:192.168.0.199 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    ETH04:01 Link encap:Ethernet HWaddr 00:1B:21:56:DE:97
    inet addr:87.234.250.2 Bcast:87.234.250.7 Mask:255.255.255.248
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    VPN99 Link encap:Ethernet HWaddr 00:FF:0C:F5:78:13
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    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)

    VPN99:00 Link encap:Ethernet HWaddr 00:FF:0C:F5:78:13
    inet addr:192.168.250.254 Bcast:192.168.250.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    dummy1 Link encap:Ethernet HWaddr 82:C4:47:FF:90:1B
    inet addr:192.168.142.142 Bcast:192.168.142.255 Mask:255.255.255.255
    UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
    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)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:188 errors:0 dropped:0 overruns:0 frame:0
    TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:22023 (21.5 Kb) TX bytes:22023 (21.5 Kb)

    Regards
    Pit


    Pit
    Member

    Hello ppalias,

    thank you for your reply and the hint with lspci.
    The output is:

    root@zeroshell root> lspci
    00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
    00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
    00:08.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
    00:0a.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev 80)
    00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
    00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
    00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
    00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
    00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
    00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
    01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] (rev 01)
    root@zeroshell root>

    As you can see the ethernetblock for 3 realtek cards is missing.
    My other identical machine shows in addition 3 times:

    00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)

    Maybe that this block is broken from one day to the other. People on-site say that the block is connected properly and led’s are working.

    I think it is a problem of broken hardware and not of zeroshell.

    Thanks again for the hint.

    Regards
    Pit

Viewing 15 posts - 16 through 30 (of 37 total)