similar to: IPv6 two or more providers, duplicating routing table does not work

Displaying 20 results from an estimated 800 matches similar to: "IPv6 two or more providers, duplicating routing table does not work"

2007 Jul 29
12
Shorewall 4.0.0 + Kernel 2.6.21.5-grsec
Hello, My hoster updated its kernel packages... It contained some old problems that should have been fixed. My servers have now a wonderful 2.6.21.5 kernel + grsec running. Both are running Debian 4.0 (stable release). mx:/etc/shorewall# iptables --version iptables v1.3.6 mx:/etc/shorewall# uname -a Linux mx.network-hosting.com 2.6.21.5-grsec-xxxx-grs-ipv4-32 #1 SMP Fri Jul 27 17:18:23 CEST
2010 Mar 20
2
2.0 beta: LMTP + Sieve fileinto broken
Hoi, somewhere between Hg revisions 10945 and 10962 filing into a subfolder using sieve Scripts (like fileinto "fwd.sixxs" here) broke Mar 20 18:14:24 mail dovecot: lmtp(27326, berni at vmail.mail.mucip.net): ojJwL3ACpUu+agAA/GZUZg: msgid=<tickets-tickets.1418885.1419129 at noc.sixxs.net>: save failed to fwd.sixxs: Mailbox doesn't exist: fwd.sixxs Used to work fine before.
2013 Nov 19
7
IPv6 connections won't be rejected nor logged
Hi, I have servers where shorewall6 won''t reject nor log: # cat /etc/shorewall6/zones fw firewall net ipv6 # cat /etc/shorewall6/interfaces net eth1 tcpflags (I also tried without "tcpflags", but no changes) # cat /etc/shorewall6/policy $FW all ACCEPT all all REJECT info # cat /etc/shorewall6/rules SECTION NEW (for testing, I removed all the rules) I am testing from
2019 Apr 01
2
Re: guestfish Remote Images IPv6 Support
I believe the bug lies in libguestfs. Taking out the commands being sent to QEMU and using qemu-img info I can recreate the error: # qemu-img info "rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" qemu-img: Could not open 'rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none': invalid
2019 Apr 01
1
Re: guestfish Remote Images IPv6 Support
This worked wonderfully!  What are the odds of getting this upstream in the near future?  I'd rather not build from source in production. # ./run guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: trace: set_tmpdir "/root/libguestfs/tmp" libguestfs:
2009 Dec 06
6
shorewall6-lite's shorecap sourcing /usr/share/shorewall-lite/lib.base?
Hey all, Just a sanity check, but should the shorecap script in shorewall6-lite be sourcing /usr/share/shorewall6-lite/lib.base rather than /usr/share/shorewall-lite/lib.base like it does currently? In fact shouldn''t there be a general s/shorewall-lite/shorewall6-lite/ in shorecap in shorewall6-lite? Maybe there is more of that lurking about as well. Also, the first line of the
2005 Oct 31
0
"disappeared" user
I would really appreciate some help figuring out why one of my students has "disappeared" from the user list, and what to do about it. I'm using Samba3 on Fedora; the client machines are running WinXP. The system has been up and running since the beginning of September. Today one of my 4th-graders was unable to log on; she didn't read the error message carefully, so she
2005 May 31
11
More Tests for 2.4.0-RC2 - strange behaviour
Hi all, I was trying to test ROUTE specific code with a multi-isp serviced box. There is a bug somewhere, but I''m not able to understand what the real problem is: when I issue a "shorewall show capabilities" I get: Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Shorewall has
2011 Dec 04
6
Shorewall 4.4.27 Beta 1
Beta 1 is now available for testing. One of the problems I''ve had with the Shorewall products is trying to keep them all in sync. There have been two copies of each shell library and four CLI programs. To simplify maintenance, I have collapsed each of the library pairs into a single library and have reduced the number of CLI programs from four to two (one for the
2011 Dec 04
6
Shorewall 4.4.27 Beta 1
Beta 1 is now available for testing. One of the problems I''ve had with the Shorewall products is trying to keep them all in sync. There have been two copies of each shell library and four CLI programs. To simplify maintenance, I have collapsed each of the library pairs into a single library and have reduced the number of CLI programs from four to two (one for the
2012 Feb 20
5
Upgrade from Shorewall 4.4.27.3 to 4.5.0.1
I''d like to ask for clarification on the upgrade procedure using tarballs. In the past, with version 4.4, I have downloaded shorewall-4.4.x.y.tar.bz2 and shorewall6-4.4.x.y.tar.bz2, extracted each, and executed ''install.sh -s'' in each directory. Now there is a new package shorewall-core-4.5.x.y.tar.bz2. As I understand it, with version 4.5, this core package needs to be
2007 Aug 13
0
Re: shorewall-4.0.2 & openvz
a.shubnik@btis.by wrote: > Hello Tom! Aleksandr, In the future, please don''t send your Shorewall support requests directly to me. Please see http://www.shorewall.net/support.htm: > I try to start last version of shorewall-4.0.2 under openvz environment > in virtual server and get follow error messages: > > gate ~ # shorewall check > Checking... > >
2016 Dec 28
0
IPv4/IPv6 mismatches of doveadm: Fatal: connect(fd00:b::1:12345) failed: Connection refused
Hi ? I recently extendend my IPsec tunnel between two mail servers to deal with IPv4 addresses in addition to IPv6 ones. (No specific reason for that.) I ran into an issue worth reporting. This is Dovecot v2.2.27 (c0f36b0) at FreeBSD STABLE-11. Previously: dovecot.conf: plugin { mail_replica = tcp:remote.test } service doveadm { inet_listener { address = [::] } } |
2011 Jun 09
1
winbind and ipv6
Hi. FreeBSD 8.2-RELEASE Samba 3.4.9 security = ads Samba as domain member. Controllers on Win2008 R2. When using IPv4 all is fine. Today I added IPv6 on controllers, winbind stopped working when using IPv6. I.e. when password server = <NAME>, which resolves to AAAA, winbind says ===Cut=== # wbinfo -t checking the trust secret via RPC calls failed error code was
2019 Mar 29
2
guestfish Remote Images IPv6 Support
I have scoured the web and can't find anything on the topic: Is IPv6 supported for remote image targets? For example: guestfish --format=raw --ro -a rbd://[fd00::cefc:1]:6789/images/CentOS-7-x86_64-GenericCloud-1901 Does not work citing the following: libguestfs: trace: set_verbose true libguestfs: trace: set_verbose = 0 libguestfs: create: flags = 0, handle = 0x5560231bdfb0, program =
2010 Oct 16
1
Interaction of Shorewall and Shorewall6 with a Teredo relay?
I looked online for documentation about this, but couldn''t find it. Is anybody else running a Teredo relay, on a firewall that has both Shorewall and Shorewall6 installed? I''m running IPv6 at home (thanks to a Hurricane Electric tunnel). I''m having trouble with external Teredo clients being able to ping my home IPv6 addresses. All of these clients can reliably ping
2019 Mar 30
0
Re: guestfish Remote Images IPv6 Support
On Fri, Mar 29, 2019 at 06:17:17PM -0500, Jonathan Wright wrote: > I have scoured the web and can't find anything on the topic: Is IPv6 > supported for remote image targets? It definitely should work, although I don't know if anyone has tried using the address explicitly (rather than a hostname which resolves to an AAAA record). > For example: > > guestfish --format=raw
2019 Apr 01
0
Re: guestfish Remote Images IPv6 Support
On Mon, Apr 01, 2019 at 08:45:48AM -0500, Jonathan Wright wrote: > Unfortunately I do need to use the address explicitly as opposed to > hostnames because the source of the data fed here is Ceph's monmap > which returns the addresses explicitly. > > I've tried all the common ways to escape the : in the v6 address to > no avail.  I definitely agree that the problem looks
2019 Apr 01
2
Re: guestfish Remote Images IPv6 Support
Unfortunately I do need to use the address explicitly as opposed to hostnames because the source of the data fed here is Ceph's monmap which returns the addresses explicitly. I've tried all the common ways to escape the : in the v6 address to no avail.  I definitely agree that the problem looks to be it parsing the colons as if the port comes next and then everything after that is
2018 Jan 30
7
[Bug 1221] New: "fib" produces strange results with an IPv6 default route
https://bugzilla.netfilter.org/show_bug.cgi?id=1221 Bug ID: 1221 Summary: "fib" produces strange results with an IPv6 default route Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5