search for: noqueu

...rameter (nloopbacks=<N>); if the driver is compiled statically into the kernel, then you may set the parameter using loopback.nloopbacks=<N> on the domain 0 kernel command line. without interface veth0 *[root@XEN01 scripts]# ip link* 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: peth0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:3...

...9;t want it to, I normally write a rule to match that logentry and put it in a file called my_rules in /etc/logcheck/ignore.d.server/ ... that worked perfectly fine. Until that rule: Logcheck keeps reporting me that: Security Events =-=-=-=-=-=-=-= Mar 16 15:45:48 uhweb64206 postfix/smtpd[21799]: NOQUEUE: reject_warning: RCPT from unknown[220.231.197.4]: 504 5.5.2 <220.231.197.4>: Helo command rejected: need fully-qualified hostname; from=<lory9 at syssrc.com> to=<diequeen at klappspaten.info> proto=ESMTP helo=<220.231.197.4> So I wrote this rule: ^\w{3} [ :0-9]{11} [._[...

Hello List, After demystifying the cause for my /sbin/ifup-local not being executed by network scripts for an Ethernet interface (don't let NetworkManager control it or ifup-local won't be executed)... ... I have a question with hopefully a simple answer: I placed an alias/description on my interface during testing and now I want to remove it. But when I try to remove it, I'm either

...systemd/system) LSM: AppArmor: enabled Libvirt version 5.0.0 qemu Version: 1:3.1+dfsg-8+deb10u7 I try to get the filtering bridge to work. This is the host, with the br0 that is connected to a trunked port ================================ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP...

someone recommended that i should give br0 the same hardware address as eno2. I did that, and restarted the vm, and it still does not work. Here is my current host interface config: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP...

...mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff promiscuity 1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 5: unt382@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff promiscuity 0 vlan protocol 802.1Q id 382 <REORDER_HDR> addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 15: macvtap3@enp3s0: <BROADCAST,MULTICAST,...

...e ''ip addr add dev gretun'' statements. But the above example is what *should* work on a Cisco, I think. It''s been a while. How do I troubleshoot this? This is all I''ve got so far: root@den1tun01:/home/root $ ip link 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP> mtu 8800 qdisc pfifo_fast qlen 1000 link/ether 00:19:b9:dd:ff:d9 brd ff:ff:ff:ff:ff:ff 3: eth0.2: <BROADCAST,MULTICAST,UP> mtu 8800 qdisc noqueue link/ether 00:19:b9:dd:ff:d9 brd ff:ff:f...

...;m either trying to do something _actually_ > not supported or I don't have the proper syntax to accomplish what I want. It doesn?t look like ?ip link? has the syntax to remove an alias, but it can be done via sysfs: # ip link show dev lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 # ip link set dev lo alias loopback # ip link show dev lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default link/loopback 00:00:00:00:00:00 brd...

...t any issue. But i did not see any traffic on the iptables forward chain due to which i am not able to control the traffic. Do i requie enable anything more to make the traffic pass through iptables forward chain. Please look into the configuration ip addr 1: lo: <LOOPBACK> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0: <NOARP> mtu 1480 qdisc noop link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0: <NOARP> mtu 1476 qdisc noop link/gre 0.0.0.0 brd 0.0.0.0 10: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000...

...sc pfifo_fast state UP mode DEFAULT group default qlen 1000 > link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff promiscuity 1 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 > 5: unt382 at enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 > link/ether 00:0d:b9:34:2a:fe brd ff:ff:ff:ff:ff:ff promiscuity 0 > vlan protocol 802.1Q id 382 <REORDER_HDR> addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 > 15: macvtap3 at enp3s0: <BR...

...X packets:1265 errors:0 dropped:0 overruns:0 frame:0 TX packets:278 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:80268 (78.3 Kb) TX bytes:58818 (57.4 Kb) ================= root]# ip addr show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:48:2b:98:96 brd ff:ff:ff:ff:ff:ff inet 207.200.44.18/28 brd 207.200.44.31 s...

I have CentOS 7 host. Two guests on bridge network setup by GUI and virt-manager. 1 CentOS 8 guest 1 Win 10 guest Both cannot access the host. They can other machines on the network. Guests can access the internet just not the host. I used virt-manager GUi to set up everything. Selected the eth0:macvtap and Bridge. I "desire" bridge network. If I select something else I get access to

...110/28 dev GDC1 ip route del 192.168.1.0/28 via 160.96.97.248 ip route add 192.168.1.0/28 via 192.168.2.110 Ok, the ip route del was necessary to get rid of the IPSec route and replace it with the gre tunnel. Linux box status: rx1000test:~# ip addre show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0a:dc:04:7d:dc brd ff:ff:ff:ff:ff:ff inet 192.168.1.97/28 brd 192.168.1.255 scope global eth1 4: eth2: <...

...I have a problem with a duplicate route entry, when using a pre-installed route and automatic take-over by the "heartbeat" daemon, which adds an address and the kernel adds an route automatically. Maybe anyone has an explanation... > ip addr 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue inet 127.0.0.1/8 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1514 qdisc pfifo_fast qlen 1000 inet 10.10.20.100/32 scope global eth0 > ip route 127.0.0.0 dev lo scope link 10.10.20.0/24 dev eth0 scope link default via 10.10.20.1 dev eth0 - -- Now I add a route for my ha...

I just realized that I hadn''t actually asked a question when I posted this before. Let me try again... I am trying to configure a Linux box with all possible VLANs (4094 of them), and a subnet on each VLAN. Creating the VLANs isn''t a problem. But, when I try to use "ip addr add ..." commands to assign an IP address to each VLAN interface, I get to do about 280 of

...l drive from the virtual server to the real server. It seems that in "VMWare Brigdged mode" Shorewall is preventing the Virtual Server from connecting to the Real Server. Required Info ------------------ shorewall version 2.2.1 ip addr show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:0d:61:1a:e2:25 brd ff:ff:ff:ff:ff:f...

...br0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply 10.32.2.51 is-at 00:30:48:34:44:6c dom0# tcpdump -ni vif3.0 arp who-has 10.32.2.51 tell 10.32.7.70 Does someone know why the dom0 br0 or vif eats the arp response? Thanks a lot, Moritz ip a l 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:30:48:34:13:dc brd ff:ff:ff:f...

...smtps/smtpd warning hash:/etc/postfix/virtual is unavailable open database /etc/postfix/virtual.db No such file. Note: I did go through creating the virtual.db and associated files but figured that it cant be correct as I want lmtp to handle it and it didn't work anyways, so I removed it. NOQUEUE reject RCPT from unknown[x.x.x.x] 451 4.3.0 <user at domain> Temporary lookup failure from=<user at domain> to=<user at domain> proto=ESMTP helo=<localhost.localdomain> -- obfuscated Tried every article I could find on the Internet to resolve this with out much luck. A...

I am trying to get wireless working on CentOS 7.3 with intel wireless 3165 ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether b8:ae:ed:77:b3:3a brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdis...

...2: peth0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 100 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 5: vif0.0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:19:d1:60:b2:6c brd ff:ff:ff:ff:ff:ff inet 10.19...