similar to: src routing question

Hi Guys, I have a little problem i dont understand why its happening, Initially i thought it was a network problem, but then i made a crossover between me and the server and shaped on that interface with as minimal as possible config this my test: $TC qdisc add dev $INTERFACE root handle 1: htb default 30 $TC class add dev $INTERFACE parent 1: classid 1:1 htb rate 10Mbit # POOL1 $TC class add

Greetings, Is there a way to tie a specific sip username to a IP address when authenticating against mysql sipfriends table? (USE_MYSQL_FRIENDS=1 USE_SIP_MYSQL_FRIENDS=1 in channels/Makefile) The reason is that I'm using Wellgate FXSes that have second/third/fourth FXS ports bugged when I use a password, but work ok when there is no password. Linking the username to a specific ip could

BACKGROUND --------------------- I have a system running Red Hat 7.1 (2.4 kernel) that I've set up on a local subnet to server as a router to the outside world, including the Internet. IP forwarding and NAT work just fine on the TCP/IP level. Outside World [10.11.0.0 network] 10.11.0.1 | |---- 10.11.0.2 Win2K MYGROUP |

hi, there was some email problems and i repeat my question too fast, but this is the second part of my questions. - only the rules and policy files give access right? ie. rules in the FORWARD chain of the filter table in iptables ? - is a line in masq file automaticaly add an accept rule too? eg. in msaq file eth0 <internal ip> allow connection from <internal ip> (local zona) to the

Hello everybody. I could not find an answer to my problem in the archive. (But that may just be me :-) ) I have a problem with proxy arp and connection from loc (localnet) and from the firewall. Works fine from internet to dmz / proxy arp and vise versa. I have a feeling the solution is simple, but I''m no guru in Linux routing etc. The problem seems to be the routing setup. loc -

Hello, Are there any good alternatives to the network-nat script on Debian Squeeze? I have tried using (network-script network-nat) and (vif-script vif-nat), but I end up with an error message like Error: Device 1 (vif) could not be connected. ip addr add 10.0.1.259 dev vif4.1 failed with configuration file directive vif =[ ''script=vif-nat,ip=10.0.1.132'' ] I need Internet

Hi, can anybody comment on the cost of matching with IPP2P vs. Layer7. Also, does a iptables rule with more complicated matching mechanism also slow down processing if all the packets are matched before they reach the rule. I.e. is the mere existence of a potentially costly rule already slowing down processing or only if packets are actually processed by it? Thanks very much in advance.

Hi I have a atrange problem and don''t know where to look anymore. I have 4 interfaces running on RHE3 on a Dell XEON server 2.8Ghz 1Gb RAM. The primary use (only one at this stage) is for the server to handle mac address authentication of clients which it does. The problem however has to do with througput. I have 3 DMZ''s which one is a private range doing masquarading and

Hi everyone, I need your help. I would like to create a front-back architecture with Xen. My physical server has only one public Interface. Currently, my DOM0 is using the network-route configuration: *(network-script ''network-route netdev=eth0'') (vif-script vif-route)* My DOM1 is configured with a public IP + proxy_arp with DOM0. DOM1 can connect any address on

This looks like a very cool feature addition to RELENG_7! Are there any performance penalties that you know of with this built in ? ---Mike At 09:13 PM 7/23/2008, Julian Elischer wrote: >julian 2008-07-24 01:13:22 UTC > > FreeBSD src repository > > Modified files: (Branch: RELENG_7) > contrib/pf/pfctl parse.y > lib/libc/sys

Ever since last night all mail from the samba list has been bouncing. I'm out of ideas...does anyone have a suggestion on what to fix. I've attached the mail notification. It seems like sendmail does think that lists.samba.org exists but I can do a successful lookup? Gerry "The lyf so short, the craft so long to learne" Chaucer ---------- Forwarded message ---------- Date:

Marcel Moolenaar wrote am 17.03.2008 17:28 (localtime): > > On Mar 17, 2008, at 3:33 AM, Poul-Henning Kamp wrote: > >> phk 2008-03-17 10:33:23 UTC >> >> FreeBSD src repository >> >> Modified files: >> sys/sys ata.h >> sbin/atacontrol atacontrol.8 atacontrol.c >> sys/dev/ata ata-all.c ata-all.h

Hello Tom, Sorry, please but i again return to IFB question. If i correct understand in current situation IFB haven't profit from ESFQ in common cases (i mean internal networks masquarading) so as we wait from ESFQ allocates bandwidth fairly per source IP(internal) but IFB don't know internal IPs. If i correct, what do you think what can help IFB to solve its main disadvantage

shorewall version 2.0.7 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:48:53:25:b2 brd ff:ff:ff:ff:ff:ff inet 81.169.188.152/32 brd 81.169.188.152 scope global eth0 3: eth1:

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 399073 src:xen 3.0.3-0-2 Bug #399073 [xen-hypervisor-3.0.3-1-i386] xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb Warning: Unknown package 'xen-hypervisor-3.0.3-1-i386' Bug

Hi Alex, and thanks for your time. Probably not. The servers are only configured like they where when they where parallel to the fw. Just the default gateway, same as for the external interface on the fw. That''s what the documentation instructed to configure the servers using arp. But is it required with extra configuration on the server connected via proxy arp? Or is it some parameter

Am 24.04.2006 um 23:17 schrieb Colin Percival: > cperciva 2006-04-24 21:17:02 UTC > > FreeBSD src repository > > Modified files: > sys/amd64/amd64 mp_machdep.c > sys/i386/i386 mp_machdep.c > Log: > Adjust dangerous-shared-cache-detection logic from "all shared data > caches are dangerous" to "a shared L1 data cache is

https://bugzilla.samba.org/show_bug.cgi?id=7870 Summary: --link-dest=${SRC} ${SRC} ${DST} can be smarter Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: weerd+rsync at

configure.ac | 2 +- src/Makefile.am | 5 +++-- src/plugin.c | 26 ++++++++++++++++++++++---- 3 files changed, 26 insertions(+), 7 deletions(-) New commits: commit ca13a1daef653a80e89250e273496ca01dfccddd Author: Benjamin Otte <otte at gnome.org> Date: Tue Nov 6 21:29:54 2007 +0100 make sure the plugin is never unloaded (#13110, reported by Tom Parker) It seems

https://bugzilla.samba.org/show_bug.cgi?id=2690 Summary: SYNOPSIS "rsync [OPTION]... SRC [SRC]... DEST" incorrect Product: rsync Version: 2.6.4 Platform: All URL: http://rsync.samba.org/ftp/rsync/rsync.html OS/Version: All Status: NEW Severity: trivial Priority: P3 Component: core