search for: venet0

Hello, ALL. I am trying to organize a transparent single sign-on concept for my Active Directory users into Dovecot via IMAP. On the user's desktop I use Thunderbird 6.0 as a mail client (MUA), Windows XP as an operating system. Domain is controlled by Windows 2008 Server SP2 with Active Directory. I have installed on my Mail server Debian GNU/Linux 6.0.2 (Squeeze) and Dovecot 2.0.13 from

I have a linux server with 3 public IPs, and I use SSH tunnelling to connect to each of them. Let's call them: 1.1.1.1 (venet0:0), 1.1.1.2 (venet0:1), 1.1.1.3 (venet0:2). When I tunnel using 1.1.1.1, outgoing IP for the public is: 1.1.1.1. But when I tunnel using 1.1.1.2 or 1.1.1.3, the outgoing IP for the public is still 1.1.1.1. I've been googling for days, and tried relevant channels on freenode. I tried to read t...

...o the internet , and with NAt rule (Via Shorewall) i can access from Internet to the 3 VPS. i want that all the 3 VPS can communicate between them. i can''t do a tcp connection from a VPS to an other , in my shorewall log in the Host, i have this error : kernel: Shorewall:FORWARD:REJECT:IN=venet0 OUT=venet0 SRC=192.168.7.185 DST=192.168.7.152 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=48986 DF PROTO=TCP SPT=47559 DPT=25 WINDOW=5840 RES=0x00 SYN URGP=0 i have this in my default policy, my Host is fw venet is the virtual network card for the VPS networking net all DROP info fw all ACCEPT loc all...

...host - Mon Sep 30 16:23:59 EDT 2013 Counters reset Mon Sep 30 16:18:46 EDT 2013 Chain FORWARD (policy DROP 0 packets, 0 bytes)  pkts bytes target     prot opt in     out     source               destination  1976  158K net_frwd   all  --  eth0   *       0.0.0.0/0            0.0.0.0/0  2767 3191K venet0_fwd  all  --  venet0 *       0.0.0.0/0            0.0.0.0/0     3   152 Reject     all  --  *      *       0.0.0.0/0            0.0.0.0/0     3   152 LOG        all  --  *      *       0.0.0.0/0            0.0.0.0/0           LOG flags 0 level 6 prefix `Shorewall:FORWARD:REJECT:'     3   152 re...

...UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:113895058 errors:0 dropped:0 overruns:0 frame:0 TX packets:113895058 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:36041459269 (33.5 GiB) TX bytes:36041459269 (33.5 GiB) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 inet6 addr: ::2/128 Scope:Compat inet6 addr: 2a01:488:66:1000:5c33:846e:0:1/128 Scope:Global UP BROADCAST POI...

Hi everybody. I''m trying to configure shorewall folowing this manual: http://www.montanalinux.org/proxmox-ve-with-shorewall.html But with shorewall check it tells me thah: Checking /etc/shorewall/interfaces... ERROR: Unknown zone (dmz) : /etc/shorewall/interfaces (line 16) How can I define it in the zone file? thanks for the help. best regards, Santiago.

...inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 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) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP BROADCAST POINTOPOINT 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 txqueu...

...ill see below. Here''s the script I wrote to replace the redhat specific setup that OpenVZ used: [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh #!/bin/bash # # Debug - take out later set -x LOGFILE=/tmp/add_ip-dbug.log exec >$LOGFILE 2>&1 FACTER_IP_ADDR=$1 FACTER_VENET_DEV=venet0 FACTER_VENET_DEV_CFG=ifcfg-$FACTER_VENET_DEV FACTER_IFNUM=$2 echo "Running puppet-ized version of redhat-add_ip.sh" /bin/cat <<EOM | /usr/bin/puppet file {"/etc/sysconfig/network-scripts/$VENET_DEV_CFG": owner => root, mode => 644, ensure =&gt...

Hi there, I'm having problems with the Grandstream Budgetone 101 on hangup - "show channels"/"show channels concise" output is still showing the call's channels as active. The problem does not exist when I use SJPhone, so I'm assuming it isn't an Asterisk configuration issue. Has anyone seen this, or better, does anyone have a fix? :) Thanks, David. --

...0:c3:f5:29:5e:ce:XX:2d:a2:6f:98:XX:6a:41:06:XX:50:f4:73:cb Unable to determine hostid. You must have at least one ethernet card [root@lvpsXXX-XXX-XXX-XXX root]# Is there any way I can get the virtuozzo server to impersonate eth0. I tried the following: ln -s /etc/sysconfig/network-scripts/ifcfg-venet0 /etc/sysconfig/network-scripts/ifcfg-eth0 and restarted but I think I am off track as it had no effect. Any help would be greatly appreciated. Thanks Steve Ducat.

...------------------------------------------ 1) Previously, if Address Type Match was not available and an interface on the firewall was (mis-)configured as shown below, then REJECT policies in Shorewall-perl would drop packets addressed to the interface rather than reject them. 3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 ... inet 127.0.0.1/32 scope host venet0 inet 206.124.146.176/32 brd 206.124.146.176 ... Note that a /32 should never be configured with a broadcast address. 2) Due to a syntax ambiguity arising from the new dynamic z...

...UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1230259094 errors:0 dropped:0 overruns:0 frame:0 TX packets:1631407780 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1140886155 (1.0 GiB) TX bytes:1095793772 (1.0 GiB) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:4412 errors:0 dropped:0 overruns:0 frame:0...

...his guide: https://www.doas.montanalinux.org/proxmox-ve-with-shorewall.html but when I run shorewall check, this error occurs: Checking... Initializing... Determining Zones... IPv4 Zones: net loc Firewall Zone: fw Validating interfaces file... ERROR: Invalid zone (dmz) in record "dmz venet0 detect routeback" the guide does not talk about the / etc/shorewall / zzones, so it is by default file /etc/shorewall/zones: #ZONE TYPE OPTIONS IN OUT # OPTIONS OPTIONS fw firewall net ipv4...

...aemons. Those rules have been deleted. 2) Previously, if Address Type Match was not available and an interface on the firewall was (mis-)configured as shown below, then REJECT policies in Shorewall-perl would drop packets addressed to the interface rather than reject them. 3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 ... inet 127.0.0.1/32 scope host venet0 inet 206.124.146.176/32 brd 206.124.146.176 ... Note that a /32 should never be configured with a broadcast address. 3) Due to a syntax ambiguity arising from the new dynamic z...

...IPADDR=10.20.0.108 NETMASK=255.255.0.0 ONBOOT=yes TYPE=Bridge cat ifcfg-vmbr0 DEVICE=vmbr0 BOOTPROTO=none DHCPCLASS= IPADDR=195.218.152.219 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Bridge cat ifcfg-vmbr0:1 DEVICE=vmbr0:1 BOOTPROTO=none IPADDR=192.168.2.203 NETMASK=255.255.255.0 ONBOOT=yes cat ifcfg-venet0 DEVICE=venet0 ONBOOT=yes STARTMODE=onboot route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 vmbr0 195.218.152.0 0.0.0.0 255.255.255.0 U 0 0...

Thank you Daniel for pointing out the errors and debug option. Both fixed and on. It made no difference. There are no errors printed and still no sound on ppers Now to Antony questions: On 06/06/2017 04:36 PM, Antony Stone wrote: > On Tuesday 06 June 2017 15:18:32 andre castro wrote: > >> I just installed asterisk in a debian server. >> All seems to be running fine, but the

Hello Guys, I got trouble to get vserver work as gate: GATE=XX.XX.XX.XX YY_PORT=YY echo "1" > /proc/sys/net/ipv4/ip_forward iptables -F -t nat iptables -t nat -A PREROUTING -p tcp -i venet0:0 --dport $YY_PORT \ -j DNAT --to-destination $GATE:$YY_PORT iptables -t nat -A POSTROUTING -p tcp --dport $YY_PORT \ -j MASQUERADE iptables -L -t nat Any suggestion? I got it in the past, but now I'm completely confused. Thanks for help. Sincerely Andy

Hi, I have a VPS running Centos 6.2 and trying to run this iptables rule: [root at myserver ~]# iptables -A INPUT -i venet0 -m state --state ESTABLISHED -j ACCEPT iptables: No chain/target/match by that name. Narrowing down the issue it seems there is no IP_CONNTRACK support but now it's called NF_CONNTRACK. However following this link: http://www.spinics.net/lists/netfilter/msg33535.html I have found...