traceroute bridge and network/interfaces

David Parks davidparks21 at yahoo.com
Sun Apr 7 09:07:25 UTC 2013


Your questions are a bit hard to follow, but here's the best I can offer as an answer to them:

 

1) Trace route:

Traceroute works by using the TTL (time to live) feature of TCP/IP. This is a number that starts at 30 (by default) and is reduced by 1 every time it hits a router. That way one packet can't go in a circles infinitely if someone misconfigured their router, eventually it'll die. When it does that router *might* send a notice back to the sender that it was dropped due to an expired TTL.

 

Traceroute starts by sending 1 packet with a TTL of 1, so it fails at the first router, and that router replies that it was dropped. In your case that was your local router at 192.168.1.1, and so traceroute knows about that router. Now it repeats with a TTL of 2, which makes it to the 2nd router before being dropped, but in this case the 2nd router simply didn't send you a notice (whoever owns that router, clearly your ISP in this case, simply set it not to do that, their prerogative). Then Traceroute repeats again with a TTL of 3, and so on until it hits the destination.

 

Short answer: you can't do anything about it.

 

2) Is the IO gear wifi adapter acting as a bridge? 

>From a look at the specs this thing seems to connect to your local WIFI network and provide physical Ethernet ports. The feature list was so horribly written on their page that it's hard to tell what it really does exactly. If it's acting as a bridge (a bridge being almost the same thing as a switch, if you're more familiar with their functionality) you'll get an IP from your home WIFI router, if it's acting as a router it will probably provide its own IPs via DHCP.

 

3) How does the router determine those settings?

That question is a little unclear, the link you pointed to shows the configuration of a router, so I assume you're talking about how a router knows to give out IPs 192.168.1.x?  If so, that's something you set in the router, by default most home routers designate IPs 192.168.1.x as the IPs they give to clients (via DHCP). This IP range is 1 of 3 that are designated by ICANN (the coordinating authorities for IPs) as internal IP ranges (e.g. they won't go over the internet). This is a good default because it's the smallest of the 3 ranges of "internal" IPs.

 

4) How do I know what settings are required for /etc/network/interfaces with this device?

In most home networking cases this should be left as automatic.

 

# The primary network interface

auto eth0

iface eth0 inet dhcp

 

If you need to set a static IP then it is *you* who needs to decide what the IPs are going to be (make sure you’re not using IPs that your router will assign automatically), and then set each device to whatever IP *you* assigned it. But again, that isn’t a normal home networking configuration, you should only do it if you have some reason to do it (for example, you’re running a web service and need the IP never to change).

 

 

 

-----Original Message-----
From: ubuntu-users-bounces at lists.ubuntu.com [mailto:ubuntu-users-bounces at lists.ubuntu.com] On Behalf Of Thufir Hawat
Sent: Sunday, April 07, 2013 3:33 PM
To: ubuntu-users at lists.ubuntu.com
Subject: traceroute bridge and network/interfaces

 

How do I find out about the *** network?

 

thufir at dur:~$

thufir at dur:~$ traceroute google.com

traceroute to google.com (173.194.33.7), 30 hops max, 60 byte packets

1  192.168.1.1 (192.168.1.1)  0.305 ms  0.338 ms  0.381 ms

2  * * *

3  tl15fl.vs.shawcable.net (64.59.147.169)  18.444 ms  19.884 ms  19.941 ms

4  66.163.68.201 (66.163.68.201)  25.567 ms  26.477 ms  27.171 ms

5  66.163.78.218 (66.163.78.218)  28.594 ms  29.720 ms  30.306 ms

6  72.14.195.246 (72.14.195.246)  22.778 ms  18.910 ms  19.718 ms

7  66.249.94.212 (66.249.94.212)  17.622 ms  18.409 ms  57.878 ms

8  209.85.253.24 (209.85.253.24)  24.866 ms  25.783 ms  24.183 ms

9  sea09s01-in-f7.1e100.net (173.194.33.7)  22.232 ms  27.047 ms  27.002 ms thufir at dur:~$ 

 

 

What I have is a an IO gear universal wifi adapter:

 

 <http://www.iogear.com/product/GWU627/> http://www.iogear.com/product/GWU627/

 

which connects to a computer, or router, with ethernet cable. It is acting as, I believe, a bridge.  Is that correct terminology?

 

Currently the IO gear wifi adapter connects to the internet port on my router, and then the computer is connected to the router.  The IO gear wifi adapter gets its connection from a *different* router, wirelessly.

 

Is the IO gear wifi adapter acting as a bridge?

 

Clicking on requirements shows:

 

    Operating System

        Windows® XP, Windows® Vista, Windows® 7

        Mac OS X v10.4 and above

        Linux® Fedora 10 (Kernel: 2.6.27.5-117)  <----

 

 <http://www.iogear.com/product/GWU627/> http://www.iogear.com/product/GWU627/

 

 

While I managed to get the device working, that was only because of some magic which the router performed:

 

 <http://askubuntu.com/a/265056/45156> http://askubuntu.com/a/265056/45156

 

How did the router determine those settings?  How do I know what settings are required for /etc/network/interfaces with this device?

 

 

thanks,

 

Thufir

 

 

-- 

ubuntu-users mailing list

 <mailto:ubuntu-users at lists.ubuntu.com> ubuntu-users at lists.ubuntu.com

Modify settings or unsubscribe at:  <https://lists.ubuntu.com/mailman/listinfo/ubuntu-users> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20130407/a42204b3/attachment.html>


More information about the ubuntu-users mailing list