Re: route problems in 5.1-RELEASE

2003-09-12 Thread Jesse Guardiani
Martin Blapp wrote:

 
 Hi,
 
Normally, if I want to swap from wi0 to fxp0, all I
have to do is:

killall dhclient
ifconfig wi0 down
ifconfig fxp0 up
dhclient fxp0
 
 Why don't you just update to 5.X, run mergemaster-
 
 Then just remove the wi0 card and plug in a ethernet
 cable to the internal NIC ? This works wonderful here.
 No manual interaction needed anymore. Dhclient had a bunch
 of fixes for this problem, the rc system had it too. All of
 them are fixed.

Ok. Glad to hear it.

I would update to -CURRENT, but I'm a little worried about my
ATA drive not being detected with the new ATAng stuff. :)

Not to mention the hastle of having to compile all my userland
stuff from source. (You can't use packages with -CURRENT, right?
Or am I mistaken?)

This isn't a beater laptop. I actually use it for real work.
So maybe I'll just wait for 5.2-RELEASE...

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net


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


route problems in 5.1-RELEASE

2003-09-11 Thread Jesse Guardiani
Howdy list,

I'm having major problems with the route command today.
My machine is an IBM Thinkpad A30p laptop, running FreeBSD
5.1-RELEASE.

I have two interfaces. wi0 and fxp0

Normally, if I want to swap from wi0 to fxp0, all I
have to do is:

killall dhclient
ifconfig wi0 down
ifconfig fxp0 up
dhclient fxp0

And I'm done. However, ocassionally this backfires,
like it did today:

My fxp0 interface is up:

fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::2d0:59ff:feaa:70ec%fxp0 prefixlen 64 scopeid 0x3
inet 192.168.1.101 netmask 0xff00 broadcast 192.168.1.255
ether 00:d0:59:aa:70:ec
media: Ethernet autoselect (100baseTX full-duplex)
status: active

And my wi0 interface is down:

wi0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::220:e0ff:fe8a:9061%wi0 prefixlen 64 scopeid 0x2
inet 192.168.1.47 netmask 0xff00 broadcast 192.168.1.255
ether 00:20:e0:8a:90:61
media: IEEE 802.11 Wireless Ethernet autoselect (none)
ssid WingNET 1:WingNET
stationname FreeBSD WaveLAN/IEEE node
channel -1 authmode OPEN powersavemode OFF powersavesleep 100
wepmode MIXED weptxkey 1
wepkey 1:128-bit

But routes to the internet are still wanting to use the wi0
interface for some reason:

[16:[EMAIL PROTECTED]:[~]# route get 206.30.215.2
   route to: 206.30.215.2
destination: 206.30.215.2
gateway: 192.168.1.1
  interface: wi0
  flags: UP,GATEWAY,HOST,DONE,WASCLONED,PROTO3
 recvpipe  sendpipe  ssthresh  rtt,msecrttvar  hopcount  mtu expire
   0 0 0 0 0 0  1500  3584
[16:[EMAIL PROTECTED]:[~]#


I can change the interface on a per-route basis, but not globally:

[16:[EMAIL PROTECTED]:[~]# route change 206.30.215.2 -iface fxp0
change host 206.30.215.2: gateway fxp0
[16:[EMAIL PROTECTED]:[~]# route get 206.30.215.2
   route to: 206.30.215.2
destination: 206.30.215.2
gateway: fxp0:0.d0.59.aa.70.ec
  interface: fxp0
  flags: UP,GATEWAY,HOST,DONE,WASCLONED,PROTO3
 recvpipe  sendpipe  ssthresh  rtt,msecrttvar  hopcount  mtu expire
   0 0 0 0 0 0  1500  3582
[16:[EMAIL PROTECTED]:[~]# route get 206.30.215.4
   route to: 206.30.215.4
destination: default
   mask: default
gateway: 192.168.1.1
  interface: wi0
  flags: UP,GATEWAY,DONE,STATIC,PRCLONING
 recvpipe  sendpipe  ssthresh  rtt,msecrttvar  hopcount  mtu expire
   0 0 0 0 0 0  1500 0
[16:[EMAIL PROTECTED]:[~]#



Some funky combination of:

ifconfig wi0 -alias

And restarting dhclient fixed the problem, but it took forever.


1.) Is this a bug?
2.) If so, has it already been fixed in -CURRENT?

Thanks!

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net


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


Re: route problems in 5.1-RELEASE

2003-09-11 Thread Kevin Oberman
 From: Jesse Guardiani [EMAIL PROTECTED]
 Date: Thu, 11 Sep 2003 16:19:42 -0400
 Sender: [EMAIL PROTECTED]
 
 Howdy list,
 
 I'm having major problems with the route command today.
 My machine is an IBM Thinkpad A30p laptop, running FreeBSD
 5.1-RELEASE.
 
 I have two interfaces. wi0 and fxp0
 
 Normally, if I want to swap from wi0 to fxp0, all I
 have to do is:
 
 killall dhclient
 ifconfig wi0 down
 ifconfig fxp0 up
 dhclient fxp0
 
 And I'm done. However, ocassionally this backfires,
 like it did today:

Jesse,

Try changing your list of commands to:
killall dhclient
ifconfig wi0 down
route flush
ifconfig fxp0 up
dhclient fxp0

That should fix it up.

I've been trying to get Lars Eggert's netswitch running with current.
It will do all of the above, but it's probably over-kill for you case.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: route problems in 5.1-RELEASE

2003-09-11 Thread Jesse Guardiani
Kevin Oberman wrote:

 From: Jesse Guardiani [EMAIL PROTECTED]
 Date: Thu, 11 Sep 2003 16:19:42 -0400
 Sender: [EMAIL PROTECTED]
 
 Howdy list,
 
 I'm having major problems with the route command today.
 My machine is an IBM Thinkpad A30p laptop, running FreeBSD
 5.1-RELEASE.
 
 I have two interfaces. wi0 and fxp0
 
 Normally, if I want to swap from wi0 to fxp0, all I
 have to do is:
 
 killall dhclient
 ifconfig wi0 down
 ifconfig fxp0 up
 dhclient fxp0
 
 And I'm done. However, ocassionally this backfires,
 like it did today:
 
 Jesse,
 
 Try changing your list of commands to:
 killall dhclient
 ifconfig wi0 down
 route flush
 ifconfig fxp0 up
 dhclient fxp0
 
 That should fix it up.

Sorry for neglecting to mention it, but I did that, multiple times,
in multiple places.

I _didn't_ do it the FIRST time, but I did do multiple times after
that.

Perhaps I should do it the first time, from now on? Would that
prevent the problem?

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net


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


Re: route problems in 5.1-RELEASE

2003-09-11 Thread Martin Blapp

Hi,

Normally, if I want to swap from wi0 to fxp0, all I
have to do is:

killall dhclient
ifconfig wi0 down
ifconfig fxp0 up
dhclient fxp0

Why don't you just update to 5.X, run mergemaster-

Then just remove the wi0 card and plug in a ethernet
cable to the internal NIC ? This works wonderful here.
No manual interaction needed anymore. Dhclient had a bunch
of fixes for this problem, the rc system had it too. All of
them are fixed.

Martin

Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP  ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93 01
PGP: finger -l [EMAIL PROTECTED]
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]