search for: 4ff

Displaying 8 results from an estimated 8 matches for "4ff".

Did you mean: 4f
2005 Mar 06
1
3 Interface problem
...fe80::260:97ff:fec9:c5e7/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:50:04:77:a3:72 brd ff:ff:ff:ff:ff:ff inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1 inet6 fe80::250:4ff:fe77:a372/64 scope link valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:02:a5:d0:92:7c brd ff:ff:ff:ff:ff:ff inet 192.168.2.254/24 brd 192.168.2.255 scope global eth2 inet6 fe80::202:a5ff:fed0:927c/...
2024 Mar 13
0
ProxyJump does not accept IPv6 for the intermediate host?
...> brackets. > ?This is a shortcut to specify a > ?.Cm ProxyJump > ?configuration directive. This would be helpful! It should probably be noted that this syntax is only valid in the -J/ ProxyJump context. Because: $ ssh root@[2a01:4f8:1c1e:528d::1] ssh: Could not resolve hostname [2a01:4ff:1f0:e68b::1]:: Name or service not known does not work. Thank you all for the prompt help!
2005 Jan 07
8
Problem with bridging/routing on three interfaces and DNAT
...link/ether 00:04:76:f7:c5:fc brd ff:ff:ff:ff:ff:ff inet6 fe80::204:76ff:fef7:c5fc/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:50:04:38:74:76 brd ff:ff:ff:ff:ff:ff inet6 fe80::250:4ff:fe38:7476/64 scope link valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:50:04:49:9a:37 brd ff:ff:ff:ff:ff:ff inet 212.60.254.66/29 brd 212.60.254.71 scope global eth2 inet6 fe80::250:4ff:fe49:9a37/6...
2007 Apr 30
0
[LLVMdev] Boostrap Failure -- Expected Differences?
...4f4 <__FUNCTION__.21879+0x14> > + 493: 72 79 jb 50e <__FUNCTION__.21945+0xe> > 495: 69 6e 67 5f 73 74 72 imul $0x7274735f,0x67(%esi),%ebp > - 49c: 75 63 jne 501 <__FUNCTION__.22032+0x1> > - 49e: 74 5f je 4ff <__FUNCTION__.21966+0x1f> > + 49c: 75 63 jne 501 <__FUNCTION__.21945+0x1> > + 49e: 74 5f je 4ff <__FUNCTION__.21879+0x1f> > 4a0: 70 00 jo 4a2 <.str4> > > 000004a2 <.str4>: > @@ -11799,61 +1...
2007 Apr 27
2
[LLVMdev] Boostrap Failure -- Expected Differences?
The saga continues. I've been tracking the interface changes and merging them with the refactoring work I'm doing. I got as far as building stage3 of llvm-gcc but the object files from stage2 and stage3 differ: warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs (Are the above two ok?) The list below is clearly bad. I think it's every object file in the
2019 May 03
3
Aw: Re: very high traffic without any load
2019 May 02
4
Aw: Re: very high traffic without any load
2019 Nov 05
5
Failed to find cifs/fs-share@dom.corp (kvno 109) in keytab
Ok, you did to much as far i can tell. You want to see this: i'll show my output, then i is better to see what i mean. this is where you start with. klist -ke |sort ( default member ) ---- -------------------------------------------------------------------------- 3 host/HOSTNAME1 at REALM.DOMAIN.TLD (aes128-cts-hmac-sha1-96) 3 host/HOSTNAME1 at REALM.DOMAIN.TLD