ifconfig rl0 does not report status on FreeBSD-4.9
Hi, The rl driver does not report it's link status on FreeBSD 4.9, at least not when using ifconfig. The chip is a Realtek 8139C+. I could not find anything about it in the archives. Any hints? # ifconfig rl0 rl0: flags=8843 mtu 1500 inet 192.168.2.2 netmask 0xff00 broadcast 192.168.2.255 ether 00:90:fb:04:5e:78 media: Ethernet autoselect (none) # ping -c 1 192.168.2.1 PING 192.168.2.1 (192.168.2.1): 56 data bytes 64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=0.514 ms --- 192.168.2.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.514/0.514/0.514/0.000 ms From dmesg: rl0: port 0xdc00-0xdcff mem 0xe700-0xe7ff irq 12 at device 9.0 on pci0 rl0: Ethernet address: 00:90:fb:04:5e:78 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto /j ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: netgraph....help
Hi, manish gautam wrote: i want to make my own node with my own specifications. how can i do that and load it and pass data through it. A good start is to do it as a userland process and use ng_socket to communicate with the netgraph subsystem. reply as soon as possible... I'm sorry if I kept you waiting. /j cheers manish Yahoo! India Education Special: Study in the UK now. Go to http://in.specials.yahoo.com/index1.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
802.11g and PCI 2.1
URGENT!!! I need a 802.11g PCI card supported by FreeBSD 5.2R which will work in a only PCI 2.1 compliant slot. All cards I saw seem to require PCI 2.2. Does anyone know of a PCI 2.1 card? Please ... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: question: source address on interface w/ aliases?
Brian Reichert wrote: On Thu, Feb 12, 2004 at 11:35:06AM -0800, Julian Elischer wrote: My expectation was that the primary IP address would be used. The primary IP address on the interface referred to in the routing table entry that is chosen for the first packet.. (last time I looked) Such was my expectation. But: is this a BSD-specific implementation? If I catch a kernel doing otherwise, can I say 'Aha! That's a bug based on documented standards' ? RFC 1122, Section 3.3.4.2 Lars -- Lars Eggert NEC Network Laboratories smime.p7s Description: S/MIME Cryptographic Signature
VPN with FreeBSD using some form of encryption
I have a home network with FreeBSD machines and a laptop running FreeBSD. The laptop connects to various networks but I'd like to access my home machines from the laptop, the home machines are behind a freebsd nat firewall. I've been using mpd for quite a while, doing a PPTP link from my laptop to home but it doesn't offer any useful encryption, and the encryption it claims to offer doesn't seem to work. Hence, limiting what I can do over the link without fear of being sniffed. I'd like being able to dial in from anywhere, yet have an encrypted link. What are my options? I've read about the IPSEC tunneling support but it seems to me that it's limited to static tunnels. Baldur ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VPN with FreeBSD using some form of encryption
Not sure if it helps your particular situation, but you might want to take a look at OpenVPN (/usr/ports/security/openvpn). It's an application layer VPN implementation (SSL) as opposed to IPSec, but seems to work well for dynamic IP addresses and endpoints behind NAT devices. Quite stable, as well. -- Art Mason Technical Support - Team F Rackspace Managed Hosting (800) 961-4454 ext. 1223 [EMAIL PROTECTED] On Fri, 2004-02-13 at 13:19, Baldur Gislason wrote: > I have a home network with FreeBSD machines and a laptop running FreeBSD. > The laptop connects to various networks but I'd like to access my home > machines from the laptop, the home machines are behind a freebsd nat > firewall. > I've been using mpd for quite a while, doing a PPTP link from my laptop to > home but it doesn't offer any useful encryption, and the encryption it claims > to offer doesn't seem to work. > Hence, limiting what I can do over the link without fear of being sniffed. > I'd like being able to dial in from anywhere, yet have an encrypted link. What > are my options? > I've read about the IPSEC tunneling support but it seems to me that it's > limited to static tunnels. > > Baldur > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: question: source address on interface w/ aliases?
On Fri, Feb 13, 2004 at 02:41:14PM +0100, Lars Eggert wrote: > Brian Reichert wrote: > >If I catch a kernel doing otherwise, can I say 'Aha! That's a bug > >based on documented standards' ? > > RFC 1122, Section 3.3.4.2 Cool! Thanks for that pointer... That section refers to 'sending a datagram', which sounds UDP-specific. Regardless of that, that section refers me to '3.3.4.3 Choosing a Source Address', which does more succinctly address my question. All I find upon a first read is: (b) The route cache may be consulted, to see if there is an active route to the specified destination network through any network interface; if so, a local IP address corresponding to that interface may be chosen. But, nothing in RFC 1122 seems to shed any light on a selection algorithm. At least thia RFC grants me more vectors of research; thanks again... > Lars > -- > Lars Eggert NEC Network Laboratories -- Brian Reichert <[EMAIL PROTECTED]> 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vlan with its own ether / mac address?
is it possible to set up a vlan device with its own ether address? I've tried the following: ifconfig vlan0 create ifconfig vlan0 vlan 1 vlandev fxp0 up ifconfig vlan0 inet 10.0.0.10 netmask 255.255.255.0 \ ether 00:a0:c9:f1:4e:6e ifconfig: ether: bad value but changing the ether value after the device is up 'works', but caused me to only have access to the vlan ip. my existing fxp0 device fxp0: flags=8843 mtu 1500 inet 10.0.0.2 netmask 0xff00 broadcast 10.255.255.255 ether 00:a0:c9:f1:4e:6d media: Ethernet autoselect (100baseTX ) status: active the faked vlan0 device: vlan0: flags=8843 mtu 1500 inet 10.0.0.10 netmask 0xff00 broadcast 10.0.0.255 ether 00:a0:c9:f1:4e:6e media: Ethernet autoselect (100baseTX ) status: active vlan: 1 parent interface: fxp0 basically I'm trying to set up dhcp to configure unknown hosts in a seperate network to allow them to register their mac address and then be allocated a ip in the "real" network. And need a way to test with several clients, but I've only got one nic in my box. looks like I'll be buying another nic and use dhcping -h and see if it does the trick - but just wanted to see if there is a all free and nice software solution. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vlan with its own ether / mac address?
On Fri, Feb 13, 2004 at 09:30:31PM +0100, Bjorn Eikeland wrote: > is it possible to set up a vlan device with its own ether address? > I've tried the following: > > ifconfig vlan0 create > ifconfig vlan0 vlan 1 vlandev fxp0 up > ifconfig vlan0 inet 10.0.0.10 netmask 255.255.255.0 \ > ether 00:a0:c9:f1:4e:6e > ifconfig: ether: bad value > > but changing the ether value after the device is up 'works', > but caused me to only have access to the vlan ip. > > my existing fxp0 device > fxp0: flags=8843 mtu 1500 > inet 10.0.0.2 netmask 0xff00 broadcast 10.255.255.255 > ether 00:a0:c9:f1:4e:6d > media: Ethernet autoselect (100baseTX ) > status: active > > the faked vlan0 device: > vlan0: flags=8843 mtu 1500 > inet 10.0.0.10 netmask 0xff00 broadcast 10.0.0.255 > ether 00:a0:c9:f1:4e:6e > media: Ethernet autoselect (100baseTX ) > status: active > vlan: 1 parent interface: fxp0 You might try putting the interface in promisc mode. I'm not sure that will be sufficent, but it might be. I suspect the problem is likely to be that the recieve filter on many NICs only supports two modes promisc and self+broadcast. You want a mode where you get self1+self2+broadcast. Some multicast filters probably do support this. > basically I'm trying to set up dhcp to configure unknown hosts > in a seperate network to allow them to register their mac address > and then be allocated a ip in the "real" network. And need a way > to test with several clients, but I've only got one nic in my box. You might be able to create virtual ethernet interfaces via tap(4) and then bridge them. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgp0.pgp Description: PGP signature
