search for: 1fff

...01 ms 6.870 ms 3 ok3ca81crs.ipv6.att.net (2001:1890:ff:ffff:12:123:6:98) 8.305 ms 8.254 ms 8.258 ms 4 sffca21crs.ipv6.att.net (2001:1890:ff:ffff:12:122:110:65) 14.199 ms 14.164 ms 14.153 ms 5 sffca401igs.ipv6.att.net (2001:1890:ff:ffff:12:122:114:5) 9.861 ms 10.163 ms * 6 2001:1890:1fff:41e:192:205:32:222 (2001:1890:1fff:41e:192:205:32:222) 9.789 ms 8.078 ms 7.365 ms 7 linode-ic-342731-sjo-b21.c.telia.net (2001:2000:3080:1ac4::2) 6.788 ms 6.327 ms 6.262 ms 8 2600:3c01:3333:4::2 (2600:3c01:3333:4::2) 7.294 ms 7.728 ms 7.705 ms 9 * * * >From Linode to AT&T: [...

On 4/28/2020 3:17 PM, Chris Adams wrote: > - gateway sends a router solicitation and gets a router advertisement > with "stateful config" set, which tells gateway to do DHCPv6 (but > default route comes from RA) I'm not seeing any outbound IPv6 traffic from my CentOS 7 box on the WAN interface. I do see RA's emitting from the LAN interface, from radvd. Is there

Hello, while checking new mtu9k-setup, I discovered that ping has some odd behaviour. If I use payloadsize > 4067, every 2nd icmp-echo-request seems to be malformed: ping -s 4068 -D 10.5.49.65 1st: 12:21:09.048447 IP 10.5.49.126 > 10.5.49.65: ICMP echo request, id 46597, seq 0, length 4076 0x0000: 4500 1000 0f2d 4000 4001 a507 0a05 317e 2nd: 12:21:10.052891 IP 10.5.49.126 >

...name="ip" unique="1" required="1"> > <longdesc lang="en"> > The IPv4 (dotted quad notation) or IPv6 address (colon hexadecimal > notation) > example IPv4 "192.168.1.1". > example IPv6 "2001:db8:DC28:0:0:FC57:D4C8:1FFF". > </longdesc> > ... > > > If it's not working I suspect the ganesha-ha.sh script may not handle > IPv6 addrs from the ganesha-ha.conf correctly. > > Please file a bug at > https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS component: > com...

Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance.

...t address are detected as in all the ranges? Similar test indicates the client ip address is in 7fff::0-ffff::0, 8fff::0-ffff::0, 9fff::0-ffff::0, afff::0-ffff::0, bfff::0-ffff::0, cfff::0-ffff::0, dfff::0-ffff::0, efff::0-ffff::0 7fff::0-ffff::0, 7eff::0-ffff::0, and is out of: 0fff::0-ffff::0, 1fff::0-ffff::0, 2fff::0-ffff::0, 3fff::0-ffff::0, 4fff::0-ffff::0, 5fff::0-ffff::0, 6fff::0-ffff::0 7dff::0-ffff::0, 7cff::0-ffff::0, 7bff::0-ffff::0, 7aff::0-ffff::0, 79ff::0-ffff::0, 78ff::0-ffff::0, 77ff::0-ffff::0, 76ff::0-ffff::0, 75ff::0-ffff::0, 74ff::0-ffff::0, 73ff::0-ffff::0, 72ff::0-ffff::0...

...packets:112 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:8904 (8.6 KiB) TX bytes:438 (438.0 B) tap6.0 Link encap:Ethernet HWaddr a6:0f:1f:2b:b5:d8 inet6 addr: fe80::a40f:1fff:fe2b:b5d8/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:472 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:36274 (35.4 KiB) TX bytes:368...

...f has been reserved pnp: 00:0c: ioport range 0xfe00-0xfe7f has been reserved pnp: 00:0c: ioport range 0xfe80-0xfeff has been reserved pnp: 00:0c: ioport range 0xcb0-0xcbf has been reserved PCI: Bridge: 0000:00:01.0 IO window: disabled. MEM window: e9300000-e95fffff PREFETCH window: e0000000-e81fffff PCI: Bridge: 0000:00:1c.0 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:1c.4 IO window: disabled. MEM window: disabled. PREFETCH window: disabled. PCI: Bridge: 0000:00:1c.5 IO window: disabled. MEM window: e8200000-e84fffff PREFETCH w...

Hi all, On dual core processor machine, I installed ubuntu-8.04 in which I installed xen-3.2. In ubuntu: # cat /proc/cpuinfo --> Shows two processors information. But in Xen on the same machine: # cat /proc/cpuinfo --> Shows only one processor information. Can anyone please explain what could be the reason behind this? Thanks Saravana

Hi, --- background ---------------------------------------------------- * what the makedumpfile is: To shorten the size of the dumpfile and the time of creating the dumpfile, makedumpfile copies only the necessary pages for analysis to the dumpfile from /proc/vmcore. You can specify the kind of unnecessary pages with dump_level. If you want to shorten the size further, enable the

...> 05e0-05ff : pnp 00:06 > 05e0-05ff : iTCO_wdt > 0ca0-0ca1 : pnp 00:0b > 0ca2-0ca2 : pnp 00:0c > 0ca3-0ca3 : pnp 00:0c > 0ca4-0ca9 : pnp 00:0b > 0caa-0cab : pnp 00:0b > 0cac-0ccb : pnp 00:0b > 0cf8-0cff : PCI conf1 > 0d00-ffff : PCI Bus 0000:00 > 1000-1fff : PCI Bus 0000:01 > 1000-10ff : 0000:01:00.0 > 1000-10ff : megasas: LSI > 2000-201f : 0000:00:1f.3 > 2000-201f : i801_smbus > 2020-203f : 0000:00:1d.2 > 2020-203f : uhci_hcd > 2040-205f : 0000:00:1d.1 > 2040-205f : uhci_hcd > 2060-207f : 0000:00:1d.0...