Re: 6.3 DHCP and static_routes

2008-02-25 Thread Andrea Venturoli

Ed Maste ha scritto:


As of FreeBSD 6.3 dhclient supports RFC3442, the classless static route
option.  If your DHCP server is including this option but not encoding
the default route using the option you'll have no default route.


Thanks for the answer; this is in fact my case.
It would be great news if I could get it to work properly! Obviously 
repeating the static routes in rc.conf was an hack due to lack of this 
support.



Now I fiddled with my dhcpd.conf and came up with this:

option local-route code 121 = string;
option local-route 00:0a:01:02:7f;
option local-route 18:c0:A8:65:0a:01:02:0d;
option local-route 18:c0:A8:67:0a:01:02:0f;
option local-routew code 249 = string;
option local-routew 00:0a:01:02:7f;
option local-routew 18:c0:A8:65:0a:01:02:0d;
option local-routew 18:c0:A8:67:0a:01:02:0f;

The problem is that only the latest route gets in the table; in this case:

192.168.10310.1.2.15  UGS 00vr0


In order to get a default route I have to comment the other two.

Any hint on this?

Thanks a lot.

 bye
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 6.3 DHCP and static_routes

2008-02-25 Thread Ed Maste
On Mon, Feb 25, 2008 at 10:30:06AM +0100, Andrea Venturoli wrote:

 Ed Maste ha scritto:
 
 As of FreeBSD 6.3 dhclient supports RFC3442, the classless static route
 option.  If your DHCP server is including this option but not encoding
 the default route using the option you'll have no default route.
 
 Thanks for the answer; this is in fact my case.
 It would be great news if I could get it to work properly! Obviously 
 repeating the static routes in rc.conf was an hack due to lack of this 
 support.
 
 
 Now I fiddled with my dhcpd.conf and came up with this:
 
 option local-route code 121 = string;
 option local-route 00:0a:01:02:7f;
 option local-route 18:c0:A8:65:0a:01:02:0d;
 option local-route 18:c0:A8:67:0a:01:02:0f;
 option local-routew code 249 = string;
 option local-routew 00:0a:01:02:7f;
 option local-routew 18:c0:A8:65:0a:01:02:0d;
 option local-routew 18:c0:A8:67:0a:01:02:0f;

Yes, the problem is that your local-route option overrides the previous
one each time, so only the last one takes effect.  You need to put them
all together as a single option, probably like

option local-route 
18:c0:A8:65:0a:01:02:0d:18:c0:A8:67:0a:01:02:0f:00:0a:01:02:7f;

and the same for the Windows code 249 version of the option.

-Ed
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 6.3 DHCP and static_routes

2008-02-25 Thread Andrea Venturoli

Ed Maste ha scritto:

On Mon, Feb 25, 2008 at 10:30:06AM +0100, Andrea Venturoli wrote:



Yes, the problem is that your local-route option overrides the previous
one each time, so only the last one takes effect.  You need to put them
all together as a single option, probably like

option local-route 
18:c0:A8:65:0a:01:02:0d:18:c0:A8:67:0a:01:02:0f:00:0a:01:02:7f;

and the same for the Windows code 249 version of the option.


Thanks a lot, this solved it.

 bye
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 6.3 DHCP and static_routes

2008-02-24 Thread Ed Maste
On Sat, Feb 23, 2008 at 01:34:54PM +0100, Andrea Venturoli wrote:

 This used to work fine with 6.2, with the default route set up by the 
 DHCP servers.
 
 After I upgraded to 6.3, I get no default route anymore. This is the 
 relevant part of my logfile:

As of FreeBSD 6.3 dhclient supports RFC3442, the classless static route
option.  If your DHCP server is including this option but not encoding
the default route using the option you'll have no default route.

Quoted from RFC 3442:

  If the DHCP server returns both a Classless Static Routes option and
 a Router option, the DHCP client MUST ignore the Router option.

This is my guess as to what you're seeing.  If this doesn't solve the
issue for you, I'd suggest looking at the DHCP packets with e.g.
wireshark.

-Ed
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


6.3 DHCP and static_routes

2008-02-23 Thread Andrea Venturoli

Hello.
This is part of my rc.conf:

ifconfig_vr0=DHCP
static_routes=a b c
route_a=192.168.101.0/24 xxx
route_b=192.168.103.0/24 yyy
route_c=192.168.106.0/24 xxx

This used to work fine with 6.2, with the default route set up by the 
DHCP servers.


After I upgraded to 6.3, I get no default route anymore. This is the 
relevant part of my logfile:


Feb 23 11:16:38 zzz kernel: DHCPDISCOVER on vr0 to 255.255.255.255 port 
67 interval 6

Feb 23 11:16:38 zzz kernel:
Feb 23 11:16:38 zzz kernel: DHCPOFFER from 10.1.2.15
Feb 23 11:16:38 zzz kernel:
Feb 23 11:16:38 zzz kernel: DHCPREQUEST on vr0 to 255.255.255.255 port 67
Feb 23 11:16:38 zzz kernel:
Feb 23 11:16:38 zzz kernel: DHCPACK from 10.1.2.15
Feb 23 11:16:38 zzz kernel:
Feb 23 11:16:38 zzz kernel: bound to 10.1.2.18 -- renewal in 1800 seconds.
Feb 23 11:16:38 zzz kernel:
Feb 23 11:16:38 zzz kernel: lo0: 
flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384

Feb 23 11:16:38 zzz kernel: inet 127.0.0.1 netmask 0xff00
Feb 23 11:16:38 zzz kernel: vr0: 
flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500

Feb 23 11:16:38 zzz kernel: options=8VLAN_MTU
Feb 23 11:16:38 zzz kernel: inet 10.1.2.18 netmask 0xff00 broadcast 
10.1.2.255

Feb 23 11:16:38 zzz kernel: ether 00:50:8d:63:65:ce
Feb 23 11:16:38 zzz kernel: media: Ethernet autoselect (100baseTX 
full-duplex)

Feb 23 11:16:38 zzz kernel: status: active
Feb 23 11:16:38 zzz kernel: add net 192.168.101.0: gateway xxx
Feb 23 11:16:38 zzz kernel: route:
Feb 23 11:16:38 zzz kernel: writing to routing socket
Feb 23 11:16:38 zzz kernel: :
Feb 23 11:16:38 zzz kernel: File exists
Feb 23 11:16:38 zzz kernel: add net 192.168.103.0: gateway yyy: route 
already in table

Feb 23 11:16:38 zzz kernel: add net 192.168.106.0: gateway xxx
Feb 23 11:16:38 zzz kernel: Additional routing options:


Has anything changed? Anyone else experiencing a similar problem? Any 
suggestion?


 bye  Thanks
av.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]