Re: network configuration problem
Hello, Steve Bertrand wrote: > > Johannes-Maria Kaltenbach wrote: > > Hello, > > > > many thanks for your help. > > > > The problem was already solved with the first answer I read > > by Steve Bertrand, > > Derek does have an important point. > > If you ever need to add any other workstations to the network, you will > want to ensure that the IP you added to FreeBSD manually does not fall > within the DHCP scope of the gateway. > > For instance, if you plug a Windows PC into the gateway, it will by > default request an address via DHCP. If the gateway provides the Windows > PC the same address as FreeBSD, you will have communication problems. > > Regards, > > Steve I've changed the address according to Derek's helpful explanation. Thank you both for your valuable help. Regards, Johannes-Maria ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network configuration problem
Warren Block wrote: On Tue, 8 Apr 2008, Steve Bertrand wrote: If you ever need to add any other workstations to the network, you will want to ensure that the IP you added to FreeBSD manually does not fall within the DHCP scope of the gateway. For instance, if you plug a Windows PC into the gateway, it will by default request an address via DHCP. If the gateway provides the Windows PC the same address as FreeBSD, you will have communication problems. It's neater and safer to keep static and dynamic addresses in separate ranges, but often not strictly necessary. I agree, however, my rule of thumb is to not trust hardware to strictly adhere to proper standards or RFC's, especially when it comes down to CPE ;) Anyone who has managed a sizable network will know that not properly managing things like this manually is asking for trouble. Cheers, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network configuration problem
On Tue, 8 Apr 2008, Steve Bertrand wrote: If you ever need to add any other workstations to the network, you will want to ensure that the IP you added to FreeBSD manually does not fall within the DHCP scope of the gateway. For instance, if you plug a Windows PC into the gateway, it will by default request an address via DHCP. If the gateway provides the Windows PC the same address as FreeBSD, you will have communication problems. It's neater and safer to keep static and dynamic addresses in separate ranges, but often not strictly necessary. DHCP servers are supposed to ping an address before assuming it's unused. That normally means you can get away with manually allocating IP addresses inside a DHCP range. Unless some well-meaning person has blocked all ICMP, or disabled the DHCP server's ping address check. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network configuration problem
Johannes-Maria Kaltenbach wrote: Hello, many thanks for your help. The problem was already solved with the first answer I read by Steve Bertrand, Derek does have an important point. If you ever need to add any other workstations to the network, you will want to ensure that the IP you added to FreeBSD manually does not fall within the DHCP scope of the gateway. For instance, if you plug a Windows PC into the gateway, it will by default request an address via DHCP. If the gateway provides the Windows PC the same address as FreeBSD, you will have communication problems. Regards, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: network configuration problem
Hello, many thanks for your help. The problem was already solved with the first answer I read by Steve Bertrand, ... > You essentially gave yourself an address outside of the gateways LAN > address scope, and then proceeded to route all unknown traffic to yourself. > > You probably want: > > # ifconfig rl0 192.168.2.100 255.255.255.0 > > ...and > > # route add default 192.168.2.1 Tanks also for your hint: > Then, for name resolution: > > # echo "nameserver ip.of.isp.dns" >> /etc/resolv.conf I'm also thankful for all the other replies to my question, of course; always happy to learn something. Regards, Johannes-Maria ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
{Disarmed} Re: network configuration problem
At 04:08 AM 4/8/2008, Johannes-Maria Kaltenbach wrote: Hello, at the moment I'm using internet an emails via a 56k modem and ppp. I want to change to DSL -- but I'm not able to do it without help. I've bought a router/gateway from my provider (Telekom/T-Online) which is called "Speedport W 502V Typ A" an has the ip address 192.168.2.1; it is connectet to an ethernet card (rl0). The provider requests DHCP, but this doesn't work; I get the message | Bogus domain search list 15: Speedport_W_502V_Typ_A (Speedport_W_502V_Typ_A) | Invalid lease option - ignoring offer several times and the error message "Network is unreachable". Then I assigned an address (e. g. 192.168.10.1) to the ethernet card with the help of ifconfig rl0 192.168.10.1 255.255.255.0 You need to setup your IP on the same subnet as your router, Check the documentation on your router and choose an address NOT given as a DHCP address. Many routers start their DHCP pool at 100, so you could try: ifconfig rl0 192.168.2.10 255.255.255.0 Then: route add default 192.168.2.1 This would work as long as the 192.168.2.10 is outside the DHCP pool. -Derek and made it the default route: route add default 192.168.10.1 output of ifconfig: | rl0: flags=8843 mtu 1500 | options=8 | inet 192.168.10.1 netmask 0xff00 broadcast 255.255.255.0 | inet6 fe80::214:85ff:fe75:eac8%rl0 prefixlen 64 scopeid 0x1 | ether 00:14:85:75:ea:c8 | media: Ethernet autoselect (100baseTX ) | status: active and netstat: | Routing tables | | Internet: | DestinationGatewayFlagsRefs Use Netif Expire | default192.168.10.1 UGS 0 2304rl0 | localhost localhost UH 0 490lo0 | 192.168.10 link#1 UC 00rl0 | 192.168.10.1 00:14:85:75:ea:c8 UHLW2 36lo0 I cannot "ping" the router/gateway: | PING 192.168.2.1 (192.168.2.1): 56 data bytes | 36 bytes from 192.168.10.1: Time to live exceeded | Vr HL TOS Len ID Flg off TTL Pro cks Src Dst | 4 5 00 5400 025f 0 01 01 29f8 192.168.10.1 192.168.2.1 | | 36 bytes from 192.168.10.1: Time to live exceeded | Vr HL TOS Len ID Flg off TTL Pro cks Src Dst | 4 5 00 5400 0269 0 01 01 29ee 192.168.10.1 192.168.2.1 | | 36 bytes from 192.168.10.1: Time to live exceeded | Vr HL TOS Len ID Flg off TTL Pro cks Src Dst | 4 5 00 5400 0273 0 01 01 29e4 192.168.10.1 192.168.2.1 etc. With "firefox http://192.168.2.1"; (to get the configuration menu of the speedport) I get the error message: | The connection was refused when attempting to contact 192.168.2.1. and with telnet: | Trying 192.168.2.1... | telnet: connect to address 192.168.2.1: No route to host | telnet: Unable to connect to remote host What I'm doing wrong? Can you please help me? Thanks, Johannes-Maria P. S.: I'm using FreeBSD 6.0-RELEASE. (That's the only operating system on my pc, so I cannot test or configure the speedport with Linux or MS-Windows.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: network configuration problem
I've bought a router/gateway from my provider (Telekom/T-Online) which is called "Speedport W 502V Typ A" an has the ip address 192.168.2.1; it is connectet to an ethernet card (rl0). 192.168.2.1/24 is in a different network than 192.168.10.1/24. Your gateway and your workstation will not be able to communicate with one another. Then I assigned an address (e. g. 192.168.10.1) to the ethernet card with the help of and made it the default route: route add default 192.168.10.1 You essentially gave yourself an address outside of the gateways LAN address scope, and then proceeded to route all unknown traffic to yourself. You probably want: # ifconfig rl0 192.168.2.100 255.255.255.0 ...and # route add default 192.168.2.1 Then, for name resolution: # echo "nameserver ip.of.isp.dns" >> /etc/resolv.conf Regards, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
Giorgos Keramidas wrote:
[ in dhclient.conf ]
interface "ath0" {
prepend domain-name-servers 196.168.1.1;
}
Neat. I used another workaround (don't remember exactly what) back then,
but this sure looks tidier.
Something to remember...
Alphons
--
VISTA - Viruses Intruders Spyware Trojans Adware
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On 2008-01-30 22:07, Alphons Fonz van Werven <[EMAIL PROTECTED]> wrote:
> Jerry McAllister wrote:
> [/etc/resolv.conf]
>
>> I think DHCP makes it if you do dynamic
>
> It did so in 6.1-RELEASE and it's not likely that this has changed.
> In fact, I had to explicitly config DHCP to not overwrite my resolv.conf
> (because I wanted my own DNS server to be queried before the ISP's).
FWIW, there's an option which may help with this:
[ in dhclient.conf ]
interface "ath0" {
prepend domain-name-servers 196.168.1.1;
}
That's what I currently use :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
no mine is not dynamic and I have the resolv.conf file set-up. It works fine now. I had some issues with FTP ing and some address conflict message for ssh/tcp. I sysinstalled and disabled SSH there, I guess probably cos inetd takes care of it and ftp also works fine now, i guess after etc/rc.conf & resolve.conf were modified Thanks a lot Bhuvana On Wed, Jan 30, 2008 at 5:07 PM, Alphons Fonz van Werven < [EMAIL PROTECTED]> wrote: > Jerry McAllister wrote: > > [/etc/resolv.conf] > > > I think DHCP makes it if you do dynamic > > It did so in 6.1-RELEASE and it's not likely that this has changed. > In fact, I had to explicitly config DHCP to not overwrite my resolv.conf > (because I wanted my own DNS server to be queried before the ISP's). > > Alphons > > -- > VISTA - Viruses Intruders Spyware Trojans Adware > > ___ > 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: Network configuration in FreeBSD
Jerry McAllister wrote: [/etc/resolv.conf] I think DHCP makes it if you do dynamic It did so in 6.1-RELEASE and it's not likely that this has changed. In fact, I had to explicitly config DHCP to not overwrite my resolv.conf (because I wanted my own DNS server to be queried before the ISP's). Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On Wed, Jan 30, 2008 at 03:09:00PM -0500, Bhuvaneswari Ramkumar wrote: > strangely my /etc has no resolv.conf file at all ! It will only have one if you make one by setting up networking. sysinstall makes one if you set up a static IP. I think DHCP makes it if you do dynamic, but I don't have much experience with DHCP. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
i got my ISP's IP address from some webpage. i am at home running DSL here is what my file looks like kv_bsd# kv_bsd# cat /etc/resolv.conf nameserver 192.168.0.1 kv_bsd# i just had to create that file On Wed, 30 Jan 2008, Bhuvaneswari Ramkumar wrote: strangely my /etc has no resolv.conf file at all ! On Wed, Jan 30, 2008 at 2:56 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: On Wed, Jan 30, 2008 at 01:01:18PM -0500, Bhuvaneswari Ramkumar wrote: Is it a cause of concern if I dont have any route marked as default ? I see so when i use the netstat command Yes. You need a default router specified because that is the address that becomes your gateway to the rest of the network. You also need a nameserver specified in your /etc/resolv.conf file unless you plan to manually specify every other host you wish to talk to. jerry On Wed, Jan 30, 2008 at 12:57 PM, Bhuvaneswari Ramkumar < [EMAIL PROTECTED]> wrote: with the above assigned IP address and net-mask I'm reading to make it work and ping my LAN successfully ( which it doesn't now) before I put them in the rc.conf script. On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: ifconfig em0 up also doesnt help ping my LAN. the ifconfig -a output now reads the IP I just added, as well as the net-mask & the 100 Mbps active linnk. quick question : I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I restart my application, is it some kind of a temporary address assignment, bcos whatever I assigned was not visible today when I re-booted and I had to do it again, probably I should set this in the conf file also ? maybe as another user said my NIC is not enabled or something like that. You have to put it in /etc/rc.conf so it will be taken care of during network initialization each time you boot. Everything at startup reads the /etc/rc.conf and finds variables it needs to do its startup and network startup does that too. So, you put in a line like: ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" and defaultrouter="1.1.1.3" Amongst a number of other startup settings in /etc/rc.conf network startup sees those and says 'oh, I know what to do with those' and runs the ifconfig, etc. Note that putting it in rc.cong only causes a 'ifconfig_em0' variable to be set to"inet 1.1.1.2 netmask 255.255.255.0" and the 'defaultrouter' variable to be set to "1.1.1.3" It is up to the startup programs to do something about it. The startup programs are generally run from the /etc/rc script and from other scripts that it runs. jerry On Wed, Jan 30, 2008 at 12:14 PM, Ashish < [EMAIL PROTECTED]> wrote: ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: | I did have an IP address assigned to my ethernet interface( using the | ifconfig command) but I'm unable to ping anybody in my LAN. In the 'ifconfig -a' output you posted earlier, the 'em0' (your desired interface) interface neither has any IP address assigned to it, nor its UP . So, if you've assigned an IP address to 'em0', then also make sure its UP, by doing 'ifconfig em0 up' . HTH -- Ashish Shukla ??? http://wahjava.wordpress.com/ ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- -- ___ 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]" *--* Kayven Riese, BSCS, MS (Physiology and Biophysics) (415) 902 5513 cellular http://kayve.net Webmaster http://ChessYoga.org *--* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
strangely my /etc has no resolv.conf file at all ! On Wed, Jan 30, 2008 at 2:56 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > On Wed, Jan 30, 2008 at 01:01:18PM -0500, Bhuvaneswari Ramkumar wrote: > > > Is it a cause of concern if I dont have any route marked as default ? > > I see so when i use the netstat command > > Yes. You need a default router specified because that is the > address that becomes your gateway to the rest of the network. > > You also need a nameserver specified in your /etc/resolv.conf file > unless you plan to manually specify every other host you wish to talk to. > > jerry > > > > > On Wed, Jan 30, 2008 at 12:57 PM, Bhuvaneswari Ramkumar < > > [EMAIL PROTECTED]> wrote: > > > > > with the above assigned IP address and net-mask I'm reading to make it > > > work and ping my LAN successfully ( which it doesn't now) before I > put them > > > in the rc.conf script. > > > > > > > > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> > > > wrote: > > > > > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar > wrote: > > > > > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > > > > > the ifconfig -a output now reads the IP I just added, as well as > the > > > > > net-mask & the 100 Mbps active linnk. > > > > > > > > > > quick question : > > > > > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime > I > > > > restart > > > > > my application, is it some kind of a temporary address assignment, > > > > bcos > > > > > whatever I assigned was not visible today when I re-booted and I > had > > > > to do > > > > > it again, probably I should set this in the conf file also ? maybe > as > > > > > another user said my NIC is not enabled or something like that. > > > > > > > > You have to put it in /etc/rc.conf so it will be taken care of > during > > > > network initialization each time you boot. Everything at startup > > > > reads the /etc/rc.conf and finds variables it needs to do its > startup > > > > and network startup does that too. So, you put in a line like: > > > > > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > > > and > > > > defaultrouter="1.1.1.3" > > > > > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > > > > > network startup sees those and says 'oh, I know what to do with > those' > > > > and runs the ifconfig, etc. > > > > Note that putting it in rc.cong only causes a 'ifconfig_em0' > variable > > > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > > > It is up to the startup programs to do something about it. > > > > > > > > The startup programs are generally run from the /etc/rc script and > > > > from other scripts that it runs. > > > > > > > > jerry > > > > > > > > > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > > > | I did have an IP address assigned to my ethernet interface( > using > > > > the > > > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > > > desired > > > > > > interface) interface neither has any IP address assigned to it, > nor > > > > its UP > > > > > > . > > > > > > So, if you've assigned an IP address to 'em0', then also make > sure > > > > its UP, > > > > > > by > > > > > > doing 'ifconfig em0 up' . > > > > > > > > > > > > HTH > > > > > > -- > > > > > > Ashish Shukla ??? > > > > > > http://wahjava.wordpress.com/ > > > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? > --- > > > > -- > > > > > > > > > > > > > > > ___ > > > > > 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: Network configuration in FreeBSD
On Wed, Jan 30, 2008 at 01:35:03PM -0500, Bhuvaneswari Ramkumar wrote: > An explicit call to /etc/netstart tells me that the route & devd with their > pids are already running - though I dont know if this takes into account the > new chages I've done & restarts the network. You will have to do a restart or a -HUP rather than a full start if things are already up and running. jerry > > On Wed, Jan 30, 2008 at 1:01 PM, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> > wrote: > > > Is it a cause of concern if I dont have any route marked as default ? > > I see so when i use the netstat command > > > > > > On Wed, Jan 30, 2008 at 12:57 PM, Bhuvaneswari Ramkumar < > > [EMAIL PROTECTED]> wrote: > > > > > with the above assigned IP address and net-mask I'm reading to make it > > > work and ping my LAN successfully ( which it doesn't now) before I put > > > them > > > in the rc.conf script. > > > > > > > > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> > > > wrote: > > > > > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > > > net-mask & the 100 Mbps active linnk. > > > > > > > > > > quick question : > > > > > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > > > restart > > > > > my application, is it some kind of a temporary address assignment, > > > > bcos > > > > > whatever I assigned was not visible today when I re-booted and I had > > > > to do > > > > > it again, probably I should set this in the conf file also ? maybe > > > > as > > > > > another user said my NIC is not enabled or something like that. > > > > > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > > > network initialization each time you boot. Everything at startup > > > > reads the /etc/rc.conf and finds variables it needs to do its startup > > > > and network startup does that too. So, you put in a line like: > > > > > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > > > and > > > > defaultrouter="1.1.1.3" > > > > > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > > > > > network startup sees those and says 'oh, I know what to do with those' > > > > and runs the ifconfig, etc. > > > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > > > It is up to the startup programs to do something about it. > > > > > > > > The startup programs are generally run from the /etc/rc script and > > > > from other scripts that it runs. > > > > > > > > jerry > > > > > > > > > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > > > | I did have an IP address assigned to my ethernet interface( > > > > using the > > > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > > > desired > > > > > > interface) interface neither has any IP address assigned to it, > > > > nor its UP > > > > > > . > > > > > > So, if you've assigned an IP address to 'em0', then also make sure > > > > its UP, > > > > > > by > > > > > > doing 'ifconfig em0 up' . > > > > > > > > > > > > HTH > > > > > > -- > > > > > > Ashish Shukla ??? > > > > > > http://wahjava.wordpress.com/ > > > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? > > > > --- -- > > > > > > > > > > > > > > > ___ > > > > > 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: Network configuration in FreeBSD
On Wed, Jan 30, 2008 at 12:57:59PM -0500, Bhuvaneswari Ramkumar wrote: > with the above assigned IP address and net-mask I'm reading to make it work > and ping my LAN successfully ( which it doesn't now) before I put them in > the rc.conf script. I should mention that the line changes if you are using DHCP for dynamic IP assignment.Then, your system will query the net for a DHCP server to assign an IP and other DNS information. I only have fixed IPs right now, so I don't know the syntax for that off the top of my head. You can look it up. jerry > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > net-mask & the 100 Mbps active linnk. > > > > > > quick question : > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > restart > > > my application, is it some kind of a temporary address assignment, bcos > > > whatever I assigned was not visible today when I re-booted and I had to > > do > > > it again, probably I should set this in the conf file also ? maybe as > > > another user said my NIC is not enabled or something like that. > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > network initialization each time you boot. Everything at startup > > reads the /etc/rc.conf and finds variables it needs to do its startup > > and network startup does that too. So, you put in a line like: > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > and > > defaultrouter="1.1.1.3" > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > network startup sees those and says 'oh, I know what to do with those' > > and runs the ifconfig, etc. > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > It is up to the startup programs to do something about it. > > > > The startup programs are generally run from the /etc/rc script and > > from other scripts that it runs. > > > > jerry > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > [EMAIL PROTECTED]> wrote: > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > | I did have an IP address assigned to my ethernet interface( using > > the > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > desired > > > > interface) interface neither has any IP address assigned to it, nor > > its UP > > > > . > > > > So, if you've assigned an IP address to 'em0', then also make sure its > > UP, > > > > by > > > > doing 'ifconfig em0 up' . > > > > > > > > HTH > > > > -- > > > > Ashish Shukla ??? > > > > http://wahjava.wordpress.com/ > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- > > -- > > > > > > > > > ___ > > > 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: Network configuration in FreeBSD
On Wed, Jan 30, 2008 at 01:01:18PM -0500, Bhuvaneswari Ramkumar wrote: > Is it a cause of concern if I dont have any route marked as default ? > I see so when i use the netstat command Yes. You need a default router specified because that is the address that becomes your gateway to the rest of the network. You also need a nameserver specified in your /etc/resolv.conf file unless you plan to manually specify every other host you wish to talk to. jerry > > On Wed, Jan 30, 2008 at 12:57 PM, Bhuvaneswari Ramkumar < > [EMAIL PROTECTED]> wrote: > > > with the above assigned IP address and net-mask I'm reading to make it > > work and ping my LAN successfully ( which it doesn't now) before I put them > > in the rc.conf script. > > > > > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> > > wrote: > > > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > > net-mask & the 100 Mbps active linnk. > > > > > > > > quick question : > > > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > > restart > > > > my application, is it some kind of a temporary address assignment, > > > bcos > > > > whatever I assigned was not visible today when I re-booted and I had > > > to do > > > > it again, probably I should set this in the conf file also ? maybe as > > > > another user said my NIC is not enabled or something like that. > > > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > > network initialization each time you boot. Everything at startup > > > reads the /etc/rc.conf and finds variables it needs to do its startup > > > and network startup does that too. So, you put in a line like: > > > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > > and > > > defaultrouter="1.1.1.3" > > > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > > > network startup sees those and says 'oh, I know what to do with those' > > > and runs the ifconfig, etc. > > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > > It is up to the startup programs to do something about it. > > > > > > The startup programs are generally run from the /etc/rc script and > > > from other scripts that it runs. > > > > > > jerry > > > > > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > > | I did have an IP address assigned to my ethernet interface( using > > > the > > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > > desired > > > > > interface) interface neither has any IP address assigned to it, nor > > > its UP > > > > > . > > > > > So, if you've assigned an IP address to 'em0', then also make sure > > > its UP, > > > > > by > > > > > doing 'ifconfig em0 up' . > > > > > > > > > > HTH > > > > > -- > > > > > Ashish Shukla ??? > > > > > http://wahjava.wordpress.com/ > > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- > > > -- > > > > > > > > > > > > ___ > > > > 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: Network configuration in FreeBSD
oh yes, I did use the right IP, netmask and interface to be configured. Now thankfully the LAN pings work, the thing I have to find out now is how to make ftp work which still keeps saying that hostname or servname not known Thanks a lot Bhuvana On Wed, Jan 30, 2008 at 2:50 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > On Wed, Jan 30, 2008 at 12:57:59PM -0500, Bhuvaneswari Ramkumar wrote: > > > with the above assigned IP address and net-mask I'm reading to make it > work > > and ping my LAN successfully ( which it doesn't now) before I put them > in > > the rc.conf script. > > I am not quite sure what you are asking here, but you do have to > have the correct IP address and netmask and default router configured. > You can't just pick numbers out of the air. I just used your > example numbers in my response. > > jerry > > > > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> > wrote: > > > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > > net-mask & the 100 Mbps active linnk. > > > > > > > > quick question : > > > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > > restart > > > > my application, is it some kind of a temporary address assignment, > bcos > > > > whatever I assigned was not visible today when I re-booted and I had > to > > > do > > > > it again, probably I should set this in the conf file also ? maybe > as > > > > another user said my NIC is not enabled or something like that. > > > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > > network initialization each time you boot. Everything at startup > > > reads the /etc/rc.conf and finds variables it needs to do its startup > > > and network startup does that too. So, you put in a line like: > > > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > > and > > > defaultrouter="1.1.1.3" > > > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > > > network startup sees those and says 'oh, I know what to do with those' > > > and runs the ifconfig, etc. > > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > > It is up to the startup programs to do something about it. > > > > > > The startup programs are generally run from the /etc/rc script and > > > from other scripts that it runs. > > > > > > jerry > > > > > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > > | I did have an IP address assigned to my ethernet interface( > using > > > the > > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > > desired > > > > > interface) interface neither has any IP address assigned to it, > nor > > > its UP > > > > > . > > > > > So, if you've assigned an IP address to 'em0', then also make sure > its > > > UP, > > > > > by > > > > > doing 'ifconfig em0 up' . > > > > > > > > > > HTH > > > > > -- > > > > > Ashish Shukla ??? > > > > > http://wahjava.wordpress.com/ > > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? > --- > > > -- > > > > > > > > > > > > ___ > > > > 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: Network configuration in FreeBSD
On Wed, Jan 30, 2008 at 12:57:59PM -0500, Bhuvaneswari Ramkumar wrote: > with the above assigned IP address and net-mask I'm reading to make it work > and ping my LAN successfully ( which it doesn't now) before I put them in > the rc.conf script. I am not quite sure what you are asking here, but you do have to have the correct IP address and netmask and default router configured. You can't just pick numbers out of the air. I just used your example numbers in my response. jerry > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > net-mask & the 100 Mbps active linnk. > > > > > > quick question : > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > restart > > > my application, is it some kind of a temporary address assignment, bcos > > > whatever I assigned was not visible today when I re-booted and I had to > > do > > > it again, probably I should set this in the conf file also ? maybe as > > > another user said my NIC is not enabled or something like that. > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > network initialization each time you boot. Everything at startup > > reads the /etc/rc.conf and finds variables it needs to do its startup > > and network startup does that too. So, you put in a line like: > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > and > > defaultrouter="1.1.1.3" > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > network startup sees those and says 'oh, I know what to do with those' > > and runs the ifconfig, etc. > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > It is up to the startup programs to do something about it. > > > > The startup programs are generally run from the /etc/rc script and > > from other scripts that it runs. > > > > jerry > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > [EMAIL PROTECTED]> wrote: > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > | I did have an IP address assigned to my ethernet interface( using > > the > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > desired > > > > interface) interface neither has any IP address assigned to it, nor > > its UP > > > > . > > > > So, if you've assigned an IP address to 'em0', then also make sure its > > UP, > > > > by > > > > doing 'ifconfig em0 up' . > > > > > > > > HTH > > > > -- > > > > Ashish Shukla ??? > > > > http://wahjava.wordpress.com/ > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- > > -- > > > > > > > > > ___ > > > 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: Network configuration in FreeBSD
Bhuvaneswari Ramkumar wrote: ok the local LAN ping works now At the risk of being obvious: please be so smart as to write down the settings (and try to understand exactly why they are the way they are) so you don't have to reinvent the wheel next time around. Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On Wed, 30 Jan 2008 19:35:03 +0100, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: An explicit call to /etc/netstart tells me that the route & devd with their pids are already running - though I dont know if this takes into account the new chages I've done & restarts the network. Try /etc/rc.d/netif restart followed by /etc/rc.d/routing restart Michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
Written by Bhuvaneswari Ramkumar on 01/30/08 13:02>> > ok the local LAN ping works now > FYI, the handbook is very helpful. (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
ok the local LAN ping works now On Wed, Jan 30, 2008 at 1:52 PM, आशीष Ashish <[EMAIL PROTECTED]> wrote: > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > | with the above assigned IP address and net-mask I'm reading to make it > work > | and ping my LAN successfully ( which it doesn't now) before I put them > in > | the rc.conf script. > > BtW, what is your network prefix and subnet mask ? Also mention the IP > address > you're trying to ping and IP address and subnet mask, you assigned to your > box ? > > -- > Ashish Shukla आशीष शुक्ल > http://wahjava.wordpress.com/ > ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: | with the above assigned IP address and net-mask I'm reading to make it work | and ping my LAN successfully ( which it doesn't now) before I put them in | the rc.conf script. BtW, what is your network prefix and subnet mask ? Also mention the IP address you're trying to ping and IP address and subnet mask, you assigned to your box ? -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- signature.asc Description: This is a digitally signed message part.
Re: Network configuration in FreeBSD
An explicit call to /etc/netstart tells me that the route & devd with their pids are already running - though I dont know if this takes into account the new chages I've done & restarts the network. On Wed, Jan 30, 2008 at 1:01 PM, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > Is it a cause of concern if I dont have any route marked as default ? > I see so when i use the netstat command > > > On Wed, Jan 30, 2008 at 12:57 PM, Bhuvaneswari Ramkumar < > [EMAIL PROTECTED]> wrote: > > > with the above assigned IP address and net-mask I'm reading to make it > > work and ping my LAN successfully ( which it doesn't now) before I put them > > in the rc.conf script. > > > > > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> > > wrote: > > > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > > net-mask & the 100 Mbps active linnk. > > > > > > > > quick question : > > > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > > restart > > > > my application, is it some kind of a temporary address assignment, > > > bcos > > > > whatever I assigned was not visible today when I re-booted and I had > > > to do > > > > it again, probably I should set this in the conf file also ? maybe > > > as > > > > another user said my NIC is not enabled or something like that. > > > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > > network initialization each time you boot. Everything at startup > > > reads the /etc/rc.conf and finds variables it needs to do its startup > > > and network startup does that too. So, you put in a line like: > > > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > > and > > > defaultrouter="1.1.1.3" > > > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > > > network startup sees those and says 'oh, I know what to do with those' > > > and runs the ifconfig, etc. > > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > > It is up to the startup programs to do something about it. > > > > > > The startup programs are generally run from the /etc/rc script and > > > from other scripts that it runs. > > > > > > jerry > > > > > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > > | I did have an IP address assigned to my ethernet interface( > > > using the > > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > > desired > > > > > interface) interface neither has any IP address assigned to it, > > > nor its UP > > > > > . > > > > > So, if you've assigned an IP address to 'em0', then also make sure > > > its UP, > > > > > by > > > > > doing 'ifconfig em0 up' . > > > > > > > > > > HTH > > > > > -- > > > > > Ashish Shukla ??? > > > > > http://wahjava.wordpress.com/ > > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? > > > --- -- > > > > > > > > > > > > ___ > > > > 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: Network configuration in FreeBSD
Is it a cause of concern if I dont have any route marked as default ? I see so when i use the netstat command On Wed, Jan 30, 2008 at 12:57 PM, Bhuvaneswari Ramkumar < [EMAIL PROTECTED]> wrote: > with the above assigned IP address and net-mask I'm reading to make it > work and ping my LAN successfully ( which it doesn't now) before I put them > in the rc.conf script. > > > On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> > wrote: > > > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > > > ifconfig em0 up also doesnt help ping my LAN. > > > > > > the ifconfig -a output now reads the IP I just added, as well as the > > > net-mask & the 100 Mbps active linnk. > > > > > > quick question : > > > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > > restart > > > my application, is it some kind of a temporary address assignment, > > bcos > > > whatever I assigned was not visible today when I re-booted and I had > > to do > > > it again, probably I should set this in the conf file also ? maybe as > > > another user said my NIC is not enabled or something like that. > > > > You have to put it in /etc/rc.conf so it will be taken care of during > > network initialization each time you boot. Everything at startup > > reads the /etc/rc.conf and finds variables it needs to do its startup > > and network startup does that too. So, you put in a line like: > > > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > > and > > defaultrouter="1.1.1.3" > > > > Amongst a number of other startup settings in /etc/rc.conf > > > > network startup sees those and says 'oh, I know what to do with those' > > and runs the ifconfig, etc. > > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > > and the 'defaultrouter' variable to be set to "1.1.1.3" > > It is up to the startup programs to do something about it. > > > > The startup programs are generally run from the /etc/rc script and > > from other scripts that it runs. > > > > jerry > > > > > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > > [EMAIL PROTECTED]> wrote: > > > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > > | I did have an IP address assigned to my ethernet interface( using > > the > > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > > desired > > > > interface) interface neither has any IP address assigned to it, nor > > its UP > > > > . > > > > So, if you've assigned an IP address to 'em0', then also make sure > > its UP, > > > > by > > > > doing 'ifconfig em0 up' . > > > > > > > > HTH > > > > -- > > > > Ashish Shukla ??? > > > > http://wahjava.wordpress.com/ > > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- > > -- > > > > > > > > > ___ > > > 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: Network configuration in FreeBSD
with the above assigned IP address and net-mask I'm reading to make it work and ping my LAN successfully ( which it doesn't now) before I put them in the rc.conf script. On Wed, Jan 30, 2008 at 12:51 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > > > ifconfig em0 up also doesnt help ping my LAN. > > > > the ifconfig -a output now reads the IP I just added, as well as the > > net-mask & the 100 Mbps active linnk. > > > > quick question : > > > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I > restart > > my application, is it some kind of a temporary address assignment, bcos > > whatever I assigned was not visible today when I re-booted and I had to > do > > it again, probably I should set this in the conf file also ? maybe as > > another user said my NIC is not enabled or something like that. > > You have to put it in /etc/rc.conf so it will be taken care of during > network initialization each time you boot. Everything at startup > reads the /etc/rc.conf and finds variables it needs to do its startup > and network startup does that too. So, you put in a line like: > > ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" > and > defaultrouter="1.1.1.3" > > Amongst a number of other startup settings in /etc/rc.conf > > network startup sees those and says 'oh, I know what to do with those' > and runs the ifconfig, etc. > Note that putting it in rc.cong only causes a 'ifconfig_em0' variable > to be set to"inet 1.1.1.2 netmask 255.255.255.0" > and the 'defaultrouter' variable to be set to "1.1.1.3" > It is up to the startup programs to do something about it. > > The startup programs are generally run from the /etc/rc script and > from other scripts that it runs. > > jerry > > > > > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish < > [EMAIL PROTECTED]> wrote: > > > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > > | I did have an IP address assigned to my ethernet interface( using > the > > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your > desired > > > interface) interface neither has any IP address assigned to it, nor > its UP > > > . > > > So, if you've assigned an IP address to 'em0', then also make sure its > UP, > > > by > > > doing 'ifconfig em0 up' . > > > > > > HTH > > > -- > > > Ashish Shukla ??? > > > http://wahjava.wordpress.com/ > > > ?-- ?- ?--- ?- ???- ?- ?--?-? --? -- ?- ?? ?-?? ?-?-?- -?-? --- > -- > > > > > > ___ > > 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: Network configuration in FreeBSD
On Wed, Jan 30, 2008 at 12:19:33PM -0500, Bhuvaneswari Ramkumar wrote: > ifconfig em0 up also doesnt help ping my LAN. > > the ifconfig -a output now reads the IP I just added, as well as the > net-mask & the 100 Mbps active linnk. > > quick question : > > I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I restart > my application, is it some kind of a temporary address assignment, bcos > whatever I assigned was not visible today when I re-booted and I had to do > it again, probably I should set this in the conf file also ? maybe as > another user said my NIC is not enabled or something like that. You have to put it in /etc/rc.conf so it will be taken care of during network initialization each time you boot. Everything at startup reads the /etc/rc.conf and finds variables it needs to do its startup and network startup does that too. So, you put in a line like: ifconfig_em0="inet 1.1.1.2 netmask 255.255.255.0" and defaultrouter="1.1.1.3" Amongst a number of other startup settings in /etc/rc.conf network startup sees those and says 'oh, I know what to do with those' and runs the ifconfig, etc. Note that putting it in rc.cong only causes a 'ifconfig_em0' variable to be set to"inet 1.1.1.2 netmask 255.255.255.0" and the 'defaultrouter' variable to be set to "1.1.1.3" It is up to the startup programs to do something about it. The startup programs are generally run from the /etc/rc script and from other scripts that it runs. jerry > > > On Wed, Jan 30, 2008 at 12:14 PM, Ashish <[EMAIL PROTECTED]> > wrote: > > > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > > | I did have an IP address assigned to my ethernet interface( using the > > | ifconfig command) but I'm unable to ping anybody in my LAN. > > > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your desired > > interface) interface neither has any IP address assigned to it, nor its UP > > . > > So, if you've assigned an IP address to 'em0', then also make sure its UP, > > by > > doing 'ifconfig em0 up' . > > > > HTH > > -- > > Ashish Shukla ??? > > http://wahjava.wordpress.com/ > > ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- > > > ___ > 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: Network configuration in FreeBSD
Bhuvaneswari Ramkumar wrote: I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I restart my application, is it some kind of a temporary address assignment, bcos whatever I assigned was not visible today when I re-booted and I had to do it again, probably I should set this in the conf file also ? maybe as another user said my NIC is not enabled or something like that. Once it works, all this stuff can be put in /etc/rc.conf, don't worry about that. Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
ifconfig em0 up also doesnt help ping my LAN. the ifconfig -a output now reads the IP I just added, as well as the net-mask & the 100 Mbps active linnk. quick question : I did an ifconfig em0 1.1.1.2 yday.should this be done everytime I restart my application, is it some kind of a temporary address assignment, bcos whatever I assigned was not visible today when I re-booted and I had to do it again, probably I should set this in the conf file also ? maybe as another user said my NIC is not enabled or something like that. On Wed, Jan 30, 2008 at 12:14 PM, आशीष Ashish <[EMAIL PROTECTED]> wrote: > ,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: > | I did have an IP address assigned to my ethernet interface( using the > | ifconfig command) but I'm unable to ping anybody in my LAN. > > In the 'ifconfig -a' output you posted earlier, the 'em0' (your desired > interface) interface neither has any IP address assigned to it, nor its UP > . > So, if you've assigned an IP address to 'em0', then also make sure its UP, > by > doing 'ifconfig em0 up' . > > HTH > -- > Ashish Shukla आशीष शुक्ल > http://wahjava.wordpress.com/ > ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
,--[ On Wednesday 30 Jan 2008, Bhuvaneswari Ramkumar wrote: | I did have an IP address assigned to my ethernet interface( using the | ifconfig command) but I'm unable to ping anybody in my LAN. In the 'ifconfig -a' output you posted earlier, the 'em0' (your desired interface) interface neither has any IP address assigned to it, nor its UP . So, if you've assigned an IP address to 'em0', then also make sure its UP, by doing 'ifconfig em0 up' . HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- signature.asc Description: This is a digitally signed message part.
Re: Network configuration in FreeBSD
I did have an IP address assigned to my ethernet interface( using the ifconfig command) but I'm unable to ping anybody in my LAN. On Tue, Jan 29, 2008 at 10:38 AM, आशीष Ashish <[EMAIL PROTECTED]> wrote: > ,--[ On Tuesday 29 Jan 2008, Giorgos Keramidas wrote: > | On 2008-01-28 21:03, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > > [...] > > | Hmmm. There seems to be something very 'odd' about your interfaces. > | > | * There is no `lo0' loopback interface, which commonly uses the > | 127.0.0.1 address. > > Quoting Bhuvaneswari's output of "ifconfig -a" and "netstat -nr": > > -- > #ifconfig -a > > em0: flags=8802 mtu 1500 > options=b > ether :0d:56:f0:f1:ba > media:Ethernet autoselect (100baseTX ) > status: active > > plip0:flags=108810 mtu 1500 > lo0:flags=8049 MTU 16384 > inet 127.0.0.1 netmask 0xff00 > inet ::1 prefixlen 128 > inet6 fe80 :: 1% lo0 prefixlen 64 scopeid 0x3 > -- > > If you notice in the above there is already a lo0 interface, it is just > that > he missed a newline between plip0 and lo0 interface lines. So it seems you > missed the lo0 interface :) . > > So all he has to do is just assign some inet address to 'em0' interface, > and > ping other nodes in his LAN :) . And then when done testing IP network in > LAN, he can add a default route and try connecting to other hosts in the > internet. > > HTH > -- > Ashish Shukla आशीष शुक्ल > http://wahjava.wordpress.com/ > ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
,--[ On Tuesday 29 Jan 2008, Giorgos Keramidas wrote: | On 2008-01-28 21:03, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: [...] | Hmmm. There seems to be something very 'odd' about your interfaces. | | * There is no `lo0' loopback interface, which commonly uses the | 127.0.0.1 address. Quoting Bhuvaneswari's output of "ifconfig -a" and "netstat -nr": -- #ifconfig -a em0: flags=8802 mtu 1500 options=b ether :0d:56:f0:f1:ba media:Ethernet autoselect (100baseTX ) status: active plip0:flags=108810 mtu 1500 lo0:flags=8049 MTU 16384 inet 127.0.0.1 netmask 0xff00 inet ::1 prefixlen 128 inet6 fe80 :: 1% lo0 prefixlen 64 scopeid 0x3 -- If you notice in the above there is already a lo0 interface, it is just that he missed a newline between plip0 and lo0 interface lines. So it seems you missed the lo0 interface :) . So all he has to do is just assign some inet address to 'em0' interface, and ping other nodes in his LAN :) . And then when done testing IP network in LAN, he can add a default route and try connecting to other hosts in the internet. HTH -- Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/ ·-- ·- ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- -- signature.asc Description: This is a digitally signed message part.
Re: Network configuration in FreeBSD
> You need to set the default gateway in /etc/rc.conf. Without a > default gateway, you will need to add a default route with the > route command. > > Without a route your machine will only be able to ping itself. Unless something has changed dramatically -- and fairly recently -- a machine that knows its own IP address and netmask should be able to ping anything on the same subnet as itself (an interface being implicitly a route to any other IP address on the same subnet). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
ok down works but delete dosent I guess the 1st one is for disabling the plip interface and the second for completely removing it , or let me know if I'm getting this wrong here. ifconfig: 10ctl(SIOCDIFADDR) : cant assign requested address is this bcos of the down I did before this command ? once again, thanks for helping out. Sincerely, Bhuvana On Mon, Jan 28, 2008 at 10:40 PM, Giorgos Keramidas < [EMAIL PROTECTED]> wrote: > On 2008-01-28 22:33, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > > Giorgos, > > > > Thanks a lot for the excellent reply, yes I do have some questions about > > this but before that: > > > > the unplumb operation for pilp0 doesnt work. > > > > ifconfig: SIOCIFDESTROY: Invalid argument > > > > is the message I get for this. > > Ok, it should be sufficient to delete the assigned address from plip0: > ># ifconfig plip0 down ># ifconfig plip0 delete > > Sorry for that; I don't use plip these days, and I couldn't test it :/ > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On 2008-01-28 22:33, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > Giorgos, > > Thanks a lot for the excellent reply, yes I do have some questions about > this but before that: > > the unplumb operation for pilp0 doesnt work. > > ifconfig: SIOCIFDESTROY: Invalid argument > > is the message I get for this. Ok, it should be sufficient to delete the assigned address from plip0: # ifconfig plip0 down # ifconfig plip0 delete Sorry for that; I don't use plip these days, and I couldn't test it :/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
Giorgos, Thanks a lot for the excellent reply, yes I do have some questions about this but before that: the unplumb operation for pilp0 doesnt work. ifconfig: SIOCIFDESTROY: Invalid argument is the message I get for this. Sincerely, Bhuvana On Mon, Jan 28, 2008 at 9:37 PM, Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2008-01-28 21:03, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > > ok here u go, the exact output of the the commands: > > Excellent! Thank you :-) > > > #ifconfig -a > > > > em0: flags=8802 mtu 1500 > > options=b > > ether :0d:56:f0:f1:ba > > media:Ethernet autoselect (100baseTX ) > > status: active > > > > plip0:flags=108810 mtu 1500 > > lo0:flags=8049 MTU 16384 > > inet 127.0.0.1 netmask 0xff00 > > inet ::1 prefixlen 128 > > inet6 fe80 :: 1% lo0 prefixlen 64 scopeid 0x3 > > See the `active' status and the `media' description? This means you > have a network cable connected and FreeBSD has autodetected that you are > using a full-duplex 100 Mbit/s link. > > That's good :) > > On 2008-01-28 21:10, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > > the netstat reads: > > > > #netstat -nr > > > > Routing tables > > > > Internet: > > Destination Gateway Flags REfs Use Netif Expire > > 127.0.0.1 127.0.0.1 UH041 lo0 > > > > > > Internet 6 > > > > Destination Gateway Flags Netif > > Expire > > ::1::1 UH lo0 > > fe80::%lo0/64 fe80::1%lo0U lo0 > > fe80::1%lo0 link#3 UHL lo0 > > ff01::/32::1 Ulo0 > > ff02 :: %lo0/32 ::1UC lo0 > > Hmmm. There seems to be something very 'odd' about your interfaces. > >* There is no `lo0' loopback interface, which commonly uses the > 127.0.0.1 address. > >* The 127.0.0.1 address is assigned to plip0 (IP over parallel > port), which seems wrong. > >* The em0 interface has no address. > > Can you try the following commands, so see if you can *manually* set up > the interfaces? > > 1. Bringing down the 'plip0 interface > - > ># ifconfig plip0 unplumb > > This should bring down and delete the plip0 interface. You don't really > need it when em0 starts working. > > 2. Bringing up the `lo0' loopback interface > --- > ># ifconfig lo0 inet 127.0.0.1/32 up > > This will bring up the `lo0' interface, with the correct address. > > 3. Bringing up the em0 interface > > > Finally, try bringing up the `em0' interface with dhclient OR ifconfig. > You don't need *both*. One of them should be sufficient... > > 3.1. Using a dynamic/automatic address for em0 > -- > > If you are using DHCP (automatic address configuration, i.e. from a DSL > modem, or similar) it should be sufficient to run: > ># dhclient em0 > > 3.2. Using a static address for em0 > --- > > If you are not using DHCP, and you have a `static' address, like the one > I use on the workstation I'm using to type this, you should be able to > use ifconfig like: > ># ifconfig inet a.b.c.d/count up > > where `a.b.c.d' is the IP address you want to assign, and `count' a > number like `24' or `28'. The correct settings depends on how your > network is configured, but an example would look like: > ># ifconfig em0 192.168.1.180/24 up > > 4. Check that em0 really got an address and is "UP" > --- > > Then you should see something like: > >em0: flags=8802 mtu 1500 > options=b >ether :0d:56:f0:f1:ba > inet 192.168.1.180 netmask 0xff00 broadcast > 192.168.1.255 > media:Ethernet autoselect (100baseTX ) >status: active > > 5. Add the default router/gateway > - > > If you see the "UP" flag in the first line, and you get the `inet' line > options correctly (address and netmask), the final step should be to > configure the `default router', i.e.: > ># route add default 192.168.1.1 > > 6. Saving it all in `/etc/rc.conf' for the next boot > > > If you get all the steps right, and you _do_ get connectivity going, > then you should be able to manually edit the file `/etc/rc.conf' and set > configure everything by using something similar to: > >network_interfaces='lo0 em0' >ifconfig_lo0='inet 127.0.0.1/32' >ifconfig_em0='inet 192.168.1.180/24' >defaultrouter='192.168.1.1' > > The syntax is really simple, but if you need an explanation of what it > all means, please feel free to ask :) > > - Giorgos > > > ___ freebsd-questio
Re: Network configuration in FreeBSD
On 2008-01-28 21:03, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > ok here u go, the exact output of the the commands: Excellent! Thank you :-) > #ifconfig -a > > em0: flags=8802 mtu 1500 > options=b > ether :0d:56:f0:f1:ba > media:Ethernet autoselect (100baseTX ) > status: active > > plip0:flags=108810 mtu 1500 > lo0:flags=8049 MTU 16384 > inet 127.0.0.1 netmask 0xff00 > inet ::1 prefixlen 128 > inet6 fe80 :: 1% lo0 prefixlen 64 scopeid 0x3 See the `active' status and the `media' description? This means you have a network cable connected and FreeBSD has autodetected that you are using a full-duplex 100 Mbit/s link. That's good :) On 2008-01-28 21:10, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > the netstat reads: > > #netstat -nr > > Routing tables > > Internet: > Destination Gateway Flags REfs Use Netif Expire > 127.0.0.1 127.0.0.1 UH041 lo0 > > > Internet 6 > > Destination Gateway Flags Netif > Expire > ::1::1 UH lo0 > fe80::%lo0/64 fe80::1%lo0U lo0 > fe80::1%lo0 link#3 UHL lo0 > ff01::/32::1 Ulo0 > ff02 :: %lo0/32 ::1UC lo0 Hmmm. There seems to be something very 'odd' about your interfaces. * There is no `lo0' loopback interface, which commonly uses the 127.0.0.1 address. * The 127.0.0.1 address is assigned to plip0 (IP over parallel port), which seems wrong. * The em0 interface has no address. Can you try the following commands, so see if you can *manually* set up the interfaces? 1. Bringing down the 'plip0 interface - # ifconfig plip0 unplumb This should bring down and delete the plip0 interface. You don't really need it when em0 starts working. 2. Bringing up the `lo0' loopback interface --- # ifconfig lo0 inet 127.0.0.1/32 up This will bring up the `lo0' interface, with the correct address. 3. Bringing up the em0 interface Finally, try bringing up the `em0' interface with dhclient OR ifconfig. You don't need *both*. One of them should be sufficient... 3.1. Using a dynamic/automatic address for em0 -- If you are using DHCP (automatic address configuration, i.e. from a DSL modem, or similar) it should be sufficient to run: # dhclient em0 3.2. Using a static address for em0 --- If you are not using DHCP, and you have a `static' address, like the one I use on the workstation I'm using to type this, you should be able to use ifconfig like: # ifconfig inet a.b.c.d/count up where `a.b.c.d' is the IP address you want to assign, and `count' a number like `24' or `28'. The correct settings depends on how your network is configured, but an example would look like: # ifconfig em0 192.168.1.180/24 up 4. Check that em0 really got an address and is "UP" --- Then you should see something like: em0: flags=8802 mtu 1500 options=b ether :0d:56:f0:f1:ba inet 192.168.1.180 netmask 0xff00 broadcast 192.168.1.255 media:Ethernet autoselect (100baseTX ) status: active 5. Add the default router/gateway - If you see the "UP" flag in the first line, and you get the `inet' line options correctly (address and netmask), the final step should be to configure the `default router', i.e.: # route add default 192.168.1.1 6. Saving it all in `/etc/rc.conf' for the next boot If you get all the steps right, and you _do_ get connectivity going, then you should be able to manually edit the file `/etc/rc.conf' and set configure everything by using something similar to: network_interfaces='lo0 em0' ifconfig_lo0='inet 127.0.0.1/32' ifconfig_em0='inet 192.168.1.180/24' defaultrouter='192.168.1.1' The syntax is really simple, but if you need an explanation of what it all means, please feel free to ask :) - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
the netstat reads: #netstat -nr Routing tables Internet: Destination Gateway Flags REfs Use Netif Expire 127.0.0.1 127.0.0.1 UH041 lo0 Internet 6 Destination Gateway Flags Netif Expire ::1::1 UH lo0 fe80::%lo0/64 fe80::1%lo0U lo0 fe80::1%lo0 link#3 UHL lo0 ff01::/32::1 Ulo0 ff02 :: %lo0/32 ::1UC lo0 On Mon, Jan 28, 2008 at 9:03 PM, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > ok here u go, the exact output of the the commands: > > #ifconfig -a > > em0: flags=8802 mtu 1500 > options=b > ether :0d:56:f0:f1:ba > media:Ethernet autoselect (100baseTX ) > status: active > > plip0:flags=108810 mtu 1500 > lo0:flags=8049 MTU 16384 > inet 127.0.0.1 netmask 0xff00 > inet ::1 prefixlen 128 > inet6 fe80 :: 1% lo0 prefixlen 64 scopeid 0x3 > > > On Mon, Jan 28, 2008 at 8:06 PM, Giorgos Keramidas < > [EMAIL PROTECTED]> wrote: > > > On 2008-01-28 18:18, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > > > On Mon, Jan 28, 2008 at 4:42 PM, Christopher Cowart < > > [EMAIL PROTECTED]> wrote: > > > > > > > > Send the list the output of the following commands: > > > > # ifconfig -a > > > > # netstat -rn > > > > > > > > With that info, we can probably help you out better. > > > > > > ifconfig -a > > > > > > em0: flags ...lot of data . > > > status: active > > > > > > ( I'm guessing this is the ethernet interface) > > > > > > netstat -rn > > > > > > routing tables: > > > Internet : > > > 127.0.0.1 ..followed by some IPs, flags(UH), etc .. > > > > > > Internet6 > > > expire followed by some hex-values and flags > > > > > > would this do or more specifics needed ? > > > > Not really, no. You are supposed to show the *exact* output of > > commands, if you expect more useful answers. > > > > Now, I understand that without networking, it may be tricky to capture > > the output and post it in an email message. > > > > If you have a floppy disk you can use the floppy to capture the output > > of these commands, i.e. by mounting it: > > > ># cd /root > ># mount -t msdosfs /dev/fd0 /mnt > ># ifconfig -a > /mnt/ifconfig.txt > ># netstat -rn > /mnt/netstat.txt > ># umount /mnt > > > > If you have a USB flash drive, you can mount that too (assuming it has a > > single FAT partition): > > > >( plug the USB flash disk into a USB socket ) > > > ># cd /root > ># mount -t msdosfs /dev/da0s1 /mnt > ># ifconfig -a > /mnt/ifconfig.txt > ># netstat -rn > /mnt/netstat.txt > ># umount /mnt > > > >( unplug the flash disk ) > > > > It will help immensely if you post the *exact* output of the commands > > mentioned by Christopher. > > > > - Giorgos > > > > ___ > > 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: Network configuration in FreeBSD
ok here u go, the exact output of the the commands: #ifconfig -a em0: flags=8802 mtu 1500 options=b ether :0d:56:f0:f1:ba media:Ethernet autoselect (100baseTX ) status: active plip0:flags=108810 mtu 1500 lo0:flags=8049 MTU 16384 inet 127.0.0.1 netmask 0xff00 inet ::1 prefixlen 128 inet6 fe80 :: 1% lo0 prefixlen 64 scopeid 0x3 On Mon, Jan 28, 2008 at 8:06 PM, Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2008-01-28 18:18, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > > On Mon, Jan 28, 2008 at 4:42 PM, Christopher Cowart < > [EMAIL PROTECTED]> wrote: > > > > > > Send the list the output of the following commands: > > > # ifconfig -a > > > # netstat -rn > > > > > > With that info, we can probably help you out better. > > > > ifconfig -a > > > > em0: flags ...lot of data . > > status: active > > > > ( I'm guessing this is the ethernet interface) > > > > netstat -rn > > > > routing tables: > > Internet : > > 127.0.0.1 ..followed by some IPs, flags(UH), etc .. > > > > Internet6 > > expire followed by some hex-values and flags > > > > would this do or more specifics needed ? > > Not really, no. You are supposed to show the *exact* output of > commands, if you expect more useful answers. > > Now, I understand that without networking, it may be tricky to capture > the output and post it in an email message. > > If you have a floppy disk you can use the floppy to capture the output > of these commands, i.e. by mounting it: > ># cd /root ># mount -t msdosfs /dev/fd0 /mnt ># ifconfig -a > /mnt/ifconfig.txt ># netstat -rn > /mnt/netstat.txt ># umount /mnt > > If you have a USB flash drive, you can mount that too (assuming it has a > single FAT partition): > >( plug the USB flash disk into a USB socket ) > ># cd /root ># mount -t msdosfs /dev/da0s1 /mnt ># ifconfig -a > /mnt/ifconfig.txt ># netstat -rn > /mnt/netstat.txt ># umount /mnt > >( unplug the flash disk ) > > It will help immensely if you post the *exact* output of the commands > mentioned by Christopher. > > - Giorgos > > ___ > 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: Network configuration in FreeBSD
ifconfig -a em0: flags ...lot of data . status: active ( I'm guessing this is the ethernet interface) lo0: similar stuff as em0 and my var/log/messages has a lot of data in it, I dont know if I'm identifying a boot message accurately but there is a line that specifies the location of a kernel boot file as /boot/kernel.I dont know if this is just default message present here On Mon, Jan 28, 2008 at 7:00 PM, Alphons Fonz van Werven < [EMAIL PROTECTED]> wrote: > Bhuvaneswari Ramkumar wrote: > > > I'm guessing it does detect the interface, network-device & all that, > bcos > > my ifconfig says the ethernet status is active. But still I'm unable to > do > > any kind of networking at all, even pings from other PCs to this one > remain > > unreachable. I'm wondering if I should configure something else in the > > sysinstall or the rc.conf file. > > Hehe. Network problem solving often seems more about magic than about > logic... > > Anyway, for starters, can you send me the output of ifconfig -a? > Also, if your NIC got detected, there should be some boot messages in > /var/log/messages. You might want to check on that. > > Alphons > > -- > VISTA - Viruses Intruders Spyware Trojans Adware > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On 2008-01-28 18:18, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > On Mon, Jan 28, 2008 at 4:42 PM, Christopher Cowart <[EMAIL PROTECTED]> wrote: > > > > Send the list the output of the following commands: > > # ifconfig -a > > # netstat -rn > > > > With that info, we can probably help you out better. > > ifconfig -a > > em0: flags ...lot of data . > status: active > > ( I'm guessing this is the ethernet interface) > > netstat -rn > > routing tables: > Internet : > 127.0.0.1 ..followed by some IPs, flags(UH), etc .. > > Internet6 > expire followed by some hex-values and flags > > would this do or more specifics needed ? Not really, no. You are supposed to show the *exact* output of commands, if you expect more useful answers. Now, I understand that without networking, it may be tricky to capture the output and post it in an email message. If you have a floppy disk you can use the floppy to capture the output of these commands, i.e. by mounting it: # cd /root # mount -t msdosfs /dev/fd0 /mnt # ifconfig -a > /mnt/ifconfig.txt # netstat -rn > /mnt/netstat.txt # umount /mnt If you have a USB flash drive, you can mount that too (assuming it has a single FAT partition): ( plug the USB flash disk into a USB socket ) # cd /root # mount -t msdosfs /dev/da0s1 /mnt # ifconfig -a > /mnt/ifconfig.txt # netstat -rn > /mnt/netstat.txt # umount /mnt ( unplug the flash disk ) It will help immensely if you post the *exact* output of the commands mentioned by Christopher. - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
At 05:38 PM 1/28/2008, Bhuvaneswari Ramkumar wrote: I'm guessing it does detect the interface, network-device & all that, bcos my ifconfig says the ethernet status is active. But still I'm unable to do any kind of networking at all, even pings from other PCs to this one remain unreachable. I'm wondering if I should configure something else in the sysinstall or the rc.conf file. On Mon, Jan 28, 2008 at 6:18 PM, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > ifconfig -a > > em0: flags ...lot of data . > status: active > > ( I'm guessing this is the ethernet interface) > > > netstat -rn > > routing tables: > Internet : > 127.0.0.1 ..followed by some IPs, flags(UH), etc .. > > Internet6 > expire followed by some hex-values and flags > > > would this do or more specifics needed ? > > > > > On Mon, Jan 28, 2008 at 4:42 PM, Christopher Cowart < > [EMAIL PROTECTED]> wrote: > > > On Mon, Jan 28, 2008 at 04:29:49PM -0500, Bhuvaneswari Ramkumar wrote: > > > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > > > I know this is a very silly question but I've searched the archives > > and any > > > suggestions are welcome. > > > > > > I think my system is not connected to the internet or any external > > network, > > > ping dosent work ( nor ftp or dig) > > > > > > When I try to do a post-install configuration and choose to enable the > > inetd > > > daemon option from the sysinstall, it doesnt invoke the editor to > > change the > > > inetd.conf at all, so I did a root-login and enabled ftp, even pftp > > and > > > other services in the file as mentioned in the installation document. > > > > This file affects running an ftp server, not an ftp client from the > > command line. > > > > > But still I'm unable to ftp to any server, the message I get is ftp: > > > hostname or servname not known or not provided. > > > > > > Do you guys have any ideas ? > > > > Send the list the output of the following commands: > > # ifconfig -a > > # netstat -rn > > > > With that info, we can probably help you out better. > > > > -- > > Chris Cowart > > Network Technical Lead > > Network & Infrastructure Services, RSSP-IT > > UC Berkeley > > > > __ You need to set the default gateway in /etc/rc.conf. Without a default gateway, you will need to add a default route with the route command. Without a route your machine will only be able to ping itself. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
I'm guessing it does detect the interface, network-device & all that, bcos my ifconfig says the ethernet status is active. But still I'm unable to do any kind of networking at all, even pings from other PCs to this one remain unreachable. I'm wondering if I should configure something else in the sysinstall or the rc.conf file. On Mon, Jan 28, 2008 at 6:18 PM, Bhuvaneswari Ramkumar <[EMAIL PROTECTED]> wrote: > ifconfig -a > > em0: flags ...lot of data . > status: active > > ( I'm guessing this is the ethernet interface) > > > netstat -rn > > routing tables: > Internet : > 127.0.0.1 ..followed by some IPs, flags(UH), etc .. > > Internet6 > expire followed by some hex-values and flags > > > would this do or more specifics needed ? > > > > > On Mon, Jan 28, 2008 at 4:42 PM, Christopher Cowart < > [EMAIL PROTECTED]> wrote: > > > On Mon, Jan 28, 2008 at 04:29:49PM -0500, Bhuvaneswari Ramkumar wrote: > > > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > > > I know this is a very silly question but I've searched the archives > > and any > > > suggestions are welcome. > > > > > > I think my system is not connected to the internet or any external > > network, > > > ping dosent work ( nor ftp or dig) > > > > > > When I try to do a post-install configuration and choose to enable the > > inetd > > > daemon option from the sysinstall, it doesnt invoke the editor to > > change the > > > inetd.conf at all, so I did a root-login and enabled ftp, even pftp > > and > > > other services in the file as mentioned in the installation document. > > > > This file affects running an ftp server, not an ftp client from the > > command line. > > > > > But still I'm unable to ftp to any server, the message I get is ftp: > > > hostname or servname not known or not provided. > > > > > > Do you guys have any ideas ? > > > > Send the list the output of the following commands: > > # ifconfig -a > > # netstat -rn > > > > With that info, we can probably help you out better. > > > > -- > > Chris Cowart > > Network Technical Lead > > Network & Infrastructure Services, RSSP-IT > > UC Berkeley > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On Mon, Jan 28, 2008 at 04:29:49PM -0500, Bhuvaneswari Ramkumar wrote: > Hi, > > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > I know this is a very silly question but I've searched the archives and any > suggestions are welcome. > > I think my system is not connected to the internet or any external network, > ping dosent work ( nor ftp or dig) > > When I try to do a post-install configuration and choose to enable the inetd > daemon option from the sysinstall, it doesnt invoke the editor to change the > inetd.conf at all, so I did a root-login and enabled ftp, even pftp and > other services in the file as mentioned in the installation document. > > But still I'm unable to ftp to any server, the message I get is ftp: > hostname or servname not known or not provided. > > Do you guys have any ideas ? Well, the first thing is to learn about 'ifconfig' Start with the handbook and the man pages. >From there, you will branch out to other network documentation. Anyway, it sounds like you did not configure or start any network device (NIC - Network Interface Card). jerry > > Thanks > Bhuvana > ___ > 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: Network configuration in FreeBSD
I configured the ethernet interface in the post-install config with my IP and net-mask, though I didnt know the gateway then. It gave me a warning that I might not be able to access remote machines, but that still dosent explain why it wont even ping the next node in my LAN. The rc.conf file does have some lines, are we looking for something specific here or should I key-in the gateway data b4 expecting anything else ? On Mon, Jan 28, 2008 at 4:39 PM, Brian <[EMAIL PROTECTED]> wrote: > Bhuvaneswari Ramkumar wrote: > > Hi, > > > > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > > I know this is a very silly question but I've searched the archives and > any > > suggestions are welcome. > > > > I think my system is not connected to the internet or any external > network, > > ping dosent work ( nor ftp or dig) > > > > When I try to do a post-install configuration and choose to enable the > inetd > > daemon option from the sysinstall, it doesnt invoke the editor to change > the > > inetd.conf at all, so I did a root-login and enabled ftp, even pftp and > > other services in the file as mentioned in the installation document. > > > > But still I'm unable to ftp to any server, the message I get is ftp: > > hostname or servname not known or not provided. > > > > Do you guys have any ideas ? > > > > Thanks > > Bhuvana > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > > > Interesting that you chose 5.5 for a new install, most anyone would > recommend something newer. Having said that, is the ether interface > enabled? If you run sysinstall, and select post install config, then > networking, then the interface in question, try to view/config it based > on the parameters your isp gave you. When you're done you should see > some lines in /etc/rc.conf specific to your config. Be careful with > this file. > > > Brian > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
ifconfig -a em0: flags ...lot of data . status: active ( I'm guessing this is the ethernet interface) netstat -rn routing tables: Internet : 127.0.0.1 ..followed by some IPs, flags(UH), etc .. Internet6 expire followed by some hex-values and flags would this do or more specifics needed ? On Mon, Jan 28, 2008 at 4:42 PM, Christopher Cowart < [EMAIL PROTECTED]> wrote: > On Mon, Jan 28, 2008 at 04:29:49PM -0500, Bhuvaneswari Ramkumar wrote: > > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > > I know this is a very silly question but I've searched the archives and > any > > suggestions are welcome. > > > > I think my system is not connected to the internet or any external > network, > > ping dosent work ( nor ftp or dig) > > > > When I try to do a post-install configuration and choose to enable the > inetd > > daemon option from the sysinstall, it doesnt invoke the editor to change > the > > inetd.conf at all, so I did a root-login and enabled ftp, even pftp and > > other services in the file as mentioned in the installation document. > > This file affects running an ftp server, not an ftp client from the > command line. > > > But still I'm unable to ftp to any server, the message I get is ftp: > > hostname or servname not known or not provided. > > > > Do you guys have any ideas ? > > Send the list the output of the following commands: > # ifconfig -a > # netstat -rn > > With that info, we can probably help you out better. > > -- > Chris Cowart > Network Technical Lead > Network & Infrastructure Services, RSSP-IT > UC Berkeley > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
I'm a newbie FreeBSD user, I've just installed the 5.5 version. I know this is a very silly question but I've searched the archives and any suggestions are welcome. RTFM begin with /usr/share/doc/en_US.ISO8859-1/books/handbook/handbook.txt (or html what you prefer) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On Mon, Jan 28, 2008 at 04:29:49PM -0500, Bhuvaneswari Ramkumar wrote: > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > I know this is a very silly question but I've searched the archives and any > suggestions are welcome. > > I think my system is not connected to the internet or any external network, > ping dosent work ( nor ftp or dig) > > When I try to do a post-install configuration and choose to enable the inetd > daemon option from the sysinstall, it doesnt invoke the editor to change the > inetd.conf at all, so I did a root-login and enabled ftp, even pftp and > other services in the file as mentioned in the installation document. This file affects running an ftp server, not an ftp client from the command line. > But still I'm unable to ftp to any server, the message I get is ftp: > hostname or servname not known or not provided. > > Do you guys have any ideas ? Send the list the output of the following commands: # ifconfig -a # netstat -rn With that info, we can probably help you out better. -- Chris Cowart Network Technical Lead Network & Infrastructure Services, RSSP-IT UC Berkeley pgpdTB3co0zcU.pgp Description: PGP signature
Re: Network configuration in FreeBSD
> > I'm a newbie FreeBSD user, I've just installed the 5.5 version. > I know this is a very silly question but I've searched the archives and > any > suggestions are welcome. > > I think my system is not connected to the internet or any external > network, > ping dosent work ( nor ftp or dig) > > When I try to do a post-install configuration and choose to enable the > inetd > daemon option from the sysinstall, it doesnt invoke the editor to change > the > inetd.conf at all, so I did a root-login and enabled ftp, even pftp and > other services in the file as mentioned in the installation document. > > But still I'm unable to ftp to any server, the message I get is ftp: > hostname or servname not known or not provided. > > Do you guys have any ideas ? > The standard install should have asked you if you want to configure your network device. The questions it would ask is which device to configure, and whether to try to configure DHCP, and whether to try to configure IPv6. It would then ask you, during install, whether to try to "bring up the network interface now?" If these questions were not part of the install, then something is not right, and someone else on this board might help you. My guess (I'm a newbie too) is that perhaps the network device was not recognized by FreeBSD 5.5? It's always possible to do network configuration post-install. I'd find some documentation on that in the handbook. I think the file that configures the network is rc.local or something. But first make sure the kernel recognized the network device. You might have to put something in /boot/loader.conf to load a kernel module for your network device? But inetd and ftp server and what not have nothing to do with your network actually working, so you were barking up the wrong tree. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
Bhuvaneswari Ramkumar wrote: Hi, I'm a newbie FreeBSD user, I've just installed the 5.5 version. I know this is a very silly question but I've searched the archives and any suggestions are welcome. I think my system is not connected to the internet or any external network, ping dosent work ( nor ftp or dig) When I try to do a post-install configuration and choose to enable the inetd daemon option from the sysinstall, it doesnt invoke the editor to change the inetd.conf at all, so I did a root-login and enabled ftp, even pftp and other services in the file as mentioned in the installation document. But still I'm unable to ftp to any server, the message I get is ftp: hostname or servname not known or not provided. Do you guys have any ideas ? Thanks Bhuvana ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Interesting that you chose 5.5 for a new install, most anyone would recommend something newer. Having said that, is the ether interface enabled? If you run sysinstall, and select post install config, then networking, then the interface in question, try to view/config it based on the parameters your isp gave you. When you're done you should see some lines in /etc/rc.conf specific to your config. Be careful with this file. Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Network Configuration with Jails. [Resolved]
> > Hello, > > > > I run a FreeBSD Jailer and I want to have multiple jails in 2 > > seperate networks. The server has 2 network interfaces and each of > > them are connected in a different network. Say vlan1 and vlan2. > > > > My problem is that all the network traffic is going through the > > first interface (vlan1). What I need is that a jail in vlan1 can't > > communicate with a jail in vlan2 (and vice-versa). > > > > Is it possible to split the network traffic in the right interfaces > > and use a diffrent default gateway for each of them ? > > > > Here is my /etc/rc.d configuration. > > > > defaultrouter="192.168.1.1" > > > > static_routes="vlan1 vlan2" > > route_vlan1="-net 192.168.1.0/24 192.168.1.1" > > route_vlan2="-net 192.168.2.0/24 192.168.2.1" > > > > # vlan1 interface config. > > ifconfig_bge0="inet 192.168.1.10 netmask 255.255.255.0" > > ifconfig_bge0_alias0="192.168.1.11 netmask 255.255.255.255" > > > > # vlan2 interface config. > > ifconfig_bge1="inet 192.168.2.10 netmask 255.255.255.0" > > ifconfig_bge1_alias0="inet 192.168.2.11 netmask 255.255.255.255" > > > > I tried to remove the default gateway but then the server was > > unreachable. I am thinking of using pf to resolve my issue. > > > >PF is probably the way to go. In particular using route-to to send traffic >originating from 192.168.2.0/24 to 192.168.2.1 > >I'm not totally sure what your static routes even accomplish. The kernel will >establish routes for directly connected networks automatically. > >So probably some rules of interest > ># keep jails from talking to each other >block in on bge0 from 192.168.2.0/24 to 192.168.1.0/24 block in on bge1 from >192.168.1.0/24 to 192.168.2.0/24 > ># ignore the default route >pass out route-to (bge1 192.168.2.1) from 192.168.2.0/24 to ! 192.168.2.0/24 \ > keep state > ># redundant because of the default route # which actually does what we want >pass out route-to (bge0 192.168.1.1) from 192.168.1.0/24 to ! 192.168.1.0/24 \ > keep state It's working perfectly. Thanks Josh ! -- Felix Langelier Unix Sysadmin [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: Network Configuration with Jails.
On Wednesday 28 November 2007 08:12:41 am Philip M. Gollucci wrote: > Félix Langelier wrote: > > Hello, > > > > I run a FreeBSD Jailer and I want to have multiple jails in 2 seperate > > networks. The server has 2 network interfaces and each of them are > > connected in a different network. Say vlan1 and vlan2. > > > > My problem is that all the network traffic is going through the first > > interface (vlan1). What I need is that a jail in vlan1 can't communicate > > with a jail in vlan2 (and vice-versa). > > > > Is it possible to split the network traffic in the right interfaces and > > use a diffrent default gateway for each of them ? > > > > Here is my /etc/rc.d configuration. > > > > defaultrouter="192.168.1.1" > > > > static_routes="vlan1 vlan2" > > route_vlan1="-net 192.168.1.0/24 192.168.1.1" > > route_vlan2="-net 192.168.2.0/24 192.168.2.1" > > > > # vlan1 interface config. > > ifconfig_bge0="inet 192.168.1.10 netmask 255.255.255.0" > > ifconfig_bge0_alias0="192.168.1.11 netmask 255.255.255.255" > > > > # vlan2 interface config. > > ifconfig_bge1="inet 192.168.2.10 netmask 255.255.255.0" > > ifconfig_bge1_alias0="inet 192.168.2.11 netmask 255.255.255.255" > > > > I tried to remove the default gateway but then the server was > > unreachable. I am thinking of using pf to resolve my issue. > > Removing the default gateway will work, but you have to add back > _similiar_ routes, you can't just remove it. PF is probably the way to go. In particular using route-to to send traffic originating from 192.168.2.0/24 to 192.168.2.1 I'm not totally sure what your static routes even accomplish. The kernel will establish routes for directly connected networks automatically. So probably some rules of interest # keep jails from talking to each other block in on bge0 from 192.168.2.0/24 to 192.168.1.0/24 block in on bge1 from 192.168.1.0/24 to 192.168.2.0/24 # ignore the default route pass out route-to (bge1 192.168.2.1) from 192.168.2.0/24 to ! 192.168.2.0/24 \ keep state # redundant because of the default route # which actually does what we want pass out route-to (bge0 192.168.1.1) from 192.168.1.0/24 to ! 192.168.1.0/24 \ keep state -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB signature.asc Description: This is a digitally signed message part.
Re: Network Configuration with Jails.
Félix Langelier wrote: > Hello, > > I run a FreeBSD Jailer and I want to have multiple jails in 2 seperate > networks. The server has 2 network interfaces and each of them are connected > in a different network. Say vlan1 and vlan2. > > My problem is that all the network traffic is going through the first > interface (vlan1). What I need is that a jail in vlan1 can't communicate with > a jail in vlan2 (and vice-versa). > > Is it possible to split the network traffic in the right interfaces and use a > diffrent default gateway for each of them ? > > Here is my /etc/rc.d configuration. > > defaultrouter="192.168.1.1" > > static_routes="vlan1 vlan2" > route_vlan1="-net 192.168.1.0/24 192.168.1.1" > route_vlan2="-net 192.168.2.0/24 192.168.2.1" > > # vlan1 interface config. > ifconfig_bge0="inet 192.168.1.10 netmask 255.255.255.0" > ifconfig_bge0_alias0="192.168.1.11 netmask 255.255.255.255" > > # vlan2 interface config. > ifconfig_bge1="inet 192.168.2.10 netmask 255.255.255.0" > ifconfig_bge1_alias0="inet 192.168.2.11 netmask 255.255.255.255" > > I tried to remove the default gateway but then the server was unreachable. > I am thinking of using pf to resolve my issue. Removing the default gateway will work, but you have to add back _similiar_ routes, you can't just remove it. -- Philip M. Gollucci ([EMAIL PROTECTED]) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration
> >> - you are NOT trying to get the second PC on the Internet > > > > No, I'm not. The agreement with my ISP doesn't allow to connect more > > than one computer to the WAN. > > LOL ;) I won't condone going against their rules, but that is what NAT > is for... > > > Part of my network's configuration is not in /etc/rc.conf . I have > > there only ifconfig_rl0="DHCP" to connect to the Internet. I used > > these commands to configure the LAN: > > #ifconfig rl0 alias 192.168.0.1 > > 192.168.0.2 > > How about: > > # ifconfig rl0 alias 192.168.0.1/24 > > I can't remember if /24 will work, if it doesn't: > > # ifconfig rl0 alias 192.168.0.1 255.255.255.0 > > > On the second PC: > > #ifconfig fxp0 192.168.0.2 192.168.0.1 > > and: > > # ifconfig fxp0 192.168.0.2/24 > > ...should get you at minimum to see each other. > > ie: from 2nd pc: > > # ping 192.168.0.1 > > ...now about that 2 pc's on the Internet thing. I think *almost* all > ISP's who offer highspeed say that. > > Steve > It works without packet loss. Thank for your advice. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration
>> - you are NOT trying to get the second PC on the Internet >> > No, I'm not. The agreement with my ISP doesn't allow to connect more > than one computer to the WAN. LOL ;) I won't condone going against their rules, but that is what NAT is for... > Part of my network's configuration is not in /etc/rc.conf . I have > there only ifconfig_rl0="DHCP" to connect to the Internet. I used > these commands to configure the LAN: > #ifconfig rl0 alias 192.168.0.1 > 192.168.0.2 How about: # ifconfig rl0 alias 192.168.0.1/24 I can't remember if /24 will work, if it doesn't: # ifconfig rl0 alias 192.168.0.1 255.255.255.0 > On the second PC: > #ifconfig fxp0 192.168.0.2 192.168.0.1 and: # ifconfig fxp0 192.168.0.2/24 ...should get you at minimum to see each other. ie: from 2nd pc: # ping 192.168.0.1 ...now about that 2 pc's on the Internet thing. I think *almost* all ISP's who offer highspeed say that. Steve > > > It's based on this, what is in the Handbook about IPv4 networks. > ___ > 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: Network configuration
> Ok, I have to assume some things here, correct me if I'm wrong: > > - both PC's are plugged into a switch/hub They are. > - your routers LAN IP address is 10.50.93.1 10.50.93.127 is my WAN's broadcast address. > - you are NOT trying to get the second PC on the Internet No, I'm not. The agreement with my ISP doesn't allow to connect more than one computer to the WAN. > > Now, I don't want to just give you my first advice, as I don't fully > understand your methods here, so please post the relevant portions of > /etc/rc.conf in relation to the network configuration. We'll then go > from there. > > Steve Part of my network's configuration is not in /etc/rc.conf . I have there only ifconfig_rl0="DHCP" to connect to the Internet. I used these commands to configure the LAN: #ifconfig rl0 alias 192.168.0.1 192.168.0.2 On the second PC: #ifconfig fxp0 192.168.0.2 192.168.0.1 It's based on this, what is in the Handbook about IPv4 networks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Network configuration
> > # ifconfig > rl0: flags=8843 mtu 1500 > options=8 > inet6 fe80::20a:cdff:fe01:9350%rl0 prefixlen 64 scopeid 0x1 > inet 10.50.93.21 netmask 0xff80 broadcast 10.50.93.127 > inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.2 > ether 00:0a:cd:01:93:50 > media: Ethernet autoselect (100baseTX ) > status: active > plip0: flags=108810 mtu 1500 > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff00 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > > # netstat -rn > Routing tables > > Internet: > DestinationGatewayFlagsRefs Use > Netif Expire > default10.50.93.1 UGS 0 3763rl0 > 10.50.93/25link#1 UC 00rl0 > 10.50.93.1 00:50:da:43:23:bc UHLW1 139 > rl0735 > 10.50.93.21127.0.0.1 UGHS00lo0 > 127.0.0.1 127.0.0.1 UH 18lo0 > 192.168.0 link#1 UC 00rl0 > 192.168.0.2ff:ff:ff:ff:ff:ff UHLWb 0 602rl0 > On the second computer (with 6.0): > #ifconfig > fxp0: flags=8843 mtu 1500 > options=8 > inet 192.168.0.2 net mask 0xff00 broadcast 192.168.0.255 > ether 00:04:23:13:ba:aa > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff00 #netstat -rn Routing tables > > Internet: > Destination Gateway > Flags > Netif Expire > default 192.168.0.1 UGS > fxp0 > 192.168.0 link#1 UC > fxp0 > 192.168.0.1 00:0a:cd:01:93:50 UHLW > fxp0 Ok, I have to assume some things here, correct me if I'm wrong: - both PC's are plugged into a switch/hub - your routers LAN IP address is 10.50.93.1 - you are NOT trying to get the second PC on the Internet Now, I don't want to just give you my first advice, as I don't fully understand your methods here, so please post the relevant portions of /etc/rc.conf in relation to the network configuration. We'll then go from there. Steve > ___ > 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: Network configuration
> # ifconfig rl0: flags=8843 mtu 1500 options=8 inet6 fe80::20a:cdff:fe01:9350%rl0 prefixlen 64 scopeid 0x1 inet 10.50.93.21 netmask 0xff80 broadcast 10.50.93.127 inet 192.168.0.1 netmask 0xff00 broadcast 192.168.0.2 ether 00:0a:cd:01:93:50 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=108810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > # netstat -rn Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default10.50.93.1 UGS 0 3763rl0 10.50.93/25link#1 UC 00rl0 10.50.93.1 00:50:da:43:23:bc UHLW1 139rl0735 10.50.93.21127.0.0.1 UGHS00lo0 127.0.0.1 127.0.0.1 UH 18lo0 192.168.0 link#1 UC 00rl0 192.168.0.2ff:ff:ff:ff:ff:ff UHLWb 0 602rl0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%rl0/64 link#1UC rl0 fe80::20a:cdff:fe01:9350%rl0 00:0a:cd:01:93:50 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#3UHL lo0 ff01::/32 ::1 U lo0 ff02::%rl0/32 link#1UC rl0 ff02::%lo0/32 ::1 UC lo0 On the second computer (with 6.0): #ifconfig fxp0: flags=8843 mtu 1500 options=8 inet 192.168.0.2 net mask 0xff00 broadcast 192.168.0.255 ether 00:04:23:13:ba:aa media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 #netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.0.1 UGS fxp0 192.168.0 link#1 UC fxp0 192.168.0.1 00:0a:cd:01:93:50 UHLW fxp0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Network configuration
> I have problems with network configuration of two computers > with FreeBSD. One has 5.4 and the second has 6.0. Both have > Pentium III compatible processors. > They are both connected to an Ethernet switch. > Computer with 5.4 has access to WAN, but there isn't any > access to computer with 6.0. > How should I configure LAN between these two computers? > I'd be grateful if you could help me. >From both boxes, perform the following, and post the output: # ifconfig # netstat -rn That will at minimum give us some info to start with. Regards, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Network configuration
I had to do one more thing: I needed to bind the IP the box got to the other adapter too. So now the ip is bound twice, but once with a netmask of 255.255.255.255. It was needed to let the clients ping the bridge by its external ip. -- Regards, Terrence Koeman MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Terrence Koeman > Sent: Sunday, July 11, 2004 17:38 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: RE: Network configuration > > Hi, > > Thank you all for the help and time. I finally got it all > working with bits > from most emails. > > I'll include my configuration here for others in the same > situation (any > comments are welcome): > > It's now: > > -- > | SDSL Modem | > | Bridged | > -- >| >-- >| xl1: 217.1.1.155, DHCP | >| Freebsd Box | >|xl0: UP, no ip | >-- >| >-- >|---| SWITCH |---| >| -- | >| || > --- --- --- > | C1: 217.1.1.156 | | C2: 217.1.1.157 | | C3: 217.1.1.158 | > --- --- --- > > (Notice the switch of xl1 and xl0, this made it work). > > xl1 and xl0 are bridged so that all clients have full > internet connectivity. > Additionally the clients share the available bandwidth > fairly, with ssh, > telnet, dns and http having a higher priority than other traffic. > > Using a private ip on xl0 and adding natd is still possible > for use in the > future. > > > FreeBSD samsara.mediamonks.net 5.2-CURRENT FreeBSD > 5.2-CURRENT #5: Sat Jul > 10 22:13:16 CEST 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAMSARA i386 > > > /sys/i386/conf/SAMSARA: > machine i386 > cpu I686_CPU > ident SAMSARA > > options SCHED_ULE # ULE scheduler > options INET# InterNETworking > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft > updates support > options UFS_DIRHASH # Improve performance on big > directories > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires > PSEUDOFS) > options PSEUDOFS# Pseudo-filesystem framework > options COMPAT_43 # Compatible with BSD > 4.3 [KEEP > THIS!] > options KBD_INSTALL_CDEV# install a CDEV entry in /dev > > options HZ=5000 > options ATA_STATIC_ID # Static device numbering > > options IPFIREWALL > options IPFIREWALL_DEFAULT_TO_ACCEPT > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=100 > options DUMMYNET > options BRIDGE > > device isa > device pci > > device fdc > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device vga # VGA video card driver > device sc > device npx > > device miibus # MII bus support > device xl # 3Com 3c90x (``Boomerang'', > ``Cyclone'') > > device random # Entropy device > device loop# Network loopback > device ether # Ethernet support > device pty # Pseudo-ttys (telnet etc) > > device bpf # Berkeley packet filter > > > /etc/rc.conf: > hostname="samsara.mediamonks.net" > > ifconfig_xl1="DHCP" > ifconfig_xl0="UP" > > jail_enable="NO" > kldxref_enable="NO" >
RE: Network configuration
f #ssh, telnet, dns, http queue 12 config pipe 1 weight 40 mask dst-ip 0x #all other ip #outgoing queues, group on src-host queue 20 config pipe 2 weight 50 mask src-ip 0x #icmp queue 21 config pipe 2 weight 99 mask src-ip 0x #ssh, telnet, dns, http queue 22 config pipe 2 weight 40 mask src-ip 0x #all other ip #queues for local system queue 30 config pipe 1 weight 50 mask dst-ip 0x queue 31 config pipe 2 weight 50 mask src-ip 0x #allow traffic on loopback interface add 00100 allow ip from any to any via lo0 #deny lost/hostile packets to the loopback addresses, return host unreach add 00110 unreach host log logamount 20 ip from any to 127.0.0.0/8 via any #deny any private address, return host unreach add 00301 unreach host log logamount 20 ip from 10.0.0.0/8 to any in via any add 00302 unreach host log logamount 20 ip from 172.16.0.0/12 to any in via any add 00303 unreach host log logamount 20 ip from 192.168.0.0/16 to any in via any #deny windows networking, return RST add 00500 reset log logamount 20 ip from any to any 135,137-139 via any #for bridged traffic, skip add skipto 2 ip from any to any via any bridged #** natd divert is possible here, if xl0 gets a private IP. ** #deny packets with a source address known on a different interface, return host unreach add 00800 unreach host log logamount 20 ip from any to any not verrevpath in # for non-bridged traffic, skip add skipto 3 ip from any to any via any #push bridged traffic in appropriate queues add 2 queue 10 icmp from any to any in recv xl1 add 20100 queue 11 ip from any 22,23,53,80 to any in recv xl1 add 20200 queue 11 ip from any to any 22,23,53,80 in recv xl1 add 20300 queue 12 ip from any to any in recv xl1 add 21000 queue 20 icmp from any to any in recv xl0 add 21100 queue 21 ip from any to any 22,23,53,80 in recv xl0 add 21200 queue 21 ip from any 22,23,53,80 to any in recv xl0 add 21300 queue 22 ip from any to any in recv xl0 add skipto 5 log logamount 20 ip from any to any via any #push non-bridged (local) traffic in appropriate queues add 3 queue 30 icmp from any to any in recv xl1 add 30100 queue 30 ip from any to any in recv xl1 add 31000 queue 31 icmp from any to any out xmit xl1 add 31100 queue 31 ip from any to any out xmit xl1 add 5 pass all from any to any I hope this helps someone in the future :) -- Regards, Terrence Koeman MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence. > -Original Message- > From: Randy Grafton [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 08, 2004 21:04 > To: [EMAIL PROTECTED] > Subject: RE: Network configuration > > I setup a little home network using my FreeBSD box as the > 'router'. There > are two boxes on my internal LAN that I wanted to have access > to from the > internet as well as provide full internet access to all internal > clients/servers. > > Like I said, I recompiled my kernel with the nat options. > I'll list the > steps here, if you've already performed them then at least I > got in some > typing practice. > > Install the kernel sources. Insert your install disk and from > the command > line run /stand/sysinstall. > Select the Configure option then the Distributions option then src and > finally sys. > Once the sources are installed you will go to > /usr/src/sys/i386/conf. Within > this directory are two files, GENERIC and LINT. Make a copy > of GENERIC with > a name of your choosing. Edit the GENERIC copy and add the > following lines: > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10 > options IPDIVERT > > Save the modified file and compile your kernel. This is done by doing: > config > cd ../../ > make > make install > reboot > > Now you'll edit your /etc/rc.conf file. > Add these lines to it: > gateway_enable="YES" > ifconfig_xl0="inet 217.1.1.155 netmask " > ifconfig_xl0_alias0="inet 217.1.1.155 netmask " > ifconfig_xl0_alias1="inet 217.1.1.156 netmask " > ifconfig_xl0_alias2="inet 217.1.1.157 netmask " > ifconfig_xl0_alias3="inet 217.1.1.158 netmask " > ifconfig_xl1="inet 192.168.1.1 netmask 255.255.255.0" > firewall_type="OPEN" > firewall_quiet="YES" > firewall_logging="YES" > natd_enable="YES" > natd_interface="xl0" > natd_flags="-f /etc/natd.conf" (explained below) > > Now create the /etc/natd.conf file with these lines: > same ports yes > dynamic yes > redirect_port tcp 192.168.1.2 217.1.1.156 > redirect_port udp 192.168.1.2 217.1.1.156 > redirect_port tcp 192.168.1.3 217.1.1.157
Re: Network configuration
Hello,
I see you have a problem here. First what kind of connectivity does your
DSL provider use? Companies like Covad, VerizonEast, Earthlink & AOL use
pppoe. So the first thing is to figure out what you provider requires DHCP,
Static, or pppoe. Then it is very simple to begin nating between the two
Networks.
biggreenwall#ipfw add divert natd all from any to any via rl0
biggreenwall# cat /etc/dhcpd.conf
subnet 192.168.50.0 netmask 255.255.255.0 {
range 192.168.50.2 192.168.50.254;
option routers 192.168.50.1;
}
biggreenwall#dhcpd rl1 -q
biggreenwall# ifconfig -a
rl0: flags=8843 mtu 1500
inet 66.24.50.87 netmask 0xff00 broadcast 66.24.50.255
inet6 fe80::230:bdff:fe26:4b28%rl0 prefixlen 64 scopeid 0x1
ether 00:30:bd:26:4b:28
media: Ethernet autoselect (100baseTX )
status: active
rl1: flags=8843 mtu 1500
inet 192.168.50.1 netmask 0xff00 broadcast 192.168.50.255
inet6 fe80::230:bdff:fe28:295b%rl1 prefixlen 64 scopeid 0x2
ether 00:30:bd:28:29:5b
media: Ethernet autoselect (10baseT/UTP)
status: active
biggreenwall# cat /etc/rc.conf
"cut to save space"
defaultrouter="66.24.50.1"
gateway_enable="YES"
hostname="biggreenwall"
ifconfig_rl0="inet 66.24.50.87netmask 255.255.255.0"
ifconfig_rl1="inet 192.168.50.1 netmask 255.255.255.0"
router_enable="YES"
sendmail_enable="NO"
natd_enable="YES"
natd_interface="rl0" # the id of your public NIC card
natd_flags="-m"
biggreenwall#
RFC1918
- Original Message -
From: "Nathan Kinkade" <[EMAIL PROTECTED]>
To: "Terrence Koeman" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 08, 2004 1:49 PM
Subject: Re: Network configuration
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Network configuration
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Nathan Kinkade > Sent: Thursday, July 08, 2004 19:49 > To: Terrence Koeman > Cc: [EMAIL PROTECTED] > Subject: Re: Network configuration > > On Thu, Jul 08, 2004 at 05:10:28PM +0200, Terrence Koeman wrote: > > Hi, > > > > I have been busy setting up a network the last 3 days, but > I cannot get it > > working. > > > > Basically I have no clue what has to be setup etc. and if I > need bridging or > > not. > > > > The situation is as follows: > > > > -- > > | SDSL Modem | > > | Bridged | > > -- > >| > > -- > > |xl0: 217.1.1.155| > > || > > |Freebsd Box | > > || > > | xl1 | > > -- > > | > > -- > > |---| SWITCH |---| > > | -- | > > || | > > --- --- --- > > | C1: 217.1.1.156 | | C2: 217.1.1.157 | | C3: 217.1.1.158 | > > --- --- --- > > > > > > The FreeBSD box has full internet connectivity and I can > also get NAT > > working, but the thing is that I need those non-private > IP's bound to the > > clients and I need ipfw between the clients and the modem. > Also I need the > > FreeBSD machine to have a non-private IP address. I have no > clue as to > > getting the packets from those clients to the internet. I > tried bridging xl0 > > and xl1 and using 217.1.1.155 as gateway, but that didn't work. > > > > Maybe someone that knows how to do something like this can > shed some light > > on it for me? > > > > Thanks in advance. > > > > -- > > Regards, > > Terrence Koeman > > You could make the FreeBSD box a bridge and still use IFPW. It really > depends on whether you will have other clients that will NOT > have public > IP addresses that will need NAT - you don't specify whether > this is the > case. For FreeBSD to be setup as a bridge/IPFW machine you will > minimally need a kernel compiled with the following options: > > options IPFIREWALL > options BRIDGE > > After you have built and installed this kernel add the > following entries > to /etc/sysctl.conf: > > net.link.ether.bridge=1 > net.link.ether.bridge_cfg=xl0,xl1 > net.link.ether.bridge_ipfw=1 > net.inet.ip.fw.enable=0 > > You will probably want to add the following lines to /etc/rc.conf so > that some IPFW rules will be loaded at boot: > > firewall_enable="YES" > firewall_type="" > > Read the firewall(7) manpage for more information. > > If you don't have console access to the FreeBSD machine > beware that the > default rule is to deny packets. Therefore if you build IPFW into the > kernel and don't allow for some basic rules to be added at > boot you will > likely be locked out from anything but console access. > There might be more clients that will require nat later. I tried this with: -217.1.1.155 bound to xl0 -nothing bound to xl1 -xl0 and xl1 bridged. -no ipfw rules and default to accept. When I try this the box is dead, no connectivity out and 217.1.1.155 is not reachable. If I try the exact same setup and bind 192.168.0.1 to xl1 I can connect to it when bridged, but the rest remains the same. -- Regards, Terrence Koeman MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Network configuration
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Lowell Gilbert > Sent: Thursday, July 08, 2004 2:17 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: Network configuration > > > "Terrence Koeman" <[EMAIL PROTECTED]> writes: > > > Hi, > > > > I have been busy setting up a network the last 3 days, but I cannot > > get it working. > > > > Basically I have no clue what has to be setup etc. and if I need > > bridging or not. > > > > The situation is as follows: > > > > -- > > | SDSL Modem | > > | Bridged | > > -- > >| > > -- > > |xl0: 217.1.1.155| > > || > > |Freebsd Box | > > || > > | xl1 | > > -- > > | > > -- > > |---| SWITCH |---| > > | -- | > > || | > > --- --- --- > > | C1: 217.1.1.156 | | C2: 217.1.1.157 | | C3: 217.1.1.158 | > > --- --- --- One thing I noticed is that there isn't an IP address assigned to xl1. This needs to be done, afaik. If you're out of IP addresses, NAT is going to be your thing, on a third interface perhaps. Here's what I'm getting at: As an example, set the IP address of xl1 to 217.1.1.154. Then, set up the routing table on the freebsd box so that all outgoing packets get passed to xl0, and any packet destined for 156, 157, or 158 get passed back to xl1. Set the default gateway on your machines to .154. This should have you up and running. If this doesn't make sense to you, send me an email and I'll try to explain further. HTH Eric Crist ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration
"Terrence Koeman" <[EMAIL PROTECTED]> writes: > Hi, > > I have been busy setting up a network the last 3 days, but I cannot get it > working. > > Basically I have no clue what has to be setup etc. and if I need bridging or > not. > > The situation is as follows: > > -- > | SDSL Modem | > | Bridged | > -- >| > -- > |xl0: 217.1.1.155| > || > |Freebsd Box | > || > | xl1 | > -- > | > -- > |---| SWITCH |---| > | -- | > || | > --- --- --- > | C1: 217.1.1.156 | | C2: 217.1.1.157 | | C3: 217.1.1.158 | > --- --- --- > > > The FreeBSD box has full internet connectivity and I can also get NAT > working, but the thing is that I need those non-private IP's bound to the > clients and I need ipfw between the clients and the modem. Also I need the > FreeBSD machine to have a non-private IP address. I have no clue as to > getting the packets from those clients to the internet. I tried bridging xl0 > and xl1 and using 217.1.1.155 as gateway, but that didn't work. I can't be sure without knowing the netmask, but it sounds like that's exactly the right idea. There's no way to tell why it went wrong when you gave neither the system configuration details or what actually happened when it "didn't work." You will probably find the FreeBSD Handbook documentation on this topic useful: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bridging.html -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org:8088/~lowell/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration
On Thu, Jul 08, 2004 at 05:10:28PM +0200, Terrence Koeman wrote: > Hi, > > I have been busy setting up a network the last 3 days, but I cannot get it > working. > > Basically I have no clue what has to be setup etc. and if I need bridging or > not. > > The situation is as follows: > > -- > | SDSL Modem | > | Bridged | > -- >| > -- > |xl0: 217.1.1.155| > || > |Freebsd Box | > || > | xl1 | > -- > | > -- > |---| SWITCH |---| > | -- | > || | > --- --- --- > | C1: 217.1.1.156 | | C2: 217.1.1.157 | | C3: 217.1.1.158 | > --- --- --- > > > The FreeBSD box has full internet connectivity and I can also get NAT > working, but the thing is that I need those non-private IP's bound to the > clients and I need ipfw between the clients and the modem. Also I need the > FreeBSD machine to have a non-private IP address. I have no clue as to > getting the packets from those clients to the internet. I tried bridging xl0 > and xl1 and using 217.1.1.155 as gateway, but that didn't work. > > Maybe someone that knows how to do something like this can shed some light > on it for me? > > Thanks in advance. > > -- > Regards, > Terrence Koeman You could make the FreeBSD box a bridge and still use IFPW. It really depends on whether you will have other clients that will NOT have public IP addresses that will need NAT - you don't specify whether this is the case. For FreeBSD to be setup as a bridge/IPFW machine you will minimally need a kernel compiled with the following options: options IPFIREWALL options BRIDGE After you have built and installed this kernel add the following entries to /etc/sysctl.conf: net.link.ether.bridge=1 net.link.ether.bridge_cfg=xl0,xl1 net.link.ether.bridge_ipfw=1 net.inet.ip.fw.enable=0 You will probably want to add the following lines to /etc/rc.conf so that some IPFW rules will be loaded at boot: firewall_enable="YES" firewall_type="" Read the firewall(7) manpage for more information. If you don't have console access to the FreeBSD machine beware that the default rule is to deny packets. Therefore if you build IPFW into the kernel and don't allow for some basic rules to be added at boot you will likely be locked out from anything but console access. Nathan -- PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=get&search=0xD8527E49 pgpeFbfUdRh20.pgp Description: PGP signature
RE: Network configuration
I haven't got any real config right now as I'm not sure about how to start with this. -- Regards, Terrence Koeman MediaMonks B.V. (www.mediamonks.com) Please quote all replies in correspondence. > -Original Message- > From: JJB [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 08, 2004 17:58 > To: [EMAIL PROTECTED] > Subject: RE: Network configuration > > Post the full content of your rc.conf file and your ipfw rule set. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Terrence Koeman > Sent: Thursday, July 08, 2004 11:10 AM > To: [EMAIL PROTECTED] > Subject: Network configuration > > Hi, > > I have been busy setting up a network the last 3 days, but I > cannot get it working. > > Basically I have no clue what has to be setup etc. and if I > need bridging or not. > > The situation is as follows: > > -- > | SDSL Modem | > | Bridged | > -- >| > -- > |xl0: 217.1.1.155| > || > |Freebsd Box | > || > | xl1 | > -- > | > -- > |---| SWITCH |---| > | -- | > || | > --- --- --- > | C1: 217.1.1.156 | | C2: 217.1.1.157 | | C3: 217.1.1.158 | > --- --- --- > > > The FreeBSD box has full internet connectivity and I can also > get NAT working, but the thing is that I need those > non-private IP's bound to the clients and I need ipfw between > the clients and the modem. Also I need the FreeBSD machine to > have a non-private IP address. I have no clue as to getting > the packets from those clients to the internet. I tried > bridging xl0 and xl1 and using 217.1.1.155 as gateway, but > that didn't work. > > Maybe someone that knows how to do something like this can > shed some light on it for me? > > Thanks in advance. > > -- > Regards, > Terrence Koeman > > MediaMonks B.V. (www.mediamonks.com) > Please quote all replies in correspondence. > > ___ > [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: Network configuration in FreeBSD
>> Am new to FreeBSD... just installed it for 2nd time today, but don't >> know what >> I did that it didn't ask me for the network configuration (ip, domain, >> etc)... once installed, is there a command to perform that task? >> >> I'm linux user, so am familiar to *nix systems, but don't know how to >> configure the network specifically on freebsd... I certainly agree with the suggestions to RTFM (Handbook), as well as sysinstall, but just for the record, the following is how you can do it from the command line. Let's assume that your network adapter is using the device name vr0 (you can look this up using the # ifconfig command), your IP address will be 192.168.0.10, your subnet mask is 255.255.255.0 your hostname is mybox.example.com, your DNS servers are 10.0.0.1 and 10.0.0.2 and finally, your default gateway is 192.168.0.1: First, edit /etc/rc.conf and add the following lines (include the quotes): ifconfig_vr0="inet 192.168.0.10 netmask 255.255.255.0" defaultrouter="192.168.0.1" hostname="mybox.example.com" Next, edit /etc/resolv.conf and add these lines: search example.com nameserver 10.0.0.1 nameserver 10.0.0.2 Now, to enable things as to not have to reboot, run the following commands: # ifconfig vr0 192.168.0.10/24 # route add default 192.168.0.1 Unless you have a firewall, you should now be able to connect to other hosts. Regards, Steve > > As another person suggested, try checking out the FreeBSD Handbook at > freebsd.org, which pretty much describes everything you need to know > when getting started w/FBSD. > > Since, no one has suggested this yet, I will: you can go back into the > installer utility by running /stand/sysinstall. The installer comes in > handy quite a bit when you don't know the actually commands to do > something (ie setting up a network interface or partitioning a disk). > > Once you run /stand/sysinstall, you can scroll all the way to the bottom > and select 'Index' and then select 'Network Interfaces'. > > HTH > -- > Don't you wish that all the people who sincerely want to help you > could agree with each other? > > /* Aaron Walker > * http://butsugenjitemple.org/~ka0ttic/ > */ > > ___ > [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: Network configuration in FreeBSD
Miguel Cardenas wrote: Hello Am new to FreeBSD... just installed it for 2nd time today, but don't know what I did that it didn't ask me for the network configuration (ip, domain, etc)... once installed, is there a command to perform that task? I'm linux user, so am familiar to *nix systems, but don't know how to configure the network specifically on freebsd... Thanks for any comment, Mike As another person suggested, try checking out the FreeBSD Handbook at freebsd.org, which pretty much describes everything you need to know when getting started w/FBSD. Since, no one has suggested this yet, I will: you can go back into the installer utility by running /stand/sysinstall. The installer comes in handy quite a bit when you don't know the actually commands to do something (ie setting up a network interface or partitioning a disk). Once you run /stand/sysinstall, you can scroll all the way to the bottom and select 'Index' and then select 'Network Interfaces'. HTH -- Don't you wish that all the people who sincerely want to help you could agree with each other? /* Aaron Walker * http://butsugenjitemple.org/~ka0ttic/ */ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
On 8 Jul 2004 at 1:52, Miguel Cardenas wrote: > Hello > > Am new to FreeBSD... just installed it for 2nd time today, but don't know what > I did that it didn't ask me for the network configuration (ip, domain, When you got to the HD partitioning in the beginning of setup you should have deleted the entire disk, then repartitioned it. If you kept the partitioning from your first install the setup routine will look in the excisting folders and use what it finds there > etc)... once installed, is there a command to perform that task? It all goes into the /etc/rc.conf file. Use your editor to make changes if you do not like what you find. > > I'm linux user, so am familiar to *nix systems, but don't know how to > configure the network specifically on freebsd... > > Thanks for any comment, > Mike kjell ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network configuration in FreeBSD
Miguel Cardenas wrote: Hello Am new to FreeBSD... just installed it for 2nd time today, but don't know what I did that it didn't ask me for the network configuration (ip, domain, etc)... once installed, is there a command to perform that task? I'm linux user, so am familiar to *nix systems, but don't know how to configure the network specifically on freebsd... Thanks for any comment, Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html The FreeBSD Handbook literally covers everything "basic" to FreeBSD. Give that a try. :) Michael -- Michael D. Whities [EMAIL PROTECTED] http://www.one-arm.com -- There are four colors of hats to watch for: Black, White, Grey, and Red. The meanings are: Cracker, Hacker, Guru, and Victim. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
