similar to: IPv4 routed virtual networks

On 12/17/2013 08:02 AM, Thiru Murugan wrote: > Hi , > > I would like to assign a Network Interface card to Physical Slot X in > the virtual machine, > > I have gone through the XML file definition[Now i have some idea on > how to position the Network Interface in Logical PCI Slot.] What is logical slot X vs. physical slot X? There are only two PCI addresses associated with

https://bugzilla.netfilter.org/show_bug.cgi?id=1327 Bug ID: 1327 Summary: Cannot use named set for matching IPv4 networks Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at

Hi, I need some hints on where to start on this one: I have an ISDN router - everything which is between 172.31.55.168 - 172.31.55.175 goes via gateway 172.31.55.169 the subnetmask is 255.255.255.248. The PC''s in the network get their IP address from a broadband router which will give dynamic ip''s and internet access to my small network. The broadband router services network

Hello all, I would like to connect two IPv4-only networks through global IPv6-only network with tinc. Could anyone tell me how to configure tinc.conf and the other config files? Thanks in advance, Ichiro Tinc: Discussion list about the tinc VPN daemon Archive: http://mail.nl.linux.org/lists/ Tinc site: http://tinc.nl.linux.org/

Hi , I would like to assign a Network Interface card to Physical Slot X in the virtual machine, I have gone through the XML file definition[Now i have some idea on how to position the Network Interface in Logical PCI Slot.] I am NOT interested in using a PCI Pass-through from the Host. currently running Fedora 19 with libvirt 1.2.0 I would like to create an network interface card on

http://bugzilla.mindrot.org/show_bug.cgi?id=401 ------- Additional Comments From yoshfuji at linux-ipv6.org 2003-01-06 12:20 ------- Created an attachment (id=194) --> (http://bugzilla.mindrot.org/attachment.cgi?id=194&action=view) patch to run openssh-3.5p1 on linux-2.2 & glibc-2.2(or later) This is modified patch for openssh-3.5p1. Patch is simplified. ------- You are

Hello, I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und IPv6 in order to be able to have Samba acting as IPv6 DNS Server. However since I have problem with sysprep domain join as soon as Samba advertises its own Domain Controller Hostname as IPv4 and IPv6 address, I would like to tell Samba to run on both protocols but only resolve to an IPv4 address. So in short: When I

On Thu, 19 Jul 2018 15:26:28 +0200 Thomas Glanzmann via samba <samba at lists.samba.org> wrote: > Hello, > I use Samba AD in Version 4.8.3 and would like to run it on IPv4 und > IPv6 in order to be able to have Samba acting as IPv6 DNS Server. > However since I have problem with sysprep domain join as soon as Samba > advertises its own Domain Controller Hostname as IPv4 and

Hello all, I just found a bug a nice bug that can be turned into a real feature on systems (usually Linux) that are built with --with-ipv4-default. If you enable IPv6 in kernel, and enable both listenaddress 0.0.0.0 and ::, sshd will error out 'address family not supported'. However, you can work around this error by starting sshd with 'sshd -4 -6'. As far as man page is

http://bugzilla.mindrot.org/show_bug.cgi?id=401 yoshfuji at linux-ipv6.org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|misc. ipv4-mapped address |ipv4 mapped address (ipv4 in |support fix |ipv6) and ipv6 support fix ------- Additional

I have two installations of dovecot 2.18, apart from the necessary changes to allow them to replicate amongst themselves the configs are identical. Both are running Ubuntu 14.04 and are kept up to date. One is running 64bit and the other 32 bit (for historical reasons). Both have ipv4 and ipv6 addresses. The 64 bit installation allows access on port 143 and 993 on both ipv4 and ipv6. The 32

https://bugzilla.netfilter.org/show_bug.cgi?id=1764 Bug ID: 1764 Summary: mapping IPv4 interval to IPv4 interval works for anonymous maps, but not for named maps Product: nftables Version: git (please specify your HEAD) Hardware: x86_64 OS: All Status: NEW Severity: enhancement

Hi folks, I want to restrict root access via ssh to certain (internal) hosts. That is what pam_access.so is for, I thought, so I configured: in /etc/security/access.conf I added (nothing in there before): + : root : 192.168.123.0/24 10.72.0.0/16 - : root : ALL in /etc/pam.d/ssh I added at the end: account required pam_access.so Then I restarted the ssh server. Basically, this kinda works.

Hi, On RHEL 5.5, I set up iptables rules for forwarding ports to some of my virtual machines. For example. iptables -t nat -A PREROUTING -i eth0 -p tcp -m tcp --dport 3380 -j DNAT --to-destination 192.168.123.2:3389 iptables -I FORWARD -d 192.168.123.2 -i eth0 -p tcp -m tcp --dport 3389 -m state --state NEW -j ACCEPT These worked fine, and I saved them with 'service iptables save'.

I found a tincd crash caused by having two "Port" statements in a host's file. I realize this is a bug in an old version of tinc that may be fixed but I spent the past few hours tracking it down so I'm sharing it in hopes others can make use of this info. I was "cleaning" up my Tinc VPN of a collection of OpenWrt routers and tincd started crashing with "Got fatal

If I execute these via command line, will they persist after a reboot? Or, should I be putting these into a file like /etc/sysctl.conf? --------------snip-------------- /sbin/sysctl -w net.ipv4.tcp_max_syn_backlog=2048 /sbin/sysctl -w net.ipv4.tcp_fin_timeout=30 /sbin/sysctl -w net.ipv4.tcp_keepalive_intvl=10 /sbin/sysctl -w net.ipv4.tcp_keepalive_probes=7 /sbin/sysctl -w

hello, i had two entry in the hosts file : ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain i wanted to remove the ::1 one as php mail() seems to have issue with it. I used: host{ ''localhost'': ip => ''::1'', alias =>

Hello Any idea what may cause this: # cat /proc/net/dev | wc -l 268 # ls -l /proc/sys/net/ipv4/conf/ | wc -l 120 all the interfaces have an ip address the kernel is 2.4.29. there are no error messages in the kernel log. -- Anton Glinkov network administrator _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl

Hello, How do I find out what is happening to my packets thru my ipsec tunnel. They just seem to disappear on the remote side. I have successfully got the pings thru when everything has an ipv6 address, but am not successful when trying to connect two ipv4 lans across an ipv6 ipsec tunnel. All fw chains both 4 and 6 are set to ACCEPT. NAT is turned off. eth0 eth1

Hi All, I tried to play a little bit with IPv6 to test our VoIP quality software with IPv6 RTP streams. I add "bindaddr=::" to the general section of the sip.conf and netstat shows that Asterisk is listing also on IPv6. My Asterisk server is behind a IPv4 NAT and was working absolutely perfect. But after my bindaddr change I got a problem with external calls. I spend some time to