08-08-2014
Let me make sure I'm clear on this -- you get packet loss when pinging your modem, but not when pinging the access point?
10 More Discussions You Might Find Interesting
1. Cybersecurity
At the moment, I have three computers at home. I want to use boardband for my three computers. But I don't want to use network at home. I have been looking for a product which call OriNoCo USB Cilent. How do I connect to the internet with my computer??
If I post this in a wrong place, please... (0 Replies)
Discussion started by: him
0 Replies
2. IP Networking
Hi,
I have a laptop with a Linksys Wireless G PCMCIA card and a cable connection goin into a router and then a patch lead from the router going to a Linksys Wireless G access point IP 192.168.1.245 with DHCP disabled.
I can connect to the access point from the laptop, but how do I get the... (1 Reply)
Discussion started by: perleo
1 Replies
3. UNIX for Dummies Questions & Answers
I installed solaris 10 x86 on my dell laptop on a partition alongside windows xp. I am able to connect to the internet in xp with both my ethernet local area connection as well as through my wireless network card. But, however i do not have clue as to how to go about it in solaris.
i did not... (0 Replies)
Discussion started by: stakes20
0 Replies
4. Linux
I am running FC4:
Linux maincomp 2.6.13-1.1532_FC4smp
I recently changed the OS from windows XP, and have a feeling that for some reason my wireless network card is slower on Fedora Core 4. The Belkin PCI 802.11b card was automatically detected and configured by FC4 when I installed the OS,... (0 Replies)
Discussion started by: dangral
0 Replies
5. Cybersecurity
Hi all,
How can I monitor packet traffic on my wireless router?
Some info
- my wireless router is netgear wgr614
- everyone can connect it i.e. no password required
- I would like to see where they connect, how they are using the internet connection
I installed wireshark and captured... (3 Replies)
Discussion started by: SaTYR
3 Replies
6. Hardware
hi
Howto identify wireless network card using Live CD? (2 Replies)
Discussion started by: ccc
2 Replies
7. Ubuntu
Hi,
I am a new to Ubuntu linux and trying to learn it. I am using ubuntu 10.04. I am getting problem in setting my wireless network. I set it up properly and was working fine. But suddenly it stopped working, though the wireless icon saying that it is connected, but can't load any page. I... (2 Replies)
Discussion started by: linux_learner
2 Replies
8. Red Hat
Hi,
I am trying to set up a wireless internet connection on my centos OS (6). I can connect via the copper using the internal LAN but cannot get the wireless connection working.
The 2 files that I have configured are:
My wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant... (1 Reply)
Discussion started by: Duffs22
1 Replies
9. Hardware
Good Day All,
There are numerous results when searching google on this issue, however, none seem to have a solution.
I have read until my eyes bleed and banged my head on the table more than once! :)
I am hoping to resolve this issue -- or at least have a decent workaround.
It is a real... (13 Replies)
Discussion started by: RogerBaran
13 Replies
10. Ubuntu
I run lubuntu from usb (try lubuntu, it's not install on my pc )
And i try to connect to network
I see the network name
And i put the pass
But it's not connect..
I tried to open hot spot on my phone and try to connect and it's not connect
I have edumax n150
Try to install new driver -... (0 Replies)
Discussion started by: popcoern
0 Replies
LEARN ABOUT DEBIAN
iodine-client-start
IODINE-CLIENT-START(8) System Administration Utilities IODINE-CLIENT-START(8)
NAME
iodine-client-start - start an iodine IPv4-over-DNS tunnel
SYNOPSIS
iodine-client-start [option]
DESCRIPTION
'iodine-client-start' starts an iodine IP-over-DNS tunnel.
-h, --help
Print help and exit
-v, --version
Print version info and exit
Invoking the program without options attempts to set up and configure an iodine IP-over-DNS tunnel using the configuration in the file
/etc/default/iodine-client or by querying the user. It tries to figure out the right way to set things up by observing the network, and if
all else fails by guessing.
QUICK CONFIGURATION
Put two lines in the file /etc/default/iodine-client
subdomain=your.tunnel.sub.domain
passwd=password_for_that_tunnel
or invoke the script with those environment variables set:
env subdomain=xxx passwd=xxx iodine-client-start
If these are not set, the script will query the user for them.
DETAILS
The configuration file consists of lines which are either comments starting with '#', or settings of the form VAR="val". Valid VARs are:
subdomain
Sample value: your.tunnel.sub.domain (no default, must be set)
passwd
Sample value: password_for_that_tunnel (no default, must be set)
testhost
Hostname to ping when testing if network is working (default: slashdot.org)
bounce_localnet
Take the local network down and then up again before starting tunnel (default: false)
test_ping_localnet
Test if the local network is working by pinging the gateway (default: true)
test_ping_tunnel
Test if the iodine tunnel is working after it has been set up by pinging the host at the other end (default: true)
test_ping_final
Test if the tunnel is working after everything is ostensibly set up by trying to ping an external host (default: true)
default_router
IP address of router on the local network---should be found automatically, set this if that fails and the program guesses wrong.
interface
Interface to use (e.g., eth1, eth0, etc) for connection to DNS server used for the iodine tunnel---should be found automatically,
set this if that fails and the program guesses wrong.
mtu
Set if tunnel MTU needs to be manually changed (lowered). Should not be necessary anymore, as recent versions of iodine negotiate an
appropriate MTU during tunnel setup. But if that negotiation does not happen, or if you are using an older version of iodine, the
default tunnel MTU is 1024, and if the local DNS server restricts to 512 byte packets you might need to use an MTU of 220.
skip_raw_udp_mode
Set "-r" option in iodine command line. With this option, iodine does not try to establish a direct UDP socket to the iodine server
on port 53. (default: true).
continue_on_error
Set if the script should continue even if a command fails. Use to test script when running as non-root. Defaults to false if run-
ning as root, true otherwise.
iodine-client-start 1.0.4 June 2014 IODINE-CLIENT-START(8)