Create Network Not Working

I have created a network on my mac which my ipod touch has successfully connected to. When I try to use Remote and 1Password, my mac will detect the ipod but in the case of remote, when I enter the code my ipod displays it just verifies for ages in itunes then stops. What is wrong?
Thanks for your time,
Declan

Howdy infernalcolonel,
It would be helpful if you gave a bit more info about the symptoms other than "it never works".
It sounds like you might be trying to create the ad-hoc wireless network from the Airport menu item and then trying to turn internet sharing on. In fact the Airport settings for this type of sharing are set up via the "Airport Options" button that is on the Internet Sharing pane.
Check that your Airport menu icon changes to a grey segment with an upward pointing arrow, and also click on it to verify the name of the network it has created.
I'd suggest that for first attempts you create your wireless network without a password and once you can successfully connect to that, implement a password.
If you've still got problems post a message back here with some more info about what exactly you're observing and doing.

Similar Messages

Macbook create network not working

Hi
Every time I try to Create Network from my Wifi dropdown menu, I get a "Connection Failed" error message. My laptop is connected via a Huauwei Modem. I've set up Internet Sharing correctly in Sharing (tick Internet Sharing box- Share your connection from: HUAWEIMobile Modem- To computers using WiFi). But when I try and start the connection nothing happens.
Any suggestions? Much appreciated!

Hi
Every time I try to Create Network from my Wifi dropdown menu, I get a "Connection Failed" error message. My laptop is connected via a Huauwei Modem. I've set up Internet Sharing correctly in Sharing (tick Internet Sharing box- Share your connection from: HUAWEIMobile Modem- To computers using WiFi). But when I try and start the connection nothing happens.
Any suggestions? Much appreciated!

MacBook Air wifi internet shared network not working on tethered android phone GT B5122

MacBook Air wifi internet shared network not working on tethered android phone GT B5122
I have created a password protected wifi internet network on my Macbook air. I tethered by Andriod phone onto this network, but the internet connection works intermittently on the phone, and when it stops working the network continues to show as connected to the shared network mostly(other times it keeps renewing the wifi IP address on the Andriod phone).
Also the network the MBA is connected to, is a hardwired one using a SSH login account in a student accomadations.
I am not sure, but all the restarting and refreshing of system, phone and wifi sharing and re-enabling wifi is not reparing the internet connecting on the wifi network for the phone
Really puzzled, if this is one of the Apple, Andriod compatability issues.
Cheers,
Vivek

Spanners91 wrote:
Hi.
I'm having trouble with the wireless connection on my new home hub 3. Most devices will connect easily, but there are three devices that have trouble connecting. These are an Android Phone (Samsung Galaxy Mini), an android tablet (Sony Tablet S) and an iPod. All of these devices work perfectly on other network connections, and other devices in the house are quite happy connecting to the network.
The Androids can see the network, and will try to connect to it, but when they do they just go through a loop of "connecting">>"acquiring IP address">>"disconnected". I have tried resetting the Home Hub with a pin, and that lets the devices connect for about 24 hours, but after that time they stop connecting again.
I'm really not sure what to do to fix the problem, so I will very much appreciate some help.
Many Thanks.
My lads SGMini connects perfectly to our hub3
Have you installed the BTFon app to these devices?
If so, you could delete it and then see what hapens.....
-+-No longer a forum member-+-

Extending wireless network, not working?

ive been trying to set up a new wireless network for a few days now and while i got this network up and running i still doubt if its exactly what i want.
i have extreme(n), time capsule(n) and an express(n). im using the extreme as my "base" which is connected to the internet and both the capsule and express are connected by wires. but whenever i use the setting "extend a wireless network", the stations will just become undetectable and not working at all. so to get my network to work i configured them all with "create a wireless network" giving them all the same network name which is working fine. but is this even roaming?

Welcome to the discussions!
When you are having extending difficulties, it's often helpful to temporarily locate the Express near your main router...across the room or in an adjacent room and test to see if that works.
If things worked fine for 6 months and suddenly you have problems, that may indicate that a new wireless network near you has been added at one of your neighbors, which is causing interference on your network.
Cordless phones are a real problem as well. My neighbor...across the street....can literally knock me off my network if he is in his front hard talking on his cordless phone. I found this out simply by accident, otherwise I would still be blaming Apple for stuff that worked fine for months and then suddenly did not work.
If the Express works close to the main router, then move the Express further away and test again. Most users locate the Express too far away from the main router when they try to extend a wireless network. A good starting location is a point that is about 1/2 to 2/3 of the distance between the main router and the area that needs more coverage.
Open AirPort Utility and click on your AirPort Express on the left and look for its AirPort ID on the right. Jot that down.
When you are testing the extension of the Express, move your laptop close the Express, and hold down the option key on your Mac while you click on the fan shaped AirPort icon at the top of the screen. Look for the BSSID. This should match the AirPort ID of the Express, indicating that your computer is connecting to the AirPort Express.

[Solved] Arch and virtual networking, not working as planned.

Running pfSense trough virtualbox, running virtual machines behind it.
What setup do I need, to get wireless LAN solely to pfSense. Currently I use the bridged setup in virtualbox as the WAN side. LAN is a host only adapter vboxnet0, all other VM's connect through that virtual adapter.
I would like to use a second host only adapter on a different subnet, but, once I create the adapter vboxnet1 and add it as second LAN card OPT1 to pfSense, internet stops working on the first LAN, though I can still ping google from the pfSense box.
How do I get Arch to not use the wireless connection but only the second host only adapter.
At the moment I use NetworkManager for the network.
Current setup (working):
Router – 192.168.1.1
Arch bare hardware, main OS – 192.168.1.9 (wireless)
pfSense WAN - 192.168.1.12 ( through wireless)
pfSense LAN - 10.10.2.1
host only adapter vboxnet0 - 10.10.2.3
I would like to add (not working):
pfSense OPT1 - 10.10.10.1
host only adapter vboxnet1 - 10.10.10.3
But this fails for unknown reasons.
What do I miss, or should I do different, thanks in advance, Mark
Last edited by qinohe (2015-01-30 12:39:32)

All is working well. I extended to four virtual adapters, one for the Arch host, and a wireless AP connected to eth0, bridged to pfSense. All applications on the host are finding the pfSense squid proxy, I have libproxy installed. Set the default gateway on the host to be the proxy of pfSense.
Now I can use my laptop to connect to insecure networks while not belonging to it, and host for friends at the same time, very nice

Help - Airport network not working - confused!!

Hello, I wonder if anyone out there can help. I have got a problem with my airport network that doesn't make any sense and I havent seen another post with the same problems.
I have an imac G5 with 10.3.9. I have a wireless network set up, with an airport wireless card and two ax boxes (the second was bought later to boost the signal when we moved the Mac to another room). Initially it set up fine and worked for about 8-9 months. Then I noticed the second ax started behaving strangely. It would occasionally turn from 'green' to flashing amber for no reason - often after it had been on for a while. Turning it off and on did not change anything. Usually though it would work again the next day after being off all night. This continued to happen randomly until a couple of months later it switched to flashing amber continually.
I thought it had 'lost' the network so I tried using the airport set up assistant to reconnect it. However the set up assistant does not recognise ax number 2 any more, so I am not able to reconnect it. At the moment I am running off a faint signal from ax number 1.
I also tried setting up a completely new network from scratch. Again the new network is fine from the base ax bx but ax number 2 is still not recognised by my mac.
I also have a wireless printer connected to the network which does not work any more. This is where things became more confusing. The printer needs a boost signal to operate so when my booster ax went wrong the printer would not work. So I moved the printer and mac nearer ax number 1 to ensure it would pick up the network. However it still didn't work. So I attempted to set up the printer as wireless again, thinking it had become 'disconnected' somehow. However during installation you have to select the network to connect to. The computer would not pick up the apple network at all from ax number 1, yet it easily recognises our neighbours network from the flat above us. Strangely when I tried turning on the faulty ax box, the printer set up program picked up the faulty ax and not the original ax. But obviously I can't use the printer from the faulty ax box because it doesnt connect to the rest of the network.
So now I am confused. I am not sure what has gone wrong and what I need to replace. Originally I thought it was the second ax box that had gone wrong. But as the printer software can identify the second ax box I am not sure that this is the problem. Could there be something wrong with the airport card? I have checked that the card is properly connected and there is nothing visibly wrong there.
If anyone can help - please reply as I am going crazy here with things not working and don't know what to do next.
Thanks, Wrenster

Hello Wrenster,
I understand why you are confused, I was too while reading your post. However I have the solution for you. I believe you are a victim of environmental interference. Someone in your neighborhood just moved in with a another network, someone had a baby and is using a baby monitor, or maybe a local ham radio operator just got his license. Who knows!
This is what you need to do. Get all the devices in the same room and preform a hard restart on each one them per http://docs.info.apple.com/article.html?artnum=108044. Remember to preform a hard restart! After performing a hard restart on all three devices check the wireless networks available. You should have 3 ( one main and 2 airport expresses) ( or two depending on how many airports you own, I am not sure from your post). If you don't have the correct amount you may a bum base station and it may need to be replaced. But if you have the correct number of wireless networks ( Apple network XXXXXXX), use the airport admin utility ( inside of the utility folder ) to locate the main base station and configure it.
You will know when you are on the configuration page when you can read Name, Contact and Location.
First change the name to the location of the main base station, ie; it is the den so name should read DEN. leave the contact and location alone. On the bottom half of the page is where you create your network, so under network name change it to your desired network name ie; when others come over to my house I have them select COWSWEAT from the network list.
Second click on the change wireless security and set the security to WEP 128 BIT and make your password. Once you have configured a successful password be sure to click on the lock on the main configuration page ( the one with password under it) to get the HEX password for your PC friends.
Third ( we are almost done ) Select the WDS tab at the top and enable this base station as a main station. Select allow other wireless client on this base station as well. Now on that empty list box below click the plus sign to the right to add other base stations to this WDS network. From here you should be able to select the other 2 base station that we have not configure yet ( but preformed a hard restart on). After you have added them ( be sure the check box for auto configure is selected) they should read in the list that was empty on the WDS page.
Now update this should start the update process and may take 5-10 mins, it should provide a summery pop-up when with each station is done.
( Also you may get a message that there is update for the base station, please preform the updates for the selected base stations)
Now when it is completed check to see how many networks you have available ( it should only be one ). Select the network and confirm that all of your base stations appear under the select a base station in Airport admin utility, then move them back to their homes around the house. Giving them 45 secs to restart they should turn green if not , they could out of range of each other or the environmental interference could be affecting them. So you my need to rearrange them until they all green.
Good Luck,
Cowsweat

PIX 501 config - access to internal network not working from remote VPN users - everything on the inside is OK

One other thing - I had a problem with the key pairing so I rebuilt the rsa 1024 and the unit started working. Unfortunately I reloaded without the config in place and now I cannot get it to work again. Any help will be greatly apprecaited although I did review a dozen other posts of people having similar problems and for some reason there is never any conclusion as to the solution and I am not sure why.
Some other info from the client end:
I just ran the stats on the client and packets are being encrypted BUT none are decrypted.
Also Tunnel received 0 and sent 115119
Encryption is 168-bit 3-DES
Authentication is HMAC-SHA1
also even though the allow LAN is selected in the Cisco VPN client it states the local LAN is disabled in the client stats
also Transparent tunneling is selcted but in the stats it states it is inactive
I am connecting with the Cisco VPN Client Ver 5.0.07.0440
This config works. It is on the internal net 192.168..40.x and all users obtain dhcp and surf the web. It has required ports opened.The problem is that you can connect remotely via the VPN and you receive an IP address from the remote-vpn pool but you cannot see any machines on the internal network. The pix is at 40.2 and you cannot ping the pix and the pix from the remote PC connecting via the VPN and youcannot ping the remote PC from the PIX console when the remote is connected and receives the first IP address in the VPN pool of 192.168.40.25
I need to see the internal network and map network drives. I have another friend that is running the same config and it works but his computer is on a linksys wireless and has an IP of 192.168.1.x and the IP he receives from the VPN pool is 192.168.1.25 so I do not know if the same network is allowing this config to work even if there is an error in the config. In my present case I obtain the ip of 192.168.40.25 from the VPN pool and my connecting pc on 192.168.1.x I really am not sure how the VPN virtual adapter works. I am assuming it routes all traffic from your connecting PC to and from the virtual adapater but I really do not know for sure.
Other people have had similar issues with accessing the internal network from the VPN. One solution was the split-tunnel, another was the natting and another had to do with the encrption where there and an issue with the encrypt and ecrypt which was stopping the communicaton via the VPN.
I still cannot seem to find the issue with this config and any help will be greatly appreciated.
This is the config
interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password somepassword
hostname hostname
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
object-group network internal_trusted_net
network-object 192.168.40.0 255.255.255.0
object-group icmp-type icmp_outside
icmp-object echo-reply
icmp-object unreachable
icmp-object time-exceeded
icmp-object source-quench
access-list OutToIn permit icmp any xxx.xxx.xxx.0 255.255.255.248 object-group icmp_outside
access-list no_nat_inside permit ip 192.168.40.0 255.255.255.0 192.168.40.0 255.255.255.0
access-list split_tunnel permit ip 192.168.40.0 255.255.255.0 192.168.40.0 255.255.255.0
access-list OutToIn permit ip any any
access-list outbound permit ip any any
(NOTE: I had many more entries in the access list but removed them. Even with the above two allowing everything it does not work)
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.xxx 255.255.255.248
ip address inside 192.168.40.2 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_client_pool 192.168.40.25-192.168.40.30
pdm history enable
arp timeout 14400
global (outside) 1 interface
I had this statement missing from the previous posted config but even with the nat (inside) 0 access-list no_nat_inside it still does not work.
nat (inside) 0 access-list no_nat_inside
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group acl_outside_in in interface outside
access-group outbound in interface inside
route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.40.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community $XXXXXX$
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set 3des_strong esp-3des esp-sha-hmac
crypto dynamic-map clientmap 50 set transform-set 3des_strong
crypto map vpn 50 ipsec-isakmp dynamic clientmap
crypto map vpn client configuration address initiate
crypto map vpn client configuration address respond
crypto map vpn client authentication LOCAL
crypto map vpn interface outside
isakmp enable outside
isakmp identity address
isakmp client configuration address-pool local vpn_client_pool outside
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash sha
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup remote-vpn split-tunnel split_tunnel
vpngroup remote-vpn idle-time 10800
vpngroup remote-vpn password ANOTHER PASSWORD
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh 192.168.40.0 255.255.255.0 inside
ssh timeout 30
console timeout 60
dhcpd address 192.168.40.100-192.168.40.131 inside
dhcpd dns xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd enable inside
username AUSER password PASSWORD privilege 15
terminal width 80
****************** End of config
I have been searching docs and other people's postings trying to obtain the info to make this work. It appears pretty much boiler plate but I believe my problem is in the natting. I am using a range in the internal network for the VPN pool and I have tried switching this to other networks but this has not helped. Unfortunately I have been unable to get the PDM to work and I believe this is a PC config thing and I did not want to waste the time on it. I read a post where a person using the PDM interface with the same problem (not being able to access the internal network) was able to go to a section in the VPN wizard and set the Address Exeption Translation. They said they originally set the VPN subnet when they did not have to. Many of the other blogs I read also stated that if the natting is not proper for the VPN pool- that it will not work but I am confused by the examples. They show as I do the complete range for an access-list called no_nat_inside but I believe it should only have the VPN pool IP range and not the entire network since the others do require natting - not sure if my thought process is correct here. Any help will be greatly apprecaited. Also this morning I just tried a boiler plate example from CISCO and it also did not do what I need for it to do. And I also connect a PC to obtain an IP to see if I can see it - no good. The PC can ping the PIX and viceversa but no one can ping the remote PC that connects via the CISCO Remote VPN client even though it receive an address from the vpnpool. Also include LAN is checked off on the client. This was mentioned in anther post.
Thank you once again.

Hi,
PIX501 is a very very old Cisco firewall that has not been sold for a long time to my understanding. It also doesnt support even close to new software levels.
If you wanted to replace the PIX501 the corresponding model nowadays would be ASA5505 which is the smallest Cisco ASA firewall with 8 switch port module. There is already a new ASA5500-X Series (while ASA5505 is of the original ASA 5500 Series) but they have not yet introduced a replacing model for this model nor have they stopped selling this unit. I have a couple of them at home. Though naturally they are more expensive than your usual consumer firewalls.
But if you wanted to replace your PIX firewall then I would probably suggest ASA5505. Naturally you could get some other models too but the cost naturally rises even more. I am not sure at what price these are sold as used.
I used some PIX501 firewalls at the start of my career but have not used them in ages since ASA5505 is pretty much the firewall model we use when we need a firewall/vpn device for a smaller network/branch site.
Here is a PDF of the original ASA5500 Series.
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps6032/ps6094/ps6120/prod_brochure0900aecd80285492.pdf
Here is a PDF of the new ASA5500-X Series
http://www.cisco.com/en/US/prod/collateral/vpndevc/ps6032/ps6094/ps6120/at_a_glance_c45-701635.pdf
I am afraid that its very hard for me atleast to troubleshoot this especially since I have not seen any outputs yet. Also the very old CLI and lack of GUI (?) make it harder to see what the problem is.
Could you provide the requested outputs?
From the PIX after connection test
show crypto ipsec sa
Screen captures of the VPN Client routing and statistics sections.
- Jouni

Bridged networking not working with nested VMware Workstation

I am having an issue that I can't seem to find any answer to....
We are running Vsphere 5.5 and I have 2 Guests each running Windows 7 64-bit. Each of these guests has VMware Workstation 10 running on them. When we P2V the systems we followed all the instructions to allow nested VMware Workstation. However, we are running into an issue where the Bridged Networking will not work. Both of the Win7 guests are on the same vlan and all of the VMs in Workstation are on the same network as well. However, while the 2 Windows 7 guests can ping each other and each of the guests can ping the VMs that are hosted locally, they cannot connect to the systems on the other guest running workstation.
I tried to upgrade the Guest NIC to VMXNet3, but that did not help.
All of the research I have done brings me to people who are having the opposite problem (ESXi nested in VMware Workstation).
How can I get the 2 bridged networks to connect?
Thanks!

The ESXi vSwitch to which the outer guests are connected must be configured for promiscuous mode and forged transmits.

Mpd --create-db not work?

$ mpd --create-db
$ cmdline: invalid option: --create-db
why?--create-db did not work for mpd anymore?

Its unbelievable. this option is gone for 6 years now. and people still complain

EA4500 Guest Network not working

A few days ago I saw there was an upgrade for my router. I clicked on it and away I went. Since updating my guest network isn't working. My android and Kindle HD find the guest network, attach but no prompt for password ever shows up like it did before. The web page will time out and die. Does anyone have a clue why my devices don't prompt for a password anymore?

cperficio wrote:
A few days ago I saw there was an upgrade for my router. I clicked on it and away I went. Since updating my guest network isn't working. My android and Kindle HD find the guest network, attach but no prompt for password ever shows up like it did before. The web page will time out and die. Does anyone have a clue why my devices don't prompt for a password anymore?'i clicked on it and away it went' could be the problem. as much as linksys would like to think it works that way, it has been shown time and time again that the best way to update is to:download the update file to a pc with a wired connection factory reset the routerflash the file from that wired pcfactory reset againconfig from scratch not a backupyou might try to do a factory reset and config and see if it clears the issue. also on those devices that are not working try forgetting the connection and connect again.

Guest Network not working in latest Airport Extreme

Just bought the latest Airport Extreme (802.11ac), and want to enable the Guest Network.
- Installed latest firmware
- Set Airport in Bridge Mode
- Enabled Wireless Network
- Enabled Guest Network
There is no connecting to Guest Network (iphone) and if possible (macbook) there is no internet.
With a previous version of Time Capsule, the Guest Network in the same setting worked like a charm.
Anybody seen this before or is the Airport Extreme working different than a Time Capsule?

According to the theory what you are saying about the A1355 is not possible.. ie there is no guest in bridge.. I have tested it and can assure you it did NOT work.. it fooled me into thinking it should and I spent many hours working on it.. our forum expert here.. Bob Timmons set me straight.
Now I am always a believer in voodoo and gremlins and maybe the tooth fairy when it comes to wireless.. it is about 80% of the above and 20% science.. so please do the test again and see if it is possible.. but I can assure you.. apple have set guest network to off in bridge.
There are ways around it.. complicated methods. ie if you extend wireless to your TC.. from another apple router where the router is on, then guest can be used. You can also use a managed switch to set vlans for the guest.
See the following which I used to research this topic.
Guest network in bridge.
https://discussions.apple.com/thread/2815541?start=15&tstart=0
https://discussions.apple.com/thread/3617532
https://discussions.apple.com/thread/5247107?start=0&tstart=0
https://discussions.apple.com/thread/4787934?start=45&tstart=0
https://discussions.apple.com/message/23127620#23127620
Good Luck.. !!

Wireless Network Not Working In Bootcamp

I have an early 2006 MacBook Pro running on Snow Leopard and I just ran Bootcamp and installed Windows Xp Pro Service Pack 2. My wireless network adaptor is an Atheros AR5006X. I've installed the drivers in Windows from the Snow Leopard disc and the hardware is recognized, and wireless networks are detected. But I can't connect to any network. I've tried going into Advanced Settings, disabled firewall, I've tried manually setting it up as a preferred network, and I've tried a few other versions of the Atheros drivers from the Internet. Nothing has worked. It always says,
"Windows is unable to connect to the selected network. The network may no longer be in range. Please refresh the list of available networks, and try to connect again."
The signal strength can even be strong and it still won't connected. I never had this problem when I first used bootcamp with the same windows xp sp2, and with the original Leopard drivers disc that you burned when configuring bootcamp.
Please help. Thanks.

There are a number of discussions on this topic. In my previous response, I was referring to the first thread:
Wireless Mouse and Keyboard Not Working in Boot Camp
http://discussions.apple.com/thread.jspa?messageID=6415376&#6415376
I got my wireless keyboard to work in Bootcamp/XP
http://discussions.apple.com/thread.jspa?messageID=6314636&#6314636
keyboard & mouse stop working after apple driver install
http://discussions.apple.com/thread.jspa?messageID=6276210&#6276210
It seems that the basic theme is that if you already installed the Leopard drivers, you will need a non-wireless (USB) keyboard to use/fix it. At this point, you will then need to go and setup the bluetooth to the wireless keyboard. My wireless mouse worked, so that was not a problem -- just the keyboard. I tried using the USB keyboard and seting up the bluetooth to the wireless keyboard, but I could not get it to recognize the bluetooth keyboard. It seems to recognize it for a brief instant, and then report and error.
I've gotten tired of iterating over this issue, so I haven't read through all of the threads. There may be a better one out there that I've missed...

Post install issue: network not working

Hi. I've installed arch and after install just issued full system upgrade (pacman -Syu). But after reboot, my network is not working anymore (can't ping even my gateway). In my rc.conf i have line
interface=eth0
so i am using dhcp. But as i said, network was working before full system upgrade (packages were downloaded). I think something must be wrong with module b44. This is output of dmesg:
b44 ssb1:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb1:0: eth0: Flow control is off for for TX and off for RX
b44 ssb1:0: eth0: powering down PHY
b44 ssb1:0: eth0: Link is down
b44 ssb1:0: eth0: powering down PHY
b44 ssb1:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb1:0: eth0: Flow control is off for for TX and off for RX
b44 ssb1:0: eth0: powering down PHY
b44 ssb1:0: eth0: Link is down
b44 ssb1:0: eth0: powering down PHY
This keeps repeating every few seconds. I tried manually restart network via /etc/rc.d/network restart, but it's still not working.

The network restarts without error?
Weird, do you see anything in pacman.log for that upgrade when processing the hooks?
Try unloading (modprobe -r b44) and loading (modprobe -i -v b44) the driver and look in the logs again then perhaps.

Guest Network Not Working On Airport Time capsule

Whenever I enable the guest network and join it, it joins fine. but it wont load any webpages or the app store, or anything. all the devices im trying to connect, connect to the guest network fine. but they just wontt get wifi signal from the TC.
I can get the normal and 5GHz network to work.
I have the TC router connected to a Tp Link modem and setup as its own network.
If i change the router mode on the TC to DHCP and NAT it works but the amber light flashes on the TC which annoys me. then it stops working and i end up having to change under network in airport utility to off (bridge mode)
Please help somebody???
Any help will be much appreciated

Check the client is getting proper DNS address .. there is a bunch of bugs..
The main bug is that guest network does not actually work when the TC is in off bridge mode.. it looks like it is going to work but it doesn't.
The TC must be the main router of the network..
So bridge your TP-Link and use PPPOE client in the TC if that is allowed by your ISP.
Or simply ignore the double NAT and then the light will go green and not bother you any more..
Or an even better solution.. use the TP-Link wireless for guest.. and use the TC in bridge for main network.. there is nothing wrong with doing that.. and in fact it will work far better since guest network is still sharing the wireless on the TC and slowing it down.

Wireless Network not Working as expected. Please Help

I have Verizon Fios install in my home. I use to have Comcast. This is the situation, before the Fios my linksys wireless router was connected directly to a modem. Now my linksys wireless router is connected to the Verizon wireless router/modem.
The problem I am having is this, my linksys wireless router is still transmitting and the new Verizon router is also transmitting. I can connect to both but only the Verizon wireless router seem to be working.
The linksys wireless router, even though I can connect to its network, is not working, that is I can't go on the internet with it.

You have to configure the router for DSL connection. Try these steps: Access the setup page of the router by launching an Browser and type on the address bar, 192.168.1.1 and press enter. When it prompts for the username and password, leave the username field empty and provide password as "admin" (Without quotes)
click on ok. On the main setup page the ""Internet Connection Type"" should be
on ""Obtain IP Automatically - DHCP “. Click on the Save Settings button.
Now click on the sub tab ""MAC address clone"".- Click on enable
Click Clone & click save settings Check WAN Ip on Status page of router ....
If getting Valid Ip .... try going online If you are getting Ip - 192.168.1.X ...change the LAN Ip to 192.168.2.1 ....Power cycle for 3-4 minutes ...Try going online
If still not working ...use Internet Connection type as PPPOE .... Use Username & Password provided by Service Provider ....Click save settings....
Look for WAN IP address again under status page ....

Create Network Not Working

Similar Messages

Maybe you are looking for