search for: local_addresses

Hallo, Another strange and difficult to understand thing - seems like all the easy bugs in 1.1 are gone ;) waehring (1.1) | +-------------------+--------------+ | | | vpnhub1 (1.1) igor (1.1) turing (1.0) | | | +-------------------+--------------+ | tokamak Whenever another node outside of the graph connects to vpnhub or igor

...I''ve restarted the server countless times to no avail, and to short-circuit the fact that I''m running the server and making page requests locally, I commented out the code in ExceptionNotifiable as such: def local_request? # remote = IPAddr.new(request.remote_ip) # !self.class.local_addresses.detect { |addr| addr.include?(remote) }.nil? false end ...and I''ve also tried: def local_addresses ''addresses = read_inheritable_attribute(:local_addresses) unless addresses addresses = [IPAddr.new("127.0.0.1")] write_inheritable_attribute(:l...

Hi everyone, So, I''ve got exception_notification working now, but not in development mode on localhost. In my ApplicationController, I''ve added: local_addresses.clear Shouldn''t that be enough? Thank you! Sean

On Fri, May 15, 2015 at 10:26:46PM +0200, Sven-Haegar Koch wrote: > Another strange and difficult to understand thing - seems like all the > easy bugs in 1.1 are gone ;) [...] > Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak > -> igor which does not match existing entry (Local address 2.3.4.5 > != unknown) > > What I think may happen is that the

On Fri, 15 May 2015, Guus Sliepen wrote: > On Fri, May 15, 2015 at 10:26:46PM +0200, Sven-Haegar Koch wrote: > > > Another strange and difficult to understand thing - seems like all the > > easy bugs in 1.1 are gone ;) > [...] > > Got ADD_EDGE from aaa_vpnhub1 (1.2.3.4 port 443) for haegar_tokamak > > -> igor which does not match existing entry (Local

Hello, I have installed a server with three physical ethernet links and some virtual interfaces: eth0 - 213.215.42.70 eth0:1 - 213.215.42.71 eth0:2 - 213.215.42.72 eth0:3 - 213.215.42.73 eth0:4 - 213.215.42.74 eth0:5 - 213.215.42.75 eth0:6 - 213.215.42.76 eth0:7 - 213.215.42.77 eth0:8 - 213.215.42.78 eth2 - 192.168.1.128 eth3 - 213.215.42.69 All traffic are routed by iproute2 and iptables

Marco Gaiarin via samba ha scritto il 25/08/20 alle 18:53: > [...] >> The only other thing I can think of at the moment is to remove >> 'winbind use default domain = yes' > > It was a try, i think in NT mode don't bother at all. on my samba server with 'winbind use default domain" set to yes dominioNT\ is removed from users and groups names... >

Mandi! Rowland penny via samba In chel di` si favelave... > Even though your users may have the same username in AD as in the NT4-style > domain, they are different users, so a few thoughts. You have 'map to guest > = bad user', so I take it you must have 'guest ok = yes' set in the shares > (you haven't shown us the shares), so try changing 'bad user' to

Hi, can't seem to login to Samba Server using notebook. OS is FreeBSD 10.3. Samba Version is 4.6.6 Connect to the remote Samba server using L2TP/IPSec connection. When trying to login it's not accepting the correct credentials. When ssh'ing to the server can login without any issue: # smbclient -Uusername //server/share Enter SERVERNAME\username's password: Domain=[DOMAINNAME]

Hi! I'm currently setting up my first mailsystem based on dovecot. For a far way, working with dovecot was very convenient, but after I had to integrate deliver, it became massivly painful. My components are postfix as MTA, postgresql as user database and dovecot as IMAP server. When translating the mail adresse into the account name, something goes terribly wrong (Mail adresses modified to

I see many entries in /var/log/secure similar to these: . . . /var/log/secure.1:Dec 31 08:00:55 gway01 sshd[7220]: Received disconnect from 93.89.144.31: 11: Bye Bye /var/log/secure.1:Dec 31 08:00:58 gway01 sshd[7221]: Failed password for root from 93.89.144.31 port 60100 ssh2 /var/log/secure.1:Dec 31 08:00:58 gway01 sshd[7222]: Received disconnect from 93.89.144.31: 11: Bye Bye

We've a Samba 4 domain (no AD, just DC) with LDAP backend on Ubuntu 14.04. This server has been migrated from files backend to LDAP by the previous maintainer, I know the version is pretty old but we cannot update at the moment. The domain works fine with some W7 and W10 (updated from 7) computers, but we have purchased a new Lenovo laptop with Win10 which joined the domain seamlessly but

Our samba server in ap-east-1 is running very slow today I noticed three things in log.smb, and I don't understand any of them ---------- #1 roughly every 80 seconds what appears to be a reconnect loop [2020/11/19 17:35:46.283315, 2] ../../source3/lib/tallocmsg.c:87(register_msg_pool_usage) Registered MSG_REQ_POOL_USAGE [2020/11/19 17:35:46.287132, 1]

Hello, A few months ago the distribution I use (Debian Testing) moved from Samba 3 to Samba 4 - I started seeing a lot of problems. Since then there are two bugs I find occurring on a regular basis: 1. Consistent dumping core on a regular basis (very rarely, if ever occurred with Samba 3) a. $ ls -ltr *core*smbd* |wc -l b. 1297 c. $ du -ach *core*smbd*|tail -n 1

Tom, I think it might be productive to fork this thread to discuss making the requirements for upstreaming a new LLVM target more explicit and open. I'd also like to gauge interest in an idea I've discussed privately with a few community members, namely the concept of having a semi-official "incubation" system whereby proposed backends could get a trial run before becoming part