9360 7.1.0.714 Problem Sharing Internet

Hi all people with BlackBerry.
This problem i have writen dynamically!!! and updatet when i upload other screenshot.
I have little problem with share internet on my BlackBerry 9360 7.1.0.746
We have in Poland free internet on UMTS 900Mhz to the end 2016 Year. On LTE is free to the end 2019.
Yes, absolute free!!! Max download is 64kB/s And this internet reconnect every one hour.
I try in my mom Samsung Galaxy Mini 2 phone and on this phone all working GREAT!
But on BlackBerry not working with OS 7.1!
Little campare device:
-Samsung can share 8 connections
-BlackBerry max 5.
Ok, now i share screenshot whats going on.
When i configure Samsung Galaxy Mini 2 with SIM AERO2 everything working great. I can share internet to my BlackBerry 9360 and my laptop
Ok, now i upload some screenshot from my blackBerry 9360 and show you what is wrong
And now i click Mobile Sharing...
And when i click Yes i got this ***** message:
And i see only this screen:
Automaticaly Mobile Hotspo turn off
Whats is going on with BlackBerry?
Samsung Galaxy dont have problems to share internet and BlackBerry cant share???
I'm flustrating this situation...
And other options:
AERO2 have APN only darmowy
No required aditional information.
This is home page this operator:
AERO2 Homepage
*On BlackBerry Device(Not router choice but directly) internet works.

Sorry, I meant BlackBerry CAN share
If you have an answer to your question then please click “Accept as Solution”
Click on the LIKE on the bottom right if the post deserves credit.
BB 8700 -> Bold 9000 -> Curve 8520 -> Bold 9700 -> Curve 9320 -> Bold 9900 -> BlackBerry Z10 + PlayBook 64 GB Wi-Fi

Similar Messages

Problems sharing internet connection - works only one way...

hey all,
i'm having a problem sharing my internet connection between our "new" iBook G4 and "old" iMac G5. (both machines are running 10.4.10.) i've seen several posts here that seem related, but no answers that have worked in my case.
here's the gist:
ideally, i'd like share the internet connection from the iMac (from our cable modem) to the iBook over the airport. so, i've set up the iMac to do this under "sharing" in system preferences. i then set up the iBook to connect to this new wireless network. under "network status", it says the iBook is connected to the iMac's network, but that the iBook doesn't have its own IP address, so it can't connect to the internet.
oddly, when i reverse the process - i.e. plug the modem into the iBook and share the connection over the airport to the iMac - it works fine. the iMac gets its own IP address and can see the internet.
a friend suggests that somehow the iBook is set up to distribute IP addresses as a router, but the iMac isn't. fine. but, i don't know how to make changes to that function.
any thoughts?

well, it's taken all day - many, many attempts. but i've finally found something that worked. the answer was burried in the middle of this guy's blog page:
http://www.tuaw.com/2007/03/26/how-to-using-your-mac-as-a-nat-router/
he says:
"I've turned off DHCP and set the address to: 192.168.0.1 and the subnet to 255.255.255.192 In making these choices I was following a hint that appeared at macOSXhints back in 2002. Once this is done I went back to the Internet tab of Sharing Preference Pane, select en4 and start it.
"Now on my other device (in this case a Xbox 360) I set it up as follows:
"IP address: 192.168.0.2 subnet: 255.255.255.192 (this is the same subnet of the en4 USB interface, above) gateway/router: 192.168.0.1 (this is the address of the en4 interface) DNS: 192.168.2.1
"(here's where the voodoo comes in, I have no idea why this DNS setting works. You would think it should be 192.168.0.1, or even the DNS server of my ISP, but those simply do not work. I suspect that it has something to do with sharing over Airport as well).
"I've also found that this will only work properly if Internet Sharing is active for my Airport interface. If I turn off the Airport interface (en1), the wired interface (en4) also dies. With these settings in place, everything seems to work properly. Keep in mind you may also need to enable certain services (which will vary with your application) in the Services tab of the Sharing Pane:"
i wasn't trying to solve quite the same problem he was, but by manually inputting the IP addresses, etc, that he did, as well as randomly enabling other "sharing" options (FTP access, etc) which seemed unrelated to internet sharing, it finally worked.
can anyone explain what this is about? it all seems pretty cryptic to me. i'm not sure what i even did...
no complaints, but it would be interesting to know.
thanks!

Problems sharing internet over Airport extreme

I have a PowerBook G4 (OS 10.4.11) with a USB wireless broadband modem connected to the internet. I bought each of my daughters a MacBook (OS 10.5), and the idea was for me to have my laptop connected to the internet, then use internet sharing via my airport extreme card so that the girls could access the internet from my connection across airport.
I have no problem using my wireless broadband to connect to the internet. I have no problem firing up my airport extreme and creating the network, and I have no problem creating the internet share. I all seems to be working at my end. On the girls MacBooks, we have no problem firing up airport and connecting to the airport network I created. However, when we fire up safari, all we get it "you are not connected to the internet".
I'm lost. Any ideas?

cdelahoy, Welcome to the discussion area!
On your PowerBook G4 do you have the firewall enabled? If so, try go to System Preferences-> Sharing preference pane and enabling Personal Web Sharing. That should open the ports needed to give Internet access to the MacBooks.
If that doesn't work, try disabling the firewall on the PowerBook G4.

Problems sharing internet connection over airport

Hi everyone-
I've researched the heck out of the forums and still cant figure out what's happening with my system. I've got a MacBook Pro with OS 10.5.2. In previous OS versions (10.4) when I was successfully sharing my ethernet internet connection, the airport icon in the status bar showed a vertical "up" arrow, indicating that my connection was being shared.
I'm trying to do the same thing in OS 10.5.2 but not succeeding in getting the same notification. I'm finding that when I access the "Sharing" folder under "System Preferences" and select "Share your internet connection from: ethernet" and "To computers using: Airport" that both settings grey out, the "Internet Sharing" button turns green and the status says "On", but no sharing occurs. I've checked using other wireless laptops and a wifi finder, but no signal from my MacBook is ever found.
I've deleted my preferences folder to start fresh, no help. I've tried sharing from different ethernet sources, no help. It just feels like the problem is in the OS somewhere, not with the internet connection.
Any insight or help would be greatly appreciated! Thanks!

seems like i got the same issue as u and i just posted it:
http://discussions.apple.com/thread.jspa?threadID=1425809

Having problems sharing internet Connection from Macbook to Vonage Adapter

Hello,
I just got my Vonage adaptor and I am trying to share the Internet connection from my Macbook Pro (10.7.3) to the Adaptor to use the Vonage service bc my router is downstairs.
I turned off my Firewall, hooked my Vonage adapter to the Macbook with the ethernet cable and then went to Sys Preferences > Sharing > Selected Internet Sharing > Share Connection from Wifi to computers using Ethernet, and it looks like everything is ok but when i try to use the phone which is connected to to Vonage Adapter, it says "Your Vonage device cannot connect to the internet, check to see if your high speed internet is down".
I went and looked at my Network preferences and it shows Ethernet connected which is the Vonage Adapter and gives the following:
IP Address: 169.254.163.167
Subnet Mask: 255.255.0.0
Is there something Im doing wrong? Ive seen on several forums that its possible to do but having bad luck. Any help is appreciated.

All I know is that I got Ubuntu to share internet and offer IPs through DHCP by using Firestarter. I am very new to Solaris, however, and am looking forward to learning about it. I've just made it my regular desktop environment. Long as you can get Solaris to configure its network interface with DHCP after your Ubuntu is configured, you should be able to share to as many clients as you'd like. Fedora also works well for that, and in my opinion, it's a better Linux than Ubuntu, though Solaris remains a better Linux than Linux, right? Har.

Problems sharing internet to macbook over wifi and bluetooth

I have an iPhone 5S with iOS 7.1.2 and I want to share its internet connection to a Macbook Pro (early 2011) with OS X Mavericks 10.9.4.
When I share using USB connection, it works fine, but with Wifi and Bluetooth I have some issues:
- Bluetooth: I have never been able to make this work. I can't pair the iPhone with the Macbook. The iPhone appeared in the list of bluetooth devices in my mac, and I tried to pair it; in the iPhone a dialog asked me to confirm if I wanted to pair with the mac, and I selected Yes. After a few seconds it disconnected. If I try to pair from my iPhone to the mac, I get an error message "Device not compatible".
- Wifi: this sometimes works but is very buggy. Sometimes the iPhone wifi network is not visible to my mac. Other times, when I select the wifi network in the mac, I get an error message that says it was not possible to connect. I have to turn off/on the wifi and internet sharing in the iPhone several times to make it work.
This is all very frustrating. Is there a way to fix this?

Same issue here with WiFi using latest iOS version on iPad Air and latest Macbook Pro. In my opinion, "Personal Hotspot" (or tethering) is totally broken on iOS.
WiFi tethering works once and then I need to enable/disable hotspot or enable/disable WiFi to make it work again. Bluetooth is so slow it's unusable. Even over USB I have to reset the iPad a couple times a day as the internet connection is displayed as online but just not working any more. Very disappointing. "it just works (not!)".

Problems sharing internet connection through Airport with a PS3

Does anybody know how to share an internet connection wirelessly with a PS3? I've tried everything including following directions from the tech support people from both Sony and my ISP (Verizon) and nothing works. Last time I've talked to Verizon I've obtained a IP number from them as Sony recommended and that did not work either. Is anybody out there with a PS3 sharing the internet connection through Airport successfully? I'd really appreciate any help. Thanks.!!
Message was edited by: pbranda

Let's double-check your Mac's Internet Sharing settings ...
To setup for Internet Sharing (Wired to Wireless):
Setup the Network
Cable Modem > (Ethernet cable) > \[Ethernet port] Mac > (wireless) > PS3
Enable Software Firewall
System Preferences > Security > Firewall
o Block all incoming connections (enabled)
Enable Internet Sharing
System Preferences > Sharing
o Select "Internet Sharing" from the options in the left column
o Share your connection from: Built-in Ethernet
o To computers using: AirPort (checked) (Note: Uncheck all other entries in the list.)
AirPort Options...
o Network Name: <anything you want>
o Channel: Automatic
o Enable encryption (using WEP) (optional)
o Password: (optional)
o Confirm Password: (optional)
o WEP Key Length: (optional)
o Click OK
o Select "Internet Sharing" again
o Click "Start" to start Internet Sharing
o Click Start

Problems sharing internet with iptables and dnsmasq

I followed this exactly: http://wiki.archlinux.org/index.php/Internet_Share
And here is my dnsmasq.conf
# Configuration file for dnsmasq.
# Format is one option per line, legal options are the same
# as the long options legal on the command line. See
# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
# The following two options make you a better netizen, since they
# tell dnsmasq to filter out queries which the public DNS cannot
# answer, and which load the servers (especially the root servers)
# uneccessarily. If you have a dial-on-demand link they also stop
# these requests from bringing up the link uneccessarily.
# Never forward plain names (without a dot or domain part)
#domain-needed
# Never forward addresses in the non-routed address spaces.
#bogus-priv
# Uncomment this to filter useless windows-originated DNS requests
# which can trigger dial-on-demand links needlessly.
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
# This option only affects forwarding, SRV records originating for
# dnsmasq (via srv-host= lines) are not suppressed by it.
#filterwin2k
# Change this line if you want dns to get its upstream servers from
# somewhere other that /etc/resolv.conf
#resolv-file=
# By default, dnsmasq will send queries to any of the upstream
# servers it knows about and tries to favour servers to are known
# to be up. Uncommenting this forces dnsmasq to try each query
# with each server strictly in the order they appear in
# /etc/resolv.conf
#strict-order
# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.
#no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.
#no-poll
# Add other name servers here, with domain specs if they are for
# non-public domains.
#server=/localnet/192.168.0.1
# Example of routing PTR queries to nameservers: this will send all
# address->name queries for 192.168.3/24 to nameserver 10.1.2.3
#server=/3.168.192.in-addr.arpa/10.1.2.3
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
#local=/localnet/
# Add domains which you want to force to an IP address here.
# The example below send any host in doubleclick.net to a local
# webserver.
#address=/doubleclick.net/127.0.0.1
# --address (and --server) work with IPv6 addresses too.
#address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
# You can control how dnsmasq talks to a server: this forces
# queries to 10.1.2.3 to be routed via eth1
# --server=10.1.2.3@eth1
# and this sets the source (ie local) address used to talk to
# 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
# IP on the machine, obviously).
# [email protected]#55
# If you want dnsmasq to change uid and gid to something other
# than root, you will need to have CONFIG_SECURITY_CAPABILITIES
# enabled in your kernel. The default uid and gid of nobody will
# be used if capability is available and this is not set.
#user=
#group=
# If you want dnsmasq to listen for DHCP and DNS requests only on
# specified interfaces (and the loopback) give the name of the
# interface (eg eth0) here.
# Repeat the line for more than one interface.
interface=eth0
# Or you can specify which interface _not_ to listen on
#except-interface=
# Or which to listen on by address (remember to include 127.0.0.1 if
# you use this.)
#listen-address=
# If you want dnsmasq to provide only DNS service on an interface,
# configure it as shown above, and then use the following line to
# disable DHCP on it.
#no-dhcp-interface=
# On systems which support it, dnsmasq binds the wildcard address,
# even when it is listening on only some interfaces. It then discards
# requests that it shouldn't reply to. This has the advantage of
# working even when interfaces come and go and change address. If you
# want dnsmasq to really bind only the interfaces it is listening on,
# uncomment this option. About the only time you may need this is when
# running another nameserver on the same machine.
bind-interfaces
# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
#no-hosts
# or if you want it to read another file, as well as /etc/hosts, use
# this.
#addn-hosts=/etc/banner_add_hosts
# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.
#expand-hosts
# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
# as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
# domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"
#domain=thekelleys.org.uk
# Set a different domain for a particular subnet
#domain=wireless.thekelleys.org.uk,192.168.2.0/24
# Same idea, but range rather then subnet
#domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
# Uncomment this to enable the integrated DHCP server, you need
# to supply the range of addresses available for lease and optionally
# a lease time. If you have more than one network, you will need to
# repeat this for each network on which you want to supply DHCP
# service.
#dhcp-range=192.168.20.100,192.168.20.149,12h
# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.
dhcp-range=192.168.20.100,192.168.20.149,255.255.255.0,12h
# This is an example of a DHCP range with a network-id, so that
# some DHCP options may be set only for this network.
#dhcp-range=red,192.168.0.50,192.168.0.150
# Supply parameters for specified hosts using DHCP. There are lots
# of valid alternatives, so we will give examples of each. Note that
# IP addresses DO NOT have to be in the range given above, they just
# need to be on the same network. The order of the parameters in these
# do not matter, it's permissble to give name,adddress and MAC in any order
# Always allocate the host with ethernet address 11:22:33:44:55:66
# The IP address 192.168.0.60
dhcp-host=00:E0:B8:9C:B7:2C,192.168.20.1
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
# Always give the host with ethernet address 11:22:33:44:55:66
# the name fred and IP address 192.168.0.60 and lease time 45 minutes
#dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m
# Give a host with ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
# that these two ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.
#dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60
# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infinite lease
#dhcp-host=bert,192.168.0.70,infinite
# Always give the host with client identifier 01:02:02:04
# the IP address 192.168.0.60
#dhcp-host=id:01:02:02:04,192.168.0.60
# Always give the host with client identifier "marjorie"
# the IP address 192.168.0.60
#dhcp-host=id:marjorie,192.168.0.60
# Enable the address given for "judge" in /etc/hosts
# to be given to a machine presenting the name "judge" when
# it asks for a DHCP lease.
#dhcp-host=judge
# Never offer DHCP service to a machine whose ethernet
# address is 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,ignore
# Ignore any client-id presented by the machine with ethernet
# address 11:22:33:44:55:66. This is useful to prevent a machine
# being treated differently when running under different OS's or
# between PXE boot and OS boot.
#dhcp-host=11:22:33:44:55:66,id:*
# Send extra options which are tagged as "red" to
# the machine with ethernet address 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,net:red
# Send extra options which are tagged as "red" to
# any machine with ethernet address starting 11:22:33:
#dhcp-host=11:22:33:*:*:*,net:red
# Ignore any clients which are specified in dhcp-host lines
# or /etc/ethers. Equivalent to ISC "deny unkown-clients".
# This relies on the special "known" tag which is set when
# a host is matched.
#dhcp-ignore=#known
# Send extra options which are tagged as "red" to any machine whose
# DHCP vendorclass string includes the substring "Linux"
#dhcp-vendorclass=red,Linux
# Send extra options which are tagged as "red" to any machine one
# of whose DHCP userclass strings includes the substring "accounts"
#dhcp-userclass=red,accounts
# Send extra options which are tagged as "red" to any machine whose
# MAC address matches the pattern.
#dhcp-mac=red,00:60:8C:*:*:*
# If this line is uncommented, dnsmasq will read /etc/ethers and act
# on the ethernet-address/IP pairs found there just as if they had
# been given as --dhcp-host options. Useful if you keep
# MAC-address/host mappings there for other purposes.
#read-ethers
# Send options to hosts which ask for a DHCP lease.
# See RFC 2132 for details of available options.
# Common options can be given to dnsmasq by name:
# run "dnsmasq --help dhcp" to get a list.
# Note that all the common settings, such as netmask and
# broadcast address, DNS server and default route, are given
# sane defaults by dnsmasq. You very likely will not need
# any dhcp-options. If you use Windows clients and Samba, there
# are some options which are recommended, they are detailed at the
# end of this section.
# Override the default route supplied by dnsmasq, which assumes the
# router is the same machine as the one running dnsmasq.
#dhcp-option=3,1.2.3.4
# Do the same thing, but using the option name
#dhcp-option=option:router,1.2.3.4
# Override the default route supplied by dnsmasq and send no default
# route at all. Note that this only works for the options sent by
# default (1, 3, 6, 12, 28) the same line will send a zero-length option
# for all other option numbers.
#dhcp-option=3
# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
# Set the NTP time server address to be the same machine as
# is running dnsmasq
#dhcp-option=42,0.0.0.0
# Set the NIS domain name to "welly"
#dhcp-option=40,welly
# Set the default time-to-live to 50
#dhcp-option=23,50
# Set the "all subnets are local" flag
#dhcp-option=27,1
# Send the etherboot magic flag and then etherboot options (a string).
#dhcp-option=128,e4:45:74:68:00:00
#dhcp-option=129,NIC=eepro100
# Specify an option which will only be sent to the "red" network
# (see dhcp-range for the declaration of the "red" network)
# Note that the net: part must precede the option: part.
#dhcp-option = net:red, option:ntp-server, 192.168.1.1
# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0 # option ip-forwarding off
#dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,0.0.0.0 # netbios datagram distribution server
#dhcp-option=46,8 # netbios node type
# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
# probably doesn't support this......
#dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
# Send RFC-3442 classless static routes (note the netmask encoding)
#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
# Send vendor-class specific options encapsulated in DHCP option 43.
# The meaning of the options is defined by the vendor-class so
# options are sent only when the client supplied vendor class
# matches the class given here. (A substring match is OK, so "MSFT"
# matches "MSFT" and "MSFT 5.0"). This example sets the
# mtftp address to 0.0.0.0 for PXEClients.
#dhcp-option=vendor:PXEClient,1,0.0.0.0
# Send microsoft-specific option to tell windows to release the DHCP lease
# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
# value as a four-byte integer - that's what microsoft wants. See
# http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
#dhcp-option=vendor:MSFT,2,1i
# Send the Encapsulated-vendor-class ID needed by some configurations of
# Etherboot to allow is to recognise the DHCP server.
#dhcp-option=vendor:Etherboot,60,"Etherboot"
# Send options to PXELinux. Note that we need to send the options even
# though they don't appear in the parameter request list, so we need
# to use dhcp-option-force here.
# See http://syslinux.zytor.com/pxe.php#special for details.
# Magic number - needed before anything else is recognised
#dhcp-option-force=208,f1:00:74:7e
# Configuration file name
#dhcp-option-force=209,configs/common
# Path prefix
#dhcp-option-force=210,/tftpboot/pxelinux/files/
# Reboot time. (Note 'i' to send 32-bit value)
#dhcp-option-force=211,30i
# Set the boot filename for netboot/PXE. You will only need
# this is you want to boot machines over the network and you will need
# a TFTP server; either dnsmasq's built in TFTP server or an
# external one. (See below for how to enable the TFTP server.)
#dhcp-boot=pxelinux.0
# Boot for Etherboot gPXE. The idea is to send two different
# filenames, the first loads gPXE, and the second tells gPXE what to
# load. The dhcp-match sets the gpxe tag for requests from gPXE.
#dhcp-match=gpxe,175 # gPXE sends a 175 option.
#dhcp-boot=net:#gpxe,undionly.kpxe
#dhcp-boot=mybootimage
# Encapsulated options for Etherboot gPXE. All the options are
# encapsulated within option 175
#dhcp-option=encap:175, 1, 5b # priority code
#dhcp-option=encap:175, 176, 1b # no-proxydhcp
#dhcp-option=encap:175, 177, string # bus-id
#dhcp-option=encap:175, 189, 1b # BIOS drive code
#dhcp-option=encap:175, 190, user # iSCSI username
#dhcp-option=encap:175, 191, pass # iSCSI password
# Test for the architecture of a netboot client. PXE clients are
# supposed to send their architecture as option 93. (See RFC 4578)
#dhcp-match=peecees, option:client-arch, 0 #x86-32
#dhcp-match=itanics, option:client-arch, 2 #IA64
#dhcp-match=hammers, option:client-arch, 6 #x86-64
#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
# Do real PXE, rather than just booting a single file, this is an
# alternative to dhcp-boot.
#pxe-prompt="What system shall I netboot?"
# or with timeout before first available action is taken:
#pxe-prompt="Press F8 for menu.", 60
# Available boot services. for PXE.
#pxe-service=x86PC, "Boot from local disk", 0
# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
#pxe-service=x86PC, "Install Linux", pxelinux
# Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
# Beware this fails on old PXE ROMS.
#pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
# Use bootserver on network, found my multicast or broadcast.
#pxe-service=x86PC, "Install windows from RIS server", 1
# Use bootserver at a known IP address.
#pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
# If you have multicast-FTP available,
# information for that can be passed in a similar way using options 1
# to 5. See page 19 of
# http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
# Enable dnsmasq's built-in TFTP server
#enable-tftp
# Set the root directory for files availble via FTP.
#tftp-root=/var/ftpd
# Make the TFTP server more secure: with this set, only files owned by
# the user dnsmasq is running as will be send over the net.
#tftp-secure
# Set the boot file name only when the "red" tag is set.
#dhcp-boot=net:red,pxelinux.red-net
# An example of dhcp-boot with an external TFTP server: the name and IP
# address of the server are given after the filename.
# Can fail with old PXE ROMS. Overridden by --pxe-service.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
# Set the limit on DHCP leases, the default is 150
#dhcp-lease-max=150
# The DHCP server needs somewhere on disk to keep its lease database.
# This defaults to a sane location, but if you want to change it, use
# the line below.
#dhcp-leasefile=/var/lib/misc/dnsmasq.leases
# Set the DHCP server to authoritative mode. In this mode it will barge in
# and take over the lease for any client which broadcasts on the network,
# whether it has a record of the lease or not. This avoids long timeouts
# when a machine wakes up on a new network. DO NOT enable this if there's
# the slighest chance that you might end up accidentally configuring a DHCP
# server for your campus/company accidentally. The ISC server uses
# the same option, and this URL provides more information:
# http://www.isc.org/index.pl?/sw/dhcp/authoritative.php
#dhcp-authoritative
# Run an executable when a DHCP lease is created or destroyed.
# The arguments sent to the script are "add" or "del",
# then the MAC address, the IP address and finally the hostname
# if there is one.
#dhcp-script=/bin/echo
# Set the cachesize here.
#cache-size=150
# If you want to disable negative caching, uncomment this.
#no-negcache
# Normally responses which come form /etc/hosts and the DHCP lease
# file have Time-To-Live set as zero, which conventionally means
# do not cache further. If you are happy to trade lower load on the
# server for potentially stale date, you can set a time-to-live (in
# seconds) here.
#local-ttl=
# If you want dnsmasq to detect attempts by Verisign to send queries
# to unregistered .com and .net hosts to its sitefinder service and
# have dnsmasq instead return the correct NXDOMAIN response, uncomment
# this line. You can add similar lines to do the same for other
# registries which have implemented wildcard A records.
#bogus-nxdomain=64.94.110.11
# If you want to fix up DNS results from upstream servers, use the
# alias option. This only works for IPv4.
# This alias makes a result of 1.2.3.4 appear as 5.6.7.8
#alias=1.2.3.4,5.6.7.8
# and this maps 1.2.3.x to 5.6.7.x
#alias=1.2.3.0,5.6.7.0,255.255.255.0
# and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
#alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
# Change these lines if you want dnsmasq to serve MX records.
# Return an MX record named "maildomain.com" with target
# servermachine.com and preference 50
#mx-host=maildomain.com,servermachine.com,50
# Set the default target for MX records created using the localmx option.
#mx-target=servermachine.com
# Return an MX record pointing to the mx-target for all local
# machines.
#localmx
# Return an MX record pointing to itself for all local machines.
#selfmx
# Change the following lines if you want dnsmasq to serve SRV
# records. These are useful if you want to serve ldap requests for
# Active Directory and other windows-originated DNS requests.
# See RFC 2782.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# If the domain part if missing from the name (so that is just has the
# service and protocol sections) then the domain given by the domain=
# config option is used. (Note that expand-hosts does not need to be
# set for this to work.)
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289 (using domain=)
#domain=example.com
#srv-host=_ldap._tcp,ldapserver.example.com,389
# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
# A SRV record indicating that there is no LDAP server for the domain
# example.com
#srv-host=_ldap._tcp.example.com
# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for PTR records.)
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for TXT records.)
#Example SPF.
#txt-record=example.com,"v=spf1 a -all"
#Example zeroconf
#txt-record=_http._tcp.example.com,name=value,paper=A4
# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
#cname=bertand,bert
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
# Log lots of extra information about DHCP transactions.
#log-dhcp
# Include a another lot of configuration options.
#conf-file=/etc/dnsmasq.more.conf
#conf-dir=/etc/dnsmasq.d
eth0 is set up for 192.168.20.1, netmask 255.255.255.0. I can get an IP from my client machine and ping 192.168.20.1, but cannot access the internet. resolv.conf on the client machine has a nameserver of 192.168.20.1. Also, Firefox time sout trying to access Google via it's static IP.
What should I do to grant the internet to my client machine?

http://wiki.archlinux.org/index.php/DNS_with_bind -> Did you try it too ?

Problems sharing internet- jaguar, leopard, wireless and ethernet

Hi
I have a MacBook with Leopard and an old iMac with Jag 10.2 on it my partner uses. We've just moved our house around and the router & airport station is now miles from the imac. The two macs are set up in the same room so I hooked up the imac and macbook with an ethernet cable with the idea that the imac could share the wireless connection via the macbook. I set up sharing on the Macbook to share the airport connection via ethernet but the connections isn't working. Any ideas anyone?

gave up and reconnected direct to modem

Problem with Internet connection sharing between eMac and Powerbook G3

Hi,
I seem to be having a slight problem with internet connection sharing.
My eMac is the main machine with the internet connection, and its running 10.4.6, the Powerbook G3 is running 10.2.8.
I can connect them all up and get online with both, but I the problem I am having is when I turn the Firewall on on the eMac, the powerbook can't connect.
Is there anyway I can keep the Firewall enabled and still use internet connection sharing?

How do I know which ports the Powerbook is using?
Also I had web sharing enabled on the eMac and it made no difference at all.
Plus I don't know if this means anything to you, trying to decipher it myself, all I can make out myself on there is port 80.
May 31 21:26:30 Craigs-Macintosh ipfw: 12190 Deny TCP 10.0.2.2:49743 67.15.24.40:80 in via en1
May 31 21:26:34 Craigs-Macintosh ipfw: Stealth Mode connection attempt to UDP 10.0.2.1:192 from 10.0.2.2:49531
May 31 21:26:34 Craigs-Macintosh ipfw: Stealth Mode connection attempt to UDP 10.0.2.1:192 from 10.0.2.2:49532
May 31 21:26:39 Craigs-Macintosh ipfw: Stealth Mode connection attempt to UDP 10.0.2.1:192 from 10.0.2.2:49533
May 31 21:26:39 Craigs-Macintosh ipfw: Stealth Mode connection attempt to UDP 10.0.2.1:192 from 10.0.2.2:49534
May 31 21:26:42 Craigs-Macintosh ipfw: 12190 Deny TCP 10.0.2.2:49743 67.15.24.40:80 in via en1
May 31 21:26:44 Craigs-Macintosh ipfw: Stealth Mode connection attempt to UDP 10.0.2.1:192 from 10.0.2.2:49535
May 31 21:26:44 Craigs-Macintosh ipfw: Stealth Mode connection attempt to UDP 10.0.2.1:192 from 10.0.2.2:49536
May 31 21:29:12 Craigs-Macintosh ipfw: 12190 Deny TCP 10.0.2.2:49746 17.254.0.91:80 in via en1
May 31 21:29:15 Craigs-Macintosh ipfw: 12190 Deny TCP 10.0.2.2:49746 17.254.0.91:80 in via en1

Problems with sharing internet connection via usb

I have been sharing the internet connection on my iPhone 5 via usb to a PC for a few years. When updating to iOS 8.3 and iTunes to 12.1 (from iOS 6 if I remember correctly) the internet sharing through usb stopped working. Sharing through wifi works and settings are the same as when usb internet share did work. Any idea on how to solve this except downgrading?
For my troubleshooting, has anyone been able to share internet via usb to PC (or Mac) with iOS 8 / iTunes 12.
PS I have unliited cellular data and iPhone is my only internet connection at home,

Mark,
There is a excellent book that teaches you how to do this (and other things) called Mac OS X Tiger: The Missing Manual (others of course)
If I remember correctly (book is on loan)
1: System Preferences>Network>Show>network port configurations (click unlock)
2: Click>Built in Firewire and drag to the top of the list (why I forget why)
3: System Preferences>Sharing>Internet>Share your connection from: Built in Ethernet (or what your using for your connection in) >To computers using: Built in Firewire>Start
4: Mac #2>Hook up Firewire 400 cable>System Preferences>Network>Location>New Location
5: Show>Network Port Configurations>Drag Built in Firewire to top of list and enable.
6: I also think you have to enable Personal Web Sharing on the Mac hosting the internet.
anyway play with it, you'll figure it out. if someone doesn't get to you.

TS2756 How can i create a new usb connection (service) on my iMac for sharing internet from my iPhone5 ( i seem have to deleted it )

How can i create a new usb connection (service) on my iMac for sharing internet from my iPhone5 ( i seem have to deleted it )
i know its not a problem whit my carrier o data plan or sharing preferences on the ipone because when i use it un my laptop it works perfectly through
the usb and even works on the Imac through wifi and bluethood tethering but NOT through usb!!.
the problem is that trying to make it work i deleted the "profile" usb iphone on the network prefereces panel. Now i only have 3 options: ethernet / wifi / bluetooth
but not the usb iPhone i used to have.
And when i try to add a new one i dont get a USB option.
can some one help me please??
this is how it looks (after the bluetooth PAN i used to have USB iPhone option)

The question would be more appropriate in the Mac forums as it is not really related to the iPhone.

Sharing internet connection from MacBook Pro to iMac G3

My goal here is to connect my iMac G3 (that I just got) to my cable internet connection. However, there are some hurdles in doing so. On the other side of my house lies my modem. It's connected to a D-Link wireless router to give my PC, Xbox 360, Wii and MacBook Pro internet all at the same time. It's too far to drag an ethernet cable, and the iMac G3 doesn't have an AirPort card (and $99 for a used wireless b adapter is ridiculous).
From what I've gathered online, OS X can share it's internet connection with another Mac via FireWire, ethernet or AirPort. AirPort is out of the question since that's how my MacBook Pro connects to the net, and since the iMac G3 doesn't have an AirPort card. I don't have anything that uses FireWire, so othe port on both machines is free, but I also don't have a cable to connect the two. I do, however, have a few spare ethernet cables, so I'd like to get this setup using them.
Thing is, I can't get it to work. Simply enabling internet sharing in System Preferences does diddly squat, and no connection is found with Network Utility on the iMac. What I'd really like here is for someone to either instruct me on how to get this to work, or point me in the direction of such an article. I haven't been able to find anything with Google so far...
Now, my MacBook Pro obvioously runs 10.4.9 with all the updates. The iMac G3, however, is running 10.3.5 at the moment. While I will be upgrading it to tiger in the near future, I kinda wanted to play around with Internet Expplorer before doing so. Being new to the Mac and all (the MBP is my first Mac), I've never used Internet Exporer on the Mac -- or 10.3 at all really, for that matter. So if it can be done, I'd like to do this with 10.3 still on the iMac, though I could upgrade it to tiger if I HAD to.
Should it matter, the iMac G3 is a 400MHz indigo unit with 256MB RAM and a 10GB HDD. It's the summer '00 model. The MacBook Pro is a revision A system with a 1.83GHz Core Duo inside. More detailed specs can be found within my profile on here, I believe.
Sorry for such a long winded post...
1.83GHz MacBook Pro 15"; 400MHz iMac G3 Indigo Mac OS X (10.4.9)

I don't have anything that uses FireWire, so othe port on both machines is free, but I also don't have a cable to connect the two. I do, however, have a few spare ethernet cables, so I'd like to get this setup using them.
Lost me there... is it Ethernet cables you're using even though it's too far? Or What?
Should be no problem Sharing the Internet connection from 101.4.9 to 10.3.x.
Just waiting for more info or clarity.

Can't connect through Shared Internet

I am sharing internet via my PPC mini (OSX 10.4.7). However, I am unable to connect my Ichat account on my new Macbook via this shared internet. The Bonjour works fine, though. I would be grateful for any suggestions.

Hi inamacworld,
Have I git this right ?
ISP shared to several Houses of which you share that connection inside the house with at least the landlord and then through your Mac Mini to your MacBook. Is that Correct ?
As this is more of a Networking problem I would suggest going to Tiger > Getting Online & Networking forum to find out about using Internet sharing and it's limits.
9:31 PM Thursday; July 27, 2006

IPhone accessing Mac Pro's shared internet via Bluetooth

I have an iPhone 4 which is running without an ATT contract (no cellular) and acting like an iPod.
I can access the Internet using the wifi arrangements on the iPhone, and this works easily.
But I would like to turn off the wifi on the iPhone and configure the iPhone to access the Internet
via the shared internet service on my Mac pro, connecting via bluetooth.
I am starting to think this is not possible, and the tethering can only go the other way, That is to
say that the iPhone can share it's cellular net access with the Mac via personal hotspot, or possibly
using bluetooth PAN or some other bluetooth connection service.
I have tried creating PAN network interfaces on the Mac Pro, and then I go to the iPhone and set
up a paired connection between the iPhone and the Mac Pro. But I just can't seem to guess the
right set of settings so that the iPhone can use the Mac Pro's internet via the PAN service.
Does PAN service only serve the iPhone's internet to an external device (like a notebook), or can
it be used in the other direction to allow the iPhone to request IP packet service from the Mac Pro?
Thoughts?
Douglas Goodall
Santa Maria, CA

I've been having the same problems as everyone else here. Trying to share internet connection from my ethernet wired iMac to my MacBook and my iPhone. Tried all the workarounds, but nothing works, or lasts very long.
Yesterday, I finally talked with AppleCare for over an hour. All their suggestions (trashing preferences, changing settings, etc.) failed, as well. The AppleCare person then put me on hold to speak to an engineer, who told her that Snow Leopard no longer supports Internet Sharing as of 10.6.1.
Not willing to accept that answer, I had them set up an appointment at the Apple Store Genius Bar for me, and after chatting with the Genius for a while, he also confirmed that Internet Sharing is no longer supported under Snow Leopard. Apparently, there were many hardware issues that the engineers decided to circumvent, and so did not include support for Internet Sharing with the internal airport in Macs. They said that the Airport it is intended to receive, not to send a signals! Yet, it worked fine, doing just that, under Tiger and Leopard! The only fix he could offer was to wipe my drive and take me back to 10.5, which I declined.
However both the guy at the Genius Bar and the lady at AppleCare inferred that Apple "may" release another update to fix this issue, if they get enough complaints and bug reports.
So, there you have it. Apple no longer officially supports Internet Sharing in Snow Leopard.

9360 7.1.0.714 Problem Sharing Internet

Similar Messages

Maybe you are looking for