Private IP shifting to wrong interface on crs start
hi,
We have a 2 node RAC (10.2.0.3) on a solaris 46 bit system.
There was a regular system maintenance activity and post that we started the services. The services came up on one RAC node but not on the other. The CSS daemon is not starting and we are getting heartbeat failed errors in logs.
We have noticed that the interface bge2 has been assigned for private IP. (confirmed from oifcfg command). But as soon as we start crs on the faulty node, it starts the private IP on bge3 interface rather than bge2. This way the nodes are not able to ping the respective private IPs of other nodes. node1 cannot ping private IP of node2 and vice-versa.
Can anyone help ?
dumbdba wrote:
Hi,
The interfaces name on all the nodes is exactly the same.
We have three interfaces on each node viz. bge1, bge2, bge3. bge2 interface caters to the private IP addresses. One node starts on bge2, but when we try and start the other node it brings up the private IP to bge3 interface.check & modify /etc/hostname.INTERFACE
modify /etc/hostname.bge2 and /etc/hostname.bge3
http://docs.sun.com/app/docs/doc/816-4554/ipconfig-118?a=view
Another idea->
Changing the IP Address:
The following startup files need to be modified to change a host's IP address.
/etc/inet/hosts: Change the IP address, file format, IP<tab>hostname.
/etc/inet/netmasks: Add a new netmask, file format, network<tab>netmask.
/etc/defaultrouter: Specify the new gateway for this subnet, file format, ipaddress.
http://www.sun.com/bigadmin/content/submitted/troubleshoot_network.jsp
Similar Messages
-
Wlc monitor client detail show wrong interface name
Hi,
Do anyone know why I see the wrong interface name when looking at the client details?
In the shown example the interface name should have been id017_publikunm not id161_admin
The vlan nunmer 2317 and IP address 10.17.237.x is correct for id017_publikum.
I hope some one out there can help.
Aksel,I know its an old post but I encountered the same problem recently. What I did was I went to the same client properties and clicked on the remove button. It removed the association and when I filtered for the same client mac address I could see it has connected to the correct interface. So it was getting the correct IP Address also.............problem solved :)
-
Where to Look for the Service Interface in the Start Step?
hi @,
I have defined a Service interface in the start step, now I want to use the same in my Web Dynpro Application to pass data and start the BPM . Where can I look at the interface generated and BPM deployed I ddn't use any WSDL but created the same using the SI tool help in BPM.
DO I have to do any other setting and or publishing the same in Registry etc.
REgards,
AmitHi There,
>Where can I look at the interface generated and BPM deployed I ddn't use any WSDL but created the same using the SI tool help in BPM.
>
>DO I have to do any other setting and or publishing the same in Registry etc.
everytime i looked up the location of an deployed WSDL i used the "Single Service Administration" in the NWA. In that tool you can search for the name of the WSDL-Interface which you connected to the startevent of your bpm-process. In a option downside the Single Service Administration you can open the WSDL which opo ups in a new browser. Copy that URL from the opened window and cut somthing like &=ws_policy at the end of the URL.
You can start a Process with this URL if you send a propper SOAP-Message to it. You don't need to publish the Service in the Service Registry to use it.
Hope this Helps
With kind regards
Markus -
Non-global zone sending TCP SYN-ACK packet over wrong interface.
After spending many hours looking at ipmon/ethereal logs, I believe I've found
a explanation (a bug?) for the following strange behaviour (Solaris 10u1):
I've got a non-global zone with Apache2 with dedicated IP and bound to interface e1000g2 of a Sun X4200 box. The global zone has a different dedicated IP bound to a different interface e1000g0.
When I point a browser at the web site, the HTML page often comes up immediately, but sometimes it will hang and only load when I press the reload browser button one or multiple times. This is reproducible with different browsers from different networks with or without DNS resolution. It's reproducible with other non-local zones configured alike and running different TCP based services (namely SSH or non-Apache HTTP).
This is what happens in a failing case (Ethereal client dump "dump_failed.txt" and IPF log "att1.txt" lines 1-3 pp): the incoming TCP SYN comes over interface e1000g2 (correct) and is passed by IPF. However, the non-global zone sends the TCP SYN-ACK package back over interface e1000g0, which is wrong and causes IPF to fail to build a correct state entry. Then, afterwards, the response packets from the webserver will be filtered by IPF, since it has no state entry.
In the success case (Ethereal client dump "dump_success.txt" and IPF log "att1.txt" lines 19-21 pp), the incoming TCP SYN is answered correctly by a TCP SYN-ACK both over interface e1000g2. IPF can build a state entry and all subsequent packets from the webserver reach the client.
=====
The non-global zone has this setup:
zonecfg:ws1> info
...snip...
net:
address: 62.146.25.34
physical: e1000g2
zonecfg:ws1>
=====
The relevant (as of the IPF log) IPF rules are:
rule 1: block out log all
rule 16: pass in log quick proto tcp from any to 62.146.25.34 port = 80 keep state
=====
If I didn't miss an important point, I suspect this to be a bug in Zones and/or IPF.
Any hints?
Thx,
Tobias
"att1.txt":
LINE PACKET_DT PACKET_FS PACKET_IFC RULE_NUMBER RULE_ACTION SOURCE_IP SOURCE_PORT DEST_IP DEST_PORT PROTOCOL TCP_FLAGS
1 08.05.2006 21:24:09 786741 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp S
2 08.05.2006 21:24:09 786863 e1000g0 16 p 62.146.25.34 80 84.56.16.159 60693 tcp AS
3 08.05.2006 21:24:09 808218 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp A
4 08.05.2006 21:24:09 837170 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AP
5 08.05.2006 21:24:09 837189 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
6 08.05.2006 21:24:09 837479 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AP
7 08.05.2006 21:24:12 823801 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AP
8 08.05.2006 21:24:12 823832 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
9 08.05.2006 21:24:13 210039 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AP
10 08.05.2006 21:24:18 839318 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AP
11 08.05.2006 21:24:18 839351 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
12 08.05.2006 21:24:19 970040 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AP
13 08.05.2006 21:24:24 840073 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AF
14 08.05.2006 21:24:30 870503 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AP
15 08.05.2006 21:24:30 870538 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
16 08.05.2006 21:24:33 480059 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
17 08.05.2006 21:24:45 347464 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AF
18 08.05.2006 21:24:45 347498 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
19 08.05.2006 21:24:47 857068 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp S
20 08.05.2006 21:24:47 857118 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp AS
21 08.05.2006 21:24:47 878257 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp A
22 08.05.2006 21:24:47 907630 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp AP
23 08.05.2006 21:24:47 907644 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp A
24 08.05.2006 21:24:47 907892 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp AP
25 08.05.2006 21:24:47 976361 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp AP
26 08.05.2006 21:24:47 976375 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp A
27 08.05.2006 21:24:47 976487 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp AP
28 08.05.2006 21:24:48 127599 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp A
29 08.05.2006 21:24:54 932569 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AFP
30 08.05.2006 21:24:54 932595 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
31 08.05.2006 21:25:00 490052 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
32 08.05.2006 21:25:02 980057 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp AF
33 08.05.2006 21:25:03 1890 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp A
34 08.05.2006 21:25:09 907916 e1000g2 16 p 84.56.16.159 60694 62.146.25.34 80 tcp AF
35 08.05.2006 21:25:09 907949 e1000g2 16 p 62.146.25.34 80 84.56.16.159 60694 tcp A
36 08.05.2006 21:25:42 948502 e1000g2 16 p 84.56.16.159 60693 62.146.25.34 80 tcp AFP
37 08.05.2006 21:25:42 948535 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp A
38 08.05.2006 21:25:54 500051 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
39 08.05.2006 21:26:54 510046 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
40 08.05.2006 21:27:54 520041 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
41 08.05.2006 21:28:54 530040 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
42 08.05.2006 21:29:54 540039 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
43 08.05.2006 21:30:54 550039 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
44 08.05.2006 21:31:54 560041 e1000g2 1 b 62.146.25.34 80 84.56.16.159 60693 tcp AFP
"dump_failed.txt":
No. Time Source Destination Protocol Info
1 0.000000 192.168.1.101 62.146.25.34 TCP 1079 > http [SYN] Seq=0 Len=0 MSS=1460
Frame 1 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 48
Identification: 0x0269 (617)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xde9d [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 0, Len: 0
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
Window size: 65535
Checksum: 0x5c3c [correct]
Options: (8 bytes)
No. Time Source Destination Protocol Info
2 0.022698 62.146.25.34 192.168.1.101 TCP http > 1079 [SYN, ACK] Seq=0 Ack=1 Win=49368 Len=0 MSS=1452
Frame 2 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: D-Link_9b:09:44 (00:0d:88:9b:09:44), Dst: FujitsuS_81:79:ea (00:30:05:81:79:ea)
Internet Protocol, Src: 62.146.25.34 (62.146.25.34), Dst: 192.168.1.101 (192.168.1.101)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 48
Identification: 0x002f (47)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 50
Protocol: TCP (0x06)
Header checksum: 0x2ed8 [correct]
Source: 62.146.25.34 (62.146.25.34)
Destination: 192.168.1.101 (192.168.1.101)
Transmission Control Protocol, Src Port: http (80), Dst Port: 1079 (1079), Seq: 0, Ack: 1, Len: 0
Source port: http (80)
Destination port: 1079 (1079)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
Window size: 49368
Checksum: 0xd017 [correct]
Options: (8 bytes)
No. Time Source Destination Protocol Info
3 0.022749 192.168.1.101 62.146.25.34 TCP 1079 > http [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0
Frame 3 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 40
Identification: 0x026a (618)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdea4 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 1, Ack: 1, Len: 0
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 65535
Checksum: 0x19dc [incorrect, should be 0xbdac]
No. Time Source Destination Protocol Info
4 0.022919 192.168.1.101 62.146.25.34 HTTP GET / HTTP/1.1
Frame 4 (476 bytes on wire, 476 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 462
Identification: 0x026b (619)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdcfd [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 1, Ack: 1, Len: 422
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 423 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 65535
Checksum: 0x1b82 [incorrect, should be 0xcda5]
Hypertext Transfer Protocol
No. Time Source Destination Protocol Info
5 3.013084 192.168.1.101 62.146.25.34 HTTP [TCP Retransmission] GET / HTTP/1.1
Frame 5 (476 bytes on wire, 476 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 462
Identification: 0x0276 (630)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdcf2 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 1, Ack: 1, Len: 422
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 423 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 65535
Checksum: 0x1b82 [incorrect, should be 0xcda5]
SEQ/ACK analysis
Hypertext Transfer Protocol
No. Time Source Destination Protocol Info
6 9.029003 192.168.1.101 62.146.25.34 HTTP [TCP Retransmission] GET / HTTP/1.1
Frame 6 (476 bytes on wire, 476 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 462
Identification: 0x027f (639)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdce9 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 1, Ack: 1, Len: 422
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 423 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 65535
Checksum: 0x1b82 [incorrect, should be 0xcda5]
SEQ/ACK analysis
Hypertext Transfer Protocol
No. Time Source Destination Protocol Info
7 21.060827 192.168.1.101 62.146.25.34 HTTP [TCP Retransmission] GET / HTTP/1.1
Frame 7 (476 bytes on wire, 476 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 462
Identification: 0x0284 (644)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdce4 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 1, Ack: 1, Len: 422
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 423 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 65535
Checksum: 0x1b82 [incorrect, should be 0xcda5]
SEQ/ACK analysis
Hypertext Transfer Protocol
No. Time Source Destination Protocol Info
8 35.561984 192.168.1.101 62.146.25.34 TCP 1079 > http [FIN, ACK] Seq=423 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0
Frame 8 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 40
Identification: 0x029a (666)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xde74 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1079 (1079), Dst Port: http (80), Seq: 423, Ack: 1, Len: 0
Source port: 1079 (1079)
Destination port: http (80)
Sequence number: 423 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0011 (FIN, ACK)
Window size: 65535
Checksum: 0x19dc [incorrect, should be 0xbc05]
"dump_success.txt":
No. Time Source Destination Protocol Info
1 0.000000 192.168.1.101 62.146.25.34 TCP 1083 > http [SYN] Seq=0 Len=0 MSS=1460
Frame 1 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 48
Identification: 0x02a3 (675)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xde63 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1083 (1083), Dst Port: http (80), Seq: 0, Len: 0
Source port: 1083 (1083)
Destination port: http (80)
Sequence number: 0 (relative sequence number)
Header length: 28 bytes
Flags: 0x0002 (SYN)
Window size: 65535
Checksum: 0x70ca [correct]
Options: (8 bytes)
No. Time Source Destination Protocol Info
2 0.020553 62.146.25.34 192.168.1.101 TCP http > 1083 [SYN, ACK] Seq=0 Ack=1 Win=49368 Len=0 MSS=1452
Frame 2 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: D-Link_9b:09:44 (00:0d:88:9b:09:44), Dst: FujitsuS_81:79:ea (00:30:05:81:79:ea)
Internet Protocol, Src: 62.146.25.34 (62.146.25.34), Dst: 192.168.1.101 (192.168.1.101)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 48
Identification: 0x006b (107)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 50
Protocol: TCP (0x06)
Header checksum: 0x2e9c [correct]
Source: 62.146.25.34 (62.146.25.34)
Destination: 192.168.1.101 (192.168.1.101)
Transmission Control Protocol, Src Port: http (80), Dst Port: 1083 (1083), Seq: 0, Ack: 1, Len: 0
Source port: http (80)
Destination port: 1083 (1083)
Sequence number: 0 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 28 bytes
Flags: 0x0012 (SYN, ACK)
Window size: 49368
Checksum: 0xb530 [correct]
Options: (8 bytes)
No. Time Source Destination Protocol Info
3 0.020599 192.168.1.101 62.146.25.34 TCP 1083 > http [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0
Frame 3 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 40
Identification: 0x02a4 (676)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xde6a [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1083 (1083), Dst Port: http (80), Seq: 1, Ack: 1, Len: 0
Source port: 1083 (1083)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 65535
Checksum: 0x19dc [incorrect, should be 0xa2c5]
No. Time Source Destination Protocol Info
4 0.020746 192.168.1.101 62.146.25.34 HTTP GET / HTTP/1.1
Frame 4 (476 bytes on wire, 476 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 462
Identification: 0x02a5 (677)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdcc3 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1083 (1083), Dst Port: http (80), Seq: 1, Ack: 1, Len: 422
Source port: 1083 (1083)
Destination port: http (80)
Sequence number: 1 (relative sequence number)
Next sequence number: 423 (relative sequence number)
Acknowledgement number: 1 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 65535
Checksum: 0x1b82 [incorrect, should be 0xb2be]
Hypertext Transfer Protocol
No. Time Source Destination Protocol Info
5 0.071290 62.146.25.34 192.168.1.101 TCP http > 1083 [ACK] Seq=1 Ack=423 Win=49368 Len=0
Frame 5 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: D-Link_9b:09:44 (00:0d:88:9b:09:44), Dst: FujitsuS_81:79:ea (00:30:05:81:79:ea)
Internet Protocol, Src: 62.146.25.34 (62.146.25.34), Dst: 192.168.1.101 (192.168.1.101)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 40
Identification: 0x006c (108)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 50
Protocol: TCP (0x06)
Header checksum: 0x2ea3 [correct]
Source: 62.146.25.34 (62.146.25.34)
Destination: 192.168.1.101 (192.168.1.101)
Transmission Control Protocol, Src Port: http (80), Dst Port: 1083 (1083), Seq: 1, Ack: 423, Len: 0
Source port: http (80)
Destination port: 1083 (1083)
Sequence number: 1 (relative sequence number)
Acknowledgement number: 423 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 49368
Checksum: 0xe046 [correct]
No. Time Source Destination Protocol Info
6 0.075838 62.146.25.34 192.168.1.101 HTTP HTTP/1.1 200 OK (text/html)
Frame 6 (413 bytes on wire, 413 bytes captured)
Ethernet II, Src: D-Link_9b:09:44 (00:0d:88:9b:09:44), Dst: FujitsuS_81:79:ea (00:30:05:81:79:ea)
Internet Protocol, Src: 62.146.25.34 (62.146.25.34), Dst: 192.168.1.101 (192.168.1.101)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 399
Identification: 0x006d (109)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 50
Protocol: TCP (0x06)
Header checksum: 0x2d3b [correct]
Source: 62.146.25.34 (62.146.25.34)
Destination: 192.168.1.101 (192.168.1.101)
Transmission Control Protocol, Src Port: http (80), Dst Port: 1083 (1083), Seq: 1, Ack: 423, Len: 359
Source port: http (80)
Destination port: 1083 (1083)
Sequence number: 1 (relative sequence number)
Next sequence number: 360 (relative sequence number)
Acknowledgement number: 423 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 49368
Checksum: 0x29b8 [correct]
Hypertext Transfer Protocol
Line-based text data: text/html
No. Time Source Destination Protocol Info
7 0.095473 192.168.1.101 62.146.25.34 HTTP GET /favicon.ico HTTP/1.1
Frame 7 (407 bytes on wire, 407 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 393
Identification: 0x02aa (682)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xdd03 [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1083 (1083), Dst Port: http (80), Seq: 423, Ack: 360, Len: 353
Source port: 1083 (1083)
Destination port: http (80)
Sequence number: 423 (relative sequence number)
Next sequence number: 776 (relative sequence number)
Acknowledgement number: 360 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 65176
Checksum: 0x1b3d [incorrect, should be 0x1e0c]
Hypertext Transfer Protocol
No. Time Source Destination Protocol Info
8 0.139786 62.146.25.34 192.168.1.101 TCP http > 1083 [ACK] Seq=360 Ack=776 Win=49368 Len=0
Frame 8 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: D-Link_9b:09:44 (00:0d:88:9b:09:44), Dst: FujitsuS_81:79:ea (00:30:05:81:79:ea)
Internet Protocol, Src: 62.146.25.34 (62.146.25.34), Dst: 192.168.1.101 (192.168.1.101)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 40
Identification: 0x006e (110)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 50
Protocol: TCP (0x06)
Header checksum: 0x2ea1 [correct]
Source: 62.146.25.34 (62.146.25.34)
Destination: 192.168.1.101 (192.168.1.101)
Transmission Control Protocol, Src Port: http (80), Dst Port: 1083 (1083), Seq: 360, Ack: 776, Len: 0
Source port: http (80)
Destination port: 1083 (1083)
Sequence number: 360 (relative sequence number)
Acknowledgement number: 776 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 49368
Checksum: 0xdd7e [correct]
No. Time Source Destination Protocol Info
9 0.144850 62.146.25.34 192.168.1.101 HTTP HTTP/1.1 404 Not Found (text/html)
Frame 9 (464 bytes on wire, 464 bytes captured)
Ethernet II, Src: D-Link_9b:09:44 (00:0d:88:9b:09:44), Dst: FujitsuS_81:79:ea (00:30:05:81:79:ea)
Internet Protocol, Src: 62.146.25.34 (62.146.25.34), Dst: 192.168.1.101 (192.168.1.101)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 450
Identification: 0x006f (111)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 50
Protocol: TCP (0x06)
Header checksum: 0x2d06 [correct]
Source: 62.146.25.34 (62.146.25.34)
Destination: 192.168.1.101 (192.168.1.101)
Transmission Control Protocol, Src Port: http (80), Dst Port: 1083 (1083), Seq: 360, Ack: 776, Len: 410
Source port: http (80)
Destination port: 1083 (1083)
Sequence number: 360 (relative sequence number)
Next sequence number: 770 (relative sequence number)
Acknowledgement number: 776 (relative ack number)
Header length: 20 bytes
Flags: 0x0018 (PSH, ACK)
Window size: 49368
Checksum: 0x7a71 [correct]
Hypertext Transfer Protocol
Line-based text data: text/html
No. Time Source Destination Protocol Info
10 0.269307 192.168.1.101 62.146.25.34 TCP 1083 > http [ACK] Seq=776 Ack=770 Win=64766 [TCP CHECKSUM INCORRECT] Len=0
Frame 10 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: FujitsuS_81:79:ea (00:30:05:81:79:ea), Dst: D-Link_9b:09:44 (00:0d:88:9b:09:44)
Internet Protocol, Src: 192.168.1.101 (192.168.1.101), Dst: 62.146.25.34 (62.146.25.34)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
Total Length: 40
Identification: 0x02af (687)
Flags: 0x04 (Don't Fragment)
Fragment offset: 0
Time to live: 128
Protocol: TCP (0x06)
Header checksum: 0xde5f [correct]
Source: 192.168.1.101 (192.168.1.101)
Destination: 62.146.25.34 (62.146.25.34)
Transmission Control Protocol, Src Port: 1083 (1083), Dst Port: http (80), Seq: 776, Ack: 770, Len: 0
Source port: 1083 (1083)
Destination port: http (80)
Sequence number: 776 (relative sequence number)
Acknowledgement number: 770 (relative ack number)
Header length: 20 bytes
Flags: 0x0010 (ACK)
Window size: 64766
Checksum: 0x19dc [incorrect, should be 0x9fbe]lev wrote:This performance regression renders openvpn with a tun adapter unusable if client and server use kernel 3.14 .
Thus I created a bug report: https://bugs.archlinux.org/task/40089
i actually noticed it to be an "either-or" type of thing; my Windows clients were seeing the same thing coming off a 3.14 openvpn server.
yeah, weird issue. like i noticed spurts of even-powers-of-2 sized packets
Client connecting to 10.10.10.6, TCP port 5001
TCP window size: 416 KByte
[ 3] local 10.10.10.1 port 40643 connected with 10.10.10.6 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 2.0 sec 512 KBytes 2.10 Mbits/sec
[ 3] 2.0- 4.0 sec 0.00 Bytes 0.00 bits/sec
[ 3] 4.0- 6.0 sec 0.00 Bytes 0.00 bits/sec
[ 3] 6.0- 8.0 sec 0.00 Bytes 0.00 bits/sec
[ 3] 8.0-10.0 sec 128 KBytes 524 Kbits/sec
[ 3] 10.0-12.0 sec 128 KBytes 524 Kbits/sec
[ 3] 12.0-14.0 sec 512 KBytes 2.10 Mbits/sec
[ 3] 14.0-16.0 sec 128 KBytes 524 Kbits/sec
[ 3] 16.0-18.0 sec 512 KBytes 2.10 Mbits/sec
[ 3] 18.0-20.0 sec 128 KBytes 524 Kbits/sec
[ 3] 20.0-22.0 sec 384 KBytes 1.57 Mbits/sec
[ 3] 22.0-24.0 sec 256 KBytes 1.05 Mbits/sec
[ 3] 24.0-26.0 sec 512 KBytes 2.10 Mbits/sec
[ 3] 26.0-28.0 sec 384 KBytes 1.57 Mbits/sec
[ 3] 28.0-30.0 sec 256 KBytes 1.05 Mbits/sec
[ 3] 30.0-32.0 sec 128 KBytes 524 Kbits/sec
[ 3] 32.0-34.0 sec 640 KBytes 2.62 Mbits/sec
[ 3] 34.0-36.0 sec 384 KBytes 1.57 Mbits/sec
[ 3] 36.0-38.0 sec 384 KBytes 1.57 Mbits/sec
[ 3] 38.0-40.0 sec 384 KBytes 1.57 Mbits/sec
[ 3] 40.0-42.0 sec 128 KBytes 524 Kbits/sec -
Packets sent out the wrong Interface on Hyper-V 2012 Failover Cluster
Here is some background information:
2 Dell PowerEdge servers running Windows Server 2012 w/ Hyper-V in a Failover Cluster environment. Each has:
1 NIC for Live Migration 192.168.80.x/24 (connected to a private switch)
1 NIC for Cluster Communication 192.168.90.x/24 (connected to a private switch)
1 NIC for iscsi 192.168.100.x/24 (connected to a private switch)
1 NIC for host management with a routable public IP (*connected to corp network) w/ gateway on this interface
1 NIC for Virtual Machine traffic (*connected to corp network)
All NICs are up, we can ping the IPs between servers on the private network and on the public facing networks. All functions of hyper-v are working and the failover cluster reports all interfaces are up and we receive no errors. Live migration
works fine. In the live migration settings i have restricted the use of the 2 NICs (live migration or cluster comm).
My problem is that our networking/security group sees on occasion (about every 10 minutes with a few other packets thrown in at different times) syn packets that are destined for the 192.168.80.3 interface goes out of the public interface and is dropped
at our border router. These should be heading out of the 192.168.80.x or 192.168.90.x interfaces without ever hitting our corporate network. Anyone have an idea of why this might be happening? Traffic is on TCP 445.
Appreciate the help.
NateHi,
Please check live migration and Cluster Communication network settings in cluster:
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Networks.
Right-click the network that you want to modify settings for, and then click Properties.
There are two options:
Allow cluster network communication on this network-- Allow clients to connect through this network
Do not allow cluster network communication on this network
If the network is used only for cluster node communication, clear “Allow clients to connect through this network” option.
Check that and give us feedback for further troubleshooting, for more information please refer to following MS articles:
Modify Network Settings for a Failover Cluster
http://technet.microsoft.com/en-us/library/cc725775.aspx
Lawrence
TechNet Community Support -
Business Service pulling wrong interface in Config Overview
Hello,
I have created a Business Service with 2 receiver (inbound) interfaces. But when I assign this business system as the configured receiver in Receiver Determination, PI 7.1 is populating the receiving interface from the the Sender's BS.
Example:
Business System - Sys1
Receiver Interface for Sys1 > Doc_Out
Business System - Sys2
Receiver Interface for Sys2 > Doc_In
Create Receiver Determination:
Sender > Sys1
Interface > Doc Out
Assign BS Sys2 as configured receiver
Open "Configuration Overview" and view the reciever interface.
Rather than showing Sys1 > Doc_In PI is showing Sys1 > Doc_Out.
Why would PI ignore the interfaces within Sys2 and use the Sender's interfaces?
Thanks,
MattI have now tried setting up Sys2 as a business system, business service and as a party/business service. And every time I create my Receiver Determination and assign Sys2 as the Receiver it points to Doc_Out from Sys1 (sender) as the receivers interface.
I would like to know how to determine if a system is a business system or a business service? Also, when should it be considered a party (rather than service without party)?
Sys2 is an external system that we exchange files with via FTP.
In IR I have Sys2 using its own SWC and namespace and I have Sys1 using the SAP SRM SERVER 5.0 SWC and sap.com/supplierenablement/global namespace. Could there be something wrong with my design in IR?
I have also tried moving the Sys1 namespace underneath the SAP SRM SERVER 5.0 SWC...but it didn't make a difference.
Any help will be appreciated!
Thanks,
Matt -
Packets sent out on wrong interface
We have a BM 3.9 SP1 server configured with two public interfaces which are
Interface 1
XXX.XXX.138.178 mask 255.255.255.240 with a secondary IP address of XXX.XXX.138.179 and is has the default route of XXX.XXX.138.177.
Interface 2
XXX.XXX.146.218 mask 255.255.255.248 with a secondary IP address of XXX.XXX.146.219.
The two interfaces are connected to different physical networks that use different routers. Static and Dynamic NAT is enabled on both interfaces and there is a static NAT to an internal machine for the secondary addresses. NAT Dynamic passthrough is set to on. There is a static route defined in Inetcfg for XXX.XXX.3.166 with the next hop on XXX.XXX.146.217 which is the gateway address for Interface 2. However when I look at TCPCON IP Routing table that static route does not show up.
The problem is that the server receives a packet on the secondary address of interface 2 (XXX.XXX.146.219) from address XXX.XXX.3.166 forwards it to the internal machine which replies but the reply is sent out the default route which is on Interface 1. After taking a packet trace with Wireshark I can see that the outgoing packet has the wrong IP address (XXX.XXX.146.219) for that network which causes it to be dropped.
Is there a limit to the number of static routes that the BM server can have? I have about 30 defined. Why would the static route show up INETCFG but not in TCPCON-IP ROUTING TABLE? I can add the static route manually in the TCPCON IP Routing Table but it does not seem to effect the delivery of the packets. They are still sent out the default route.Is it possible you have an incorrect subnet mask for the problem static
route?
This should work. I've done it myself, and I have one of my client's
systems doing this now for 4-5 years. S2S VPN on a dedicated NIC and
T1, default route pointing to the other public nic's router. Added
static route to the remote VPN server public address with next
hop=router of VPN NIC, and it's fine.
If the route doesn't show up in TCPCON, I think there could be a typo
in the route you entered or the public IP?
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com *** -
Why does PI pickup wrong interface, in the interface determination step
I configured a scenario in id.
In ID, i can see the following when i open the interface determintation that i created.
Sender Details:
Communication Component:Sys_Sample_One_D
Interface: UserMasterQuery_Outb
Namespace: urn:sample.com:I_Legacy_JDBC_Application
Receiver Details:
Communication Component:Sys_Sample_Two_D
Interface:EmployeeEmailProcessing_Inb
Namespace:urn:sample.com:I_Legacy_FileApplication
Interface Mapping: UserMasterResultset_to_EmployeeEmail
But when i execute the scenario, and when i see in the the Interface determination pipeline step in moni, it is showing:
<SAP:Main..
<SAP:Sender>
<SAP:Service>Sys_Sample_One_D</SAP:Service>
<SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="" scheme=""/>
<SAP:Service>Sys_Sample_Two_D</SAP:Service>
<SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
<SAP:Mapping notRequired="Y"/>
</SAP:Receiver>
<SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface>
In the <SAP:Receiver> section, the <SAP:Service>Sys_Sample_Two_D</SAP:Service> is as per my configuratioin,
but <SAP:Interface namespace="urn:sample.com:I_Legacy_JDBC_Application">UserMasterQuery_Outb</SAP:Interface> is not the interface that i configured as the receiver interface, infact this is the sender interface.
the correct receiver interface to be pickedup is EmployeeEmailProcessing_Inb
and finally it is showing the error in moni, in the Technical Routing pipeline step
<SAP:AdditionalText>No standard agreement found for , Sys_Sample_One_D, , Sys_Sample_Two_D,
urn:sample.com:I_Legacy_JDBC_Application, UserMasterQuery_Outb</SAP:AdditionalText>
the error i can see later, but i would like the right interface to be determined by PI,
i refreshed various caches etc, recreated the config objects in ID, but it is not picking up the right receiver interface.
any inputs appreciated, to find out what went wrong.
thanks,
Madhu.Two threads which has some discussion regarding this happening in PI 7.1.Hope it gives you some help.
Incorrect Receiver Determination
Reciver Problem
And, as you have checked your Interface determination similarly can you also check your receiver determination.
Does the receiver determination have the correct receiver at the bottom ? -
Private modifier not allowed within Interface
hello,
Can someone explain to me the logic behind not being able to declare a method's modifier as "private" when defining my Interface? When I do so the compiler generates the following error:
"modifer private not allowed here at line 23, column 16"
I change it back to public and its fine. One would think that the compiler would allow one to declare a method private within an Interface so long as the Implementation matches? Thanks in advanced.The idea behind interfaces is to provide information to the outside world about a class that implements the interface. Specifically, it lets the outside world know about certain methods that can be called on instances of that class. That way, a class can use instances of any class that implements a given interface rather than commiting itself to one specific implementation only.
Since the outside world cannot see private methods, it doesn't make sense for interfaces to prescribe private methods in the first place. In fact, how a class deals with implementing a method is none of the interface's business... -
Alt+Shift works wrong in CS5 Dreamweaver
When I working in main window (designer) and press Alt+Shift (standard switching language), the following happens:
1. Toolbars Style rendering, Document, Standard blinks
2. Dreamweaver window looses focus, so I am not able to type anymore unless I click it.
3. The focus goes on the Snippets tab.
4. HOME, END and TAB keyboard keys stop working
Are this a bug or some keyboard shortcut? If this a some shortcut, how I can change it? (in Edit - Keyboard shortcuts I can't find it)OS: Win 7 64 bit Ultimate
It's occur every time when I do this in Dreamweaver, independently of other programs running. -
Audio midi network setup wrong interface
I am having difficulty establishing a wireless MIDI connection between my Macbook Pro (10.8) and my iPad.
When I open the Audio MIDI setup application and go to MIDI Studio and click Network, it detects my iPad, and I can supposedly connect to it, but nothing works. I look at the address which says:
host-12:5006
10.211.55.2:5006
10.37.129.2:5006
However, both devices are on a network starting with 128.237....
When I run ipconfig, i see that these two adresses are coming from vnic0 and vnic1 which I traced back to Parallels.app--they are virtual interface devices for running windows, etc.
Basically, I get the feeling that Audio MIDI setup.app isn't getting the right ip addresses to function.
Or am I completely misunderstanding something here?
ThanksYou can disable all the Parallels services temporarily by typing the following in Utilities/Terminal.app. It will ask for the root password.
sudo launchctl stop com.parallels.desktop.launchdaemon
To enable it again, enter:
sudo launchctl start com.parallels.desktop.launchdaemon
The background services must be running for Parallels to run so remember they are back on when you're done with your audio session. -
OSX sends out Dhcp requests thru the wrong interface
I have setup an Xserve so far only providing file services over AFP. It is located in our computer room on a different broadcast domain. I use a separate machine as a DNS. I would like to use my Xserve's 2nd ethernet interface to provide Netboot/Netinstall services on a 192.168.x.x network for bulk imaging of our clients. I have enabled Dhcp and setup Netboot on the eth1 but the system.log shows that it is floding my computer room network sending dhcp requests from eth0.
I have checked the bootpd.plist file and the settings seem ok.Check your terminology.
it is floding my computer room network sending dhcp requests from eth0.
The only way it would send any DHCP traffic on en0 would be if en0 was configured to use DHCP for its own configuration.
Running as a DHCP server is entirely passive - nothing happens until the server receives a request from a client on the LAN. Only at that point does the DHCP server send any traffic out over the wire.
In addition, 'flood' is a relative term. How much traffic are we talking here? Are you talking a few packets such as in the normal DHCP client request/refresh cycle, or are you talking hundreds of packets a second? -
While upgrading my iPhone 3GS to iOS 4.2 something went wrong and came up with the message "The iPhone could not be restored. An unknown error occurred [1015]." Now it will not start at all. It just stays on screen with USB and the iTune picture. What can I do to get it going again. I only tried to upgrade because I was prompted to up-grade and now I am helpless. I did a backup before starting the upgrade. The error message did not tell what to do next. Any help is very much appreciated.
Usually that means the iPhone was hacked to unlock it from the original
carrier .
Updating the operating system locks it back to that original carrier
You could try this
http://support.apple.com/kb/TS3281
However if the iPhone was hacked it is probably a paper weight now
and as this is an Apple hosted forum you can get no further help here -
[SOLVED] Graphical Interface doesn't start with Radeon HD 7670M
Hi everyone!
I just bought a new laptop: Toshiba Satellite L855-14Z with a Radeon HD 7670M graphic chip.
I installed Arch Linux and everything works fine except the graphical interface.
I have tried 3 options and all result in strange log files:
1. KMS DISABLED / OPEN-SOURCE-DRIVER
Output on screen: Reached Graphical Interface
Xorg.0.log:
[ 8.777]
X.Org X Server 1.13.2
Release Date: 2013-01-24
[ 8.777] X Protocol Version 11, Revision 0
[ 8.777] Build Operating System: Linux 3.7.4-1-ARCH x86_64
[ 8.777] Current Operating System: Linux march 3.7.5-1-ARCH #1 SMP PREEMPT Mon Jan 28 10:03:32 CET 2013 x86_64
[ 8.777] Kernel command line: root=/dev/sda2 ro radeon.modeset=0 rootfstype=ext4 systemd.unit=graphical.target initrd=EFI\arch\initramfs-arch.img
[ 8.777] Build Date: 25 January 2013 09:33:50AM
[ 8.777]
[ 8.777] Current version of pixman: 0.28.2
[ 8.777] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 8.777] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8.777] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 8 09:38:51 2013
[ 8.812] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 8.839] (==) No Layout section. Using the first Screen section.
[ 8.839] (==) No screen section available. Using defaults.
[ 8.839] (**) |-->Screen "Default Screen Section" (0)
[ 8.839] (**) | |-->Monitor "<default monitor>"
[ 8.839] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 8.839] (==) Automatically adding devices
[ 8.839] (==) Automatically enabling devices
[ 8.839] (==) Automatically adding GPU devices
[ 8.872] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 8.872] Entry deleted from font path.
[ 8.893] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 8.893] Entry deleted from font path.
[ 8.893] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 8.893] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 8.893] Entry deleted from font path.
[ 8.893] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 8.893] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 8.893] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 8.893] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 8.894] (II) Loader magic: 0x7fcc40
[ 8.894] (II) Module ABI versions:
[ 8.894] X.Org ANSI C Emulation: 0.4
[ 8.894] X.Org Video Driver: 13.1
[ 8.894] X.Org XInput driver : 18.0
[ 8.894] X.Org Server Extension : 7.0
[ 8.894] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 8.897] (--) PCI:*(0:1:0:0) 1002:6840:1179:fb22 rev 0, Mem @ 0xb0000000/268435456, 0xc0000000/131072, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
[ 8.897] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 8.905] Initializing built-in extension Generic Event Extension
[ 8.905] Initializing built-in extension SHAPE
[ 8.906] Initializing built-in extension MIT-SHM
[ 8.906] Initializing built-in extension XInputExtension
[ 8.906] Initializing built-in extension XTEST
[ 8.906] Initializing built-in extension BIG-REQUESTS
[ 8.906] Initializing built-in extension SYNC
[ 8.906] Initializing built-in extension XKEYBOARD
[ 8.906] Initializing built-in extension XC-MISC
[ 8.906] Initializing built-in extension SECURITY
[ 8.906] Initializing built-in extension XINERAMA
[ 8.906] Initializing built-in extension XFIXES
[ 8.906] Initializing built-in extension RENDER
[ 8.906] Initializing built-in extension RANDR
[ 8.906] Initializing built-in extension COMPOSITE
[ 8.906] Initializing built-in extension DAMAGE
[ 8.906] Initializing built-in extension MIT-SCREEN-SAVER
[ 8.906] Initializing built-in extension DOUBLE-BUFFER
[ 8.906] Initializing built-in extension RECORD
[ 8.906] Initializing built-in extension DPMS
[ 8.906] Initializing built-in extension X-Resource
[ 8.906] Initializing built-in extension XVideo
[ 8.906] Initializing built-in extension XVideo-MotionCompensation
[ 8.906] Initializing built-in extension XFree86-VidModeExtension
[ 8.906] Initializing built-in extension XFree86-DGA
[ 8.906] Initializing built-in extension XFree86-DRI
[ 8.906] Initializing built-in extension DRI2
[ 8.906] (II) LoadModule: "glx"
[ 8.924] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8.939] (II) Module glx: vendor="X.Org Foundation"
[ 8.939] compiled for 1.13.2, module version = 1.0.0
[ 8.939] ABI class: X.Org Server Extension, version 7.0
[ 8.939] (==) AIGLX enabled
[ 8.940] Loading extension GLX
[ 8.940] (==) Matched ati as autoconfigured driver 0
[ 8.940] (==) Matched ati as autoconfigured driver 1
[ 8.940] (==) Matched vesa as autoconfigured driver 2
[ 8.940] (==) Matched modesetting as autoconfigured driver 3
[ 8.940] (==) Matched fbdev as autoconfigured driver 4
[ 8.940] (==) Assigned the driver to the xf86ConfigLayout
[ 8.940] (II) LoadModule: "ati"
[ 8.940] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 8.948] (II) Module ati: vendor="X.Org Foundation"
[ 8.948] compiled for 1.13.2, module version = 7.1.0
[ 8.948] Module class: X.Org Video Driver
[ 8.948] ABI class: X.Org Video Driver, version 13.1
[ 8.948] (II) LoadModule: "radeon"
[ 8.948] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 8.980] (II) Module radeon: vendor="X.Org Foundation"
[ 8.980] compiled for 1.13.2, module version = 7.1.0
[ 8.980] Module class: X.Org Video Driver
[ 8.980] ABI class: X.Org Video Driver, version 13.1
[ 8.980] (II) LoadModule: "vesa"
[ 8.981] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 8.987] (II) Module vesa: vendor="X.Org Foundation"
[ 8.987] compiled for 1.13.0, module version = 2.3.2
[ 8.987] Module class: X.Org Video Driver
[ 8.987] ABI class: X.Org Video Driver, version 13.0
[ 8.987] (II) LoadModule: "modesetting"
[ 8.987] (WW) Warning, couldn't open module modesetting
[ 8.987] (II) UnloadModule: "modesetting"
[ 8.987] (II) Unloading modesetting
[ 8.987] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 8.987] (II) LoadModule: "fbdev"
[ 8.988] (WW) Warning, couldn't open module fbdev
[ 8.988] (II) UnloadModule: "fbdev"
[ 8.988] (II) Unloading fbdev
[ 8.988] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 8.988] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
ATI Radeon IGP330M/340M/350M (U2) 4337,
ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
ATI Radeon X800PRO (R420) JI (AGP),
ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
ATI Radeon Mobility 9800 (M18) JN (AGP),
ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
ATI Radeon Mobility M7 LW (AGP),
ATI Mobility FireGL 7800 M7 LX (AGP),
ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
ATI FireGL Mobility 9000 (M9) Ld (AGP),
ATI Radeon Mobility 9000 (M9) Lf (AGP),
ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
ATI Radeon Mobility 9600 (M10) NQ (AGP),
ATI Radeon Mobility 9600 (M11) NR (AGP),
ATI Radeon Mobility 9600 (M10) NS (AGP),
ATI FireGL Mobility T2 (M10) NT (AGP),
ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
ATI Radeon Mobility X300 (M22) 5460 (PCIE),
ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
ATI Radeon X800PRO (R423) UI (PCIE),
ATI Radeon X800LE (R423) UJ (PCIE),
ATI Radeon X800SE (R423) UK (PCIE),
ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
ATI FireGL unknown (R423) UR (PCIE),
ATI FireGL unknown (R423) UT (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility FireGL V5000 (M26) (PCIE),
ATI Mobility Radeon X700 XL (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Mobility Radeon X700 (M26) (PCIE),
ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
ATI Radeon Mobility 9100 IGP (U3) 5835,
ATI Radeon XPRESS 200 5954 (PCIE),
ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
ATI Radeon XPRESS 200M 5975 (PCIE),
ATI Radeon XPRESS 200 5A41 (PCIE),
ATI Radeon XPRESS 200M 5A42 (PCIE),
ATI Radeon XPRESS 200 5A61 (PCIE),
ATI Radeon XPRESS 200M 5A62 (PCIE),
ATI Radeon X300 (RV370) 5B60 (PCIE),
ATI Radeon X600 (RV370) 5B62 (PCIE),
ATI Radeon X550 (RV370) 5B63 (PCIE),
ATI FireGL V3100 (RV370) 5B64 (PCIE),
ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
ATI Mobility Radeon X800 XT (M28) (PCIE),
ATI Mobility FireGL V5100 (M28) (PCIE),
ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
ATI Radeon X850 XT PE (R480) (PCIE),
ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
ATI Radeon X850 XT (R480) (PCIE),
ATI Radeon X800XT (R423) 5D57 (PCIE),
ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
ATI Radeon X700 PRO (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
ATI Mobility Radeon X1700, ATI Radeon X2300HD,
ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
AMD FireStream 9250, ATI FirePro V8700 (FireGL),
ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
ATI Mobility Radeon HD 4670, ATI FirePro M5750,
ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
ATI Mobility Radeon HD 3850 X2, ATI RV670,
ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
ATI FireGL V3600, ATI Radeon HD 2600 LE,
ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
SUMO, SUMO, SUMO, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
ATI Radeon 4100, ATI Mobility Radeon HD 4200,
ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
AMD Radeon HD 6300 Series Graphics,
AMD Radeon HD 6200 Series Graphics, PALM, PALM, PALM, CYPRESS,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
AMD Firestream 9350, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
ATI Mobility Radeon HD 5800 Series,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter,
ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
ATI Mobility Radeon HD 5000 Series,
ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
ATI Mobility Radeon Graphics, CEDAR,
ATI FirePro (FireGL) Graphics Adapter,
ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
BARTS, BARTS, Mobility Radeon HD 6000 Series,
Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
ARUBA, ARUBA, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI,
TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, PITCAIRN, PITCAIRN,
PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
VERDE, VERDE, VERDE, VERDE, VERDE, VERDE
[ 8.994] (II) VESA: driver for VESA chipsets: vesa
[ 8.994] (++) using VT number 1
[ 9.005] (II) [KMS] drm report modesetting isn't supported.
[ 9.005] (II) [KMS] drm report modesetting isn't supported.
[ 9.005] (II) [KMS] drm report modesetting isn't supported.
[ 9.005] (II) [KMS] drm report modesetting isn't supported.
[ 9.005] (II) [KMS] drm report modesetting isn't supported.
[ 9.005] (EE) Screen 0 deleted because of no matching config section.
[ 9.005] (II) UnloadModule: "radeon"
[ 9.005] (EE) Screen 0 deleted because of no matching config section.
[ 9.005] (II) UnloadModule: "radeon"
[ 9.005] (EE) Screen 0 deleted because of no matching config section.
[ 9.005] (II) UnloadModule: "radeon"
[ 9.005] (EE) Screen 0 deleted because of no matching config section.
[ 9.005] (II) UnloadModule: "radeon"
[ 9.005] (II) Loading sub module "vbe"
[ 9.005] (II) LoadModule: "vbe"
[ 9.005] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 9.013] (II) Module vbe: vendor="X.Org Foundation"
[ 9.013] compiled for 1.13.2, module version = 1.1.0
[ 9.013] ABI class: X.Org Video Driver, version 13.1
[ 9.013] (II) Loading sub module "int10"
[ 9.013] (II) LoadModule: "int10"
[ 9.013] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 9.017] (II) Module int10: vendor="X.Org Foundation"
[ 9.017] compiled for 1.13.2, module version = 1.0.0
[ 9.017] ABI class: X.Org Video Driver, version 13.1
[ 9.017] (II) VESA(0): initializing int10
[ 9.017] (EE) VESA(0): Cannot read V_BIOS (3) Input/output error
[ 9.017] (II) UnloadModule: "vesa"
[ 9.017] (II) UnloadSubModule: "int10"
[ 9.017] (II) Unloading int10
[ 9.017] (II) UnloadSubModule: "vbe"
[ 9.017] (II) Unloading vbe
[ 9.017] (II) UnloadModule: "radeon"
[ 9.018] (EE) Screen(s) found, but none have a usable configuration.
[ 9.018]
Fatal server error:
[ 9.018] no screens found
[ 9.018] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 9.018] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 9.018] (EE)
[ 9.020] Server terminated with error (1). Closing log file.
I have no "xinitrc" and no "xorg.conf".
2. KMS ENABLED / OPEN-SOURCE-DRIVER
This is the strangest: I just get a blank black screen with a little strip on top with the gnome 3 wallpaper in it. The height of the strip is only 2mm, but there is definetly a blue wallpaper.
3. KMS DISABLED / PROPIETARY DRIVER
Output on screen: Reached Graphical Interface
Xorg.0.log:
[ 48.111]
X.Org X Server 1.13.2
Release Date: 2013-01-24
[ 48.111] X Protocol Version 11, Revision 0
[ 48.111] Build Operating System: Linux 3.7.4-1-ARCH x86_64
[ 48.111] Current Operating System: Linux march 3.7.5-1-ARCH #1 SMP PREEMPT Mon Jan 28 10:03:32 CET 2013 x86_64
[ 48.111] Kernel command line: root=/dev/sda2 ro nomodeset rootfstype=ext4 systemd.unit=graphical.target initrd=EFI\arch\initramfs-arch.img
[ 48.112] Build Date: 25 January 2013 09:33:50AM
[ 48.112]
[ 48.112] Current version of pixman: 0.28.2
[ 48.112] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 48.112] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 48.112] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 8 10:19:07 2013
[ 48.112] (==) Using config file: "/etc/X11/xorg.conf"
[ 48.113] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 48.113] (==) ServerLayout "aticonfig Layout"
[ 48.113] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
[ 48.113] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
[ 48.113] (**) | |-->Device "aticonfig-Device[0]-0"
[ 48.113] (==) Automatically adding devices
[ 48.113] (==) Automatically enabling devices
[ 48.113] (==) Automatically adding GPU devices
[ 48.113] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 48.113] Entry deleted from font path.
[ 48.113] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 48.113] Entry deleted from font path.
[ 48.113] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 48.113] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 48.113] Entry deleted from font path.
[ 48.113] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 48.113] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 48.113] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 48.113] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 48.113] (II) Loader magic: 0x7fcc40
[ 48.113] (II) Module ABI versions:
[ 48.113] X.Org ANSI C Emulation: 0.4
[ 48.113] X.Org Video Driver: 13.1
[ 48.113] X.Org XInput driver : 18.0
[ 48.113] X.Org Server Extension : 7.0
[ 48.115] (--) PCI:*(0:1:0:0) 1002:6840:1179:fb22 rev 0, Mem @ 0xb0000000/268435456, 0xc0000000/131072, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
[ 48.116] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 48.116] Initializing built-in extension Generic Event Extension
[ 48.116] Initializing built-in extension SHAPE
[ 48.116] Initializing built-in extension MIT-SHM
[ 48.116] Initializing built-in extension XInputExtension
[ 48.116] Initializing built-in extension XTEST
[ 48.116] Initializing built-in extension BIG-REQUESTS
[ 48.116] Initializing built-in extension SYNC
[ 48.116] Initializing built-in extension XKEYBOARD
[ 48.116] Initializing built-in extension XC-MISC
[ 48.116] Initializing built-in extension SECURITY
[ 48.116] Initializing built-in extension XINERAMA
[ 48.116] Initializing built-in extension XFIXES
[ 48.116] Initializing built-in extension RENDER
[ 48.116] Initializing built-in extension RANDR
[ 48.116] Initializing built-in extension COMPOSITE
[ 48.116] Initializing built-in extension DAMAGE
[ 48.117] Initializing built-in extension MIT-SCREEN-SAVER
[ 48.117] Initializing built-in extension DOUBLE-BUFFER
[ 48.118] Initializing built-in extension RECORD
[ 48.118] Initializing built-in extension DPMS
[ 48.119] Initializing built-in extension X-Resource
[ 48.119] Initializing built-in extension XVideo
[ 48.120] Initializing built-in extension XVideo-MotionCompensation
[ 48.121] Initializing built-in extension XFree86-VidModeExtension
[ 48.121] Initializing built-in extension XFree86-DGA
[ 48.122] Initializing built-in extension XFree86-DRI
[ 48.122] Initializing built-in extension DRI2
[ 48.122] (II) "glx" will be loaded by default.
[ 48.122] (II) LoadModule: "glx"
[ 48.122] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 48.122] (II) Module glx: vendor="Advanced Micro Devices, Inc."
[ 48.122] compiled for 6.9.0, module version = 1.0.0
[ 48.123] Loading extension GLX
[ 48.123] (II) LoadModule: "fglrx"
[ 48.123] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 48.132] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
[ 48.132] compiled for 1.4.99.906, module version = 9.1.11
[ 48.132] Module class: X.Org Video Driver
[ 48.132] (II) Loading sub module "fglrxdrm"
[ 48.132] (II) LoadModule: "fglrxdrm"
[ 48.132] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 48.133] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
[ 48.133] compiled for 1.4.99.906, module version = 9.1.11
[ 48.133] (II) AMD Proprietary Linux Driver Version Identifier:9.01.11
[ 48.133] (II) AMD Proprietary Linux Driver Release Identifier: 9.012
[ 48.133] (II) AMD Proprietary Linux Driver Build Date: Dec 19 2012 14:41:10
[ 48.133] (++) using VT number 2
[ 48.133] (WW) Falling back to old probe method for fglrx
[ 48.136] (II) Loading PCS database from /etc/ati/amdpcsdb /etc/ati/amdpcsdb.default
[ 48.137] ukiDynamicMajor: failed to open /proc/ati/major
[ 48.137] ukiDynamicMajor: failed to open /proc/ati/major
[ 48.138] (--) Chipset Supported AMD Graphics Processor (0x6840) found
[ 48.138] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[ 48.139] (II) AMD Video driver is running on a device belonging to a group targeted for this release
[ 48.139] (II) AMD Video driver is signed
[ 48.139] (II) fglrx(0): pEnt->device->identifier=0x102fb40
[ 48.140] (II) fglrx(0): === [xdl_xs113_atiddxPreInit] === begin
[ 48.140] (II) Loading sub module "vgahw"
[ 48.140] (II) LoadModule: "vgahw"
[ 48.140] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 48.140] (II) Module vgahw: vendor="X.Org Foundation"
[ 48.140] compiled for 1.13.2, module version = 0.1.0
[ 48.140] ABI class: X.Org Video Driver, version 13.1
[ 48.140] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
[ 48.140] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 48.140] (==) fglrx(0): Default visual is TrueColor
[ 48.140] (**) fglrx(0): Option "DPMS" "true"
[ 48.140] (==) fglrx(0): RGB weight 888
[ 48.140] (II) fglrx(0): Using 8 bits per RGB
[ 48.141] (==) fglrx(0): Buffer Tiling is ON
[ 48.141] (II) Loading sub module "fglrxdrm"
[ 48.141] (II) LoadModule: "fglrxdrm"
[ 48.141] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 48.141] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
[ 48.141] compiled for 1.4.99.906, module version = 9.1.11
[ 48.142] ukiDynamicMajor: failed to open /proc/ati/major
[ 48.142] ukiDynamicMajor: failed to open /proc/ati/major
[ 48.143] (**) fglrx(0): NoAccel = NO
[ 48.143] (**) fglrx(0): AMD 2D Acceleration Architecture enabled
[ 48.143] (--) fglrx(0): Chipset: "AMD Radeon HD 7600M Series" (Chipset = 0x6840)
[ 48.143] (--) fglrx(0): (PciSubVendor = 0x1179, PciSubDevice = 0xfb22)
[ 48.143] (==) fglrx(0): board vendor info: third party graphics adapter - NOT original AMD
[ 48.143] (--) fglrx(0): Linear framebuffer (phys) at 0xb0000000
[ 48.143] (--) fglrx(0): MMIO registers at 0xc0000000
[ 48.143] (--) fglrx(0): I/O port at 0x00003000
[ 48.143] (==) fglrx(0): ROM-BIOS at 0x000c0000
[ 48.147] (EE) fglrx(0): V_BIOS address 0x0 out of range
[ 48.147] (II) fglrx(0): Invalid ATI BIOS from int10, the adapter is not VGA-enabled
[ 48.147] (EE) fglrx(0): Invalid video BIOS signature!
[ 48.147] (EE) fglrx(0): GetBIOSParameter failed
[ 48.147] (EE) fglrx(0): PreInitAdapter failed
[ 48.147] (EE) fglrx(0): PreInit failed
[ 48.147] (II) fglrx(0): === [xdl_xs113_atiddxPreInit] === end
[ 48.149] (II) UnloadModule: "fglrx"
[ 48.150] (II) UnloadSubModule: "fglrxdrm"
[ 48.150] (II) Unloading fglrxdrm
[ 48.150] (II) UnloadSubModule: "vgahw"
[ 48.150] (II) Unloading vgahw
[ 48.150] (II) UnloadSubModule: "fglrxdrm"
[ 48.150] (EE) Screen(s) found, but none have a usable configuration.
[ 48.150]
Fatal server error:
[ 48.150] no screens found
[ 48.150] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 48.150] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 48.150] (EE)
[ 48.157] Server terminated with error (1). Closing log file.
xorg.conf:
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Section "Module"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
And "fglrxinfo" gives me "Error: unable to open display (null)"
Any help would be much appreciated!
Last edited by mjb (2013-02-08 15:41:16)Yes I did, but it didn't help.
I solved the problem now, but it was rather complicated and is only a workaround. If anyone is having the same problem:
1) I installed the open source drivers and enabled KMS
2) I copied the efi shell from the arch boot disk to the rEFInd folder
3) Now everytime I start my laptop I have to start the EFI-Shell (v1) first. This somehow changes the resolution. I exit the shell and start arch. X works.
I have no idea why this works, but it is the only thing that does. If anyone knows what this means, I'd appreciate your help.
By the way: Step 3 also solves this issue -
"HTTPS hostname wrong" for a hostname starts with a number
Does anyone know about why HttpsClient throws the error for a hostname starts with a number. I have no problem with other hostname but only for the hostname starts with a number. The certificate works fine with Browser. I am sure the hostname in the certificate and in the request are exactly the same.
I know how to skip the hostname verification, but I don't want to do that for security concern.
Can sun develpoer shed some light how to verify the hostname in HttpsClient?
java.io.IOException: HTTPS hostname wrong: should be
<1company.mydomain.com>
at sun.net.www.protocol.https.HttpsClient.b(DashoA6275)
at sun.net.www.protocol.https.HttpsClient.afterConnect(DashoA6275)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(DashoA6275)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:574)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(DashoA6275)
at java.net.URL.openStream(URL.java:960)
Thanks
Al8079I looked at the RFCs you mention, and they do seem to indicate that host/domain names cannot start with digits...however if you look at RFC 1123 closely it says:
RFC1123 APPLICATIONS LAYER -- GENERAL October 1989
2. GENERAL ISSUES
This section contains general requirements that may be applicable to
all application-layer protocols.
2.1 Host Names and Numbers
The syntax of a legal Internet host name was specified in RFC-952
[DNS:4]. One aspect of host name syntax is hereby changed: the
restriction on the first character is relaxed to allow either a
letter or a digit. Host software MUST support this more liberal
syntax.
Host software MUST handle host names of up to 63 characters and
SHOULD handle host names of up to 255 characters.
Maybe you are looking for
-
How can you put a setting that you can only move to a next slide by clicking on the forward button?
I am very sorry if there is somewhere already given an answer to this but can somebody help me please? When I use a space, enter or click in my quiz, they move on to the next slide without answering the previous question completely. How can I make su
-
Error when testing a webservice
hi, I am using Jdev 11 g errors and using the Web service tutorial. Some errors with embedded server (cannot locate policy file). The OS is windows 2003 server SP2 (2GB ram). Please help. [Starting OC4J using the following ports: HTTP=8988, RMI=23891
-
All attachments opening as plain text
Apparently without any changing of settings the mail program is opening all attachments as plain text. This occurs although the program is available to open the attachment. I know the attachments can be saved to the desktop and then opened, but this
-
Jax-ws reading fault saop messges - error parsing the xml source
i have a class for reading soap messages including fault: class it.xx.SOAPListener.LoggingHandler, handleFault is the method like: public boolean handleFault(SOAPMessageContext c) { try { SOAPMessage msg = c.getMessage(); msg.writeTo(System.out); } c
-
Selection screen: no sequence check for select option
Hello everyone, I am an SAP starter and this will is my first question: I am making a program that approves a stock demand over several levels. When a level approves, the demand goes to the next level. for example: level 1 = planning level 2 = manage