Re: [Ekiga-list] Ekiga on Ubuntu using DSL 302G D-Link modem

[Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr>]

mat101 wrote:
> Eugen Dedu wrote:
>> mat101 wrote:
>>  
>>> ael wrote:
>>>    
>>>> On Thu, Feb 25, 2010 at 01:25:46PM +1100, mat101 wrote:
>>>>  
>>>>      
>>>>>>>       Connection-specific DNS Suffix  . :
>>>>>>>       IP Address. . . . . . . . . . . . : 10.1.1.10
>>>>>>>       Subnet Mask . . . . . . . . . . . : 255.0.0.0
>>>>>>>       Default Gateway . . . . . . . . . : 10.1.1.1
>>>>>>>                     
>>>> The ip address (10.1.1.10 above) is that of your computer - or more
>>>> exactly of that particular interface: ethernet?
>>>>
>>>>  
>>>>      
>>>>>>> Some sites claim the above ipconfig output indicates my router ip
>>>>>>> number is
>>>>>>> 10.1.1.1, and yet other sites claim it is 10.1.1.10.
>>>>>>>                     
>>>> If you had run that command *on the router/modem*, then indeed it would
>>>> suggest that was the address (of one of its interfaces). But you ran it
>>>> on your computer, so it is telling about that.
>>>>
>>>>  
>>>>      
>>>>>>> suggested my router ip number should be 192.168.15.1.
>>>>>>>                     
>>>> Above 192.168... seems weird unless it is the factory default
>>>> setting for your router/modem.
>>>>
>>>>  
>>>>      
>>>>>>> confusing.
>>>>>>>                     
>>>>> Thanks for the response ael.
>>>>>
>>>>> My unsuccessful efforts to create NAT Rule Entries for the modem was
>>>>> my feeble attempt to follow the Ekiga-behind-a-NAT-router
>>>>> instructions on the wiki. These rules were manipulated by entering
>>>>> the modem's Admin. Panel through a browser via 'http://10.1.1.1'.
>>>>>             
>>>> So that confirms that the router/modem has the local interface
>>>> bound to 10.1.1.1.
>>>>
>>>>  
>>>>      
>>>>> The cmd.exe/ipconfig output on XP showed a 'Gateway Address' and 'IP
>>>>>             
>>>> I don't understand why you are using an alien op system when you
>>>> have far more powerful tools at your disposal under linux. Maybe
>>>> you are just moving away and are used the the old ways?`
>>>>
>>>>  
>>>>      
>>>>> Address' (see above). When I ping the 'Gateway Address' 10.1.1.1 in
>>>>> a terminal window on ubuntu, the modem lights do flash, and the
>>>>> output in the terminal window indicates an interaction with the
>>>>> modem. The modem lights also flash when I ping the 'IP Address' of
>>>>> 10.1.1.10. Trying to ping other ip numbers results in 'Destination
>>>>> Host Unreachable'.
>>>>>             
>>>> All just what is expected: the router/local LAN port is 10.1.1.1 .
>>>>
>>>>  
>>>>      
>>>>> If I point my browser to the IP Address of 10.1.1.10 I get a 'Failed
>>>>> to Connect' browser response.
>>>>>             
>>>> You are pointing back at yourself, and presumably you are not running
>>>> an http server like apache, or it is configured only to respond to
>>>> local
>>>> requests.
>>>>
>>>>  
>>>>      
>>>>> Your question: "Who set up your router: not you?"
>>>>> Answer: Yes, I (clumsily) set up the router. Entering
>>>>> http://10.1.1.1 in a browser allows me to enter the modem's Admin.
>>>>> Panel and manipulate settings. I had to place the modem in 'bridging
>>>>> mode' in order to get access to the outside world. My computer is
>>>>> the only computer connected to the modem.
>>>>>             
>>>> I suspect that "bridging mode" is your whole problem. But I may be
>>>> wrong. Can others comment?
>>>>
>>>>
>>>>  
>>>>      
>>>>> The following output is produced when I type 'route' in a terminal
>>>>> window on ubuntu:
>>>>>
>>>>> Kernel IP routing table
>>>>> Destination     Gateway         Genmask         Flags Metric Ref
>>>>> Use Iface
>>>>> link-local      *               255.255.0.0     U     1000  
>>>>> 0       0 eth0
>>>>> 10.0.0.0        *               255.0.0.0       U     1     
>>>>> 0       0 eth0
>>>>> default         10.1.1.1        0.0.0.0         UG    0     
>>>>> 0       0 eth0
>>>>>             
>>>> That just confirms what I said above. You might want to look at
>>>> ipconfig eth0 as well, just for interest. Again, you may need to be
>>>> root (sudo, etc).
>>>>
>>>>  
>>>>      
>>>>> I hope the above brings me closer to finding a solution.
>>>>>             
>>>> As I say, I suspect that you should not be using bridging mode...
>>>>
>>>> ael
>>>> _______________________________________________
>>>> ekiga-list mailing list
>>>> ekiga-list gnome org
>>>> http://mail.gnome.org/mailman/listinfo/ekiga-list
>>>>
>>>>         
>>> Thanks ael.
>>>
>>> " I don't understand why you are using an alien op system when you have
>>> far more powerful tools at your disposal under linux. Maybe you are just
>>> moving away and are used the the old ways? "  -  I have just moved to
>>> linux and I am still trying to find my way around the os. Hence I find
>>> myself moving between os.s at this stage to 'better' diagnose my modem
>>> problem. Apologies for mentioning the other os.
>>>
>>> In a previous post I indicated that this modem works perfectly with
>>> another voip program on my ubuntu system (sk*pe) - allowing me to see
>>> and hear the other person. But I want to avoid this other program, and
>>> prefer to use Ekiga instead.
>>>
>>> Does the code in Ekiga simply preclude such an interaction with a DSL
>>> 302G modem (in bridging mode)?
>>>     
>>
>> To my knowledge, ekiga does not work in one type of NAT: Symmetric NAT.
>>   This type of NAT cannot be served by a VoIP program without a "trick".
>>  Skipe works in this case too because it uses the other users of skipe
>> as proxies, otherwise said the other users give (are forced to give)
>> ressources (CPU and network bandwidth) for Symmetric NAT skipe users.
>>
>>   
> Thanks Eugen.
> 
> Ekiga certainly seems to have a few difficulties with Symmetric NAT.
> 
> I followed kapetr's earlier advice and configured twinkle with an
> iptel.org sip account - voip works well with twinkle on ubuntu with my
> DSL modem. This sip account seems to override the necessity for
> client-side NAT-churning by offering a server-side STUN service.
> 
> Twinkle doesn't have video, and I'm not too fond of the app's name, but
> at least I've stopped using sk*pe.

To my knowledge: I forgot to add that another solution is to have a
public proxy for all the symmetric nat users.  This can work for audio
traffic, but for (the much higher bw consuming) video traffic this is
overkill.  And it seems iptel provides such a service, but for audio only.

I added this info to the web page
http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#Symmetric_NAT:_Dynamic_navigation_of_NAT_routers

-- 
Eugen