slightly complex query - one machine with two network interfaces
Hello list, I hope you can help. I have a freebsd 8.0-R machine with a wired and a wireless interface. The wired network has real IP addresses. I want the wireless to talk to the wireless network which is behind a NAT/firewall. The wireless interface on the freebsd box does not want to route traffic (although it would be nice if it could function as a repeater if a wireless laptop was in the vicinity closer to it than the actual access point, but that's another matter). All I want the wireless interface on the freebsd box to do right at this moment is to talk to the other wireless devices. The network is 192.168.0.0/24 Now, if I bring both interfaces up on the freebsd box, routing on that box turns horrible. but the routing table looks normal with 0.0.0.0 traffic going out on the wired re0 interface. I can ping the wireless interface from another computer on the private network, but that's about it. Can anyone give me pointers on how to make the wireless interface more usable? basically, I want to export via either nfs or samba some shares to the wireless network, but routing ropiness seems to kill this. cheers -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: slightly complex query - one machine with two network interfaces
John wrote: Hello list, I hope you can help. I have a freebsd 8.0-R machine with a wired and a wireless interface. The wired network has real IP addresses. I want the wireless to talk to the wireless network which is behind a NAT/firewall. The wireless interface on the freebsd box does not want to route traffic (although it would be nice if it could function as a repeater if a wireless laptop was in the vicinity closer to it than the actual access point, but that's another matter). All I want the wireless interface on the freebsd box to do right at this moment is to talk to the other wireless devices. The network is 192.168.0.0/24 Now, if I bring both interfaces up on the freebsd box, routing on that box turns horrible. but the routing table looks normal with 0.0.0.0 traffic going out on the wired re0 interface. I can ping the wireless interface from another computer on the private network, but that's about it. Can anyone give me pointers on how to make the wireless interface more usable? basically, I want to export via either nfs or samba some shares to the wireless network, but routing ropiness seems to kill this. Hmmm... this isn't a particularly complex setup really. By bringing up your wireless i/f and assigning it an IP and netmask, you should create a route to the directly attached network (192.168.0.0/24) automatically. Given that, you should certainly have the capability to ping other hosts on that network, and they should be able to ping you. If there isn't an entry for 192.168.0.0/24 in the output of % netstat -rn (note: it may be printed as 192.168.0/24) then try something like this: # route add -net 182.168.0.0/24 -interface wlan0 wlan0 should be the correct interface on 8.0-R but other OS versions will probably need to substitute the particular device matching their hardware. If that doesn't work, then please show us some real data: the output from # ifconfig -a # netstat -rn plus any /etc/rc.conf settings relating to ifconfig or wlan. Once you've got the basic networking going, it's downhill from there. You'll need to provide some sort of means of doing name resolution for the wireless network (minimally this means adding entries to /etc/hosts, but it could require fiddling with /etc/resolv.conf or other possibilities). You need to be careful that the source address of packets you send into the wireless lan is the IP number on your wlan interface otherwise hosts on the wlan will send their replies out through the NAT gateway (their default route) instead of straight back to you. By and large this will just work automatically -- there are some software packages where you can override the normal behaviour, but presumably you should know if you've set up anything like that. If you suspect this is a problem, use tcpdump or wireshark to capture and examine the traffic passing across your wlan interface. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: slightly complex query - one machine with two network interfaces
On Sun, Nov 29, 2009 at 10:56:11AM +, Matthew Seaman wrote: Thanks for your help! I will try what you suggest when I'm back at home. -- John - comp dot john at googlemail dot com OpenBSD firewall | FreeBSD desktop | Ubuntu Karmic laptop GPG: 0xF08A33C5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: slightly complex query - one machine with two network interfaces
Date: Sun, 29 Nov 2009 10:16:53 + From: John comp.j...@googlemail.com Subject: slightly complex query - one machine with two network interfaces To: freebsd-questions freebsd-questions@freebsd.org Message-ID: 20091129101652.gb48...@potato Content-Type: text/plain; charset=us-ascii it. Can anyone give me pointers on how to make the wireless interface more usable? basically, I want to export via either nfs or samba some shares to the wireless network, but routing ropiness seems to kill this. I suggest you should be careful here. By default NFS seems to assume that only trusted hosts (not users) will connect. If your share is read-only that may not be a problem (depending on the information shared). You should also make sure samba is using (sufficiently strongly) encrypted passwords as well. You may want to read the security section of the handbook. Regards, James Phillips PS: If I want to be paranoid over wireless I need new hardware. My PII 350 can only do SSH (128 bit 3-DES?) at ~1MB/s. __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to have two active network interfaces on a laptop
I'm wondering how I should handle my laptops network interfaces. I'm often forced to wait for bsdstats, ntpd and sshd to time out if I'm not connected. Even if I am connected on one interface the default gateway is assigned to the interface that is not connected. I've found some information about profile.sh but it was unclear if this is still implemented in Freebsd. How do I go about solving this? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
combining network interfaces
Hello, Is there a way in FreeBSD to combine a number of network interfaces to one virtual interface on which I can tcpdump all the traffic of those interfaces at once? Thanks, -- Frederique ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: combining network interfaces
Frederique Rijsdijk wrote: Hello, Is there a way in FreeBSD to combine a number of network interfaces to one virtual interface on which I can tcpdump all the traffic of those interfaces at once? You're talking about bridging. Look at http://www.freebsd.org/doc/en/books/handbook/network-bridging.html Section 31.5.7.1 is what you're asking for. -- Jacques Manukyan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: combining network interfaces
Jacques Manukyan mlfree...@streamingedge.com writes: Frederique Rijsdijk wrote: Hello, Is there a way in FreeBSD to combine a number of network interfaces to one virtual interface on which I can tcpdump all the traffic of those interfaces at once? You're talking about bridging. Look at http://www.freebsd.org/doc/en/books/handbook/network-bridging.html Section 31.5.7.1 is what you're asking for. I don't think he wants to forward the traffic between those interfaces, though; just dump them all together. I'm not sure, though. If I'm right, I don't think tcpdump can do that directly. One idea might be to run a firewall to choose the packets and to forward a copy to a dummy interface that can be monitored. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: combining network interfaces
Lowell Gilbert wrote: Jacques Manukyan mlfree...@streamingedge.com writes: Frederique Rijsdijk wrote: Hello, Is there a way in FreeBSD to combine a number of network interfaces to one virtual interface on which I can tcpdump all the traffic of those interfaces at once? You're talking about bridging. Look at http://www.freebsd.org/doc/en/books/handbook/network-bridging.html Section 31.5.7.1 is what you're asking for. I don't think he wants to forward the traffic between those interfaces, though; just dump them all together. I'm not sure, though. You're right. If I'm right, I don't think tcpdump can do that directly. One idea might be to run a firewall to choose the packets and to forward a copy to a dummy interface that can be monitored. It might be an idea. Somehow I think it should be possible in a more simple way. Now reading 'man 4 lagg'... -- Frederique ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: combining network interfaces
--On April 9, 2009 5:18:26 PM +0200 Frederique Rijsdijk frederi...@isafeelin.org wrote: Hello, Is there a way in FreeBSD to combine a number of network interfaces to one virtual interface on which I can tcpdump all the traffic of those interfaces at once? Take a look at netgraph. pgpG4EBL9ulad.pgp Description: PGP signature
Re: combining network interfaces
Frederique Rijsdijk wrote: Is there a way in FreeBSD to combine a number of network interfaces to one virtual interface on which I can tcpdump all the traffic of those interfaces at once? pflog(4) might be a possibility. -- Christian Laursen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Reconfiguring network interfaces
On Sun, Jul 6, 2008 at 8:12 AM, Mel [EMAIL PROTECTED] wrote:
On Sunday 06 July 2008 16:06:49 David Allen wrote:
I need to make several wholesale changes to a few different systems,
and I'd prefer to do it over SSH without losing connectivity where
possible. I know I can use ifconfig, or edit /etc/rc.conf directly
and reboot, but is there a canonical way to make the changes in
/etc/rc.conf and reload those changes to ensure everything is in a
known state? From what I can determine, running netif stop/start
would work, but would require I do that locally.
So, you want to make changes to a machine and confirm they're correct, but
when they're not, the old settings should be restored:
0) make sure sshd listens on all ip's ('INADDR_ANY'), not preconfigured set.
# cp -p /etc/rc.conf /etc/rc.conf.BEFORE_CHANGE
# ${EDITOR} /etc/rc.conf
# cp -p /etc/rc.conf /etc/rc.conf.CHANGES
Then this script, say /root/bin/testrc.sh:
=
#!/bin/sh
/etc/rc.d/netif stop
sleep 1
/etc/rc.d/netif start
# sleep for 5 minutes, should be ample time to re-establish the ssh
# connection.
sleep 300
# We were not killed, this means the connection is faulty
cp -p /etc/rc.conf.BEFORE_CHANGE /etc/rc.conf
/etc/rc.d/netif stop
sleep 1
/etc/rc.d/netif start
=
Then run as:
daemon -p /var/run/testrc.pid /root/bin/testrc.sh
When you can log back in, simply:
kill `cat /var/run/testrc.pid` ; rm /var/run/testrc.pid
And rm /etc/rc.conf.BEFORE_CHANGE if you feel comfy.
If you couldn't log back in, inspect /etc/rc.conf.CHANGES and adjust, rm the
pid file, rince and repeat.
LOL. You've turned what was could have been an awkward scenario and a
cheap and dirty hack into something almost elegant. Me, I'm just
trying to save some trips but I'm sure there's enough of us who have
encountered a situation where physical access is out of the question
or simply not doable.
My thanks to everyone that replied.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Reconfiguring network interfaces
I need to make several wholesale changes to a few different systems, and I'd prefer to do it over SSH without losing connectivity where possible. I know I can use ifconfig, or edit /etc/rc.conf directly and reboot, but is there a canonical way to make the changes in /etc/rc.conf and reload those changes to ensure everything is in a known state? From what I can determine, running netif stop/start would work, but would require I do that locally. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reconfiguring network interfaces
At 09:06 AM 7/6/2008, David Allen wrote: I need to make several wholesale changes to a few different systems, and I'd prefer to do it over SSH without losing connectivity where possible. I know I can use ifconfig, or edit /etc/rc.conf directly and reboot, but is there a canonical way to make the changes in /etc/rc.conf and reload those changes to ensure everything is in a known state? From what I can determine, running netif stop/start would work, but would require I do that locally. You pretty much need to be on the console rather than ssh'd in to make those changes interactively. You can do them remotely via a cron job or at job, but any mistake will require a trip to the console. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reconfiguring network interfaces
David Allen wrote: I need to make several wholesale changes to a few different systems, and I'd prefer to do it over SSH without losing connectivity where possible. I know I can use ifconfig, or edit /etc/rc.conf directly and reboot, but is there a canonical way to make the changes in /etc/rc.conf and reload those changes to ensure everything is in a known state? From what I can determine, running netif stop/start would work, but would require I do that locally. You could also use the alias featue, adding the new ip, sshing into the new ip, and dump the old ip. ** Though I haven't tried this method personally. ** HTH cya Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reconfiguring network interfaces
On Sunday 06 July 2008 16:06:49 David Allen wrote:
I need to make several wholesale changes to a few different systems,
and I'd prefer to do it over SSH without losing connectivity where
possible. I know I can use ifconfig, or edit /etc/rc.conf directly
and reboot, but is there a canonical way to make the changes in
/etc/rc.conf and reload those changes to ensure everything is in a
known state? From what I can determine, running netif stop/start
would work, but would require I do that locally.
So, you want to make changes to a machine and confirm they're correct, but
when they're not, the old settings should be restored:
0) make sure sshd listens on all ip's ('INADDR_ANY'), not preconfigured set.
# cp -p /etc/rc.conf /etc/rc.conf.BEFORE_CHANGE
# ${EDITOR} /etc/rc.conf
# cp -p /etc/rc.conf /etc/rc.conf.CHANGES
Then this script, say /root/bin/testrc.sh:
=
#!/bin/sh
/etc/rc.d/netif stop
sleep 1
/etc/rc.d/netif start
# sleep for 5 minutes, should be ample time to re-establish the ssh
# connection.
sleep 300
# We were not killed, this means the connection is faulty
cp -p /etc/rc.conf.BEFORE_CHANGE /etc/rc.conf
/etc/rc.d/netif stop
sleep 1
/etc/rc.d/netif start
=
Then run as:
daemon -p /var/run/testrc.pid /root/bin/testrc.sh
When you can log back in, simply:
kill `cat /var/run/testrc.pid` ; rm /var/run/testrc.pid
And rm /etc/rc.conf.BEFORE_CHANGE if you feel comfy.
If you couldn't log back in, inspect /etc/rc.conf.CHANGES and adjust, rm the
pid file, rince and repeat.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reconfiguring network interfaces
would work, but would require I do that locally. You could also use the alias featue, adding the new ip, sshing into the new ip, and dump the old ip. ** Though I haven't tried this method personally. ** but i did. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
virtualized network interfaces within jails
Hello all I'm attempting to run bind from multiple jails in 6.2, but I can't sem to configure my jail such that its unable to see any other physical interfaces. I want to run several jails on the same physical interface with a vlan associated with each virtual interface. Each finished jail should appear to have only one interface running virtually on a physical NIC in the host OS. Once inside the jail, I only want to see the virtual interface appear as a physical interface, without indicating it is associated with a vlan on the host OS. Xen on fedora appears to be able to do this, but I'd prefer to get this working as a jail. Hardware appears to be suported (Dell 1950, with Broadcom NetX2 cards)... any help is appreciated. ~Joe - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: virtualized network interfaces within jails
On Wed, July 11, 2007 17:05, Joe Barnes wrote: Hello all I'm attempting to run bind from multiple jails in 6.2, but I can't sem to configure my jail such that its unable to see any other physical interfaces. I want to run several jails on the same physical interface with a vlan associated with each virtual interface. Each finished jail should appear to have only one interface running virtually on a physical NIC in the host OS. Once inside the jail, I only want to see the virtual interface appear as a physical interface, without indicating it is associated with a vlan on the host OS. Xen on fedora appears to be able to do this, but I'd prefer to get this working as a jail. http://www.freebsd.org/news/status/report-2007-04-2007-06.html#Network-Stack-Virtualization Rgds, Patrick Hardware appears to be suported (Dell 1950, with Broadcom NetX2 cards)... any help is appreciated. ~Joe - Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to configure switching between network interfaces?
How to configure switching between network interfaces? I would like to determine how, or if, the following can be accomplished with FreeBSD. Configuration: A BSD box setup with 1 GbE NIC and a 4 port 10/100 NIC The GbE interface will have a static IP configured (192.168.10.x/24) Planned Implementation: Along with possibly serving other data such as NFS or HTTP traffic, I would like the interfaces to work as a switch. The GbE interface is a fiber optic NIC which connects to the rest of the network 100 or so meters away. I plan to use the other 4 interfaces to attach hosts to my network. I would prefer all of my hosts to be on the same subnet if possible, otherwise I would just configure routing between the appropriate interfaces. My question then is: Can the interfaces be configured to function as a switch would, allowing the connected hosts to recieve DHCP and other traffic routing from the fiber optic interface via the FreeBSD box. I know that in a basic configuration, 2 interfaces on the same subnet are not a best practice and would required special routing information. I assume that somewhere this can be configured. A good shove in the right direction would be most appreciated. Thanks, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to configure switching between network interfaces?
Myself, I'd get a couple of small fiber/ethernet convertors and then connect everything to a small ethernet switch. A bit more money, but simpler and I like simple. -- Martin On 12/31/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: How to configure switching between network interfaces? I would like to determine how, or if, the following can be accomplished with FreeBSD. Configuration: A BSD box setup with 1 GbE NIC and a 4 port 10/100 NIC The GbE interface will have a static IP configured (192.168.10.x/24) Planned Implementation: Along with possibly serving other data such as NFS or HTTP traffic, I would like the interfaces to work as a switch. The GbE interface is a fiber optic NIC which connects to the rest of the network 100 or so meters away. I plan to use the other 4 interfaces to attach hosts to my network. I would prefer all of my hosts to be on the same subnet if possible, otherwise I would just configure routing between the appropriate interfaces. My question then is: Can the interfaces be configured to function as a switch would, allowing the connected hosts to recieve DHCP and other traffic routing from the fiber optic interface via the FreeBSD box. I know that in a basic configuration, 2 interfaces on the same subnet are not a best practice and would required special routing information. I assume that somewhere this can be configured. A good shove in the right direction would be most appreciated. Thanks, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to configure switching between network interfaces?
[EMAIL PROTECTED] wrote: How to configure switching between network interfaces? I would like to determine how, or if, the following can be accomplished with FreeBSD. Configuration: A BSD box setup with 1 GbE NIC and a 4 port 10/100 NIC The GbE interface will have a static IP configured (192.168.10.x/24) Planned Implementation: Along with possibly serving other data such as NFS or HTTP traffic, I would like the interfaces to work as a switch. The GbE interface is a fiber optic NIC which connects to the rest of the network 100 or so meters away. I plan to use the other 4 interfaces to attach hosts to my network. I would prefer all of my hosts to be on the same subnet if possible, otherwise I would just configure routing between the appropriate interfaces. My question then is: Can the interfaces be configured to function as a switch would, allowing the connected hosts to recieve DHCP and other traffic routing from the fiber optic interface via the FreeBSD box. I know that in a basic configuration, 2 interfaces on the same subnet are not a best practice and would required special routing information. I assume that somewhere this can be configured. A good shove in the right direction would be most appreciated. You can configure the interfaces together as a bridge and FreeBSD will act as a smart switch-- see the bridge(4) manpage or the Handbook for more info. Note that this configuration might make sense if you wanted to impose firewall rules to limit cross-segment traffic while still letting the client machines all be on one subnet. Or you might divert all WWW traffic seen going by to a transparent proxy server. But unless you plan to do something with this traffic like that-- if all you want to do is have a switch-- you'd otherwise be better off getting a 4-port gigabit Cu or Fibre switch then setting up a dedicated server for the task. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to configure switching between network interfaces?
Thanks, I believe thats what i'm looking for. I will probably end up with a cu-fiber switch, but I wanted to know if that was possible in theroy. The switches make more sense anyway because, otherwise, i'll have to setup a makeshift bridge on the server on the other end of the fiber. - Mike - Original Message - From: Chuck Swiger [EMAIL PROTECTED] Date: Sunday, December 31, 2006 12:49 pm Subject: Re: How to configure switching between network interfaces? To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org [EMAIL PROTECTED] wrote: How to configure switching between network interfaces? I would like to determine how, or if, the following can be accomplished with FreeBSD. Configuration: A BSD box setup with 1 GbE NIC and a 4 port 10/100 NIC The GbE interface will have a static IP configured (192.168.10.x/24) Planned Implementation: Along with possibly serving other data such as NFS or HTTP traffic, I would like the interfaces to work as a switch. The GbE interface is a fiber optic NIC which connects to the rest of the network 100 or so meters away. I plan to use the other 4 interfaces to attach hosts to my network. I would prefer all of my hosts to be on the same subnet if possible, otherwise I would just configure routing between the appropriate interfaces. My question then is: Can the interfaces be configured to function as a switch would, allowing the connected hosts to recieve DHCP and other traffic routing from the fiber optic interface via the FreeBSD box. I know that in a basic configuration, 2 interfaces on the same subnet are not a best practice and would required special routing information. I assume that somewhere this can be configured. A good shove in the right direction would be most appreciated. You can configure the interfaces together as a bridge and FreeBSD will act as a smart switch-- see the bridge(4) manpage or the Handbook for more info. Note that this configuration might make sense if you wanted to impose firewall rules to limit cross-segment traffic while still letting the client machines all be on one subnet. Or you might divert all WWW traffic seen going by to a transparent proxy server. But unless you plan to do something with this traffic like that-- if all you want to do is have a switch-- you'd otherwise be better off getting a 4-port gigabit Cu or Fibre switch then setting up a dedicated server for the task. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Wireless adapter not shown in Network Interfaces in KDE Control M odule
I installed FreeBSD 6.1 on Compaq Evo N800c laptop. After installing KDE internal NIC fxp0 appeared in Network Settings. I added Proxim wireless PCMCIA card, recompile the kernel and I can see it in output of ifconfig: UNIX# ifconfig fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.1.39 netmask 0xfc00 broadcast 192.168.3.255 ether 00:08:02:63:54:b0 media: Ethernet autoselect (100baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:20:a6:57:4e:f1 media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid Puppy channel 6 authmode OPEN privacy OFF txpowmax 36 protmode CTS burst bintval 100 In KDE Network settings I can see only fxp0 card. Help please, Thanks, Nathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: multiple network interfaces
On 8/18/05, Daniel Valencia [EMAIL PROTECTED] wrote: Hello, everybody Is there any limit as of how many interfaces can freebsd handle? Im trying to build a switch in a PC box, putting multiple NICs and some software... The issue is, even though all of the cards work correctly by themselves, once I put them together, it doesnt matter what slots i use, I can never make more than two of them work. For even though all the rest appear up as well, I cant ping neither them nor their peers (Im using crossover cables). As nobody provided a better reply, I can only suggest to try another OS to see if the hardware is OK. -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
multiple network interfaces
Hello, everybody Is there any limit as of how many interfaces can freebsd handle? Im trying to build a switch in a PC box, putting multiple NICs and some software... The issue is, even though all of the cards work correctly by themselves, once I put them together, it doesnt matter what slots i use, I can never make more than two of them work. For even though all the rest appear up as well, I cant ping neither them nor their peers (Im using crossover cables). Thank you, Daniel Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
configuring two network interfaces, same subnet
Hello people!, I'm trying to configure 2 network interfaces in the same subnet, because i want to use one interface for NS and the other for MX, if i try bash-2.05b# ifconfig em0 aa.bb.dd.1 netmask 255.255.255.0 bash-2.05b# ifconfig em1 aa.cc.ee.2 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): File exists ok they both cannot be in the same subnet. i know that i cannot have them both in the same subnet without modifying the routing, but im confussed about it. i also tried after settin' one of the ips, deleting the routing bash-2.05b# route delete aa.bb.cc.0 and then setting the ip bash-2.05b# ifconfig em0 aa.bb.dd.1 netmask 255.255.255. ok i can now set the 2 ips in the same subnet but my DNS stops working, i dont want to change the submask, for any of my ips well im confused about it, so i hope you guys could adress me in the right direction, Thanks in advance, Alfredo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: configuring two network interfaces, same subnet
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alfredo Aguirre Sent: 13 June 2005 19:11 To: freebsd-questions@freebsd.org Subject: configuring two network interfaces, same subnet Hello people!, Hi I'm trying to configure 2 network interfaces in the same subnet, because i want to use one interface for NS and the other for MX, if i try bash-2.05b# ifconfig em0 aa.bb.dd.1 netmask 255.255.255.0 bash-2.05b# ifconfig em1 aa.cc.ee.2 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): File exists ok they both cannot be in the same subnet. Yep this thread here http://lists.freebsd.org/pipermail/freebsd-net/2003-July/001108.html Seems to cover it quite well. i know that i cannot have them both in the same subnet without modifying the routing, but im confussed about it. i also tried after settin' one of the ips, deleting the routing bash-2.05b# route delete aa.bb.cc.0 and then setting the ip bash-2.05b# ifconfig em0 aa.bb.dd.1 netmask 255.255.255. ok i can now set the 2 ips in the same subnet but my DNS stops working, i dont want to change the submask, for any of my ips As far as I know you cannt have 2 interfaces on the same subnet full stop on freebsd, and to be fair I cant see what advantage it would give you if you could. Vince well im confused about it, so i hope you guys could adress me in the right direction, Thanks in advance, Alfredo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: configuring two network interfaces, same subnet
Vince dijo: Hello people!, Hi I'm trying to configure 2 network interfaces in the same subnet, because i want to use one interface for NS and the other for MX, if i try bash-2.05b# ifconfig em0 aa.bb.dd.1 netmask 255.255.255.0 bash-2.05b# ifconfig em1 aa.cc.ee.2 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): File exists ok they both cannot be in the same subnet. Yep this thread here http://lists.freebsd.org/pipermail/freebsd-net/2003-July/001108.html Seems to cover it quite well. yep i've checked there and it says: 8- I have two interfaces on a 192.168.1 network and I open a socket, bind the local address to INADDR_ANY and the remote address to something else on the 192.168.1 network, which interface do I pick for outgoing packets? The dark secret in OpenBSD and NetBSD here is that they always pick the same one. You think you're load balancing by putting two interfaces in there, but the general truth is that you're just pouring electrons into unused hardware unless you've carefully configured the system to make use of both interfaces. --8 i'd like to configure one ip for the mail and other one for the dns, to have Alias sound good but the machine has 2 nics already and i dont want to have unused hardware. i know that i cannot have them both in the same subnet without modifying the routing, but im confussed about it. i also tried after settin' one of the ips, deleting the routing bash-2.05b# route delete aa.bb.cc.0 and then setting the ip bash-2.05b# ifconfig em0 aa.bb.dd.1 netmask 255.255.255. ok i can now set the 2 ips in the same subnet but my DNS stops working, i dont want to change the submask, for any of my ips As far as I know you cannt have 2 interfaces on the same subnet full stop on freebsd, and to be fair I cant see what advantage it would give you if you could. so it wont give any advantage just having one nic for each one (the NS and the mail server)? Vince well im confused about it, so i hope you guys could adress me in the right direction, Thanks in advance, Alfredo Thanks in advance, Alfredo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Best way to handle network interfaces on a laptop?
So, I've got a laptop with two network interfaces (a wired one, xl0, and a wireless, wi0). The network setup around here gives me a static IP for the wired inteface, and DHCP for the wireless. My question has (I think) to do with routing; when I have the config for xl0 in /etc/rc.conf, and it starts on boot, starting wi0 doesn't help with connectivity. Specifically, much of the use of this machine is in unwired sorts of places, where I want to use the wi0 interface and not the xl0 interface. If I don't have xl0 in /etc/rc.conf, and then dhclient wi0, it works fine. If I do have xl0 in rc.conf, I can't figure out how to make wi0 route things if it isn't plugged into a wire. ifconfig xl0 down, which I thought would work, doesn't. Help? Thanks! --Mac pgpm8a5tCnebi.pgp Description: PGP signature
Re: Best way to handle network interfaces on a laptop?
On Mar 29, 2005, at 5:56 PM, Mac Mason wrote: Specifically, much of the use of this machine is in unwired sorts of places, where I want to use the wi0 interface and not the xl0 interface. If I don't have xl0 in /etc/rc.conf, and then dhclient wi0, it works fine. If I do have xl0 in rc.conf, I can't figure out how to make wi0 route things if it isn't plugged into a wire. Try: route delete default route add default IP_of_wireless_NIC It may be that deleting the default route first, before you grab a lease via dhclient wi0 would also set up a new default route for you... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to transparently set-up two differently configured network interfaces?
Hi all, I find myself with little time to find a neat solution for the following situation: We have a Shuttle on which fbsd 5.2.1 is installed. Now, the machine used to have just one network interface, of which I'd simply switch the settings when the machine needs to be used for demo purposes, rather than running in our local network. So, I just installed a second network interface, and I'd like the machine to become smart enough to do the following: -Boot, check if rl0 has a cable attached to it, and if so, use that as active network interface, with fixed settings (gateway, nameserver, and IPv4 address all set to 192.168.1.1). -if rl0 does not have a cable attached to it, use DHCP on interface rl1 and use that. Sounds relatively straightforward. So I set the settings of the rl0 and rl1 network interfaces (via sysinstall) to reflect just that. However, when doing so, the gateways seem to get shared, and just get set to 192.168.1.1. Can anyone point me to the proper means of setting this up properly? Normally I would RTFM regarding dhclient.conf and such, but unfortunately I find myself with very little time available for spending on it, so I hope someone can give me a quick pointer in the right direction... Cheerz! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
shutting down network interfaces
I have two netcards and want to shut down one of them without rebooting. -- Best regards, flux mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shutting down network interfaces
flux wrote: I have two netcards and want to shut down one of them without rebooting. As root: #ifconfig xl1 down where xl1 is the name/number of the interface. HTH, Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shutting down network interfaces
On Thu, 18 Dec 2003 17:02:48 -0800 flux [EMAIL PROTECTED] probably wrote: I have two netcards and want to shut down one of them without rebooting. What do you mean by shutting it down? Not sure, but may it be # ifconfig down /dev/whatever ? -- Best regards, flux mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- DoubleF A tautology is a thing which is tautological. pgp0.pgp Description: PGP signature
Re: shutting down network interfaces
I have two netcards and want to shut down one of them without rebooting. You have been directed to the man page for ifconfig several times now. Probably it is about time to look it over. Also, try setting your system clock correctly. jerry -- Best regards, flux mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: shutting down network interfaces
At 08:02 PM 12/18/2003, you wrote: I have two netcards and want to shut down one of them without rebooting. man ifconfig will tell you what to do. the short answer: ifconfig interface_card down ie : ifconfig ed0 down cheers dave ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Network interfaces
Hi, I have a Inspiron 5100 and I install FreeBSD 4.8 on it. The computer has an integrated NIC. After installation and typing ifconfig I see the there was no network interfaces detected. Typing /stand/sysinstall and checking the network interfaces configuration I see the fallowing: faith0 unknown network interface type sl0 SLIP interface on device /dev/cuaa0 (COM1) ppp0PPP interface on device /dev/cuaa0 (COM1) Thank you for your time. Sincerely Artem Tkachenko ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network interfaces
On Tuesday 12 August 2003 00:34, Tkachenko, Artem N wrote: Hi, I have a Inspiron 5100 and I install FreeBSD 4.8 on it. The computer has an integrated NIC. After installation and typing ifconfig I see the there was no network interfaces detected. Typing /stand/sysinstall and checking the network interfaces configuration I see the fallowing: faith0unknown network interface type sl0 SLIP interface on device /dev/cuaa0 (COM1) ppp0 PPP interface on device /dev/cuaa0 (COM1) I don't have an inspiron to test this, but I found the following link with Google : http://jturner.tapetrade.net/docs/installing_freebsd_on_inspirion5100.html Basically the page says your laptop has a broadcom 4400 NIC which can be used through an unsupported driver. Hope this helps... grtz, Daan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Network interfaces
Check /var/run/dmesg.boot file and look for boot messages to see if the Nic hardware is found. If so then you have to read the kernel source for the correct kernel option to add to your kernel source and recompile to active the software drivers for you Nic hardware. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tkachenko, Artem N Sent: Monday, August 11, 2003 6:35 PM To: Freebsd-Config (E-mail); Freebsd-Questions (E-mail) Subject: Network interfaces Hi, I have a Inspiron 5100 and I install FreeBSD 4.8 on it. The computer has an integrated NIC. After installation and typing ifconfig I see the there was no network interfaces detected. Typing /stand/sysinstall and checking the network interfaces configuration I see the fallowing: faith0 unknown network interface type sl0 SLIP interface on device /dev/cuaa0 (COM1) ppp0PPP interface on device /dev/cuaa0 (COM1) Thank you for your time. Sincerely Artem Tkachenko ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: numb...network interfaces...
- Original Message - From: [EMAIL PROTECTED] Date: Sun, 15 Dec 2002 23:16:46 +0200 (EET) To: [EMAIL PROTECTED] Subject: Re: number of network interfaces supported In article [EMAIL PROTECTED] you wrote: | Hello, | | Are there any restrictions on the number of network interfaces |supported | by kernel? I need at least 6. | | Where did Yoou get so many slots ? :) The casinophobic reply includes the phrase, but you'd need eight to make a spider. Somewhere in an itchy corner of a biochemical memory system the number 4 (four) echos quietly. Has that gone the way of the lumbering wd(4)? Are the dual fang-marks circumscribing its skull an anthropological mystery? If I pulled out an old 486dx2-80 and poked three NE2000, two EE-8/16, and three 3c900TX how fast could I send my credit card numbers to Homeland Security (sic)? There's a child in British Honduras who could use those 72-pin SIMMs, won't you please think of him? Love, Franklin Pierce -- ___ Get your free email from http://mymail.operamail.com Powered by Outblaze To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
number of network interfaces supported
Hello, Are there any restrictions on the number of network interfaces supported by kernel? I need at least 6. Thanks, Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: number of network interfaces supported
In article [EMAIL PROTECTED] you wrote: Hello, Are there any restrictions on the number of network interfaces supported by kernel? I need at least 6. Where did Yoou get so many slots ? :) -- AY7-UANIC || AY15-RIPE To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: number of network interfaces supported
On Sun, 2002-12-15 at 21:16, [EMAIL PROTECTED] wrote: In article [EMAIL PROTECTED] you wrote: Hello, Are there any restrictions on the number of network interfaces supported by kernel? I need at least 6. The simplest way to achieve this would be to get a couple of quad ethernet cards, I would think. Where did Yoou get so many slots ? :) -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: number of network interfaces supported
On Sunday, 15 December 2002 at 22:23:09 +0300, Alexey Koptsevich wrote: Hello, Are there any restrictions on the number of network interfaces supported by kernel? I need at least 6. I don't know of any hard limit, but it would be pretty high. There have been more than 6 by default in the past, so I don't think you should have any problem. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
