Re: [lwip-users] Double netIf on the same hw

[Piero 74]

Kieran...

our board works as IP communicator for other devices. It uses UDP packet for signaling events, but, for maintenance reasons, it always listen on specific port for an incoming TCP connection... so works as tcp server.
Our customer wants the possibility to use the board on network using dynamic ip, so using DHCP, but in general they cannot know current dynamic ip without network administrator help. 
My idea is to have another tcp listener bind on interface with fixed ip, which can provide connection for maintenance, using crossover cable. In opposite, if someone already know the dynamic ip, can do maintenace everywhere in a network.

A different idea could be to use a udp broadcast request, but many networks have router configured to drop packets with broadcast address 255.255.255.255.

Piero.

2008/2/19, Kieran Mansley <address@hidden>:

On Tue, 2008-02-19 at 12:32 +0100, Piero 74 wrote:
> Hi all!
>
> i'm thinking if it's possible to define TWO different netif on the
> same, which work in this way:
>
> - the first is binded on FIXED ip, ie. 192.168.0.1 and is always up
> - the second use DHCP, and can change IP dependingo on network.

It should be theoretically possible (you could do this sort of thing on
Linux with a software bridge for example) but I'm not sure what it gives
you: if you can talk to the 192.168.0.1 address, why does it need the
second interface?  If you can't talk to the 192.168.0.1 address, why
bother having it?  i.e. I can see why you might want one or the other
but not both.

Kieran



_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users