search for: p3p1

Shorewall 4.5.15 3 Interface setup em1 p3p1 p4p4 ppp0 Hi, Since changing to NetworkManger on Fedora 18 I can no longer connect to the DSL Modem, which is connected to Interface em1. When the NetworkManger brings up the interfaces and ppp0, it no longer assigns an IP to em1. If I have ppp0 disabled and NetworkManger brings up the interf...

...<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: p3p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:13:3b:12:02:21 brd ff:ff:ff:ff:ff:ff 3: p4p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:e0:4c:44:01:95 brd ff:ff:ff:ff:ff:...

hi guys I have a qemu guest and openvswitch bridge and the guest fails to start: $ virsh start work8 error: Failed to start domain work8-vm-win2016 error: Cannot get interface MTU on 'ovsbr0': No such device LXC guest which uses the same source network starts just fine. I'm on Centos 7 with openvswitch-2.9.0-3.el7.x86_64 from centos-openstack-pike repo and

...536 qdisc noqueue state UNKNOWN > group default > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: p3p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 00:13:3b:12:02:21 brd ff:ff:ff:ff:ff:ff > 3: p4p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP group default qlen 1000 > link/ether 00:e0:4c:44:...

...page you reference above (e.g. "enp2s0"). Even my F20 system seems a bit up in the air - what had been called "wlan0" in F17 is now called "wlp3s0" (which seems like one of the new names), but an ExpressCard ethernet plugged into the system is still classified as "p3p1".

...OWN >> group default >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> inet 127.0.0.1/8 scope host lo >> valid_lft forever preferred_lft forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: p3p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group >> default qlen 1000 >> link/ether 00:13:3b:12:02:21 brd ff:ff:ff:ff:ff:ff >> 3: p4p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast >> state UP group default qlen 1000 >> lin...

...saw a lot of attempts in the logs, and the ipset created was filling up. I did some more research, and decided to use a few rich rules to block these attempts. I currently have these in place: #firewall-cmd --list-all public (active) ? target: default ? icmp-block-inversion: no ? interfaces: p3p1 ? sources: ? services: dhcpv6-client ftp http https imap imaps pop3 pop3s smtp-submission smtps ssh ? ports: 110/tcp 995/tcp 143/tcp 993/tcp 25/tcp 21/tcp ? protocols: ? masquerade: no ? forward-ports: ? source-ports: ? icmp-blocks: ? rich rules: ??????? rule family="ipv4" sour...

...global] >     server role = active directory domain controller >     netbios name = server_name >     realm = DOMAIN.LAN >     workgroup = DOMAIN > >     server services = -dns > >     idmap_ldb:use rfc2307 = yes > >     bind interfaces only = yes >     interfaces = p3p1 > Nothing wrong with the lines above > idmap config DOMAIN:range = 600-4000000 >     idmap config DOMAIN:backend = tdb >     idmap uid = 600-4000000 >     idmap gid = 600-4000000 > >     winbind gid = 600-4000000 >     winbind uid = 600-4000000 Well, if you are going to get...

...ey will be dropped by the network core as a martian source. If you enable logging of martian packets (via /proc/sys/net/ipv4/conf/*/log_martians), you will see an entry in your syslog similar to this: localhost kernel: [19202.736982] IPv4: martian source 192.168.19.150 from 192.168.19.255, on dev p3p1 As such, this is not a netfilter bug - it is simply the way Linux works. Closing. -- Configure bugmail: https://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

Hi, I have already tried to change for bindaddr=0.0.0.0 but it didn't worked. 2016-08-26 11:44 GMT-03:00, Frank Vanoni <mailinglist at linuxista.com>: > On Fri, 2016-08-26 at 10:12 -0300, Vitor Mazuco wrote: > >> bindaddr = all > > Try: > > bindaddr=0.0.0.0 > > > > > -- > _____________________________________________________________________

Hi everyone, I want to set ACL's on some directories for AD users with chown command, but it doesn't work. wbinfo -u is ok and return all users. i.e : DOMAIN\administrator DOMAIN\user ... if I try :      #chown -R "DOMAIN\user" /my_dir I obtain this :     chown: incorrect user : "DOMAIN\\user" chown systematically "adds" a backslash, but I don't

...;network> <name>macvtap_passthrough’</name> <forward mode=’passthrough> <interface dev=’vf0’ /> <interface dev=’vf1’ /> .. .. </forward> </network> <network> <name>’macvtap_bridge’</name> <forward mode=’bridge’> <interface dev=’p3p1’/> </forward> </network> Save it and run the following commands:  virsh net-define macvtap_passthrough.xml  virsh net-start macvtap_passthrough Make sure all of your virtual interfaces that you used in the xml file are up. for i in $(ifconfig –a | awk ‘/eth/ {print $1}’); do ifconf...

...m going to next try a CentOS 6.2 LiveUSB using the 32-bit LiveDVD instead of the 64-bit one, hopefully set up as identically as possible to the 64-bit one I've been using, and then see if it's a 32-bit versus 64-bit NIC driver issue or similar. Incidentally, the ethernet device gets a 'p3p1' device name instead of 'eth0.' I'm somewhat concerned by this, since I'm upgrading the laptop in question to CentOS 6.2 as part of this process, so I want to track down the problem so that if I need to install the 32-bit version instead of the 64-bit version I can. So, if an...

Hi, When I initially boot my system, it fails to bring up the network. Once booted, if I run "systemctl restart network.service", or even stop, wait a while, then start, it starts up fine and all is well. I'm running Fedora 19 (updated). I followed the instructions on this page to set up a bridged network: http://wiki.libvirt.org/page/Networking I note however that I did *not*

...smb.conf of AD server : --- [global] dns forwarder = IP_OF_ADSERVER netbios name = ADSERVER realm = EXAMPLE.DOMAIN.FR server role = active directory domain controller workgroup = EXAMPLE idmap_ldb:use rfc2307 = yes server services = -dns ntlm auth = yes bind interfaces only = yes interfaces = lo p3p1 log level = 3 log file = /var/log/samba/samba_ad.log max log size = 1000 [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [netlogon] path = /usr/local/samba/var/locks/sysvol/example.domain.fr/scripts read only = No ---

...t:50700000(size=2097152) *-network description: Ethernet interface product: I210 Gigabit Network Connection vendor: Intel Corporation physical id: 0 bus info: pci at 0000:0a:00.0 logical name: p3p1 version: 03 serial: 00:e0:4b:4a:9e:ed size: 1Gbit/s capacity: 1Gbit/s width: 32 bits clock: 33MHz capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-f...