Re: systemd and variable network (help needed)
another example perl -pi -e "s/^ServerName .*$/ServerName $HOME_SERVER_NAME/g" /etc/cups/client.conf how do I do this with systemd? I'll try now the _netdev option and see if it works for me without systemd thanks in advance
Re: systemd and variable network (help needed)
On Wednesday 06 January 2016 12:45:43 deloptes wrote: > I do this with two custom init script > - network script (checks the interface and network/domain) > and updates fstab, resolv.conf + mounts nfs if 1) I do a similar task with a script located in /etc/network/if-up.d/ This is executed when systemd sets up network with NetworkManager. HTH -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
systemd and variable network (help needed)
Hi, I'm willing to start using systemd, but there is one major issue that prevent me to do so. I have following use cases regarding network setup. 1) home office - my home is on a nfs share - the nfs share mounted via fstab before user gets to login prompt - eth0 no firewall required - wireless off except bluetooth 2) company office - user has a stand allone profile - eth0 firewall active (not too strict rules) - wireless and bluetooth off 3) on the road - user has a stand allone profile (same as 2) - wireless on, bluetooth off - wlan0 firewall active (strict rules) I do this with two custom init script - network script (checks the interface and network/domain) and updates fstab, resolv.conf + mounts nfs if 1) - firewall script - iptables classic + custom checks How can I solve this with systemd? Can I tell systemd to execute a/the script after something else was done and where do I set this? Debian Jessie in use here Highly appreciated, thanks in advance.
Re: systemd and variable network (help needed)
On Wed 06 Jan 2016 at 12:45:43 +0100, deloptes wrote: > I'm willing to start using systemd, but there is one major issue that > prevent me to do so. > > I have following use cases regarding network setup. > > 1) home office > - my home is on a nfs share > - the nfs share mounted via fstab before user gets to login prompt > - eth0 no firewall required > - wireless off except bluetooth > 2) company office > - user has a stand allone profile > - eth0 firewall active (not too strict rules) > - wireless and bluetooth off > 3) on the road > - user has a stand allone profile (same as 2) > - wireless on, bluetooth off > - wlan0 firewall active (strict rules) > > I do this with two custom init script > - network script (checks the interface and network/domain) > and updates fstab, resolv.conf + mounts nfs if 1) > - firewall script - iptables classic + custom checks > > How can I solve this with systemd? Can I tell systemd to execute a/the > script after something else was done and where do I set this? > > Debian Jessie in use here Why not try systemd before anticipating any issues? 'init=/bin/systemd' on the kernel command line for trial runs.
Re: systemd and variable network (help needed)
On Wed 06 Jan 2016 at 15:57:12 +0100, deloptes wrote: > Brian wrote: > > > Why not try systemd before anticipating any issues? 'init=/bin/systemd' > > on the kernel command line for trial runs. > > I have tried it - this is the reason I ask the question. > > The nfs share with my home did not mount, so script either did not execute, > or executed inappropriate. Did journalctl have anything to say on this?
Basic(?) network help, please...
Since I don't do this often, what may be very easy is confusing me. I have switched from DSL (static IP) to cable internet (5 static IPs). I have a sort of network diagram (in a format that I hope can be easily viewed) available at neidorff.com . Below the line there is a link that says Network Diagram. Some things are not quite right. Under the DSL setup (old) the router provided me with a translated set of addresses, so that I could use the 192.168.2.* range to connections to the router. With cable, I have 5 static IPs, but the cable modem only provides ports for the static IPs. I changed the configuration of the NIC that connects from the server to the cable modem to match a static IP. I can't get PCs on the local LAN (192.168.1.x) to connect to the net using the cable provider's nameservers. If I use the nameservers of my old provider (which are still active for me, for now) they can connect to the net. Why is this? How do I correct it? Here is the routing table $route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 108.58.151.192 0.0.0.0 255.255.255.248 U 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 0.0.0.0 108.58.151.193 0.0.0.0 UG 0 0 0 eth0 Thanks for any help, Mark -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101291354.50604.m...@neidorff.com
Re: Basic(?) network help, please...
On Sat, 29 Jan 2011 13:54:50 -0500, Mark Neidorff wrote: (...) I can't get PCs on the local LAN (192.168.1.x) to connect to the net using the cable provider's nameservers. If I use the nameservers of my old provider (which are still active for me, for now) they can connect to the net. Why is this? How do I correct it? There are some things in the air that may require further investigation. First, as per your description (five static IP), I guess you have been given a very nice cable modem gateway device but most surely it is somehow limited/restricted/customized by your provider, so you should contact them and ask for a basic configuration setup start-up guide. I say this because some providers give their users a login username/ password and let them to manage their devices from their internal subnetwork. Second, you should ask yourself about the network setup do you have in mind... that is, cable modems (unless otherwise specified) are just gateways with no routing capabilities and act in the same way like the old dial-up serial modems: they connect your machine (the one to which is attached) directly to the web (which is good if you have a web server behind the cable modem that you want to be reachable from outside) but maybe you don't want all your machines are also acting in that way, like public servers. So, dependending on what you have in mind, you may also need to have a router with nat capabilities that: 1/ Hide your internal network machines (so you can use 192.168.0.x addresses) and keep them out of the Internet. 2/ Provide addictional DHCP/DNS functionalities, in the event the cable- modem do not. And last, you can use whatever DNS servers you prefer (like the ones from OpenDNS or Google's) but usually the ones that your isp provides are better (lower latency and fast response). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.29.21.19...@gmail.com
Re: Basic(?) network help, please...
Thanks. You have clarified exactly what I need to know. Mark On Saturday 29 January 2011 04:19 pm, Camaleón wrote: On Sat, 29 Jan 2011 13:54:50 -0500, Mark Neidorff wrote: (...) I can't get PCs on the local LAN (192.168.1.x) to connect to the net using the cable provider's nameservers. If I use the nameservers of my old provider (which are still active for me, for now) they can connect to the net. Why is this? How do I correct it? There are some things in the air that may require further investigation. First, as per your description (five static IP), I guess you have been given a very nice cable modem gateway device but most surely it is somehow limited/restricted/customized by your provider, so you should contact them and ask for a basic configuration setup start-up guide. I say this because some providers give their users a login username/ password and let them to manage their devices from their internal subnetwork. Second, you should ask yourself about the network setup do you have in mind... that is, cable modems (unless otherwise specified) are just gateways with no routing capabilities and act in the same way like the old dial-up serial modems: they connect your machine (the one to which is attached) directly to the web (which is good if you have a web server behind the cable modem that you want to be reachable from outside) but maybe you don't want all your machines are also acting in that way, like public servers. So, dependending on what you have in mind, you may also need to have a router with nat capabilities that: 1/ Hide your internal network machines (so you can use 192.168.0.x addresses) and keep them out of the Internet. 2/ Provide addictional DHCP/DNS functionalities, in the event the cable- modem do not. And last, you can use whatever DNS servers you prefer (like the ones from OpenDNS or Google's) but usually the ones that your isp provides are better (lower latency and fast response). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101291722.12473.m...@neidorff.com
network help
I am using debian etch. my network is not working. When I do lsmod it shows 8139too,8139cp (I only have 1 network connection). When I rmmod 8139too and rmmod 8139cp then modprobe 8139too It is detected. I then /etc/init.d/networking restart and I still have no network. When I init 1, basically do the rmmod above and modprobe 8139too then init 3 my network is fine. Where can I look as to why my network is not coming up correctly. I tried to blacklist 8139cp but that made no difference. I am booting debian from a USB thumbdrive. Thanks, Jerry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: network help
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/07/08 12:17, Jerry Geis wrote: I am using debian etch. my network is not working. When I do lsmod it shows 8139too,8139cp (I only have 1 network connection). When I rmmod 8139too and rmmod 8139cp then modprobe 8139too It is detected. I then /etc/init.d/networking restart and I still have no network. When I init 1, basically do the rmmod above and modprobe 8139too then init 3 my network is fine. Where can I look as to why my network is not coming up correctly. I tried to blacklist 8139cp but that made no difference. I am booting debian from a USB thumbdrive. Open another terminal window (or flip to another vterm), and run: tail -f /var/log/syslog Then in the original window, restart networking. The syslog results may prove useful. Also look at dmesg | tail. - -- Ron Johnson, Jr. Jefferson LA USA Kittens give Morbo gas. In lighter news, the city of New New York is doomed. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhyb3UACgkQS9HxQb37Xmfy2wCfRC5Z+IsWF3haLlNO/AOD/nnl 9jwAnjKrsuilH9EfYKdpzN2Vql71/Sz7 =L6kL -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: network help
Ron Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/07/08 12:17, Jerry Geis wrote: I am using debian etch. my network is not working. When I do lsmod it shows 8139too,8139cp (I only have 1 network connection). When I rmmod 8139too and rmmod 8139cp then modprobe 8139too It is detected. I then /etc/init.d/networking restart and I still have no network. When I init 1, basically do the rmmod above and modprobe 8139too then init 3 my network is fine. Where can I look as to why my network is not coming up correctly. I tried to blacklist 8139cp but that made no difference. I am booting debian from a USB thumbdrive. Open another terminal window (or flip to another vterm), and run: tail -f /var/log/syslog Then in the original window, restart networking. The syslog results may prove useful. Also look at dmesg | tail. - -- I found it /etc/udev/rules.d/something-network had 2 entries on for the 8139cp and one for the 8139too. I removed the 8139cp and change 8139too to be eth0 and it started working... Thanks, Jerry
script to connect the first wifi network[help nedded]
Howdy .. i have a laptop and i travel alot so i worte a small script to the next things: 1.search for wifi network and connect to the it finds #i hope to find a way to search one that have the strogest signal. 2.if lan (eth0) is connected then run connection script #hope to find a way to determine what gateway gave my the link and then run a sutile script : !/bin/bash T1=`iwlist eth1 scan|grep ESSID` if [ $T1 != 1 ];then echo $T1 iwconfig eth1 ESSID `iwlist eth1 scan|grep ESSID |tr -d ESSID:` mode manged #if anyone know how to detrmine the strongest signal and one that is not encrypted dhclient eth1 fi T2=`dmesg |grep eth0|grep -o link up` if [ $T2 != ]; then #pptp client script cs # fi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: :::Debian Network Help:::
Hi Trinatek, Seems like you're having a problem with Debian GNU/Linux rather than Debian GNU/Hurd. Network setup is different on Debian GNU/Hurd. Can somebody help this gentleman (and drop debian-hurd), please? Michael On Wed, Dec 31, 2003 at 11:05:13PM -0600, Trinatek Trinatek wrote: For some reason, i cant get my networking to work with Debian (I've also tried Knoppix)... When installing Debian, for some reason it can never detect the network card or anything, I've tried many different ways to fix it but cant... When I try to install Debian, it stops me at the Network part, is there a way i can skip that part of the installation, or even better a way for it to detect my network card? When I try to set up the network manually by entering Host IP and etc, it says something simalar to Network is configured but not yet activated, Im not sure what is going on... === COMPUTER HARDWARE (As shown, in order in Window's Device Manager) === -Alienware- Intel(R) Pentium(R) 4 CPU 3.06GHz 3.07Ghz 512 of RAM [HARWARE] Computer ACPI Multiprocessor PC Disk drives ST3120024A Display Adapters Radeon 9800 PRO Radeon 9800 PRO - Secondary DVD/CD-ROM drives ARTEC WSM-52X SAMSUNG DVD-ROM SD-616Q Floppy disk controller Standard floppy disk controller Human Interface Devices HID-compliant device Microsoft USB IntelliMouse Explorer 3.0 USB Human Interface Device IDE ATA/ATAPI controllers Intel(r) 82801BA Bus Master IDE Controller Primary IDE Channel Secondary IDE Channel IEEE 1394 Bus host controllers OHCI Compliant IEEE 1394 Host Controller Imaging devices Lexmark X5100 Series Keyboards Standard 101/102-Key or Microsoft Natural PS/2 Keyboard Mice and other pointing devices Microsoft USB IntelliMouse Explorer 3.0 Monitors SyncMaster 150MPlus/150MP, SyncMaster Magic CX151MPplus/CX151MP SyncMaster 150MPlus/150MP, SyncMaster Magic CX151MPplus/CX151MP Network adapters 1394 Net Adapter Intel(R) PRO/100 VE Network Connection Ports (COM LPT) Communications Port (COM1) ECP Printer Port (LPT1) Processors Intel(R) Pentium(R) 4 CPU 3.06GHz Intel(R) Pentium(R) 4 CPU 3.06GHz SCSI and RIAD controllers ST3SHARK SCSI Controller Sound, video and game controllers Audio Codecs Creative Game Port Creative SB Audigy Legacy Audio Drivers Legacy Video Capture Devices Media Control Devices Video Codecs System devices ACPI Fixed Feature Button Direct memory access controller Intel Processor to AGP Controller Intel(R) 82801BA LPC Interface Controller - 2440 Intel(R) 82801BA/CA PCI Bridge - 244E Intel(R) 82850 Processor to I/O Controller - 2530 ISAPNP Read Data Port Microcode Update Devices Microsoft ACPI-Compliant System Motherboard resources Motherboard resources Motherboard resources Numeric data processor PCI bus Plug and Play Software Device Enumerator PnP BIOS Extension Programmable interrupt controller System board System CMOS/real time clock System speaker System timer Terminal Server Device Redirector Universal Serial Bus Controllers Intel(r) 82801Ba/BAM USB Universal Host Controller - 2442 Intel(r) 82801Ba/BAM USB Universal Host Controller - 2444 NEC PCI to USB Enhanced Host Controller (B1) NEC PCI to USB USB Open Host Controller NEC PCI to USB USB Open Host Controller USB Composite Device USB Printing Support USB Root Hub USB Root Hub USB Root Hub USB Root Hub USB Root Hub === _ Make your home warm and cozy this winter with tips from MSN House Home. http://special.msn.com/home/warmhome.armx -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: :::Debian Network Help:::
On Wed, Dec 31, 2003 at 11:05:13PM -0600, Trinatek Trinatek wrote: For some reason, i cant get my networking to work with Debian (I've also tried Knoppix)... When installing Debian, for some reason it can never detect the network card or anything, I've tried many different ways to fix it but cant... When I try to install Debian, it stops me at the Network part, is there a way i can skip that part of the installation, or even better a way for it to detect my network card? When I try to set up the network manually by entering Host IP and etc, it says something simalar to Network is configured but not yet activated, Im not sure what is going on... === COMPUTER HARDWARE (As shown, in order in Window's Device Manager) === Network adapters 1394 Net Adapter Intel(R) PRO/100 VE Network Connection If Knoppix doesn't find your network card, that's fairly bad news. Do you have two NICs in this box? A 1394 and an Intel? I'm not at all familiar with a 1394, and don't even know for sure that's a NIC. The Intel however should just work with Knoppix, and should work fairly easily with Debian. You don't say how you're installing Debian (CD, floppy, etc), but I suspect it's via either a full-blown Debian installer CD or a netinstall CD. In either case, you may need the installer with a 2.4 kernel instead of a 2.2 kernel. (During the install, shell out to a virtual terminal - Alt-F2, and run uname -a to see what version kernel you have.) If you do have two NICs, it may be that Knoppix and/or the Debian installer is getting confused about which NIC to use. For now, to make things simpler, I'd remove the 1394 NIC and just do the install with the Intel NIC, which should use the eepro100 module I believe. After you have your network working with that NIC, you can put the 1394 back in and work on getting it configured if necessary. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: :::Debian Network Help:::
On Thu, 01 Jan 2004 09:12:44 -0600 Kent West [EMAIL PROTECTED] wrote: ... 1394 Net Adapter ... Intel(R) PRO/100 VE Network Connection ... things simpler, I'd remove the 1394 NIC and just do the install with the Intel NIC, which should use the eepro100 module I believe. After you have your network working with that NIC, you can put the 1394 back in and work on getting it configured if necessary. ... Hi Well, the first one is a virtual nw adapter created by windows for network over firewire, witch is as far as i know not supported by standard debian kernel. For the Intel one: I also have a Intel(R) PRO/100 VE in my notebook and had to use the preliminary bootfloppies from here: http://people.debian.org/~blade/bf3024 ,because I wasnt able to get it running with the bf2.4 2.4.18ner kernel. I havent tried knoppix on it though. For now it seems that the url from above is dead at the moment I think (since the debian server compromise). But since I didn't have any problem with any more recent kernel (2.4.22 and above, though up to 2.4.23 with -ac patches) knoppic should work I think. Mayby this helps yours Albert -- Albert Dengg [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Network Help
I know this is a Debian news group, but the networking stuff should be Linux platform independant. Right? We just had a new Intel Itanium IA64 file server installed at the office. I installed TurboLinux ( O/S came with system ). The system is on a closed/secure LAN. When I log into the system, I can ping other system on the LAN. When I'm on another system I can ping the new IA64 system. All seems to be OK. What I can't do is rlogin/telnet/ftp/ssh into the new IA64 system from other machines on our LAN. I removed the # comments from the ftp/telnet/shell/etc. lines in the /etc/inetd.conf file and restarted the IA64 system (yeah I know, but old habits are hard to break. Besides, no one is on the system yet except root.) What am I missing? What else do I have to do to activate rlogin/telnet/ftp/ssh services? What can I look for when I get back to the office on Monday? Thanks for your help... -- -=[cwa]=- Debian 2.2_r2 GNU/Linux
Re: Network Help
On Sat, Jun 16, 2001 at 01:55:33PM -0400, Christopher W. Aiken wrote: I know this is a Debian news group, but the networking stuff should be Linux platform independant. Right? We just had a new Intel Itanium IA64 file server installed at the office. I installed TurboLinux ( O/S came with system ). The system is on a closed/secure LAN. When I log into the system, I can ping other system on the LAN. When I'm on another system I can ping the new IA64 system. All seems to be OK. What I can't do is rlogin/telnet/ftp/ssh into the new IA64 system from other machines on our LAN. I removed the # comments from the ftp/telnet/shell/etc. lines in the /etc/inetd.conf file and restarted the IA64 system (yeah I know, but old habits are hard to break. Besides, no one is on the system yet except root.) What am I missing? What else do I have to do to activate rlogin/telnet/ftp/ssh services? What can I look for when I get back to the office on Monday? Try ipchains -L and look for deny rules, just having all policies set to accept should be ok for a local lan. Also have a look at the log messages, maybe the ftpd daemon isn't found by inetd or can't be executed for some reason, does it work for localhost? -- ,---. Name: Alson van der Meulen Personal: [EMAIL PROTECTED] School: [EMAIL PROTECTED] `---' Sorry, we deleted that package last week... -
Re: Network Help
On Saturday 16 June 2001 12:55, Christopher W. Aiken wrote: I know this is a Debian news group, but the networking stuff should be Linux platform independant. Right? We just had a new Intel Itanium IA64 file server installed at the office. I installed TurboLinux ( O/S came with system ). The system is on a closed/secure LAN. When I log into the system, I can ping other system on the LAN. When I'm on another system I can ping the new IA64 system. All seems to be OK. What I can't do is rlogin/telnet/ftp/ssh into the new IA64 system from other machines on our LAN. I removed the # comments from the ftp/telnet/shell/etc. lines in the /etc/inetd.conf file and restarted the IA64 system (yeah I know, but old habits are hard to break. Besides, no one is on the system yet except root.) What am I missing? What else do I have to do to activate rlogin/telnet/ftp/ssh services? What can I look for when I get back to the office on Monday? Hi Chris, Did you try installing the right daemons? :)
Net network help, please
I'm having a little trouble I could do with some help with, if possible. I have Corel Linux installed. I have a windwosNT network with a NT DHCP / WINS server. It worked fine, the linux box intergrated pretty well, although the DHCP server showed the IP but not the name of the machine. I need to change the IP block in preparation for firewalling an internet feed I am getting. I changed to 192.168.1.x for all the machines, the DHCP/WINS machine is 192.168.1.10 Although the Linux box has been given an IP, I can't ping it from another machine and it can't ping anybody. It seems to be able to get an IP from the DHCP server, the name shows up in the name table so it must be getting to the WINS server, but it is not on the network, and I can't ping it. Any ideas? I don't know the Linux commands to test it, I tried ifconfig and the card has the correct IP and subnetmask. What should the gateway be in this case? Chris Mason Box 340, The Valley, Anguilla, British West Indies Tel: 264 497 5670 Fax: 264 497 8463 USA Fax (561) 382-7771 Take a virtual tour of the island http://net.ai/ The Anguilla Guide Find out more about NetConcepts www.netconcepts.ai bwz*mq
Re: network help
G. Kapetanios wrote: Following your suggestion I pinged my gateway by IP rsther than name. The thing hang after printing a line. So maybe what you say about the card not working correctly is right. I was wondering: Win98 has no problem with recognizing and using the card. Why should Linux ? As this is not my computer tha card is there to stay. Additonally I would like to use the box as a server for math application to be accessed through telnet only . So I need to be sure that the card is the problem and if so remove Deibian Do you know any methods that can tell me fpor certain that the card is to blame ? Well, the gateway might not allow ping packets. You can try to 'traceroute -n' it and see if that works. Also you have not said anything about what is in you /etc/resolve.conf file. If the card works in WinBlows, then I see no reason why it would not work in Debian. Are you sure that the kernel is detecting the IO Port and IRQ correctly for the network card? -- Paul Miller [EMAIL PROTECTED]begin:vcard n:Miller;Paul x-mozilla-html:FALSE org:Talons adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:President note:The Spirit of the University of North Texas x-mozilla-cpt:;0 fn:Paul Miller end:vcard
Re: network help
Subject: Re: network help
Date: Fri, Mar 12, 1999 at 04:30:30PM +
In reply to:G. Kapetanios
Quoting G. Kapetanios([EMAIL PROTECTED]):
Following your suggestion I pinged my gateway by IP rsther than name.
The thing hang after printing a line. So maybe what you say about the card
not working correctly is right.
I was wondering: Win98 has no problem with recognizing and using
the card. Why should Linux ?
As this is not my computer tha card is there to stay.
Additonally I would like to use the box as a server for math application
to be accessed through telnet only .
So I need to be sure that the card is the problem and if so remove Deibian
Do you know any methods that can tell me fpor certain that the card is to
blame ?
Thanks again for your help
George
George
I assume that your trying to network a linux box to a Win95 box. If
that is so I found that if I put in a gateway on my Linux box my
network didn't work at all.
I changed the network script to
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask${NETMASK}
/sbin/route add -net ${NETWORK} netmask ${NETMASK} # for 2/2/x Kernels
then route -n
VT1 root-Deb-Slink:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
ifconfig
eth0 Link encap:Ethernet HWaddr 00:40:05:3D:34:51
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:646 errors:0 dropped:0 overruns:0 frame:0
TX packets:657 errors:0 dropped:0 overruns:0 carrier:0
Collisions:0
Interrupt:9 Base address:0x6200
HTH
Wayne
--
APL is a write-only language. I can write programs in APL, but I
can't read any of them.
-- Roy Keir
___
Wayne T. Topa [EMAIL PROTECTED]
Re: network help
Following your suggestion I pinged my gateway by IP rsther than name. The thing hang after printing a line. So maybe what you say about the card not working correctly is right. I was wondering: Win98 has no problem with recognizing and using the card. Why should Linux ? As this is not my computer tha card is there to stay. Additonally I would like to use the box as a server for math application to be accessed through telnet only . So I need to be sure that the card is the problem and if so remove Deibian Do you know any methods that can tell me fpor certain that the card is to blame ? Thanks again for your help George On Thu, 11 Mar 1999, Paul Miller wrote: G. Kapetanios wrote: Thanks for the reply ifconfig gives the followng loLink encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 eth0 Link encap:Ethernet HWaddr 00:00:E8:CC:28:7D inet addr:194.81.117.61 Bcast:194.81.117.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 Interrupt:3 Base address:0x300 route -n gives Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 194.81.117.00.0.0.0 255.255.255.0 U 0 01 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 194.81.117.10.0.0.0 UG1 01 eth0 Notice that 194.81.117.1 is the gateway I have given in the configuration This info looks fine to me. dmesg gives the following network card related info. loading device 'eth0'... ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED]) NE*000 ethercard probe at 0x300: 00 00 e8 cc 28 7d eth0: NE2000 found at 0x300, using IRQ 3. loading device 'eth1'... Now why does it say loading device eth1? I have no clue. Hmmm... It seems to me that the card is correctly detected the problem is with the gateway I guess since route (not route -n) hangs Just for grins try pinging 194.81.117.1. Do not use the host name. Use the IP address. Does it still give you problems? If it does not, you should take a look at /etc/resolve.conf and make sure you have your DNS server listed there. The reason why route hangs is because your machine cannot find a host name for the IP address of your gateway. If you cannot ping an IP address, the network card might not be workign right. It could be a bad network cable or wall jack. Hope this helps -- Paul Miller [EMAIL PROTECTED] --- George Kapetanios Churchill College Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED] U.K. WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html ---
Re: network help
Thanks for the reply ifconfig gives the followng loLink encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 eth0 Link encap:Ethernet HWaddr 00:00:E8:CC:28:7D inet addr:194.81.117.61 Bcast:194.81.117.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 Interrupt:3 Base address:0x300 route -n gives Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 194.81.117.00.0.0.0 255.255.255.0 U 0 01 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 194.81.117.10.0.0.0 UG1 01 eth0 Notice that 194.81.117.1 is the gateway I have given in the configuration dmesg gives the following network card related info. loading device 'eth0'... ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED]) NE*000 ethercard probe at 0x300: 00 00 e8 cc 28 7d eth0: NE2000 found at 0x300, using IRQ 3. loading device 'eth1'... It seems to me that the card is correctly detected the problem is with the gateway I guess since route (not route -n) hangs Any help will be appreciated Thanks On Wed, 10 Mar 1999, Paul Miller wrote: G. Kapetanios wrote: Hi, I am trying to set up thi computer at work with Debian. All works fine apart from the network. This is a novell environment. I have set up one computer in a novell environment before and it was fine. however here I have problems. The newtwork card is working OK as far as I can tell. On boot the kernel finds it and although some mention of the eth1 interface is made at that stage, ifconfig states that eth0 is used. I can ping myself either using localhost or the IP Can you give us the output of dmesg dealing with your network card? address or the name of the machine. Ifconfig reports that lo and eth0 is up. But any attempt to ftp ping telnet anything outside of the machine does not work. route reports the localnet and 127.0.0.0 and then hangs. No gateway seems to be available as * is in place of the gateway. However I am using the same number as the other Win98 computers report in the TCP/IP installed gateways in network in control panel. I have not seen this problem before and I am at a loss for solving. Any help will be appreciated. What would help here would be the output of ifconfig and 'route -n'. The -n tells route not to do DNS lookup for host names, but print IP addresses. What is your gateway's IP, and what is your netmask? Thanks George --- George Kapetanios Churchill College Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED] U.K. WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html --- -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Paul Miller [EMAIL PROTECTED] --- George Kapetanios Churchill College Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED] U.K. WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html ---
Re: network help
G. Kapetanios wrote: Thanks for the reply ifconfig gives the followng loLink encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 eth0 Link encap:Ethernet HWaddr 00:00:E8:CC:28:7D inet addr:194.81.117.61 Bcast:194.81.117.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 Interrupt:3 Base address:0x300 route -n gives Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 194.81.117.00.0.0.0 255.255.255.0 U 0 01 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 00 lo 0.0.0.0 194.81.117.10.0.0.0 UG1 01 eth0 Notice that 194.81.117.1 is the gateway I have given in the configuration This info looks fine to me. dmesg gives the following network card related info. loading device 'eth0'... ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED]) NE*000 ethercard probe at 0x300: 00 00 e8 cc 28 7d eth0: NE2000 found at 0x300, using IRQ 3. loading device 'eth1'... Now why does it say loading device eth1? I have no clue. Hmmm... It seems to me that the card is correctly detected the problem is with the gateway I guess since route (not route -n) hangs Just for grins try pinging 194.81.117.1. Do not use the host name. Use the IP address. Does it still give you problems? If it does not, you should take a look at /etc/resolve.conf and make sure you have your DNS server listed there. The reason why route hangs is because your machine cannot find a host name for the IP address of your gateway. If you cannot ping an IP address, the network card might not be workign right. It could be a bad network cable or wall jack. Hope this helps -- Paul Miller [EMAIL PROTECTED]begin:vcard n:Miller;Paul x-mozilla-html:FALSE org:Talons adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:President note:The Spirit of the University of North Texas x-mozilla-cpt:;0 fn:Paul Miller end:vcard
network help
Hi, I am trying to set up thi computer at work with Debian. All works fine apart from the network. This is a novell environment. I have set up one computer in a novell environment before and it was fine. however here I have problems. The newtwork card is working OK as far as I can tell. On boot the kernel finds it and although some mention of the eth1 interface is made at that stage, ifconfig states that eth0 is used. I can ping myself either using localhost or the IP address or the name of the machine. Ifconfig reports that lo and eth0 is up. But any attempt to ftp ping telnet anything outside of the machine does not work. route reports the localnet and 127.0.0.0 and then hangs. No gateway seems to be available as * is in place of the gateway. However I am using the same number as the other Win98 computers report in the TCP/IP installed gateways in network in control panel. I have not seen this problem before and I am at a loss for solving. Any help will be appreciated. Thanks George --- George Kapetanios Churchill College Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED] U.K. WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html ---
Re: network help
G. Kapetanios wrote: Hi, I am trying to set up thi computer at work with Debian. All works fine apart from the network. This is a novell environment. I have set up one computer in a novell environment before and it was fine. however here I have problems. The newtwork card is working OK as far as I can tell. On boot the kernel finds it and although some mention of the eth1 interface is made at that stage, ifconfig states that eth0 is used. I can ping myself either using localhost or the IP Can you give us the output of dmesg dealing with your network card? address or the name of the machine. Ifconfig reports that lo and eth0 is up. But any attempt to ftp ping telnet anything outside of the machine does not work. route reports the localnet and 127.0.0.0 and then hangs. No gateway seems to be available as * is in place of the gateway. However I am using the same number as the other Win98 computers report in the TCP/IP installed gateways in network in control panel. I have not seen this problem before and I am at a loss for solving. Any help will be appreciated. What would help here would be the output of ifconfig and 'route -n'. The -n tells route not to do DNS lookup for host names, but print IP addresses. What is your gateway's IP, and what is your netmask? Thanks George --- George Kapetanios Churchill College Cambridge, CB3 0DSE-Mail: [EMAIL PROTECTED] U.K. WWW: http://garfield.chu.cam.ac.uk/~gk205/work_info.html --- -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Paul Miller [EMAIL PROTECTED]begin:vcard n:Miller;Paul x-mozilla-html:FALSE org:Talons adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:President note:The Spirit of the University of North Texas x-mozilla-cpt:;0 fn:Paul Miller end:vcard
