Re: Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Bill Moss
I removed the first patch from dhcpcd.c and applied the patch to buildmsg.c. It works. Here is what ethereal shows 324 UDP data & PAD_STOP +8 UDP header = 332 UDP total +20 IP header = 352 UDPIP +14 Ethernet header = 366 total I tried #define PAD_STOP304 and it also works 304 UDP

Re: Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Dan Williams
Bill, Can you apply this patch to current CVS copy of NM? It changes dhcpcd/buildmsg.c only. It now pads the message to over 300 bytes and ensures that the message is always an even number of bytes long. Thanks, Dan On Fri, 11 Feb 2005, Bill Moss wrote: > I think older hardware may reject

Re: Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Bill Moss
I think older hardware may reject messages that are too short. The UDP part of the message contains a BOOTP section of options and there was a time when BOOTP messages had a minimize size of 300 bytes. If this is what the SMC is doing, the a message with a UDP part of 297 bytes will not pass mu

Re: Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Dan Williams
On Fri, 11 Feb 2005, Bill Moss wrote: > Your patch did not work. From experience with dhcpcd.c, I knew it would > not work but I also knew how to fix it. The 1.265 and 1.270-mypatch > discovery messages that work are 346 bytes and the UDP part is 312. The > 1.270 discovery message that does not

Re: Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Bill Moss
Your patch did not work. From experience with dhcpcd.c, I knew it would not work but I also knew how to fix it. The 1.265 and 1.270-mypatch discovery messages that work are 346 bytes and the UDP part is 312. The 1.270 discovery message that does not work is 331 bytes and the UDP part is 297. I

Re: Problem (and the patch) when having multiple search domains on a network.

2005-02-11 Thread Colin Walters
On Fri, 2005-02-11 at 22:51 +0100, Tomislav Vujec wrote: >On Fri, 11 Feb 2005 09:21:10 -0500, Colin Walters wrote: >> Tomislav, thanks for the patch. This should already be fixed in the >> latest CVS though. Which version of NetworkManager are you using? > >The fix in the patch you posted would w

Re: Problem (and the patch) when having multiple search domains on a network.

2005-02-11 Thread Tomislav Vujec
On Fri, 11 Feb 2005 09:21:10 -0500, Colin Walters wrote: > Tomislav, thanks for the patch. This should already be fixed in the > latest CVS though. Which version of NetworkManager are you using? The fix in the patch you posted would work too, but I can't find it in the CVS. It seems that there i

Re: Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Dan Williams
On Fri, 2005-02-11 at 16:02 -0500, Bill Moss wrote: > Bootstrap Protocol identical down to > > 1.270: > Option 53 DHCP Message TYPE = DHCP Discover > Option 57: Maximum DHCP Message Size = 548 > Option 51: IP Address Lease Time = infinity > Option 55: Parameter Request List > Option 12: Host Name

Re: define u64 too

2005-02-11 Thread Dan Williams
On Fri, 2005-02-11 at 16:32 +0100, [EMAIL PROTECTED] wrote: > /usr/include/linux/ethtool.h:243: error: syntax error before "u64" > > hm, i have to define u64 too... Fixed, thanks. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org

Re: nm_system_device_add_ip6_link_address / debian backend

2005-02-11 Thread Dan Williams
On Fri, 2005-02-11 at 16:32 +0100, [EMAIL PROTECTED] wrote: > looks like the version from the redhat backend works in debian too, > and it solves the problems i had with wired devices and ipv6... > > attached patch to add function to debian backend. Applied, thanks. Dan

Ethereal comparison 1.265 vs 1.270 DHCP Discover

2005-02-11 Thread Bill Moss
Bootstrap Protocol identical down to 1.270: Option 53 DHCP Message TYPE = DHCP Discover Option 57: Maximum DHCP Message Size = 548 Option 51: IP Address Lease Time = infinity Option 55: Parameter Request List Option 12: Host Name = "localhost.localdomain" == SMC DHCP does not send an ARP. It is stu

1.270 connects are work

2005-02-11 Thread Bill Moss
Version 1.270 connects are work to Cisco AP's. -- Bill Moss Professor, Mathematical Sciences Clemson University ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list

define u64 too

2005-02-11 Thread j
/usr/include/linux/ethtool.h:243: error: syntax error before "u64" hm, i have to define u64 too... j Index: src/NetworkManagerDevice.c === RCS file: /cvs/gnome/NetworkManager/src/NetworkManagerDevice.c,v retrieving revision 1.95 diff

nm_system_device_add_ip6_link_address / debian backend

2005-02-11 Thread j
looks like the version from the redhat backend works in debian too, and it solves the problems i had with wired devices and ipv6... attached patch to add function to debian backend. j Index: src/backends/NetworkManagerDebian.c === RCS

1.265 connection 1.270 not connecting

2005-02-11 Thread Bill Moss
1.265 connects to SMC AP/DHCP server, but 1.270 does not. Will try ethereal over the weekend. I am assuming that NM sends a discovery message that the DHCP server does not like and so does not reply. Here is bit from the syslog for the version at changelog 1.265. This is a ACK reply from the DH

Re: CVS 8/2 compile error

2005-02-11 Thread Dan Williams
On Fri, 2005-02-11 at 09:29 -0500, Dan Williams wrote: > On Fri, 2005-02-11 at 09:24 -0500, Colin Walters wrote: > > On Tue, 2005-02-08 at 13:34 +0100, Tom Parker wrote: > > >Getting errors on NetworkManagerDevice.c, because I don't appear to have > > >a "pci/types.h". No idea where the heck this

Re: CVS 8/2 compile error

2005-02-11 Thread Dan Williams
On Fri, 2005-02-11 at 09:24 -0500, Colin Walters wrote: > On Tue, 2005-02-08 at 13:34 +0100, Tom Parker wrote: > >Getting errors on NetworkManagerDevice.c, because I don't appear to have > >a "pci/types.h". No idea where the heck this would be (on a Debian > >system), but then worked out that we

Re: CVS 0209 make error

2005-02-11 Thread Dan Williams
On Thu, 2005-02-10 at 20:47 -0500, Sven wrote: > well, all i know is that the current developer CVS has it fixed... > > Sven > > On Thu, 2005-02-10 at 20:42 -0500, Paul Dugas wrote: > >Tried to get someone to look at this earlier this week. It's due to the > >colon in the "[encoding: UTF-8]" li

Re: CVS 8/2 compile error

2005-02-11 Thread Colin Walters
On Tue, 2005-02-08 at 13:34 +0100, Tom Parker wrote: >Getting errors on NetworkManagerDevice.c, because I don't appear to have >a "pci/types.h". No idea where the heck this would be (on a Debian >system), but then worked out that we only needed a few types from it and >so wrote a patch. > >Index

Re: Problem (and the patch) when having multiple search domains on a network.

2005-02-11 Thread Colin Walters
On Fri, 2005-02-11 at 13:58 +0100, Tomislav Vujec wrote: >Hi, > >When the "domainName" DHCP option contains spaces, nm-named-manager >proclaims it as invalid, although multiple domain names are often used >in the DHCP server configuration. The attached patch fixes this >behavior. Tomislav, thanks

VPN integration

2005-02-11 Thread Anders Östling
Hi I read a note a few weeks ago about integration of VPN functions into NM. Today I am using vpnc as a standalone solution, but it would be great to have this integrated with NM. What are the status and plans? If you need help with testing, please let me know. Anders __

Problem (and the patch) when having multiple search domains on a network.

2005-02-11 Thread Tomislav Vujec
Hi, When the "domainName" DHCP option contains spaces, nm-named-manager proclaims it as invalid, although multiple domain names are often used in the DHCP server configuration. The attached patch fixes this behavior. 2005-02-11 Tomislav Vujec <[EMAIL PROTECTED]> * named/nm-named-manage