Results 1 to 1 of 1
Here's what I'm looking at: Code: $ xhost access control enabled, only authorized clients can connect INET:220.127.116.11$ xhost -18.104.22.168 22.214.171.124 being removed from access control list $ xhost access control ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 10-07-2011 #1
- Join Date
- Oct 2011
Comcast ISP in my XHOST; FAST Search & Transfer in XAUTH list
Here's what I'm looking at:
$ xhost access control enabled, only authorized clients can connect INET:126.96.36.199$ xhost -188.8.131.52 184.108.40.206 being removed from access control list $ xhost access control enabled, only authorized clients can connect $ xhost - access control enabled, only authorized clients can connect
IP: 220.127.116.11Appear in my xhost file? Please tell me I haven't been monitored by my ISP.
ISP: Comcast Cable
Organization: Comcast Cable
Services: None detected
Assignment: Dynamic IP
Also, here is my XAUTH list:
$ xauth list 18.104.22.168:0 MIT-MAGIC-COOKIE-1 a15731cb97f21cda4ed7c6af82248607 changed-machine-name.local/unix:0 MIT-MAGIC-COOKIE-1 93838a2763343a22e3e7c5d97713c848 169.254.203.9:0 MIT-MAGIC-COOKIE-1 93838a2763343a22e3e7c5d97713c848 Changed-Machine-Name.local/unix:0 MIT-MAGIC-COOKIE-1 78075f4bd5140c473ce8c271553cbd86 192.168.1.143:0 MIT-MAGIC-COOKIE-1 78075f4bd5140c473ce8c271553cbd86 changed-machine-name.local:0 MIT-MAGIC-COOKIE-1 78075f4bd5140c473ce8c271553cbd86 $ xauth info Authority file: /Users/~username/.Xauthority File new: no File locked: no Number of entries: 6 Changes honored: yes Changes made: no Current input: (argv):1
ISP: FAST Search & Transfer
Organization: FAST Search & Transfer
Services: None detected
Assignment: Static IP
I'm pretty sure 169.254.203.9 might be a self issued IP address on my machine when airport (macOSX.6) cannot pull DHCP. That happens often without cause; my netbook will not connect to router when other machines using that router are fine. Restarts don't cure...
192.168.1.143 is a valid IP address in the router range BUT it is NOT one that should get used since my range starts at .115 and there are no more than 10 devices ever connecting to it including phones, etc.
In the list above, notice the capitalized version of "Changed-Machine-Name" vs the "changed-machine-name" - that is not an error, it is as it appears.
I loaded WireShark and found some more weird $!
WireShark showed packets going between my actual IP and the 192.168.1.143. Also there is some linking and bridging going on in my en1 (wireless) interface. I couldn't figure that out. There were a lot of name resolves that popped up giving both the Capitalized Machine Name and the uncapitalized version, seemingly talking to each other.
Here's the weirdest thing. I went and change my machine name and netname from Machine Name to something completely different (it was capitalized in my settings.) That something different immediately began resolving in WireShark but the lowercase original machine name was unchanged and also continued to show. If they were the same but with case-text ignored; then they would have both resolved to the changed name, right?
So, please... what's up? Am I paranoid? Should I ask about what kinds of CA certificates you guys have normally... gov't +/- various other corporate stuff? I'm a total newbie and have stayed up all night for the last 4 nights attempting to figure this out. Thanks.