Re: [lwip-users] eCos - PPP - TCP - LwIP

[Ashish Anand]

[1] No issue of firewall, since I used "service iptables stop".

[2] When I telnet, I get something similar:

 ip_input: iphdr->dest 0xfb0000e0 netif->ip_addr 0x401a8c0 (0xe0, 
>>>>> 0x1a8c0, 
>>>>> 0xfb00000)ip_input: iphdr->dest 0xfb0000e0 netif->ip_addr 0x100007f 
>>>>> (0xe0, 
>>>>> 0x7f, 0xfb000000) 
>>>>> ip_input: packet not for us. 
>>>>> ip_forward: not bouncing packets back on incoming interface. 
>>>>> 

Except that this time, the (hex) IP address is 192.168.1.4 (board IP)
instead of the MDNS IP.
So even these packets are considered "not for us"!

It's really strange, why all this complication is arising!



Jonathan Larmour wrote:
> 
> Ashish Anand wrote:
>> Yes yes yes.......I used Ethereal.
>> The 254 IP is some process in the Linux box (MDNS Protocol - Ignore
>> that).
>> I was monitoring the ppp interface through Ethereal and when I telnet to
>> the
>> board, it shows TCP syn packets going out to the board. But there is no
>> SYN/ACK coming back from the board.
> 
> But the board is clearly able to receive broadcast IP packets, and 
> netif->ip_addr is also clearly set correctly. If it gets sent down the 
> link, it really should be able to be seen. You could enable the PPP 
> debugging (PPP_DEBUG) specifically to see if _any_ event happens on the 
> target when the SYNs are sent.
> 
> Is there any chance your linux host is packet filtering (i.e. firewalling) 
> outbound packets? Just because you can see it in ethereal, doesn't mean
> the 
> firewall allowed it through.
> 

-- 
View this message in context: 
http://www.nabble.com/eCos---PPP---TCP---LwIP-tf3219708.html#a9043821
Sent from the lwip-users mailing list archive at Nabble.com.