search for: p4p1

...1503-01.iso, selecting minimal install in Anaconda. > After the install, the wireless interface shows up unmanaged by NetworkManager. > > Before, I thought this could be due to using the minimal install media. > > ?[root at localhost ~]# nmcli d > DEVICE TYPE STATE CONNECTION > p4p1 ethernet connected p4p1 > lo loopback unmanaged -- > wlp1s0 wifi unmanaged -- > > After installing the same way in Centos7, the wireless card is automaticaly managed by NetworkManager as far as I > can tell. > > lspci shows the right kernel module so this is not a driver issue....

...alled from a CentOS-7-x86_64-DVD-1503-01.iso, selecting minimal install in Anaconda. After the install, the wireless interface shows up unmanaged by NetworkManager. Before, I thought this could be due to using the minimal install media. ?[root at localhost ~]# nmcli d DEVICE TYPE STATE CONNECTION p4p1 ethernet connected p4p1 lo loopback unmanaged -- wlp1s0 wifi unmanaged -- After installing the same way in Centos7, the wireless card is automaticaly managed by NetworkManager as far as I can tell. lspci shows the right kernel module so this is not a driver issue. I use the same wifi cards in all...

I have just installed 6.3 on a machine that was previously running 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo, wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a static IP as I intend to for this to be machine used on my LAN only. However, when I do /usr/sbin/setup -> Network Configuration the device is not listed. Can anyone tell me why this is happening and how I can fix it. Or if not how I can s...

...s, em1 gets an IP of 192.168.1.2. Then when I get NetworkManger to bring up ppp0, it removes the IP on em1. The DSL Modems internal IP is 192.168.1.254 In the shorewall interface file, I have: net ppp0 detect routefilter,tcpflags,blacklist modem em1 detect loc p3p1 detect tcpflags,dhcp dmz p4p1 detect tcpflags,dhcp In the shorewall masq file, I have: ppp0 10.10.1.0/24 ppp0 10.10.2.0/23 em1 10.10.1.0/24 em1 10.10.2.0/23 p4p1 10.10.1.0/24 Is there any config change that I can do in Shorewall, to be able to connect to the DSL Modem when ppp0 is up. Thanks, Patrick. --------...

...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:ff inet 192.168.25.25/24 brd 192.168.25.255 scope global p4p1 valid_lft forever preferred_lft forever inet6 2804:7f1:4080:fe45:2e0:4...

...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:ff > inet 192.168.25.25/24 brd 192.168.25.255 scope global p4p1 > valid_lft forever preferred_lft forever > inet6...

...eferred_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:ff >> inet 192.168.25.25/24 brd 192.168.25.255 scope global p4p1 >> valid_lft forever preferred_lft foreve...

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 > > > > > -- > _____________________________________________________________________

...1503-01.iso, selecting minimal install in Anaconda. > After the install, the wireless interface shows up unmanaged by NetworkManager. > > Before, I thought this could be due to using the minimal install media. > > ?[root at localhost ~]# nmcli d > DEVICE TYPE STATE CONNECTION > p4p1 ethernet connected p4p1 > lo loopback unmanaged -- > wlp1s0 wifi unmanaged -- > > After installing the same way in Centos7, the wireless card is automaticaly managed by NetworkManager as far as I > can tell. > > lspci shows the right kernel module so this is not a driver issue....

Fred Smith wrote: > On Tue, Jun 09, 2015 at 11:51:46AM +0200, johan.vermeulen7 at telenet.be > wrote: >> Hello All, >> >> on the latest installs I've done, on 2 different types of Latitude >> laptops, with 3 different wireless cars, of Centos7 and Mate desktop, >> it looks to me like NetworkManager is nog managing wireless. >> When clicking the nm icon

...MI version: 0.9 [ 12.996550] asus_wmi: SFUN value: 0x0 [ 12.997368] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input8 [ OK ] Reached target Sound Card. [ 13.000433] asus_wmi: Disabling ACPI video driver [ 13.001747] systemd-udevd[292]: renamed network interface eth0 to p4p1 systemd-fsck[432]: /dev/sda1: recovering journal systemd-fsck[432]: /dev/sda1: clean, 397/128016 files, 218778/512000 blocks systemd-fsck[438]: /dev/sdb2: recovering journal [ OK ] Started File System Check on /dev/disk/by-uuid/760e0...2-0788cf687e33. Mounting /boot... systemd-fsck[438]:...

...the installed server,? /root/anaconda-ks.cfg contains: # Firewall configuration firewall --enabled --port=111:tcp,111:upd,875:tcp,875:upd --service=ssh,nfs But after install "firewall-cmd --list-all" returns: public (active) ? target: default ? icmp-block-inversion: no ? interfaces: p4p1 ? sources: ? services: ssh dhcpv6-client ? ports: ? protocols: ? masquerade: no ? forward-ports: ? source-ports: ? icmp-blocks: ? rich rules: An idea about my mistake ? Thanks Patrick -- =================================================================== | Equipe M.O.S.T. |...

...t;like" the default names. [*not a show stopper but it should be fixed*] Instead, the the bridge definition, use "br0" for the connection name and the device name. For the "slave" definition (the real physical NIC), use the <physical_device_name> such as p33p1 or p4p1 or em0 or whatever. I then rebooted the host to make sure everything was clean and the netowrk came up fine on br0. Then, using virt-manager, I took an existing VM, deleted the virtual NIC, added a new virtual NIC using br0. After booting up the VM, you need to edit its network configuration...

.... [ 13.896821] (Note that use of the override may cause unknown side effects.) [ OK ] Found device /dev/hvc0. [ OK ] Found device OCZ-AGILITY4. Starting File System Check on /dev/disk/by-uuid/36ed...bcc39058642c... [ 14.015704] systemd-udevd[313]: renamed network interface eth0 to p4p1 systemd-fsck[453]: /dev/sdb2: recovering journal systemd-fsck[453]: /dev/sdb2: clean, 2376910/15122432 files, 46885876/60466432 blocks (check in 2 mounts) [ OK ] Started File System Check on /dev/disk/by-uuid/36edb...5-bcc39058642c. Mounting /home... [ 14.065454] asus_wmi: ASUS WMI gen...

...xxp 0000:04:08.0: Found a Wildcard: Wildcard TE420 (5th Gen) wct4xxp 0000:04:08.0: firmware: requesting dahdi-fw-oct6114-128.bin VPM450: echo cancellation for 128 channels wct4xxp 0000:04:08.0: VPM450: hardware DTMF disabled. wct4xxp 0000:04:08.0: VPM450: Present and operational servicing 4 span(s) p4p1: no IPv6 routers present dahdi_devices pci:0000:04:08.0: local span 1 is already assigned span 1 dahdi_devices pci:0000:04:08.0: local span 2 is already assigned span 2 dahdi_devices pci:0000:04:08.0: local span 3 is already assigned span 3 dahdi_devices pci:0000:04:08.0: local span 4 is already as...

...00.0] MSI interrupts enabled [ 1.810443] nouveau [ PFB][0000:01:00.0] RAM type: DDR2 [ 1.810444] nouveau [ PFB][0000:01:00.0] RAM size: 512 MiB [ 1.810446] nouveau [ PFB][0000:01:00.0] ZCOMP: 379904 tags [ 1.816929] systemd-udevd[324]: renamed network interface eth0 to p4p1 [ 1.844784] nouveau [ PTHERM][0000:01:00.0] FAN control: none / external [ 1.844795] nouveau [ PTHERM][0000:01:00.0] fan management: automatic [ 1.844797] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes [ 1.864815] nouveau [ CLK][0000:01:00.0] 20: core 400 MHz shader 400...