Self Assigned IP + Firewall Disabled = No security?

Hi everyone. My 8600M GT card died last week, so I had my logic board replaced and my Macbook Pro returned to me a few days ago. Before the logic board replacement, I had no issues connecting wirelessly to my Apple Airport Extreme (newest model with 7.4.2 firmware). After the replacement, I couldn't connect and found another topic in this forum concerning the Self-Assigned IP issue. So, I decided to disable my firewall as it was only way I could connect regularly without having to re-enter network information or delete .plists from the Library folder every time I restarted the MBP. Now that my wireless is working, I have no firewall for security. I understand others are having the same problems, so I would like to know what everyone is using as an alternative to the OS firewall.

If you are using an Airport Extreme base station, then you have a hardware firewall, so the software firewall is redundant.
However, you may be able to get it working correctly.
Do you have MAC address filtering set up on your AEBS? If so, I imagine you would need to change the MAC address of your computer since it probably changed.
I don't know if any of the below will fix the issue, but it is what I would try. The preference files will be recreated to default settings after you delete them.
First, I'd delete the keychain entry for connecting to the AEBS (both login and system keychain), and remove the AEBS from the preferred networks in Network Prefs. Restart the AEBS and try to connect.
Second, create a new Network location in Network system prefs. See if it will connect correctly, now.
Third, delete the /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist. This will require you to set up your network interfaces again, so jot down some notes on the settings unless you can remember anything you set up special. You can add an interface (airport, ethernet) by clicking on the add button at the bottom of the list.
Fourth, delete /Library/Preferences/SystemConfiguration/preferences.plist. Lots more stuff to reset, preference wise. If you open the plist first, you can get an idea of what is stored in that file that you will have to reset.

Similar Messages

Disable windows firewall with endpoint security

Hello NG
I created a new endpoint security policy with ZCM11
Now on the Firewall setting i configured following
Default Behavior: Inherit
Disable Windows Firewall and register Endpoint Security Management Firewall
in Windows Security Center: Yes
My question now. Is the endpoint Security Management Firewall enabled? Are
all port blocked by default?
Where can I see what port are blocked by Endpoint Security?
Regards Ramon

Ramon,
here's the doc reference: http://www.novell.com/documentation/...a/brz5hk9.html
Shaun Pond

WiFi, Self-Assigned IP (secured networks only), and Knocking Other Devices Off Network

My MacBook Pro (3,1) refuses to initially connect to any secured WiFi network (home, work, hotel, etc.). First it self-assigns an IP address and gives that little "!" symbol in the WiFi icon. Then, after a few moments, it connects to the Internet but knocks every other computer and device (iPads, cell phones, etc.) off the network. When you go to reconnect the other computers and devices, the MacBook Pro gets knocked off the network and then refuses to connect to the router at all (you get an instant "timed out" error) until a restart. It has absolutely NO problems whatsoever connecting to a non-secure network (free WiFi, WiFi without a password at home, or those public hotspots that take you to a webpage to agree to the terms before connecting).
The following are true of my MBP:
1. The entire harddrive has been replaced (not original). I had this problem before and after this replacement.
2. The OS has been upgraded / wiped / reinstalled more times than I care to count. I started having this problem with the original upgrade to OS X 10.5.x and have continued through to its current OS (10.8). No particular OS was more or less difficult that I could tell. It currently has a fresh (re-wiped) install of OS 10.8.
3. The AirPort card has been replaced.
4. The issues are consistent regardless of my location or the router / services I am connected to. I have no problems at all if there is no security - I have the above problems when trying to connect to a secure network (any security). I can be at home in my own house or in a hotel or airport - if there is no password, it connects no problem - if you have to type a password, forget it.
5. The computer doesn't have any problems using an Ethernet connection, and the WiFi behaves the same with or without an Ethernet connection (in other words, I can be connected to the Ethernet fine, but the WiFi can still self-assign an IP - the 169. whatever)
Any thoughts? Things I could try? Things I could be doing differently?

Do this the stuff you find at the bottom of this thread:
https://discussions.apple.com/thread/3864270?tstart=0

Self assigned ip and can't connect wirelessly on any apple device

Man oh man... this issue has been festering for almost an entire year now and I have not found a solution. Last August (2009) my macbook stopped wirelessly connecting to my ATT 2WIRE dsl modem saying it had a self assigned ip address. I bought the computer in July and could connect with no issues for about a month. Ever since then, I've been connected via ethernet with slow connection. At the same time, the 2 iPhones in our household also could not connect wirelessly. One G5 could connect wirelessly but was extremely weak and often dropped the signal.
I did tons of research and found zillions of other people with this issue and no resolution. I've tried every solution on macrumors, and apple discussions with no results... I've disabled firewall, renewed DHCP, tried DHCP manual (which then changes the status to say I'm connected, but nothing works in my browser), restarted, etc. At work, I can connect to our Linksys router wirelessly with no issues. When my friends come over, their macbooks and iPhones don't work either!
Originally I thought the issue was my modem so I ordered another one. Same issue. Just this week I was at my wits end and cancelled my service with ATT and switched to Clear. I acquired a Linksys router to connect to the Clear Modem and I'm STILL having this issue. The difference is now that my iPhone can connect wirelessly but my macbook still cannot. The router is a Linksys WRT51ab. My macbook pro is on version 10.5.8. I can only assume that some kind of update to airport is causing the problem. As of now, my IPv4 address is: 169.254.111.225
Please someone help me! I promise some kind of reward if you can help me fix this.

Based on the model number, your Linksys router is OLD.
I'd actually suspect that your router has been the problem.
You can download the full user manual here --> http://homedownloads.cisco.com/downloads/wrt51ab_ug.pdf
I don't know if you ever secured your wireless router or renamed it from the factory defaults.
If it your Linksys wireless router is not password secured, it's possible that someone else changed settings about the time things stopped connecting.
Regardless, you can completely reset the Linksys to the factory defaults by holding down the Reset button on the Linksys for more than 10 seconds.
Do that first.
Then see if things 'magically' start connecting again. I'm guessing the phones will connect, but the Mac still won't, because of the IP address in the current configuration.
If not, here's how to configure your Mac network settings.
On your Mac, in System Preferences, Internet and Network, Network,
Click on Location, Edit Location
Click the + sign to create a new location called '_test'
(The underscore before the name will put it at the top of your Locations list where it's easy to find)
Select Ethernet (wired)
First, we'll let DHCP try to set the address.
Click Apply.
Move the selection back to Ethernet, and watch the Status.
If it shows Connected and IP address appears after a few moments, at least the WIRED configuration is working.
Now IF the Wired configuration works, lets move on to the wireless configuration...
(If the Wired configuration is still not working, post back and we'll work through it.)
Still in System Preferences, Internet and Network, Network, with the _test location you just created...
Select the AirPort interface in the left column.
Turn AirPort On.
If no Network Name appears, click on the up/down button and select Join Other Network and select your Linksys router name.
Click 'Apply'.
Leave DHCP settings alone and watch the Status to see if it connects.
Let me know what happens!

Self Assigned IP Address redux

I am getting the "Self Assigned IP Address" in my Airport connection and I can't troubleshoot the problem.
Here's my setup and what I have been looking to accomplish..
I have an iMac G5 with a built-in Airport Extreme card running Leopard 10.5.3. I have created a network to provide my AppleTV and my work laptop with access to the internet. I've turned Internet sharing on, and have security set to a the WEP 128 key..
Recently I had to exchange my AppleTV for a new one, and during the 2 weeks I was without AppleTV - something has changed (and as I think through the issue, I'm not certain about when the last time I played youtube or purchased content - maybe the new appleTV doesn't have anything to do with it, and it was a software upgrade), as I am no longer able to access YouTube content or the iTunes Music store to authorize my purchased content or to purchase new music/movies. However, I am able to watch movie trailers, and preview songs. It connects to the network fine, shows a strong signal, but something isn't quite right.
I've performed about every known solution to the AppleTV problem, and have an open post over in the AppleTV area, but in tracking down my issue, I see that my Airport connection is showing that it has a "self-assigned IP Address" and my not be able to connect to the internet. My thoughs are that if i get the self-assigned IP address problem solved, I'll solve the ITMS/YouTube issue on the AppleTV.
My internet connection is via Verizon DSL, with a DSL modem, connected directly to my iMac with an ethernet cable. (no external router/firewall)
I find it interesting that I can watch trailers, preview music from ITMS with the 'Self-assigned IP' but not access ITMS for purchases, etc.
I do not have any expertise in networking and for the most part am just following what posts I've seen out there suggest to try - trashing the com.apple.airport.pref's - restarting in 'Safe' mode, etc. Rebuilding the network connections from scratch, etc. Repairing Keychain access, disabling the built in firewall, etc. Just can't get by this issue.
Anyone with any thoughts?

hey guys...I found the problem...it helped me very much just try to change the wireless mode from 11bgn mixed to 11bg mixed...do this from router settings . . .I guess this will help you

Self Assigned IP address – can't figure this out. Frustrated.

This is a long post but bear with me. It proposes a challenge for the mac connoisseur. Who knows? Might be fun?
OK, here goes:
Please help. I have been trying to fix this for about 7 months. I first noticed this issue when I started traveling around the country, from hotel to hotel. While others (PC's and Mac's) had no trouble connecting to the free wifi at these hotels, I did. I kept getting "self-assigned i.p."
This was extremely frustrating. I often had to call up the i.t. guys and ask them to help me manually put in ip address, subnet mask, router (gateway), and dns. This worked much of the time but not always.
Let me also say that, sometimes it worked perfectly! I'd say about 25% of the time (at these hotels) my internet worked perfectly – just connected immediately. The other 75... "self-assigned i.p."
I just spoke to the mac "geniuses" and they told me it's not an issue with my computer at all (either hardware or software). Are you kidding me?!?! How can they explain everyone else's internet working except mine. And I'm talking like 100 or more different hotels in a 4 month period. They were trying to tell me that it was just a coincidence every time! "You'd be surprised" one guy said. Hahaha. They said that the routers aren't accepting my computer's whatever. OK, well WHY?! The router works for everyone but me. It's something wrong with my computer right?! Well no one acknowledged this.
More background info:Just had my airport card and logic board replaced. Computer came back and the sheet said "passed all hardware tests." BUT, none of my issues (I had other ones too involving battery life and not being able to access certain websites) were fixed.
I went to an apple store. They told me to do an erase and reinstall or whatever. So I did that (by dragging and dropping everything I'd saved on an external hard drive using disk utility). By the way, I also upgraded from leopard to snow leopard. So now, if I have the same issues after this I'll know both leopard and snow leopard are screwed up.... right?
OK, so I followed their instructions on deleting and reinstalling to a tee and guess what?! Everything worked! Or so it seemed. Battery fine. Websites now accessible. I figured the airport issue was fixed too. But now that I'm not touring anymore and the airport works in my house, I never encountered any issues. Until now. At my work.
I got a new job and it's one in which I HAVE to have a computer that connects to the internet. So of course, the same issue with self assigned i.p. presents itself. Everyone else in the office has no problem. Including a Mac person that used to work there.
I've been reading some other threads that are just completely confusing me. One of them might be the solution but I thought I'd detail my troubles so that some smart computer person out there can diagnose my specific problem and give me a specific fix.
I noticed that many people believe there was a bug in one of the 10.5 updates. I am pretty quick to install updates (maybe I shouldn't be because I hear that the first updates are often buggy and maybe you should wait for a while). But this problem has continued now with Snow Leopard too so... I don't know. I don't know anything anymore. I have tried everything. And Apple is telling me it's not a problem with my computer. Give me a break.
One more interesting quirk: before doing the erase and reinstall my computer could not find the Apple Store's network. After the erase and reinstall it works. That's why I assumed everything was fine! But no. And now the Mac people are saying there's no problem because they can't see it.
BTW, I have tried all the obvious things. It's not an obvious thing. But I mean, if you think it is... then tell me I guess. But I've been in the advanced tab thousands of times. I feel like I've exhausted everything in there.
Thank you thank you thank you in advance if someone is actually able to solve my issue.

continuation of console log:
Feb 1 13:08:45 localhost kernel[0]: npvhash=4095
Feb 1 13:08:45 localhost kernel[0]: PAE enabled
Feb 1 13:08:45 localhost kernel[0]: 64 bit mode enabled
Feb 1 13:08:45 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
Feb 1 13:08:45 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
Feb 1 13:08:45 localhost kernel[0]: standard timeslicing quantum is 10000 us
Feb 1 13:08:45 localhost kernel[0]: migtable_maxdispl = 73
Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Quarantine
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Sandbox
Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Feb 1 13:08:45 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 1 13:08:45 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Feb 1 13:08:45 localhost kernel[0]: MAC Framework successfully initialized
Feb 1 13:08:45 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Feb 1 13:08:45 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Feb 1 13:08:45 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Feb 1 13:08:45 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
Feb 1 13:08:45 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
Feb 1 13:08:45 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string> <key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Feb 1 13:08:45 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Feb 1 13:08:45 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
Feb 1 13:08:45 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0 /AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver /IOAHCIBlockStorageDevice/IOBlockStorageDriver/FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
Feb 1 13:08:45 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Feb 1 13:08:45 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
Feb 1 13:08:46 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
Feb 1 13:08:46 localhost kernel[0]: systemShutdown false
Feb 1 13:08:47 localhost kernel[0]: NVDANV50HAL loaded and registered.
Feb 1 13:08:47 localhost kernel[0]: Previous Shutdown Cause: 5
Feb 1 13:08:47 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
Feb 1 13:08:47 localhost kernel[0]: DSMOS has arrived
Feb 1 13:08:47 localhost kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
Feb 1 13:08:47 localhost kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Feb 1 13:08:56 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
Feb 1 13:09:05 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:12:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:15:38 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:15:39 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image path: /var/vm/sleepimage
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: sizeof(IOHibernateImageHeader) == 512
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 5
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernateallocpages flags 00000000, gobbling 0 pages
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: System SafeSleep
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall start
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall time: 114 ms
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: pages 274489, wire 35250, act 50684, inact 887, spec 62, zf 137, throt 0, could discard act 24613 inact 28670 purgeable 6142 spec 128044
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall found pageCount 87020
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen(0)
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: writing 86158 pages
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image1Size 73471488
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: PMStats: Hibernate write took 4108 ms
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: all time: 4108 ms, comp time: 592 ms, deco time: 0 ms,
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image 166148608, uncompressed 353234944 (86239), compressed 162715248 (46%), sum1 dc78ee00, sum2 4fe372a2
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatewriteimage done(0)
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: sleep
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Wake reason = UHC3
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: System Wake
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Previous Sleep Cause: 0
Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: USB (UHCI)ort 2 on bus 0x5d has remote wakeup from some device
Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 13:41:09 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:50:04 Michael-Pines-MacBook-Pro kernel[0]: IOHIDSystem::relativePointerEventGated: VBL too high (33307137), capping to 20000000
Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: systemShutdown true
Feb 1 15:24:13: --- last message repeated 1 time ---
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext loading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext unloading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext autounloading now disabled.
Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kernel requests now disabled.
Feb 1 15:24:32 localhost kernel[0]: npvhash=4095
Feb 1 15:24:32 localhost kernel[0]: PAE enabled
Feb 1 15:24:32 localhost kernel[0]: 64 bit mode enabled
Feb 1 15:24:32 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
Feb 1 15:24:32 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
Feb 1 15:24:32 localhost kernel[0]: standard timeslicing quantum is 10000 us
Feb 1 15:24:32 localhost kernel[0]: migtable_maxdispl = 73
Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Quarantine
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Sandbox
Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Feb 1 15:24:32 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 1 15:24:32 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Feb 1 15:24:32 localhost kernel[0]: MAC Framework successfully initialized
Feb 1 15:24:32 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Feb 1 15:24:32 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Feb 1 15:24:32 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Feb 1 15:24:32 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
Feb 1 15:24:32 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
Feb 1 15:24:32 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key> <string ID="1">IOResources</string><key>IOResourceMatch</key> <string ID="2">boot-uuid-media</string></dict>
Feb 1 15:24:32 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
Feb 1 15:24:32 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
Feb 1 15:24:32 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0 /IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriv er /FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
Feb 1 15:24:32 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
Feb 1 15:24:32 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
Feb 1 15:24:33 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
Feb 1 15:24:33 localhost kernel[0]: systemShutdown false
Feb 1 15:24:44 localhost kernel[0]: Previous Shutdown Cause: 5
Feb 1 15:24:44 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
Feb 1 15:24:44 localhost kernel[0]: NVDANV50HAL loaded and registered.
Feb 1 15:24:44 localhost kernel[0]: DSMOS has arrived
Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
Feb 1 15:24:51 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
Feb 1 15:24:52 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
Feb 1 15:25:35 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

Self-assigned IP !!! Can't connect via Ethernet

Hi all,
This is my problem:
- Now every time I connect my MBP (running 10.6.4) to my hall's network (staying on campus, in uni) it appears as "Self-assigned IP" and cannot connect to the internet for the Ethernet. It suddenly happened a few days ago and I have no clue what caused that
- Airport's working well
- Using Windows on Parallels and can still connect to the Internet despite that the Mac OS X does not at the same time, my friends' laptops have no problems as well
- Tried taking the IP, subnet mask, router( I suppose in Windows it is called Gateway ) details and typing in manually for the Ethernet settings on OSX but still cannot connect to the Internet. The status is Connected and "Ethernet is currently active and has the IP address 137.xxx.xx.xx."
- When I bring my laptop to a different place and connect via Ethernet, it works well, too, I just leave the setting to be "Using DHCP"
I've seen that lots of people have met this issue, also loads of advices have been given:
- reset the router ... --> I'm connecting to the hall's network, so that's impossible for me to do
- sudo ipfw list , sudo ipfw flush .. --> nothing changed afterwards
- someone suggested uninstalling any VMware --> tried uninstalling parallels desktop and the problem's still there
- untick the "Use Passive FTP Mode" for ethernet --> no difference
- Security settings ,Firewall --> firewall was even off when the issue 1st appeared
So ANY SUGGESTIONS PLEAAASSSSSSSSSEE !!!! I'm sick of having to turn to Windows just to access the internet
Thanks in advance

fr1d4y13 wrote:
Apart from this one "*4) In the folder /Library/Preferences (not <yourhomefolder>/Library/Preferences), move the folder SystemConfiguration onto the Desktop, then restart your computer. See if you can now make your AirPort connection work.* " , I've tried all the other ways suggested but didn't work.
I'm wondering what it means by "move" here :? Is that "copying and then delete the original" :??
A "move" operation is normally considered equivalent to (although more efficient) than "copying and delete the original". Just drag the folder out of its original folder and onto the Desktop, which will make it be no longer in its original folder.
I've seen others post advice about moving out specific files in that folder. That probably works just as well if not better (as it leaves in place other files not involved in networking), but I haven't spent the time to determine just which files should be moved.

Self assigned ip address-Could someone help me?

There are two Powerbooks in my house which connects wirelessly to the internet and an airport express that joins the existing wireless connection.
When I'am using mine, I can connect without any problem, but when my girlfriend uses her mac we both get the self-assigned ip address. The only way to connect after that is by reseting the router.
This is what i did in both computers after I read some posts here (BUT THE PROBLEM CONTINUES) and I don't know what else to do:
"....1. Reset Open Firmware. As you turn on the machine, press & hold CmdOption+OF until you get a screen that says "Welcome to Open Firmware". At the prompt, enter "reset-nvram" (without the quotes). Press return. Enter "reset-all". Press return and the machine will restart.
2. Open network preferences. In airport, go to advanced. Check the box that says disconnect the wireless network when logging out. (It seems incredible that it would work, but apparently it sometimes does.)
3. Restart in "Safe" mode (hold down "Shift" while restarting). Once in Safe mode simply restart again in regular mode. http://docs.info.apple.com/article.html?artnum=306879
4. Go into your keychain and find the password key for your network. If you connect to a WAP it will be the name of that WAP. Then in the key click on the access control tab. It probably shows selected applications. Change this to "Allow all applications to access this item"........"
Thanks.
K.

My wife's PB G4 was doing the same thing. Worked fine at the Apple Store but had issues on my all Apple network at home. After resetting the routers, recreating the network etc I finally disabled the firewall and all seems to be working.

"Self-Assigned IP"

I just bought a new +Macbook Pro+ and have been using the internet on it for at least 3 weeks with no problems up until today. A "*Self-Assigned IP*" error is showing and I have tried everything to fix it. I am using a Netgear router if that means anything. Any suggestions or solutions to this problem?

Not sure why this happens, but the same problem came up on my wife's 13 inch MacBook. Here's what we have to do to get it working: Go into System Preferences, select Security, select Firewall, and check Allow All Incoming Connections. Select Show All at the top, select Network and see if an IP address has been assigned. This usually fixes her problem and then it works fine for months. Just make sure you go back to the Security and Firewall and put the selection back to where it was to begin with.

Self-assigned IP address problem - My solution

I am new to this board and created an ID just to write this post. When I searched for this self-assigned IP problem, I found almost 1 million results on Google so obviously I am not alone.
I have this problem off and on on the wireless network at home with a Netgear router. It has never happened at my office with a D-Link router. Never happened at Starbucks or McDonalds (yes, they all offer WiFi here). But it happened at one Pizza Hut and it also at Christchurch airport about a week ago.
Deleting one of the plist files worked once at home many months ago but this week nothing worked. My Mac usually goes back to normal by itself after I "****" it out at other WiFi networks but not this time. As a last resort, I asked my brother (our family's I.T. guy) to change the router as I had not tried that fix. He didn't do it but a day later, he gave me to oddest solution that worked in a blink of an eye.
The solution? Key in a wrong password!!!
1) Go to Keychain Access, delete the keychain for the problematic network.
2) Connect back to the network
3) Enter a WRONG password that is similar to the right one. For example, if your password is Apple123, try APPLE123. You should still connect to the network and get a self-assigned IP.
4) Repeat Step 1. To be safe, you might want to re-boot now. I did but probably didn't have to!
5) Repeat Step 2
6) Enter the right password
I'm not all that techie so all I understood from what he said was:
1) It's probably a non-Apple router bug
2) It's a hex key problem. The password wasn't being encoded/decoded properly so the router wasn't assigning the computer an IP address. Wasn't even reading the password which is why I could connect with a wrong one.
He deduced that from reading a post from a guy in Spain who thought he had carelessly entered the wrong password and was wasting the community's time with his posting. I had read that post a couple of days ago too! But obviously I thought the Spaniard had just entered the wrong password and there was no fix for me to try out. My brother is a genius!
I guess it then makes sense why fixes like:
1) Disabling the firewall
2) Deleting preference lists
3) Deleting keychains
4) Changing the router
5) Renewing DHCP lease
6) Resetting the router
...have worked for many people and not others. None of them actually fix the cause of the problem. Having searched for 3 days, I could not find the REAL reason why this happened. Personally from all I have read, I think it must be a hex key problem with Netgear and Linksys routers. I see those 2 names mentioned a **** of a lot. Maybe it's another one of those gadgets built more for PCs that don't work perfectly with Macs all the time. We used to have an Apple Airport Extreme base station but that got fried by lightning. It was not cheap.... So technically, it really isn't Apple's problem. I think if we used an Apple router, we wouldn't have a self-assigned IP address. Maybe that's why they haven't "fixed" the problem after so many years.
Anyway, let me know if my brother's fix worked for you.
This is my good deed for the weekend! Goodnight....!

Hello, thanks for the tip/post, & a warm welcome to the forums!

Self Assigned IP / DHCP problem : sharing my fix.

Okay. I WAS frustrated for a long two weeks before I figure this out. It seems that this problem has affected a LOT of people out there, and since I now am (supposedly) free of this thing, I want to share my hypothesis of the problem's roots (A) and my fix (B).
Note that:
- i'm free of this problem since the last one week, so .. well, hopefully this is right.
- the problem happens almost anywhere, with any router types, and in any connection type, be it ethernet or wireless a/b/g/n.
- the problem is automagically fixed by running into safe mode.
- the problem keeps happening again and again, although you have powercycled everything of the electronic peripherals in your house, even by disconnecting your phone/ADSL line and main power fuse.
- disabling the Mac OS X Application Firewall sometimes cures it, but most of the time it happens again.
- AFAIK (correct me if i'm wrong), the ipfw, mother of all OS firewall, exists within Mac OS X, and the Mac OS X Application Firewall (i call this OSXAF) has nothing to do with ipfw.
A. My hypothesis and the reasons.
* for an unknown reason, there is a rule created for ipfw that tells it to block the ports 67 and 68, both are the common DHCP ports.
* because of that, your Mac cannot contact with any DHCP servers, anywhere. This forces your mac to assign an IP address by itself.
* disabling OSXAF incidentally removes that rule, but after (one or a few times) reconnect or reboot, the rule appears again.
* powercycling your routers or anything related does not concern ipfw, thus has no effect whatsoever to the problem.
B. My fix.
1. Get the WaterRoof free ipfw frontend (forgot the site, just google)
2. Open it.
3. Go to Static Rules part.
4. Find everything which reads "deny blah blah blah port blah,blah,67,68,blah blah"
5. Edit those rules so that there is no 67 and 68 inside.
6. Open tools -> rules configuration -> save to startup configuration -> yes.
7. Open tools -> startup script -> install startup script -> yes.
That's all.
For me, this seems to be a permanent fix. Please note that the startup script mentioned before exists in all *nix-based machines, so don't worry about startup time, there'll be no slowdowns (again, please correct me if i'm wrong, i had only little experience with *nixes). Besides, i suspect that if you don't save and reinstall that script, the previous script is the one which has 67 and 68 inside.
Hopefully this helps. Any corrections, comments, suggestions, and/or knowledge are welcome.
Cheers,
-bam, the noob.

OK, so a little background -
I have an MBP with 10.5.5 (which I downloaded yesterday, so that's not the issue). This year at school they upgraded the wireless system and network control to Foundry routers and Bradford Securities Network Control. Problem is, my computer is intermittently and randomly having a hard time sticking with one IP and staying away from a self-assigned 169 IP. The System Prefs are fine, and even when I change to manual settings for the IP, it doesn't stick. I checked the terminal (tcpdump) and it seemed to be having a tough time accepting one of the two IPs the servers offered (there are two servers for redundancy). It asked for an IP, gets two offers, and then asks again. I was stumped, and so were the IT guys on campus. And it's not just me, many other 10.5 users are having the issue. And it's not the network, because nobody else is having the issue but 10.5 users. Certificate problems are similarly eliminated from possibility.
The IT guy showed my this thread, and I was excited, so I first tried to just shut off the Firewall all together, and that worked, briefly, but now it doesn't matter if the Firewall is on or off, the problem persists. I tried your WaterRoof method, and the similar program NoobProof, but there were no rules relating to ports 67 or 68 at all, let alone denying them. (As a side note, when my FW is off, there's only the rule allowing all IPs in and out, and when it's on (but only allowing specific programs) it gives a second rule that denies "icmp from any to me in imcptypes 8." No idea what that means.) I've been watching tcpdump and the FW logs closely (as well as the console itself), but nothing has changed. The only interesting thing is that when the IP changes from the (good) 137 IP I'm supposed to have to the (bad) 169 IP, often times (in fact, most times) there is no firewall activity. The console says that the en1 link (wireless) is now down, and the tcpdump picks up the computer asking for an IP again, but the firewall logs pick up nothing, neither through the console or through WaterRoof. Which is weird, because I thought it was a FW problem (as did the IT guys), but the logs show that only occasionally when the servers offer me an IP does the FW block the request, but not all the time.
As another point to note, this is not only an issue with the wireless. The wired connection (Ethernet right into the wall, and attempted from many different plug-in sites) also has this issue.
My only conclusion is that the FW is buggy, or that the logs are missing denials, neither of which makes much sense, IMHO.
Any thoughts?
EDIT: Shutting off the FW often solves the problem, but not always. Sometimes I can get a correct IP even with the FW in full swing without anything popping up in the logs. And sometimes I can't.
Message was edited by: kangasaurus

Self-Assigned IP via router - no internet access - HELP!

Hi all,
I have 10.5.7 leopard installed on my C2D Macbook.
In the past, I never had any issues connecting to wireless routers with internet connection.
As of late, I am currently getting 'Self assigned IP address' which does not allow me to connect to the internet. It is connected to the router, but just no internet access. I can see the other Shared computers (Windows PC and mate's macbook pros) but just no web access. And they do not have a problem connecting to the internet.
I have attempted the following:
1) Turned on & off Airport.
2) Deleted network connections and re-created them, rebooted in safe & PRAM modes.
3) Deleted router Key chain permissions & changed permissions to 'access all'.
4) Deleted plist files from /Library/Preferences/SystemConfiguration/
5) Off Firewall & verified against the logs to ensure it is disabled.
6) Re-installed 10.5.7 combo updates.
7) Rebooted router, changed router channel, etc. Router is on the latest Netgear firmware.
8) Assigned IP address and entered the DNS, router values manually in Leopard.
9) Clicked on renew DHCP lease several thousands to no avail..
Occasionally, DHCP will work. But once I reboot & awake the mac the internet connection drops and 'Self Assigned IP' happens.
Does anyone else have any ideas? My only conclusion is that the bug is in Leopard 10.5.7.

Make sure your router has the latest firmware. If you are out of range of the WiFI or in a marginal area, this error simply indicates that your computer is not able to access an internet router/server and simply assigns the default IP address which is of the form 169.254.xxx.xxx. Basically it's a flag that lets you know you are not connected to a DHCP server.

Airport self-assigned IP address, no internet

We got a new router from Verizon and my Mac will not connect. Network Status gave this message: 'Airport is connected to the network xxxxxx. Airport has a self-assigned IP address and may not be able to connect to the Internet.
How do I fix this an get connected to the internet?
Thanks in advance,
Mike from Baltimore

I have also encountered this problem and I have been researching it all over the internet all evening and trying everything I could find a suggestion for. Here's what I have: Two G4 Powerbooks, one is a 550MHz 15" Powerbook, the other is a 1.5 GHz 17" Powerbook, they are both running 10.4.11 with all the updates that Software Update has to offer, the 17" is connecting via built in Airport Extreme card, the 15" is connecting via Sonnets Aria Extreme PC card. I have AT&T DSL and I'm using the 2Wire modem/router they provided me with. Neither of the Powerbooks can connect wirelessly to the internet. Furthermore, they cannot even ping the wireless router. 4 days ago, both were connecting without any trouble (and had been able to reliably every day since the beginning of August when I hooked everything up). I have made no changes to my router's settings over the weekend. Nor had I made any changes to the Powerbooks' settings during that time. It just stopped working. If I wire one or both of them to the router with ethernet cables, connection works fine. My Desktop G4 which is normally wired into the router via ethernet, connects fine so I know my internet service is available.
So far, I've restarted both machines numerous times, restarted the router numerous times. Reset the WEP password. Changed the wireless security to WPA. Changed it back to WEP. Trashed the airport plist. deleted every wireless network entry in Keychain. Disabled DHCP and assigned IP numbers manually. Changed the wireless channel (I've tried 1, 6, and 11 with and without interference robustness).
I've been reading posts about this issue on half a dozen web forums (dating back to as early as June 2004). It appears to affect a variety of routers (2Wire, Netgear, Linksys), a variety of machines (Powerbooks, iBooks, MacBookPros, iMacs) a variety of OSes (10.3, 10.4, 10.5).
This thing is really getting me down. Anybody have any other ideas?

WiFi self assigned IP and no internet connection after OS & iTunes upgrade

I have two likely related issues that started as a direct result of upgrading to OS X 10.8.5 and/or iTunes 11:
Starting tonight, after upgrading my OS and iTunes I am no longer able to use Home Sharing between my iMac and Apple TV. Apple TV is logged in to my network and Home Sharing is on, on both devices (signed in to the same account), but Apple TV says Home Sharing is not connecting to my iMac. My iPhone 5 is also not showing a Home Sharing connection.
I've restarted both my iMac and Apple TV several times. Logged in and out several times. Turned Home Sharing off/on several times, power cycled and reset my network modem once.
While trouble shooting my Home Sharing connection I noticed that under my Network settings, Wi-Fi is yellow instead of green and reads "Self-Assigned IP... Wi-Fi has the self-assigned IP address xxx.xxx.xxx.xx and will not be able to connect to the Internet.".
When I go back to Apple TV I've found that althought it's connectted to my iMac through WiFi and I can see my purchased movies I can't view them becasue there is no connection to the iTunes Store (no internet coinnection through WiFi). But my actual network connection on my iMac is just fine.
So it seems that my new OS or iTunes upgrade has caused my WiFi to no longer allow an internet connection across teh wireless network.
Can anybody here tell me why that would happen and how can I fix it?
Any help is greatly appreciated,
David

Back up all data before making any changes.
Step 1
Take all the applicable steps in this support article.
Step 2
If you're running OS X 10.8.4 or later, run Wireless Diagnostics and take the remedial steps suggested in the summary that appears, if any. The program also generates a large file of information about your system, which would be used by Apple Engineering in case of a support incident. Don't post the contents here.
Step 3
If you're not using a wireless keyboard or trackpad, disable Bluetooth by selecting Turn Bluetooth Off from the menu with the Bluetooth icon. If you don't have that menu, open the Bluetooth preference pane in System Preferences and check the box marked Show Bluetooth in menu bar. Test. Continue if you find that Wi-Fi is faster with Bluetooth disabled.
From that same menu, select Open Bluetooth Preferences. If the box labeled Discoverable is checked, uncheck it. Click the Advanced button, and in the sheet that opens, uncheck the top three boxes, if any are checked. Click OK. Enable Bluetooth and test again.
If the application called "Bluetooth Setup Assistant" is running, quit it.
Step 4
This step will erase all your settings in the Network preference pane. Make a note of them before you begin, and recreate them afterwards. It may be helpful to take screenshots of the preference pane.
Triple-click the line below on this page to select it:
/Library/Preferences/SystemConfiguration
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu.* A folder should open with an item named "SystemConfiguration" selected. Move the selected item to the Trash. You may be prompted for your administrator password.
*If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). In the Finder, select
Go ▹ Go to Folder...
from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.
Step 5
Reset the System Management Controller.
Step 6
Make a "Genius" appointment at an Apple Store, or go to another authorized service center.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional — ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

Why ASA creates self assigned certificate on each reboot

Hi Everyone,
I noticed
"By default, the security appliance has a self-signed certificate that is regenerated every time the device is rebooted. We can purchase your own certificate from vendors, such as Verisign t, or you can configure the ASA to issue an identity certificate to itself. This certificate remains the same even when the device is rebooted.
Need to know the reason behind the creation of self assigned certificate on each reboot?
Regards
MAhesh

Hello Mahesh,
As you mention that's by default and by desing,
That would help us in the case we set a SSL session to the box (Anyconnect, ASDM) as we will not need to go a step further and manually create or generate an SSL certificate,
Why?
Because the firewall will do it automatically, altough if you purchase one from a CA you can overwrite it by installing the certificate and set it as the SSL certificate for any SSL session,
For Networking Posts check my blog at http://laguiadelnetworking.com/
Cheers,
Julio Carvajal Segura

Self Assigned IP + Firewall Disabled = No security?

Similar Messages

Maybe you are looking for